This patch is a clean-up patch for refactor-error-messages bp
which remove the exception message from base message otherwise
the same exception message display twice like
this https://ibb.co/XyFWMdz .
Change-Id: Ie0538de1dd8df45009ca24bab379980d7d1b9613
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg
- Update classifiers
- Switch to using sphinx-build
- Use openstackdocstheme instead of python2 only oslosphinx
- Remove install_command from tox.ini, the default is fine
- Fix two hacking problems, those were masked by ignore
to an empty string.
Change-Id: I8f67f8a7998a16805cbda52854a6b0f0ade05dc8
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix warnings found.
Change-Id: If966592a0f0d2c1000d5dc1ddafe2a3bcae88551
This patch does several things at once:
- Remove mox from KarborApiTest. Use mock instead
of mox3 to mock out the karborclient.
- Use mock to mout the karborclient.
- Drop mox3 from the test-requirements.txt.
This is apart of the mox community goal for Rocky.
Change-Id: Iea9e65778777746682895521f17ca69f5c27f7fd
Signed-off-by: Charles Short <zulcss@gmail.com>
Currently, karbor use 'calendar' format as the default
time format, but karbor-dashboard use 'crontab', this
makes the trigger creation failed. This patch convert
the time format of the dashboard to canlendar to make
it work.
Change-Id: I7a89365005af3256bdf02478dd60428a118a8bbe
Closes-Bug: #1613587
Currently, previous page in checkpoints pagination not
work, it always throw an error in the web page. It is
because that checkpoints in karbor do not need reverse
the order (checkpoints are sorted by 'timestamp@id' in
the backend, so we can not do the reverse only be the
id or name)
This patch will fix it.
Change-Id: I45c3e7337bf2ee9d3f2fbf9ee7a438884b8b8ca9
Closes-Bug: #1714909
Patch [0] added filtering for plan parameters, to only send parameters
of resources whose type is being protected. This introduced a bug where
per resource parameters were not sent.
Fix that by apply the filtering correctly.
[0] https://review.openstack.org/492393/
Change-Id: Ic3cdefe1a27587de4e887e509075e7c43a314262
Make restore target optional, user can use default target or
specified restore target by choose the checkbox.
Change-Id: I732dcb684c4b60568817f8fa9ff806955ebaa9a6
Once the restore operation is successfully initialized,
redirect to the restore page to get restore state and progress.
Change-Id: I3d3fccbb36dd28d65461b1a18a844fe11e1692b6
When watching the restore page, update (poll?) the restore
status. If a restore is in_progress, user shouldn't refresh
the page to see it is success.
Change-Id: Idca8860f726eaf5a450e8335b112b9d845b26377
Co-authored-by: xiangxinyong <xiangxinyong@huawei.com>
The restore api has updated, so update this.
and add validate for url
Change-Id: Ibe9dec6f356359eb1535d7f643d235f2547a770d
Co-authored-by: xiangxinyong <xiangxinyong@huawei.com>
When watching the checkpoint page, update (poll?) the checkpoint
status. If a checkpoint is protecting, user shouldn't refresh
the page to see it is available.
Change-Id: I4dd046a3314219586b83837593ebb16fb1217077
Closes-Bug: #1622594
Click on "show checkpoints" of the provider page, provider filtering
options of checkpoint page always display the default value.
Change-Id: I2b414018c6faaf5a0a437e92fc207b4506ea1b15
User is unable to update the Protection Plan from the dashboard
- updating name, status, resources and parameters.
Change-Id: I5dfcc9507689a27d1a6bfdc9ca8f9f4711ba797a
Closes-Bug: #1643338
In checkpoints/views.py, IndexView class, get_data() method, we list
the checkpoints for a provider.
After that, we iterate the checkpoints for that provider and get the
provider using karbor client. This is not necessary: all the checkpoints
are from the same provider, and even if they weren't, we could use karbor
client to get each provider only once.
Change-Id: I790116137a321570c6d386e435f24a5efde2e607
Closes-Bug: #1643331
The django issue [1] have already fixed. So we can remove the file now.
[1] https://code.djangoproject.com/ticket/7198
Change-Id: Ic9ff376b6f11d0f7db8e9bde144e5581b44c0cb0
The operation logs ui is broken and throws the following exception:
'IndexView' object has no attribute '_more'.
It should be solved by removing the paging function.
Change-Id: I04a3ae4cea5593b992914f97f3ed9547730d4c87
Closes-Bug: #1643515