rubygem-staypuft: HA deployment fails because rabbitmq-server failed to start on one of the hosts (Mnesia on rabbit@525400868093 could not connect to node). Steps: ------- (1) Install Staypuft. (2) Attempt create nova-network HA deployment Results: --------- - on one of the hosts service rabbitmq-server failed to start - deployment failed. It seems that there was DNS issue with the short names ping to 525400868092 ping: unknown host 525400868092 but... ping -c1 525400868092.lab.eng.rdu2.redhat.com 64 bytes from 525400868092.lab.eng.rdu2.redhat.com (192.168.0.6): icmp_seq=1 ttl=64 time=0.253 ms Environment: ------------- ruby193-rubygem-staypuft-0.1.17-1.el6ost.noarch puppet-3.6.2-1.1.el6.noarch puppet-server-3.6.2-1.1.el6.noarch openstack-puppet-modules-2014.1-19.1.el6ost.noarch openstack-foreman-installer-2.0.15-1.el6ost.noarch foreman-1.6.0.21-1.el6sat.noarch rhel-osp-installer-0.1.1-1.el6ost.noarch journalctl -u puppet --------------------- Jul 16 20:33:35 525400868093.lab.eng.rdu2.redhat.com puppet-agent[3036]: Could not start Service[rabbitmq-server]: Execution of '/usr/bin/systemctl start rabbitmq-server' returned 1: Job for rabbitmq-server.serv Jul 16 20:33:35 525400868093.lab.eng.rdu2.redhat.com puppet-agent[3036]: Wrapped exception: Jul 16 20:33:35 525400868093.lab.eng.rdu2.redhat.com puppet-agent[3036]: Execution of '/usr/bin/systemctl start rabbitmq-server' returned 1: Job for rabbitmq-server.service failed. See 'systemctl status rabbitmq Jul 16 20:33:35 525400868093.lab.eng.rdu2.redhat.com puppet-agent[3036]: (/Stage[main]/Rabbitmq::Service/Service[rabbitmq-server]/ensure) change from stopped to running failed: Could not start Service[rabbitmq-s /var/log/rabbitmq/rabbit\@525400868093.log ------------------------------------------- =INFO REPORT==== 16-Jul-2014::20:30:36 === Limiting to approx 924 file handles (829 sockets) =ERROR REPORT==== 16-Jul-2014::20:30:36 === Mnesia(rabbit@525400868093): ** ERROR ** Mnesia on rabbit@525400868093 could not connect to node(s) [rabbit@525400868092]
Marked as a known issue. Fix will be to update the discovery plugin to not ever assign an all-numeric hostname. Set known issue, removed blocker and exception, added GA3 flag.
hosts should now be prefixed with mac
Verified : ruby193-rubygem-staypuft-0.2.2-1.el6ost.noarch Unable to reproduce when using the Workaround: Change the hostnames of your discovered machines to include at least one non-numeric character Result: DNS resolution succeeds
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