Bug 1129970

Summary:	After Staypuft installation RPC infrastructure is using wrong IP, external instead of internal.
Product:	Red Hat OpenStack	Reporter:	Toni Freger <tfreger>
Component:	rubygem-staypuft	Assignee:	Mike Burns <mburns>
Status:	CLOSED DUPLICATE	QA Contact:	Omri Hochman <ohochman>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	5.0 (RHEL 7)	CC:	mburns, oblaut, yeylon
Target Milestone:	---
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-14 12:04:05 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 Toni Freger 2014-08-14 05:59:58 UTC

Description of problem:
All RPC messages transmits from computes and networker to controller through staypuft host, since in configuration file external IP of controller is configured instead of internal-management IP 192.168.0.X

[root@maca25400868096 ~]# ip r get 10.35.102.75
10.35.102.75 via 192.168.0.1 dev eth1  src 192.168.0.3 

In my setup it caused several problems during amqp transmission between compute\networker and controller.

Prints from rabbitmq log of controller http://pastebin.test.redhat.com/227910   

Main problem in this deployment configuration is, if the staypaft host for some reason won't transmit RPC packets, all openstack deployment will stop working. 

Version-Release number of selected component (if applicable):

ruby193-rubygem-staypuft-0.1.22.el6ost

How reproducible:
100%

Steps to Reproduce:
1.Installation via Staypuft installer

Comment 1 Mike Burns 2014-08-14 12:04:05 UTC

Duplicate of multiple other bugs.  IP addresses on the wrong network stem from foreman changing host ip addresses on every facter run.  This setting has been changed.

Separately, ruby193-rubygem-staypuft-0.1.22.el6ost is very old.  Can you confirm you're using the right builds?

*** This bug has been marked as a duplicate of bug 1126332 ***