Bug 856674 - configure hits a 401 error
configure hits a 401 error
Product: CloudForms Cloud Engine
Classification: Red Hat
Component: aeolus-configure (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: rc
: ---
Assigned To: Steve Linabery
Dave Johnson
Depends On:
  Show dependency treegraph
Reported: 2012-09-12 10:46 EDT by Dave Johnson
Modified: 2012-12-12 10:18 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-12-12 10:18:35 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dave Johnson 2012-09-12 10:46:18 EDT
Description of problem:
Install the from the latest upstream nightly is showing a error in configure 

notice: /Stage[main]/Aeolus::Profiles::Common/Aeolus::Conductor::Temp_admin[temporary-administrative-user-7b426ae65f6bf69e5bd8013af355fec85bcbf61eca309574]/Exec[create_temp_admin]/returns: executed successfully

notice: /Stage[main]/Aeolus::Profiles::Common/Aeolus::Conductor::Temp_admin[temporary-administrative-user-7b426ae65f6bf69e5bd8013af355fec85bcbf61eca309574]/Exec[grant_temp_admin_privs]/returns: executed successfully

err: /Stage[main]/Aeolus::Profiles::Common/Aeolus::Conductor::Login[temporary-administrative-user-7b426ae65f6bf69e5bd8013af355fec85bcbf61eca309574]/Web_request[temporary-administrative-user-7b426ae65f6bf69e5bd8013af355fec85bcbf61eca309574-conductor-login]/post: change from  to https://localhost/conductor/user_session failed: An exception was raised when invoking web request: Invalid HTTP Return Code: 401, was expecting one of 200
Comment 2 Mike Orazi 2012-09-13 09:42:00 EDT
This was the result of a mis-matched.  aeolus-configure was expecting the form name to be one value, but the corresponding aeolus-conductor rpm was not built/pushed correctly.

This should be addressed with the new conductor rpm.
Comment 3 Dave Johnson 2012-09-17 13:05:47 EDT
Good to go using 2012-09-14.5 puddle
Comment 4 James Laska 2012-12-12 10:18:35 EST
Marking this bug CLOSED CURRENTRELEASE based on comment#3.  Please reopen if the problem has not   been addressed in the 1.1 product.

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