Hide Forgot
Description of problem: All of the /etc/init.d/deltacloud-* script created by aeolus-configure claim to be "deltacloud-core" in their header. For example, this is from the deltacloud-ec2-us-east-1 script (not deltacloud-core): #!/bin/bash # # # deltacloud-core startup script for deltacloud-core server # # chkconfig: - 97 03 # description: deltacloud-core is primary server process for the \ # Deltacloud Core component. # <snip> It should say "deltacloud-ec2-us-east-1" instead of "deltacloud-core". Probably just a cut-n-paste error when creating them or something: Version-Release number of selected component (if applicable): The 0.3.0 RHEL 6.1 release rpms: aeolus-all-0.3.0-1.el6.fc14.noarch aeolus-configure-2.0.1-1.el6.fc14.noarch aeolus-conductor-0.3.0-1.el6.fc14.noarch aeolus-conductor-daemons-0.3.0-1.el6.fc14.noarch aeolus-conductor-doc-0.3.0-1.el6.fc14.noarch
I believe this should be moved to on_qa.
We have moved to a single deltacloud-core instance for all providers. There is only one init script moving forward.
All of the /etc/init.d/deltacloud-* have been removed and only single instance of deltacloud-core exists for all providers. There is only one init script. #vi /etc/init.d/deltacloud-core !/bin/sh # # deltacloud-core Deltacloud API Core # chkconfig: 345 90 60 # description: deltacloud-core is primary server process for the \ # Deltacloud Core component. ### BEGIN INIT INFO # Provides: deltacloud-core # Required-Start: # Required-Stop: verified on: [root@tyan-gt24-09 aeolus-conductor]# rpm -qa | grep aeolus aeolus-conductor-doc-0.4.0-0.20110926211134git1cc372b.fc15.noarch aeolus-conductor-daemons-0.4.0-0.20110926211134git1cc372b.fc15.noarch rubygem-aeolus-image-0.1.0-3.20110919115936gitd1d24b4.fc15.noarch aeolus-configure-2.0.2-4.20110923140029gitff33f9b.fc15.noarch aeolus-conductor-0.4.0-0.20110926211134git1cc372b.fc15.noarch aeolus-all-0.4.0-0.20110926211134git1cc372b.fc15.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0586.html