rubygem-staypuft: neutron deployment doesn't advance, the IPs used to register the computes in foreman, moved to the controller during deployment. Environment: openstack-puppet-modules-2014.2.8-1.el7ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch openstack-foreman-installer-3.0.8-1.el7ost.noarch rhel-osp-installer-0.5.4-1.el7ost.noarch ruby193-rubygem-staypuft-0.5.9-1.el7ost.noarch rhel-osp-installer-client-0.5.4-1.el7ost.noarch Steps to reproduce: 1. Install rhel-osp-installer 2. Configure/run Neutron deployment (one controller+2 computes) Result: The deployment doesn't complete. Checking the systems, I realized that the IP used by computes are in use by the controller. I verified the IPs resided on computes right after they were provisioned with OS. Expected result: The IP registered in foreman should stay on the respective compute host.
Reproduced the bug on the same (bare metal) environment.
After assigning hosts to deployment and assigning the networks, I click on "Access all details" button. I see that "ceilometer_admin_vip" will use the IP that was assigned to first compute, and "heat_admin_vip" will use the IP assigned to the second compute.
Moving the admin_api and management traffic types to a separate subnet (away from the default subnet) should resolve it. I see no collisioning IPs in the list of IPs under "Access all details" after moving the mentioned types.
The workaround suggested in comment #5 worked for me. Have a successful deployment.
same issue as bug 1176423 *** This bug has been marked as a duplicate of bug 1176423 ***