Hide Forgot
Description of problem: In the 0.3.0 release of Aeolus, both /etc/init.d/deltacloud-core and /etc/init.d/deltacloud-mock are set to use port 3002. The core one starts first, so the mock one silently fails (!). Changing the port number to 3005 for mock in the mock startup script, then adjusting the port through the Conductor UI (mock provider account) lets it work. Version-Release number of selected component (if applicable): aeolus-configure-2.0.1-1.el6.20110721154028git42b1e20.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 aeolus-all-0.3.0-1.el6.fc14.noarch How reproducible: Every time. Steps to Reproduce: 1. Install Aeolus 0.3.0 on RHEL 6.1, using the 0.3.0 release rhel-aeolus.repo file. 2. Run aeolus-configure as super-user. 3. Try adding a mock provider account through Conductor. It fails here, due to mock being unable to start, due to the above mentioned port conflict. Expected results: Mock should work "out of the box" through the Conductor interface. Therefore, Mock should be running on a port that doesn't conflict with deltacloud-core (ie 3005). aeolus-configure will need to set up mock with that port number when it runs. Additional info:
Lets just make sure we're not overriding rhevm and vsphere I think rhevm currently uses 3005, vphsere useses 3006 by default in aeolus-configure
Good point. We'll need to check.
As discussed on IRC and the aeolus-devel mailing list, this is really being caused by deltacloud-core startup script being enabled. The correct solution is for aeolus-configure to disable /etc/init.d/deltacloud-core as part of it's setup run. This lets the mock driver start on port 3002, in it's expected location, and everything "just works".
As a workaround for now, the installation instructions on the Aeolus website now has a step included to disable this.
this should be fixed when we get single instance dc
Fixed on: aeolus-configure-2.0.2-4.20110914145605git811b13e.fc15.noarch aeolus-conductor-0.4.0-0.20110914191507git6354644.fc15.noarch aeolus-conductor-devel-0.4.0-0.20110914191507git6354644.fc15.noarch aeolus-all-0.4.0-0.20110914191507git6354644.fc15.noarch aeolus-conductor-doc-0.4.0-0.20110914191507git6354644.fc15.noarch aeolus-conductor-daemons-0.4.0-0.20110914191507git6354644.fc15.noarch
Aziza please verify these bugs.. Thank you!
mock seems to be setup correctly in latest builds... able to add a provider account, realms .etc.. [root@unused ~]# rpm -qa | grep aeolus aeolus-conductor-doc-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-conductor-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-conductor-daemons-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-all-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-conductor-devel-0.4.0-0.20110922165939git5b371be.fc15.noarch aeolus-configure-2.0.2-4.20110921102958gitcaa9608.fc15.noarch rubygem-aeolus-image-0.1.0-3.20110922120732gita0b9a44.fc15.noarch [root@unused ~]# less /var/log/deltacloud-core/mock.log
closing out old bugs
perm close