Bug 1117918

Summary:	Rubygem-Staypuft: HA deployment fails because cluster nodes can't communicate while installation.
Product:	Red Hat OpenStack	Reporter:	Leonid Natapov <lnatapov>
Component:	rubygem-staypuft	Assignee:	Scott Seago <sseago>
Status:	CLOSED ERRATA	QA Contact:	Leonid Natapov <lnatapov>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 7)	CC:	ajeain, hbrock, mburns, morazi, oblaut, sasha
Target Milestone:	ga
Target Release:	Installer
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-21 18:05:07 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:

Description Leonid Natapov 2014-07-09 15:57:42 UTC

Rubygem-Staypuft: HA deployment fails because cluster nodes can't communicate while installation.
It is intentional that all cluster nodes will be reachable when the cluster is being set up through puppet. However when the hosts in discovery mode they have low level network. Network values should be valid by the time puppet tries to configure the cluster (or more precisely valid within an hour from the first attempt if hosts are in the process of coming up). So, puppet tries to run "pcs auth" command to authenticate with other nodes and fails with the following error:  
Error: unable to connect to pcsd on 192.168.0.8
Unable to connect to 192.168.0.8 ([Errno 113] No route to host)

Probably the install should be happening on the three nodes in parallel to avoid this situation.

How to reproduce:
1.Create new HA deployment.
2.Try to deploy.

Comment 1 Hugh Brock 2014-07-10 12:36:22 UTC

Symptom here was that the other nodes in the cluster were not provisioning because of two issues: Foreman net/DHCP bug and Staypuft incorrect cluster control IP parameter. This is fixed in rubygem-staypuft-0.1.9 which will be in a poodle this morning

Comment 10 Alexander Chuzhoy 2014-08-12 13:17:07 UTC

Verified: rhel-osp-installer-0.1.9-1.el6ost.noarch


This particular error doesn't reproduce.

Comment 11 errata-xmlrpc 2014-08-21 18:05:07 UTC

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/RHBA-2014-1090.html