Bug 1292735 - Unable to log in to the Red Hat Customer Portal from the RHEV-M.
Summary: Unable to log in to the Red Hat Customer Portal from the RHEV-M.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: redhat-support-plugin-rhev
Version: 3.5.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Spenser Shumaker
QA Contact: Spenser Shumaker
URL:
Whiteboard: subeng
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-18 08:50 UTC by Kumar Mashalkar
Modified: 2019-09-12 09:37 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-31 15:12:13 UTC
oVirt Team: Sub-Eng
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Login failed screen (70.02 KB, image/jpeg)
2015-12-18 08:50 UTC, Kumar Mashalkar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1300668 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1300668

Description Kumar Mashalkar 2015-12-18 08:50:59 UTC 
Created attachment 1107050 [details]
Login failed screen

Description of problem:
After upgrading RHEV-M to Version 3.5.6.2-0.1.el6ev it is no longer possible to log in to the Red Hat Customer Portal from the RHEV-M. All users are affected.

Version-Release number of selected component (if applicable):
3.5.6.2-0.1.el6ev

How reproducible:
By upgrading RHEV-M to Version 3.5.6.2-0.1.el6ev

Steps to Reproduce:
1. Upgrade RHEV-M to version 3.5.6.2-0.1 
2. Login to RHEVM admin portal
3. From Log viewer --> Login --> Sign in with Red Hat login.

Actual results:
Login Failed!

Expected results:
Login in successful

Additional info:
Tried with earlier and RHEV 3.6 beta version. It is working fine.
Comment 1 Yaniv Lavi 2016-01-12 15:35:55 UTC 
Is the customer using a admin user?
Comment 2 Kumar Mashalkar 2016-01-18 02:05:43 UTC 
Yes. Customer is using admin user. Also we were able to reproduce this issue on one of our test environment which was upgraded to version 3.5.6
Note You need to log in before you can comment on or make changes to this bug.