Hide Forgot
Installing : aeolus-conductor-0.0.3-0.fc1420110325210029gitba5d50b.x86_64 112/123 warning: user aeolus does not exist - using root warning: group aeolus does not exist - using root Installing : aeolus-conductor-daemons-0.0.3-0.fc1420110325210029gitba5d50b.x86_64 113/123 This causes database.yml to have the wrong ownership which causes some issues during aeolus-configure. aeolus-configure-2.0.0-5.fc1420110325170056gitf6daedb.noarch aeolus-conductor-daemons-0.0.3-0.fc1420110325210029gitba5d50b.x86_64 aeolus-conductor-0.0.3-0.fc1420110325210029gitba5d50b.x86_64 aeolus-conductor-doc-0.0.3-0.fc1420110325210029gitba5d50b.x86_64
Moved aeolus user creation to %pre instead of %pre daemons so it would be available when the file ownership of database.yml is being set. 943202ebef891d98c3e3fd3f3e679af7dbfd73d8
Looks good on the 2011-04-15 AMI (ami-18fa0671) however, it looks like they cleaned up /root directory and removed install.log. Aeolus cleanup and configure ran successfully without error so considering this good to go. [root@ip-10-245-207-112 ~]# rpm -qa | grep aeolus aeolus-conductor-doc-0.0.3-6.el6.x86_64 aeolus-conductor-0.0.3-6.el6.x86_64 aeolus-conductor-daemons-0.0.3-6.el6.x86_64 aeolus-configure-2.0.0-8.el6.noarch
release pending...
release pending 3
release pending.. 2
perm close
closing out old bugs