Bug 1127461

Summary:	Rubygem-Staypuft: HA-neutron deployment fails - the corosync.conf has a nodelist consisting of IP addresses from different subnets.
Product:	Red Hat OpenStack	Reporter:	Alexander Chuzhoy <sasha>
Component:	rubygem-staypuft	Assignee:	Scott Seago <sseago>
Status:	CLOSED ERRATA	QA Contact:	Leonid Natapov <lnatapov>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	5.0 (RHEL 7)	CC:	aberezin, ajeain, lnatapov, mburns, yeylon
Target Milestone:	ga
Target Release:	Installer
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ruby193-rubygem-staypuft-0.2.1.el6ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-21 18:08:21 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 Alexander Chuzhoy 2014-08-06 22:30:46 UTC

Rubygem-Staypuft:  HA-neutron deployment fails - the corosync.conf has a nodelist consisting of IP addresses from different subnets.


Environment:
rhel-osp-installer-0.1.6-5.el6ost.noarch
openstack-foreman-installer-2.0.16-1.el6ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch
openstack-puppet-modules-2014.1-19.9.el6ost.noarch


Steps to reproduce:
1. Install rhel-osp-installer
2. Create/run an HA neutron deployment with 2 computes.

Result:
The deployment gets stuck on installing the controllers - 60%.
Running "pcs cluster status" on different nodes shows that there are 2 clusters:
A: consisting of 2 nodes
B: consisting of 1 node.
The corosync.conf has a nodelist consisting of IP addresses from 2 different subnets. Cluster "A" nodes IPs from one subnet, and cluster "B" uses the IP taken from another NIC- different subnet.


Expected:
Deployment should complete with no issues.

Comment 4 Alexander Chuzhoy 2014-08-11 20:41:53 UTC

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


This particular issue doesn't reproduce now.

Comment 6 errata-xmlrpc 2014-08-21 18:08:21 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