Bug 1328209 - Cloud : Instance Grid/Tile View Icon click says "page does not exist"
Summary: Cloud : Instance Grid/Tile View Icon click says "page does not exist"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.6.0
Assignee: Ladislav Smola
QA Contact: Shveta
URL:
Whiteboard: cloud:vm:ui
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 17:52 UTC by Shveta
Modified: 2016-06-29 15:50 UTC (History)
6 users (show)

Fixed In Version: 5.6.0.5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 15:50:55 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)
page does not exist (18.25 KB, image/png)
2016-04-18 17:52 UTC, Shveta 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Shveta 2016-04-18 17:52:39 UTC 
Created attachment 1148259 [details]
page does not exist

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Add a cloud provider .
2. Click on the provider , go to Instances
3. Click on Grid/ Tile or list view . All three icon shows "page does not exist "

Actual results:


Expected results:


Additional info:
5.6.0.1-beta2.20160413141124_e25ac0e
Comment 2 Shveta 2016-04-21 21:50:52 UTC 
All Relationship links from Cloud provider have same issue . Images/Availability zone etc
Comment 3 Milan Zázrivec 2016-04-22 08:42:55 UTC 
https://github.com/ManageIQ/manageiq/pull/8141
Comment 4 Shveta 2016-05-04 17:53:13 UTC 
Fixed .
Verified in 

5.6.0.5-beta2.4.20160503153816_1fb554f
Comment 6 errata-xmlrpc 2016-06-29 15:50:55 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
Note You need to log in before you can comment on or make changes to this bug.