Red Hat Bugzilla – Bug 1109417
Adding a new Security Rule to a Security Group shouldn't remove the sort on the table
Last modified: 2016-04-26 13:25:37 EDT
Description of problem: If I'm manually adding security rules to a security group, I don't think it's unreasonable for me to have the table sorted on Port or Protocol while I'm building out the group, but if I have the table sorted, each time you add a new rule, it reverts to the default sort of the table. (Side question, how is the table sorted by default? It doesn't appear to be port or direction or protocol, or ether type, or remote, or even when the rule was created. It just looks like a jumbled mess, hence why I want to keep it sorted...) If I have the table sorted on Port, so I can keep track of which ones I've added already easily, it would be great if Horizon was smart enough to keep the sort applied, and just add the new rule, rather than forcing me to resort the table again, click add, create the rule, sort the table again, etc etc. It would also be nice if there was a table sort indicator, but that's probably a topic for another bug :)
Created attachment 908695 [details] Default view of ports in an Icehouse instance
Created attachment 908696 [details] Same rules as other Icehouse instance, default view when you open up the group
Created attachment 908697 [details] What is the sort here?
Fixed in Juno upstream, may want to consider for backport.
Looking at the Launchpad status, looks like this should be included in the 2014.1.2 rebase (bug 1127430). Tweaking the flags to indicate so.
Verified ======== python-django-horizon-2014.1.2-2.el7ost.noarch
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/RHSA-2014-1335.html