Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1530276

Summary:	Disks -> Images table selection not saved but still highlighted when navigating disks
Product:	[oVirt] ovirt-engine	Reporter:	Kevin Alon Goldblatt <kgoldbla>
Component:	Frontend.WebAdmin	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	bugs, ratamir
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-02 12:40:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	UX	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kevin Alon Goldblatt 2018-01-02 12:35:16 UTC

Description of problem:
Via Webadmin Disks - Images view is not displayed when navigating into a specific disk view and then back to the Disks view even though the Images selection is still highlighted

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0.2-0.1.el7.noarch
vdsm-4.20.9.3-1.el7ev.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Webadmin tab - Disks -> Select Images - Storage Domains can be viewed
2. Select disk and view properties
3. Navigate back to Disks >>>>> Images selection is still highlighted but the view is that of the "All" selection and storage domains are no longer displayed
4. Need to click the Images selection again for it to work. If the display goes back to the default "All" view between navigation then the Images view should not be highlighted

Actual results:
Images View is still highlighted but not displayed

Expected results:
If Images view is highlighted it should be displayed

Additional info:
See attached screen shots

Comment 1 Raz Tamir 2018-01-02 12:40:23 UTC


*** This bug has been marked as a duplicate of bug 1506473 ***