On 03/08/2012, at 8:47 PM, Jiří Stránský wrote:
On 3.8.2012 11:45, Justin Clift wrote:
> As a first step, can you please grab the versions of Aeolus pieces which are
installed?
>
> $ rpm -qa|grep -i aeolus|sort
> $ rpm -qa|grep -i imagefactory
> $ rpm -qa|grep -i iwhd
Here it is:
[root@f16-aeolus ~]# rpm -qa|grep -i aeolus|sort
aeolus-all-0.10.6-1.fc16.noarch
aeolus-conductor-0.10.6-1.fc16.noarch
aeolus-conductor-daemons-0.10.6-1.fc16.noarch
aeolus-conductor-doc-0.10.6-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
[root@f16-aeolus ~]# rpm -qa|grep -i imagefactory
imagefactory-jeosconf-ec2-rhel-1.1.1-1.fc16.noarch
imagefactory-jeosconf-ec2-fedora-1.1.1-1.fc16.noarch
imagefactory-1.1.1-1.fc16.noarch
[root@f16-aeolus ~]# rpm -qa|grep -i iwhd
iwhd-1.5-1.fc16.x86_64
Hmmmm, those are definitely the correct ones. As a quick check here, I just
did a new install of F16 into a VM on my desktop, then ran the same
aeolus-configure command you did (-p ec2,mock).
That one worked - admin user was created - so at least we're not 100%
busted for everyone's installations. :)
Next steps:
* In the Aeolus web UI, are there any users apart from "admin" the Users
area? (Administer -> Users)
I've seen temporary admins users left over sometimes, so I'm wondering
if maybe that's happening.
* The full log file from the configure run should be located here:
/var/log/aeolus-configure/aeolus-configure.log
Can you please email it to me, off-list?
I'll go through it, comparing your run to the one I just did, and see
if there's anything obvious which stands out.
Regards and best wishes,
Justin Clift
--
Aeolus Community Manager
http://www.aeolusproject.org