Created attachment 770637 [details] Horizon log file Description of problem: Horizon will not display security rules when adding new rule to default Output will be " Something went wrong! " Horizon log file attached Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.view security rule using default security group 2.add new rule " $quantum security-group-rule-create default --direction ingress --protocol udp --port-range-min 100 --port-range-max 200" 3.try to edit security group again in GUI you will get an error Actual results: Expected results: Additional info:
The new rule is added in CLI, but cause error in GUI , until it is removed
Overall, quantum security group management will greatly improve in Havana thanks to https://blueprints.launchpad.net/horizon/+spec/quantum-security-group . For this particular error however, commit 706560f6d2 would be sufficient to fix it and could be considered for a backport to Grizzly.
Fixed upstream for Havana in M1, and backported to Grizzly - it should be part of 2013.1.3 on Aug 8th.
Hi Lon What info is needed ? Ofer
Verified on Havana running rhel6.5 with: openstack-neutron-2013.2-0.3.3.b3.el6ost.noarch python-django-horizon-2013.2-0.13b3.el6ost.noarch I've added 2 rules by CLI and then 1 rule by GUI. The security-group-rule-list afterwards was: +--------------------------------------+----------------+-----------+----------+------------------+--------------+ | id | security_group | direction | protocol | remote_ip_prefix | remote_group | +--------------------------------------+----------------+-----------+----------+------------------+--------------+ | 0299a845-7ddf-4ee9-adb0-c85af6db72e5 | default | ingress | icmp | | | | 43117c91-a5f3-4fd1-a95c-9206e05ec5bd | default | egress | | | | | 54e197d0-1f89-47a0-ac6c-d37c14e44493 | default | ingress | | | default | | 57c8ce31-2ee2-46e4-aa36-de9b45021e61 | default | ingress | udp | | | | 5cdaf516-66bd-45c3-acd0-4008fdd231c9 | default | egress | udp | | default | | 6bfd4855-f889-4f43-96ee-f60f83828891 | default | ingress | | | default | | 7fd8e368-6e47-4319-89c4-2a8bf17c7cee | default | egress | | | | | 94e6b451-e42d-422d-8602-3fa6c1b4f59e | default | ingress | | | default | | f1447506-53d3-4f4a-99b9-a608207cf7af | default | ingress | | | default | | f40248f7-ad75-468f-8fae-0a8d92d1a4eb | default | egress | | | | | f53106c0-1573-4afc-83da-ff0f6aac5002 | default | egress | | | | +--------------------------------------+----------------+-----------+----------+------------------+--------------+ so did the Horizon. Then I deleted 2 rules via the Horizon, and the table was: +--------------------------------------+----------------+-----------+----------+------------------+--------------+ | id | security_group | direction | protocol | remote_ip_prefix | remote_group | +--------------------------------------+----------------+-----------+----------+------------------+--------------+ | 0299a845-7ddf-4ee9-adb0-c85af6db72e5 | default | ingress | icmp | | | | 43117c91-a5f3-4fd1-a95c-9206e05ec5bd | default | egress | | | | | 54e197d0-1f89-47a0-ac6c-d37c14e44493 | default | ingress | | | default | | 6bfd4855-f889-4f43-96ee-f60f83828891 | default | ingress | | | default | | 7fd8e368-6e47-4319-89c4-2a8bf17c7cee | default | egress | | | | | 94e6b451-e42d-422d-8602-3fa6c1b4f59e | default | ingress | | | default | | f1447506-53d3-4f4a-99b9-a608207cf7af | default | ingress | | | default | | f40248f7-ad75-468f-8fae-0a8d92d1a4eb | default | egress | | | | | f53106c0-1573-4afc-83da-ff0f6aac5002 | default | egress | | | | +--------------------------------------+----------------+-----------+----------+------------------+--------------+ and the Horizon was correct.
I don't think this requires doc text for 4.0, as it was superseded by the new improved Neutron Security Groups management feature later on during the development cycle.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html