On 13/07/2012, at 6:01 PM, Marcus Moeller wrote:
On 07/13/2012 09:59 AM, Justin Clift wrote:
> On 13/07/2012, at 4:39 PM, Marcus Moeller wrote:
> <snip>
>> I got at least an:
>>
>> Error: admin configure node is missing
>> "/etc/aeolus-configure/nodes/admin_configure" does not exist
>> exiting
>>
>> if I try to run aeolus-configure with the admin profile.
>
>
> Ouch, that's not supposed to happen. (obviously)
>
> If you run this, what's the result?
>
> $ rpm -qa | grep -i aeolus | sort
>
> Just wanting to check which versions of things you have
> installed before I start panicing. :)
Np, we habe been using Spacewalk for a long time to deploy Fedora, so we know what it
means to use broken software ;)
aeolus-all-0.10.5-1.fc16.noarch
aeolus-conductor-0.10.5-1.fc16.noarch
aeolus-conductor-daemons-0.10.5-1.fc16.noarch
aeolus-conductor-doc-0.10.5-1.fc16.noarch
aeolus-configure-2.6.1-1.fc16.noarch
rubygem-aeolus-cli-0.5.0-1.fc16.noarch
rubygem-aeolus-image-0.5.0-1.fc16.noarch
Ahhh, can see the cause. You grabbed the updated Aeolus packages from the updates testing
repo too, not just Deltacloud. ;)
It's not a problem (hopefully!), it just means that when you run aeolus-configure, you
should leave off the "admin" argument.
("admin" bit is only for the 0.10.4 version rpms, not later)
Just to be ultra clear, you'll now be running this:
$ sudo aeolus-configure -p ec2,whatever_else_you_need_here
Instead of:
$ sudo aeolus-configure -p admin,ec2,whatever_else_you_need_here
For the OpenStack support, I'm still not sure though. And ironically, the
developer who has doing coding stuff with it went on holiday last friday.
(timing!) :>
+ Justin
Greets
Marcus
--
Aeolus Community Manager
http://www.aeolusproject.org