Bug 859937 - "$("#notifications").html("\nThe username and password is incorrect" while navigating to cloud resource zone properties page.
Summary: "$("#notifications").html("\nThe username and password is incorrect" while na...
Keywords:
Status: CLOSED DUPLICATE of bug 858997
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-24 12:37 UTC by Aziza Karol
Modified: 2012-09-25 13:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-25 13:47:53 UTC
Embargoed:


Attachments (Terms of Use)
err (49.01 KB, image/png)
2012-09-24 12:38 UTC, Aziza Karol
no flags Details

Description Aziza Karol 2012-09-24 12:37:57 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
I got this issue when navigating to properties,roles assignments and catalog images pages of Default cloud resource zone.see attached screenshot.

"$("#notifications").html("\nThe username and password is incorrect" is dislayed.
After relogin this issue did not occur.


Additional info:
rpm -qa | grep aeolus
aeolus-conductor-daemons-0.13.8-1.el6cf.noarch
rubygem-aeolus-cli-0.7.1-1.el6cf.noarch
aeolus-configure-2.8.6-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-0.13.8-1.el6cf.noarch
aeolus-conductor-doc-0.13.8-1.el6cf.noarch
aeolus-all-0.13.8-1.el6cf.noarch

Comment 1 Aziza Karol 2012-09-24 12:38:56 UTC
Created attachment 616545 [details]
err

Comment 3 Mike Orazi 2012-09-25 13:47:53 UTC
I'm fairly certain this is a duplicate of 858997 which happened after a session timeout.  The descriptions are pretty consistent, but if this is a distinct issue please re-open.

*** This bug has been marked as a duplicate of bug 858997 ***


Note You need to log in before you can comment on or make changes to this bug.