Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1125321

Summary: rubygem-staypuft: The networker host in the deployment wasn't send to reboot, I had to manually reboot the host to finish the deployment.
Product: Red Hat OpenStack Reporter: Omri Hochman <ohochman>
Component: ruby193-rubygem-foreman-tasksAssignee: Mike Burns <mburns>
Status: CLOSED WONTFIX QA Contact: Omri Hochman <ohochman>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0 (RHEL 6)CC: mburns, rhos-maint, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: Installer   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-29 14:49:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
production.log none

Description Omri Hochman 2014-07-31 14:55:05 UTC
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)

Comment 3 Petr Chalupa 2014-08-08 11:05:30 UTC
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