[openstack-dev] [Ironic][Bifrost] Manually enrolling a node

Michael Still mikal at stillhq.com
Sun Mar 4 20:33:17 UTC 2018


Ok, so I applied your patch and redeployed. I now get a list of drivers in
"ironic driver-list", and I can now enroll a node.

Interestingly, the node sits in the "enroll" provisioning state for ages
and doesn't appear to ever get a meaningful power state (ever being after a
five minute wait). There are still no logs in /var/log/ironic, and grepping
for the node's uuid in /var/log/syslog returns zero log items.

Your thoughts?

Michael



On Mon, Mar 5, 2018 at 7:04 AM, Mark Goddard <mark at stackhpc.com> wrote:

> The ILO hardware type was also not loading because the required management
> and power interfaces were not enabled. The patch should address that but
> please let us know if there are further issues.
> Mark
>
>
> On 4 Mar 2018 7:59 p.m., "Michael Still" <mikal at stillhq.com> wrote:
>
> Replying to a single email because I am lazier than you.
>
> I would have included logs, except /var/log/ironic on the bifrost machine
> is empty. There are entries in syslog, but nothing that seems related (its
> all periodic task kind of stuff).
>
> However, Mark is right. I had an /etc/ironic/ironic.conf with "ucs" as a
> hardware type. I've removed ucs entirely from that list and restarted
> conductor, but that didn't help. I suspect https://review.opensta
> ck.org/#/c/549318/3 is more subtle than that. I will patch in that change
> and see if I can get things to work after a redeploy.
>
> Michael
>
>
>
> On Mon, Mar 5, 2018 at 5:45 AM, Mark Goddard <mark at stackhpc.com> wrote:
>
>> Hi Michael,
>>
>> If you're using the latest release of biifrost I suspect you're hitting
>> https://bugs.launchpad.net/bifrost/+bug/1752975. I've submitted anfox
>> for review.
>>
>> For a workaround, modify /etc/ironic/ironic.conf, and set
>> enabled_hardware_types=ipmi.
>>
>> Cheers,
>> Mark
>>
>> On 4 Mar 2018 5:50 p.m., "Julia Kreger" <juliaashleykreger at gmail.com>
>> wrote:
>>
>>> > No valid host was found. Reason: No conductor service registered which
>>> > supports driver agent_ipmitool. (HTTP 400)
>>> >
>>> > I can't see anything helpful in the logs. What driver should I be
>>> using for
>>> > bifrost? agent_ipmitool seems to be enabled in ironic.conf.
>>>
>>> Weird, I'm wondering what the error is in the conductor log. You can
>>> try using "ipmi" for the hardware type that replaces
>>> agent_ipmitool/pxe_ipmitool.
>>>
>>> -Julia
>>>
>>> ____________________________________________________________
>>> ______________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: OpenStack-dev-request at lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180305/0ce3d811/attachment.html>


More information about the OpenStack-dev mailing list