Bug 1109417

Summary:

Adding a new Security Rule to a Security Group shouldn't remove the sort on the table

Product:

Red Hat OpenStack

Reporter:

Matt Reid <mreid>

Component:

python-django-horizon

Assignee:

Julie Pichon <jpichon>

Status:

CLOSED ERRATA

QA Contact:

Ido Ovadia <iovadia>

Severity:

low

Docs Contact:

Priority:

low

Version:

4.0

CC:

ajeain, aortega, athomas, jpichon, mrunge, sgordon, yeylon

Target Milestone:

Keywords:

Triaged, ZStream

Target Release:

5.0 (RHEL 7)

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

python-django-horizon-2014.1.2-1.el7ost

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-09-30 17:18:43 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Bug Depends On:

Bug Blocks:

1099570

Attachments:

Description	Flags
Default view of ports in an Icehouse instance	none
Same rules as other Icehouse instance, default view when you open up the group	none
What is the sort here?	none

Description Matt Reid 2014-06-13 19:49:09 UTC

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 :)

Comment 1 Matt Reid 2014-06-13 19:50:08 UTC

Created attachment 908695 [details]
Default view of ports in an Icehouse instance

Comment 2 Matt Reid 2014-06-13 19:50:49 UTC

Created attachment 908696 [details]
Same rules as other Icehouse instance, default view when you open up the group

Comment 3 Matt Reid 2014-06-13 19:51:21 UTC

Created attachment 908697 [details]
What is the sort here?

Comment 4 Julie Pichon 2014-06-24 09:31:34 UTC

Fixed in Juno upstream, may want to consider for backport.

Comment 7 Julie Pichon 2014-09-04 13:44:37 UTC

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.

Comment 9 Ido Ovadia 2014-09-21 15:04:50 UTC

Verified
========
python-django-horizon-2014.1.2-2.el7ost.noarch

Comment 11 errata-xmlrpc 2014-09-30 17:18:43 UTC

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