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

Bug 1364528

Summary:	rerunning instack-undercloud-installer with a different ip address does not work
Product:	Red Hat OpenStack	Reporter:	Jason Montleon <jmontleo>
Component:	instack-undercloud	Assignee:	James Slagle <jslagle>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Arik Chernetsky <achernet>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0 (Liberty)	CC:	dsneddon, jcoufal, mburns, rhel-osp-director-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-14 16:43:31 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:
Bug Depends On:
Bug Blocks:	1273561

Description Jason Montleon 2016-08-05 15:34:59 UTC

Description of problem:
When rerunning instack-install-undercloud with a different IP address I see the following errors and swift returns a 503 post install when I do a 'swift list'

Notice: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[container]/Exec[rebalance_container]/returns: /usr/lib/python2.7/site-packages/swift/common/ring/builder.py:406: RingValidationWarning: Replica count of 3.0 requires more than 2 devices
Notice: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[container]/Exec[rebalance_container]/returns:   'num_devices': num_devices,
Notice: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[container]/Exec[rebalance_container]/returns: No partitions could be reassigned.
Notice: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[container]/Exec[rebalance_container]/returns: Either none need to be or none can be due to min_part_hours [24].
Error: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[container]/Exec[rebalance_container]: Failed to call refresh: swift-ring-builder /etc/swift/container.builder rebalance returned 1 instead of one of [0]
Error: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[container]/Exec[rebalance_container]: swift-ring-builder /etc/swift/container.builder rebalance returned 1 instead of one of [0]
Notice: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[object]/Exec[rebalance_object]/returns: /usr/lib/python2.7/site-packages/swift/common/ring/builder.py:406: RingValidationWarning: Replica count of 3.0 requires more than 2 devices
Notice: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[object]/Exec[rebalance_object]/returns:   'num_devices': num_devices,
Notice: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[object]/Exec[rebalance_object]/returns: No partitions could be reassigned.
Notice: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[object]/Exec[rebalance_object]/returns: Either none need to be or none can be due to min_part_hours [24].
Error: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[object]/Exec[rebalance_object]: Failed to call refresh: swift-ring-builder /etc/swift/object.builder rebalance returned 1 instead of one of [0]
Error: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[object]/Exec[rebalance_object]: swift-ring-builder /etc/swift/object.builder rebalance returned 1 instead of one of [0]


Version-Release number of selected component (if applicable):
instack-undercloud-2.2.7-4.el7ost.noarch

How reproducible:
Seems every time

Steps to Reproduce:
1. Run the installer with an ip address, say 192.168.234.254
2. rerun the installer with a different address, like 192.168.234.253

Actual results:
rerun of installation leave the director in a broken state

Expected results:
director functions properly.

Additional info:

Comment 2 Dan Sneddon 2016-10-14 16:43:31 UTC

I believe this bug is now fixed. I recently installed the Undercloud using an OSP 9 puddle, and was able to change the Undercloud IP and reinstall. I may have needed to delete the br-ctlplane interface first, I don't recall.

If this bug is still showing up in OSP 9/10, please reopen this bug.

Comment 3 Dan Sneddon 2016-10-14 16:46:29 UTC

In the worst case scenario, I believe this procedure will wipe out the traces of the old IP and allow the undercloud to be reinstalled with a new address (note you should be logged in via console or via a different IP than the one on br-ctlplane):

1) sudo ifdown br-ctlplane
2) sudo ovs-vtsctl del-br br-ctlplane
3) sudo rm /etc/sysconfig/network-scripts/ifcfg-brctlplane
4) sudo rm /etc/sysconfig/network-scripts/ifcfg-eth1 # Use correct NIC here

Then run "openstack undercloud install" after modifying undercloud.conf to the new value.