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

[Rhys Oxenham]

Have you specified Qpid authentication in any of the rest of the services? I suspect that Qpid is set up to use authentication but none of the other services are.

On 2 Jul 2014, at 18:30, Lodgen, Brad <Brad.Lodgen at centurylink.com> wrote:

> # GENERATED BY PUPPET
> #
> # Configuration file for qpidd. Entries are of the form:
> #   name=value
> #
> # (Note: no spaces on either side of '='). Using default settings:
> # "qpidd --help" or "man qpidd" for more details.
> port=5672
> max-connections=65535
> worker-threads=17
> connection-backlog=10
> auth=yes
> realm=QPID
> 
> 
> -----Original Message-----
> From: Rhys Oxenham [mailto:roxenham at redhat.com] 
> Sent: Wednesday, July 02, 2014 12:27 PM
> To: Lodgen, Brad
> Cc: rdo-list at redhat.com
> Subject: Re: [Rdo-list] RH OpenStack v4 Evaluation: Initial Setup: First Compute Node Doesn't Show Up in Hypervisor List
> 
> No worries! 
> 
> Can you paste out your /etc/qpidd.conf file from the controller? (Make sure you sanitise the output)
> 
> Cheers
> Rhys
> 
> 
> On 2 Jul 2014, at 18:23, Lodgen, Brad <Brad.Lodgen at centurylink.com> wrote:
> 
>> 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 at redhat.com]
>> Sent: Wednesday, July 02, 2014 12:14 PM
>> To: Lodgen, Brad
>> Cc: rdo-list at 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 at centurylink.com> wrote:
>> 
>>> Hi folks,
>>> 
>>> I have an issue where I've just done the initial setup and added a controller node, it finished, then I added a compute node, it finished, but I don't see the compute node in the hypervisor list on the dashboard. I'm using the RH OpenStack evaluation version 4. I have five hosts present in Foreman.
>>> 
>>> -Foreman host (purely for Foreman)
>>> -Controller host (applied Controller(Nova) host group) -Compute Host 
>>> (applied Compute(Nova) host group)
>>> -2 other hosts (not host group applied, but one will be compute and 
>>> one will be storage)
>>> 
>>> Did I miss something on the controller/compute host group parameters that would cause it to not show up in the dashboard?
>>> _______________________________________________
>>> Rdo-list mailing list
>>> Rdo-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/rdo-list
>> 
>