Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1511335

Summary: [downstream clone - 4.1.8] Bookmarks are not sorted after upgrade
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engineAssignee: Ravi Nori <rnori>
Status: CLOSED ERRATA QA Contact: samuel macko <smacko>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.6CC: gklein, lsurette, lveyde, mgoldboi, mperina, oourfali, pstehlik, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone: ovirt-4.1.8Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: ovirt-engine-4.1.8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1504777 Environment:
Last Closed: 2017-12-12 09:23:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1504777    
Bug Blocks:    

Description rhev-integ 2017-11-09 07:48:10 UTC
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1504777 +++

Description of problem:
After upgrade from 4.1.5 to the bookmarks are not sorted

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create bookmarks 
2. Bookmarks are not sorted in by name but random added to the list

Actual results:
Bookmarks are random added to the list

Expected results:
Sorted bookmarks as in previous 4.1.5

Additional info:
The screenshots attached

(Originally by Jaroslav Spanko)

Comment 5 samuel macko 2017-11-29 11:37:33 UTC
Verified in Red Hat Virtualization Manager Version:

Verified by following the reproducer.

Comment 8 errata-xmlrpc 2017-12-12 09:23:28 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.