Hide Forgot
Created attachment 922957 [details] production.log rubygem-staypuft: The networker host in the deployment wasn't send to reboot, I had to manually reboot the host to finish the deployment. It's not always reproducible: I've done nonHA-neutron-vxlan deployment, After the controller got to 100%, the second host (networker) was hang in the discovery-image and I needed to manually reboot the networker host in order to finish the deployment. environment: ------------ puppet-3.6.2-1.1.el6.noarch puppet-server-3.6.2-1.1.el6.noarch openstack-puppet-modules-2014.1-19.8.el6ost.noarch ruby193-rubygem-staypuft-0.1.22-1.el6ost.noarch foreman-1.6.0.21-2.el6sat.noarch ruby193-rubygem-foreman_discovery-1.3.0-2.el6sat.noarch foreman-postgresql-1.6.0.21-2.el6sat.noarch (attached production.log)
The problem is that the API for restarting the host is not reporting success or failure so Staypuft cannot detect failure. It would need to be fixed in foreman-discovery, see https://github.com/theforeman/foreman_discovery/blob/develop/app/models/host/managed_extensions.rb#L16-L25