Hide Forgot
Description of problem: domains are not being sorted the same in the left side of the ui compared to the right side Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
5.4.z MR: http://gitlab.cloudforms.lab.eng.rdu2.redhat.com/cloudforms/cfme/merge_requests/739
New commit detected on cfme/5.4.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=1520fa744706db6a0958dbadd1734d27a3a3e55c commit 1520fa744706db6a0958dbadd1734d27a3a3e55c Merge: d8bf7e3 acd52a4 Author: Dan Clarizio <dclarizi> AuthorDate: Thu Jan 21 12:03:29 2016 -0500 Commit: Dan Clarizio <dclarizi> CommitDate: Thu Jan 21 12:03:29 2016 -0500 Merge branch '54z_bz_1300080' into '5.4.z' Fixed tree building & right cell code to order Domain by Priority Desc https://bugzilla.redhat.com/show_bug.cgi?id=1300080 @dclarizi please review, this is a 5.4.z only fix. Code has been updated/refactored on upstream & 5.5.z branches so this is not an issue on those two branches. before:   after:   See merge request !739 vmdb/app/controllers/miq_ae_class_controller.rb | 4 ++-- vmdb/app/presenters/tree_builder_ae_class.rb | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-)
New commit detected on cfme/5.4.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=acd52a402aab5e51d2b85ac9216525f69ad6456a commit acd52a402aab5e51d2b85ac9216525f69ad6456a Author: Harpreet Kataria <hkataria> AuthorDate: Wed Jan 20 16:09:20 2016 -0500 Commit: Harpreet Kataria <hkataria> CommitDate: Wed Jan 20 16:09:20 2016 -0500 Fixed tree building & right cell code to order Domain by Priority Desc https://bugzilla.redhat.com/show_bug.cgi?id=1300080 vmdb/app/controllers/miq_ae_class_controller.rb | 4 ++-- vmdb/app/presenters/tree_builder_ae_class.rb | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-)
Verified in 5.4.5.2
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. https://rhn.redhat.com/errata/RHBA-2016-0171.html