Bug 1338803

Summary:	Container Providers default Display as set in Settings does not get applied to Providers View
Product:	Red Hat CloudForms Management Engine	Reporter:	Einat Pacifici <epacific>
Component:	UI - OPS	Assignee:	zakiva
Status:	CLOSED ERRATA	QA Contact:	Einat Pacifici <epacific>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.6.0	CC:	hkataria, jhardy, mfeifer, mpovolny, obarenbo, simaishi
Target Milestone:	GA	Flags:	epacific: automate_bug+
Target Release:	5.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	container
Fixed In Version:	5.6.0.9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-29 16:05:22 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:

Description Einat Pacifici 2016-05-23 12:54:06 UTC

Description of problem:
When setting a user default settings for Container Providers, the default setting does not get applied to Providers view

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

How reproducible:
Always

Steps to Reproduce:
0.Ensure Providers is set to list view
1.Settings - My settings - default views
2.Set Containers - Container Providers
3.Select Tile View
4. Go to Compute --> Containers --> Providers

Actual results:
The Providers should be shown in Tile View

Expected results:
The Providers are shown in list view

Comment 2 Harpreet Kataria 2016-05-23 13:42:07 UTC

Federico,

Please send this back to me if this is not a containers specific bug.

Thanks,
~Harpreet

Comment 3 zakiva 2016-05-29 08:13:38 UTC

Bug fix: https://github.com/ManageIQ/manageiq/pull/8917

Comment 4 Einat Pacifici 2016-06-07 11:03:17 UTC

Verified. When setting view in Settings --> Configuration --> Default views. The selection can be seen in the Providers screen.

Comment 6 errata-xmlrpc 2016-06-29 16:05:22 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.

https://access.redhat.com/errata/RHBA-2016:1348