aeolus-configure -p rhevm,ec2 error
Berezovski, Vladimir
Vberezovski at nds.com
Tue Dec 20 11:26:29 UTC 2011
Hi Tomas ,
I followed your solution . Looks much better .Thanks .
But , can you comment these events :
#/usr/sbin/aeolus-configure -p rhevm,ec2
Launching aeolus configuration recipe...
err: /Stage[main]/Aeolus::Profiles::Rhevm/Web_request[rhevm-check-export-path-is-export-type]/get: change from to https://rhevm2.il.nds.com:8443/api/storagedomains?search=export failed: An exception was raised when invoking web request: Invalid HTTP Return Code: 401,
was expecting one of 200
notice: /Stage[main]/Aeolus::Profiles::Rhevm/Mount[/mnt/rhevm-nfs]: Dependency Web_request[rhevm-check-export-path-is-export-type] has failures: true
warning: /Stage[main]/Aeolus::Profiles::Rhevm/Mount[/mnt/rhevm-nfs]: Skipping because of failed dependencies
And when aeolus-restart-services afterwars :
Starting libvirtd ...
libvirtd: libvirtd is managed by upstart and started, use initctl instead
FAILURE: Starting libvirtd daemon:
Exit code is 1 although conductor's service is available .
Also I do not see in the providers list Amazon ones , only rhevm .
By the way , if I'd like to enable VSphere provider the aeolus-configure command should be like aeolus-configure -p ec2,rhevm,vsphere ?
/Vlad .
-----Original Message-----
From: Tomas Sedovic [mailto:tsedovic at redhat.com]
Sent: Tuesday, December 20, 2011 1:09 PM
To: Berezovski, Vladimir
Cc: aeolus-devel at lists.fedorahosted.org
Subject: Re: aeolus-configure -p rhevm,ec2 error
On 12/20/2011 10:09 AM, Berezovski, Vladimir wrote:
> Hi ,
>
> I updated Aeolus to 0.7.0-4 version on RH6 host : yum update aeolus-all
>
> Now when reconfigure providers I get this error :
>
> #/usr/sbin/aeolus-configure -p rhevm,ec2
>
> err:
> /Stage[main]/Aeolus::Profiles::Rhevm/Aeolus::Conductor::Login[admin]/Web_request[admin-conductor-login]/post:
> change from to https://localhost/conductor/user_session failed: An
> exception was raised when invoking web request: Invalid HTTP Return
> Code: 500,
>
> was expecting one of 200
>
> In conductor's page I see the following message :
>
> "A secret is required to generate an integrity hash for cookie session
> data. Use config.secret_token = "some secret phrase of at least 30
> characters"in config/initializers/secret_token.rb.tt"
>
> If I'm not mistaken the file
> /usr/lib/ruby/gems/1.8/gems/railties-3.0.10/lib/rails/generators/rails/app/templates/config/initializers/secret_token.rb.tt
> is to be fixed .
>
> Can you advise how secret_token.rb.tt should look like ( example ) ?
>
> Thanks
>
> *Best regards ,*
>
> *Vladimir Berezovski *
>
>
> ------------------------------------------------------------------------
> This message is confidential and intended only for the addressee. If you
> have received this message in error, please immediately notify the
> postmaster at nds.com and delete it from your system as well as any copies.
> The content of e-mails as well as traffic data may be monitored by NDS
> for employment and security purposes.
> To protect the environment please do not print this e-mail unless necessary.
>
> An NDS Group Limited company. www.nds.com
Hi Vladimir,
Actually, the issue seems to be with aeolus-configure, rather than the
rails initializer template.
One of our recent updates was that we removed the default secret token
from Conductor and instead modified Configure to regenerate it every
time it's run.
However, it seems that the Aeolus Configure RPM has not yet been updated.
This should fix your problem (run as root):
# echo Conductor::Application.config.secret_token =
\'$(</dev/urandom tr -dc a-f0-9 | head -c128)\' >>
/usr/share/aeolus-conductor/config/initializers/secret_token.rb
# aeolus-restart-services
For the reference, the secret token file for Conductor is located here:
/usr/share/aeolus-conductor/config/initializers/secret_token.rb
And it should contain this line:
Conductor::Application.config.secret_token = 'XXX'
where XXX is a string of sufficient length and entropy.
Hope this helps and sorry for the trouble.
Thomas
--
No trees were killed to send this message, but a large number of
electrons were terribly inconvenienced.
More information about the aeolus-devel
mailing list