ubuntu-translations-coordinators team mailing list archive
-
ubuntu-translations-coordinators team
-
Mailing list archive
-
Message #11845
[Bug 1902944] Re: Cannot create a swift container, mandatory "Storage Policy" dropdown field is empty
** Project changed: charm-ceph-radosgw => ubuntu-translations
** No longer affects: ubuntu-translations
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1902944
Title:
Cannot create a swift container, mandatory "Storage Policy" dropdown
field is empty
Status in Ubuntu Cloud Archive:
Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
Fix Committed
Status in Ubuntu Cloud Archive victoria series:
Fix Committed
Status in horizon package in Ubuntu:
Fix Released
Status in python-swiftclient package in Ubuntu:
Fix Released
Status in horizon source package in Focal:
Fix Committed
Status in python-swiftclient source package in Focal:
Fix Committed
Status in horizon source package in Groovy:
Fix Committed
Status in python-swiftclient source package in Groovy:
Fix Released
Status in horizon source package in Hirsute:
Fix Released
Status in python-swiftclient source package in Hirsute:
Fix Released
Bug description:
[Impact]
focal-ussuri, charms revision 20.10
I can't create a container with GUI. When entering "Containers" tab,
the error "Error: Unable to fetch the policy details." appears.
If I proceed and try to create a container, I can't click "Submit"
button until I select a Storage Policy. But the mandatory "Storage
Policy" dropdown field is empty. See attached screenshot.
I can, however, create a container with a CLI. `openstack container
create c1` works fine.
[Test Case]
Deploy horizon with ceph radosgw instead of swift, navigate to http://horizon-ip/horizon/project/containers/ and attempt to create a container. With the package and charm fixes in this bug, it will be successful. Otherwise it will fail as described in this bug.
Note, we also want to test horizon with swift proper for this bug to
ensure it still works with the dashboard.
[Regression Potential]
It's possible this could regress horizon with swift proper as a backend so it should also be regression tested.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1902944/+subscriptions