Follow-up from yesterday... is this the same default in RDO, to have qpidd.conf default to auth=yes? Does that mean I have something on the compute side misconfigured? It looks to me like the username/password is the same on the controller/compute. For now, I've had to disable puppet agent on the controller, as it keeps resetting "auth=no" back to "auth=yes", and I don't see a host group parameter that would change that. -----Original Message----- From: Lodgen, Brad Sent: Wednesday, July 02, 2014 2:01 PM To: 'Rhys Oxenham' Cc: &#39;rdo-list(a)redhat.com&#39; Subject: RE: [Rdo-list] RH OpenStack v4 Evaluation: Initial Setup: First Compute Node Doesn't Show Up in Hypervisor List So even though the default controller puppet module configures qpidd.conf to say "auth=yes", I changed it to "auth=no" and restarted qpidd service. I now see my compute host in the dashboard. Is that a misconfiguration in RHOSv4 that I should submit for a change somewhere? -----Original Message----- From: Lodgen, Brad Sent: Wednesday, July 02, 2014 12:53 PM To: 'Rhys Oxenham' Cc: &#39;rdo-list(a)redhat.com&#39; Subject: RE: [Rdo-list] RH OpenStack v4 Evaluation: Initial Setup: First Compute Node Doesn't Show Up in Hypervisor List The settings in the controller/compute host group parameters regarding qpidd are all default, except for the host, which is the private IP of the controller. I haven't made any changes outside of the Foreman host group parameters and I don't see any compute host group parameters that would allow me to specify whether a service uses Qpid authentication or not. I did change the compute host group parameter "auth_host" and "nova_host" (originally by default set to 127.0.0.1) to the private IP of the controller. Would that have any effect? -----Original Message----- From: Rhys Oxenham [mailto:roxenham@redhat.com] Sent: Wednesday, July 02, 2014 12:35 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 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(a)centurylink.com&gt; 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@redhat.com] > Sent: Wednesday, July 02, 2014 12:27 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 > > 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(a)centurylink.com&gt; 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@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: >> >>> 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(a)redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >> >

From looking at puppet-qpid it should have done this for you.

No worries. I understand you're busy and thank you for the assistance. To answer your question: yes, following the change and qpidd restart, the logs showed successful communication and the initial compute node showed up as a hypervisor in the dashboard. I also successfully added a second compute node. Success here relies upon disabling the puppet agent so it doesn't change auth back to yes; otherwise, communication fails. -----Original Message----- From: Rhys Oxenham [mailto:roxenham@redhat.com] Sent: Thursday, July 03, 2014 11:13 AM 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 Sorry I didn't respond to this... I have auth set to no in my environment, but that's just for testing. Do things work when auth is set to no and the service is restarted? On 3 Jul 2014, at 17:11, Lodgen, Brad <Brad.Lodgen(a)centurylink.com&gt; wrote: > Follow-up from yesterday... is this the same default in RDO, to have qpidd.conf default to auth=yes? > > Does that mean I have something on the compute side misconfigured? It looks to me like the username/password is the same on the controller/compute. > > For now, I've had to disable puppet agent on the controller, as it keeps resetting "auth=no" back to "auth=yes", and I don't see a host group parameter that would change that. > > > > > -----Original Message----- > From: Lodgen, Brad > Sent: Wednesday, July 02, 2014 2:01 PM > To: 'Rhys Oxenham' > Cc: &#39;rdo-list(a)redhat.com&#39; > Subject: RE: [Rdo-list] RH OpenStack v4 Evaluation: Initial Setup: > First Compute Node Doesn't Show Up in Hypervisor List > > So even though the default controller puppet module configures qpidd.conf to say "auth=yes", I changed it to "auth=no" and restarted qpidd service. I now see my compute host in the dashboard. > > Is that a misconfiguration in RHOSv4 that I should submit for a change somewhere? > > > > -----Original Message----- > From: Lodgen, Brad > Sent: Wednesday, July 02, 2014 12:53 PM > To: 'Rhys Oxenham' > Cc: &#39;rdo-list(a)redhat.com&#39; > Subject: RE: [Rdo-list] RH OpenStack v4 Evaluation: Initial Setup: > First Compute Node Doesn't Show Up in Hypervisor List > > The settings in the controller/compute host group parameters regarding qpidd are all default, except for the host, which is the private IP of the controller. > > I haven't made any changes outside of the Foreman host group parameters and I don't see any compute host group parameters that would allow me to specify whether a service uses Qpid authentication or not. > > I did change the compute host group parameter "auth_host" and "nova_host" (originally by default set to 127.0.0.1) to the private IP of the controller. Would that have any effect? > > > -----Original Message----- > From: Rhys Oxenham [mailto:roxenham@redhat.com] > Sent: Wednesday, July 02, 2014 12:35 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 > > 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(a)centurylink.com&gt; 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@redhat.com] >> Sent: Wednesday, July 02, 2014 12:27 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 >> >> 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(a)centurylink.com&gt; 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@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: >>> >>>> 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(a)redhat.com >>>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >> >