Cannot create a swift container, mandatory "Storage Policy" dropdown field is empty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
High
|
Unassigned | ||
Ussuri |
Fix Released
|
High
|
Unassigned | ||
Victoria |
Fix Released
|
High
|
Unassigned | ||
horizon (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Focal |
Fix Released
|
High
|
Unassigned | ||
Groovy |
Fix Released
|
High
|
Unassigned | ||
Hirsute |
Fix Released
|
High
|
Unassigned | ||
python-swiftclient (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Focal |
Fix Released
|
High
|
Unassigned | ||
Groovy |
Fix Released
|
High
|
Unassigned | ||
Hirsute |
Fix Released
|
High
|
Unassigned |
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://
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.
CVE References
Changed in python-swiftclient (Ubuntu Groovy): | |
importance: | Undecided → High |
status: | New → Triaged |
no longer affects: | charm-openstack-dashboard |
description: | updated |
tags: |
added: verification-focal-done removed: verification-needed-focal |
affects: | charm-ceph-radosgw → ubuntu-translations |
no longer affects: | ubuntu-translations |
tags: |
added: verification-done-focal removed: verification-focal-done verification-needed |
Attached (error- log-storage- policy. txt) see relevant error messages from /var/log/ apache2/ error.log on one of the openstack-dashboard units, with debugging enabled (juju config openstack-dashboard debug=true).