Re: [Rdo-list] RH OpenStack v4 Evaluation: Initial Setup: First Compute Node Doesn't Show Up in Hypervisor List

Thanks for the quick response! Based on the below log findings and what I just found searching, is this caused by the controller host group parameter "freeipa" being set to the default "false"? Change it to "true"? On the compute node, I'm seeing this over and over in the compute log: Unable to connect to AMQP server: Error in sasl_client_start (-1) SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Cannot determine realm for numeric host address). Sleeping 5 seconds On the controller conductor log: Unable to connect to AMQP server: Error in sasl_client_start (-1) SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Cannot determine realm for numeric host address). Sleeping 5 seconds In the controller messages file: python: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Cannot determine realm for numeric host address) -----Original Message----- From: Rhys Oxenham [mailto:roxenham@redhat.com] Sent: Wednesday, July 02, 2014 12:14 PM To: Lodgen, Brad Cc: rdo-list(a)redhat.com Subject: Re: [Rdo-list] RH OpenStack v4 Evaluation: Initial Setup: First Compute Node Doesn't Show Up in Hypervisor List Hi Brad, Have you checked the nova-compute logs in /var/log/nova/compute.log (on your new compute node?) This should point towards why it's unable to connect/start etc. I suspect that it's unable to join the message queue, and hence show up as an available hypervisor. Many thanks Rhys On 2 Jul 2014, at 18:05, Lodgen, Brad <Brad.Lodgen(a)centurylink.com&gt; wrote: