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):
Steps to Reproduce:
1.Installation via Staypuft installer
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 ***