On Thu, Apr 30, 2015 at 08:15:35AM -0400, James Slagle wrote: > Hi, there were a few different threads related to rdo-manager and encountering > rabbitmq errors related to the hostname when installing the undercloud. > > I was able to reproduce a couple different issues, and in my environment it > came down to $HOSTNAME not matching the defined FQDN hostname. You could > use hostnamectl to set a hostname, but that does not update $HOSTNAME in your > current shell. > > rabbitmq-env, which is sourced at the start of rabbitmq-server, reads the > hostname from $HOSTNAME in some scenarios, and then uses that value to define > the rabbit node name. Therefore, if you have a mismatch between $HOSTNAME and > the actual FQDN, things can go off the rails with rabbitmq. > > I've tried to address this issue in this patch: > https://review.gerrithub.io/#/c/232052/ > > For the virt-setup, setting of the FQDN hostname and adding it to /etc/hosts > will now be done automatically, with the instack.localdomain used. The hostname > can always be redefined later if desired. > > For baremetal, I've added some notes to the docs to hopefully cover the > requirements. > > -- > -- James Slagle > -- Good catch James. Hopefully this will unblock a number of folks who have been hitting this. --Hugh -- == Hugh Brock, hbrock(a)redhat.com == == Senior Engineering Manager, Cloud Engineering == == Tuskar: Elastic Scaling for OpenStack == == http://github.com/tuskar == "I know that you believe you understand what you think I said, but I’m not sure you realize that what you heard is not what I meant." --Robert McCloskey _______________________________________________ Rdo-list mailing list Rdo-list(a)redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe(a)redhat.com

On Thu, Apr 30, 2015 at 09:23:54AM -0400, Mohammed Arafa wrote: > James > > will the shortname also be added to the hosts file along with the fqdn? We could. The patch I proposed does not however, it merely addresses the issues I was seeing. > > On Thu, Apr 30, 2015 at 9:03 AM, Hugh O. Brock <hbrock(a)redhat.com&gt; wrote: > > > On Thu, Apr 30, 2015 at 08:15:35AM -0400, James Slagle wrote: > > > Hi, there were a few different threads related to rdo-manager and > > encountering > > > rabbitmq errors related to the hostname when installing the undercloud. > > > > > > I was able to reproduce a couple different issues, and in my environment > > it > > > came down to $HOSTNAME not matching the defined FQDN hostname. You could > > > use hostnamectl to set a hostname, but that does not update $HOSTNAME in > > your > > > current shell. > > > > > > rabbitmq-env, which is sourced at the start of rabbitmq-server, reads the > > > hostname from $HOSTNAME in some scenarios, and then uses that value to > > define > > > the rabbit node name. Therefore, if you have a mismatch between > > $HOSTNAME and > > > the actual FQDN, things can go off the rails with rabbitmq. > > > > > > I've tried to address this issue in this patch: > > > https://review.gerrithub.io/#/c/232052/ > > > > > > For the virt-setup, setting of the FQDN hostname and adding it to > > /etc/hosts > > > will now be done automatically, with the instack.localdomain used. The > > hostname > > > can always be redefined later if desired. > > > > > > For baremetal, I've added some notes to the docs to hopefully cover the > > > requirements. > > > > > > -- > > > -- James Slagle > > > -- > > > > Good catch James. Hopefully this will unblock a number of folks who have > > been hitting this. > > > > --Hugh > > > > -- > > == Hugh Brock, hbrock(a)redhat.com == > > == Senior Engineering Manager, Cloud Engineering == > > == Tuskar: Elastic Scaling for OpenStack == > > == http://github.com/tuskar == > > > > "I know that you believe you understand what you think I said, but I’m > > not sure you realize that what you heard is not what I meant." > > --Robert McCloskey > > > > _______________________________________________ > > Rdo-list mailing list > > Rdo-list(a)redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com > > > > > > -- > > > < https://candidate.peoplecert.org/ReportsLink.aspx?argType=1&id=13D642... > > > *805010942448935* > < https://www.redhat.com/wapps/training/certification/verify.html?certNumbe... > > > *GR750055912MA* > < https://candidate.peoplecert.org/ReportsLink.aspx?argType=1&id=13D642... > > > *Link to me on LinkedIn <http://www.linkedin.com/in/mohammedarafa>* -- -- James Slagle --

On Thu, Apr 30, 2015 at 08:15:35AM -0400, James Slagle wrote: > For baremetal, I've added some notes to the docs to hopefully cover the > requirements. I'm not familiar with AMQP. Is there a particular reason why rabbitmq is so sensitive to hostname issues? I was surprised to run into this with a packstack install the other day, especially given that packstack configures everything uses ip addresses rather than names. rabbitmq seems to perform some sort of reverse-lookup of the hostname, and there was a stale dns entry out there that it was picking up. This wouldn't have caused a problem for anything else (because the entire configuration is based on ip addresses rather than hostnames), but it prevented rabbitmq from starting up correctly. Is there any chance that we should also be pursuing this as a bug in rabbitmq? Or is there a configuration we can tweak in rabbitmq that will make it less sensitive to hostname issues?