Description of problem: After installing console when user tries to log in console prompts for username and password. Issue can be easily reproducible by restarting the ovirt engine. Attached the screenshot to the bug. Version-Release number of selected component (if applicable): rhsc-3.1.0-0.0.scratch.master.el6.noarch How reproducible: Always Steps to Reproduce: 1. Install the new downstream build of rhgsc 2. Login into console. 3. Actual results: Adim will be prompted with username and password. Expected results: There should be no dialog which prompts for username and dashboard. Additional info:
Created attachment 1029362 [details] Attaching the screenshot for the username and password dialog box
Devel nacking this one - as this issue was not reproducible on a running engine. And as per original BZ, it is reproducible only when ovirt-engine is restarted while the user was not logged out. This is a corner case, IMO.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Re-opening to retriage.
(In reply to Sahina Bose from comment #3) I've encountered this issue after fresh install. -> not a corner case.
Fresh install and a new browser instance?
(In reply to Sahina Bose from comment #7) > Fresh install and a new browser instance? I would need to retest to confirm that.
i see this issue with fresh install
Even I saw this today. Strangely it comes only for the first login after setup. Afterwords even if someone else try to login from different system it doesn't come . Also it says 'REST API' not 'ENGINE'. We have investigate this more.
Please try admin@internal/<engine password> should work.
(In reply to Stanislav Graf from comment #13) Workaround ========== (1) go to trends (2) Input admin@internal (admin pass) (3) Input nagiosadmin (nagios pass) Works for me! Removing TestBlocker
Doc text is edited. Please sign off to be included in Known Issues.
Edited the doc-text.Edited version looks good to me
Looks good to me
Updated the Known Issue chapter with the modified text.
*** Bug 1144018 has been marked as a duplicate of this bug. ***
HTTP Header "Prefer": "persistent-auth" is not being sent as part of REST API calls from Trends tab. As a result, engine invalidates the existing REST API session and asks for a password to create a new session. This header should be part of all REST API Calls. More info at : http://lists.ovirt.org/pipermail/devel/2014-July/008148.html http://www.ovirt.org/Features/RESTSessionManagement Note: Dashboard is working without any issue as it sends the header.
This bug is verified and found no issues. Steps followed: 1. install fresh RHSC 2. login as admin 3. checked that user is not prompted for userid password. logged out from console and logged in again adn no issue. also other tabs were tested to make sure userid/passwd not prompted. Last login: Wed Aug 26 04:07:11 2015 from dhcp-0-136.blr.redhat.com [root@casino-vm5 ~]# rpm -qa | grep rhsc rhsc-restapi-3.1.1-0.63.el6.noarch rhsc-extensions-api-impl-3.1.1-0.63.el6.noarch rhsc-setup-base-3.1.1-0.63.el6.noarch rhsc-setup-plugin-ovirt-engine-3.1.1-0.63.el6.noarch rhsc-webadmin-portal-3.1.1-0.63.el6.noarch rhsc-setup-plugins-3.1.0-3.el6rhs.noarch rhsc-cli-3.0.0.0-0.2.el6rhs.noarch rhsc-lib-3.1.1-0.63.el6.noarch rhsc-tools-3.1.1-0.63.el6.noarch redhat-access-plugin-rhsc-3.0.0-3.el6rhs.noarch rhsc-sdk-python-3.0.0.0-0.2.el6rhs.noarch rhsc-branding-rhs-3.1.0-1.el6rhs.noarch rhsc-setup-plugin-ovirt-engine-common-3.1.1-0.63.el6.noarch rhsc-backend-3.1.1-0.63.el6.noarch rhsc-dbscripts-3.1.1-0.63.el6.noarch rhsc-3.1.1-0.63.el6.noarch rhsc-doc-3.1.0-1.el6eng.noarch rhsc-monitoring-uiplugin-0.2.4-1.el6rhs.noarch rhsc-log-collector-3.1.0-1.0.el6rhs.noarch rhsc-setup-3.1.1-0.63.el6.noarch [root@casino-vm5 ~]#
Hi Ramesh, The doc text is updated. Please review it and share your technical review comments. If it looks ok, then sign-off on the same.
Doc text looks good. Approved.
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://rhn.redhat.com/errata/RHBA-2015-1848.html