[Bug 1840465] Please test proposed package
corey.bryant at canonical.com
Mon Dec 2 14:53:47 UTC 2019
Hello Tobias, or anyone else affected,
Accepted horizon into stein-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
Please help us by testing this new package. To enable the -proposed
sudo add-apt-repository cloud-archive:stein-proposed
sudo apt-get update
Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-stein-needed to verification-stein-done. If it does
not fix the bug for you, please add a comment stating that, and change
the tag to verification-stein-failed. In either case, details of your
testing will help us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
** Changed in: cloud-archive/stein
Status: Triaged => Fix Committed
** Tags added: verification-stein-needed
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to horizon in Ubuntu.
[SRU] Fails to list security groups if one or more exists without
Status in Ubuntu Cloud Archive:
Status in Ubuntu Cloud Archive queens series:
Status in Ubuntu Cloud Archive rocky series:
Status in Ubuntu Cloud Archive stein series:
Status in Ubuntu Cloud Archive train series:
Status in OpenStack Dashboard (Horizon):
Status in horizon package in Ubuntu:
Status in horizon source package in Bionic:
Status in horizon source package in Disco:
Status in horizon source package in Eoan:
Horizon 14.0.2 (rocky)
If a security group without any rules exists the listing of security groups fails with a KeyError.
Traceback (most recent call last):
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line 127, in _wrapped
data = function(self, request, *args, **kw)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/network.py", line 44, in get
security_groups = api.neutron.security_group_list(request)
File "/usr/lib/python2.7/site-packages/horizon/utils/memoized.py", line 95, in wrapped
value = cache[key] = func(*args, **kwargs)
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 1641, in security_group_list
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 372, in list
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 359, in _list
return [SecurityGroup(sg) for sg in secgroups.get('security_groups')]
File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py", line 240, in __init__
for rule in sg['security_group_rules']]
By default, new security groups created through horizon or CLI include
2 default security rules. Upon managing those rules and removing them
(to perhaps add others or limit traffic completely), the security
group page errors out and prevents listing of *all* security groups if
the empty security group is within the list to be displayed.
Therefore, not only is the empty security group affected, but all
others as well, as they cannot be listed. The root cause of the bug is
that the payload does not include the expected key
"security_group_rules" for that security group when there are no
A fix has been implemented for Train (from master), Stein, Rocky and
Queens releases and should be backported so the issue is addressed on
previous those releases. The fix prevents the crash by ensuring the
key "security_group_rules" is present with an empty list in case it
was not included in the payload.
1. Reproducing the issue
1a. Go to the Security Group section at Project > Network > Security Groups
1b. Create a security group
1c. Click the Manage Rules button for that security group you just created
1d. Delete the two default rules
1e. Go back to the Security Group section at Project > Network > Security Groups
1f. Security groups are no longer being listed and there will be an error popup: "Error: Unable to retrieve security groups.".
2. Install the package with the fixed code
3. Confirm bug has been fixed
3a. Repeat step 1a, you will notice that now security groups can be
listed, including the empty one you had previously created
3b. Repeat steps 1b through 1e, the newly created and emptied security
group can also be listed along the others.
Given the following indicators:
a. Upstream CI passed, for all releases the fix is being backported.
b. The small scope of the problem: a key error prevents the page from being rendered. The fix is to make sure the key is always present, since it is always expected.
c. The fix is very simple, and during tests we can see that the other pages handle an empty list properly as the value for the "security_group_rules" key.
We can safely state that the regression potential is negligible.
To manage notifications about this bug go to:
More information about the Ubuntu-openstack-bugs