Bug 1333573

Summary: Opening https://<IP>/ems_infra/4?display=vms# link to appliance redirects you and throws up 404 error
Product: Red Hat CloudForms Management Engine Reporter: luke couzens <lcouzens>
Component: ApplianceAssignee: Šimon Lukašík <slukasik>
Status: CLOSED ERRATA QA Contact: luke couzens <lcouzens>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: abellott, dajohnso, jhardy, mfalesni, mfeifer, obarenbo, slukasik
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: webui
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-29 15:58:06 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:
Attachments:
Description Flags
error page none

Description luke couzens 2016-05-05 21:44:00 UTC
Created attachment 1154391 [details]
error page

Description of problem:When opening a link to https://<IP>/ems_infra/4?display=vms# while not being logged in to appliance you get redirected to https://<IP>/ems_infra/show/1


Version-Release number of selected component (if applicable):5.6.0.5-beta2.4


How reproducible:100%


Steps to Reproduce:
1.Provision configured appliance
2.Add vsphere provider
3.navigate to infrastructure-providers
4.click on vsphere provider
5.click on vms & instances
6.copy url
7.Log out of appliance
8.paste copied link into browser
9.login to appliance

Actual results:
redirects to error page not found

Expected results: Directed to vms and instances page


Additional info:

Comment 4 Šimon Lukašík 2016-06-02 08:10:20 UTC
This has been fixed in upstream https://github.com/ManageIQ/manageiq/pull/8993

Basically, it is the same issue as bug 1329009. Moving to ON_QA to get proper verification.

Comment 5 luke couzens 2016-06-03 00:21:08 UTC
Verified in 5.6.0.9

Comment 7 errata-xmlrpc 2016-06-29 15:58:06 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