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

I think the issue is that the default behaviour of the client was changed in the queens (2.0.0). Previously the default microversion was 1.9, but now it is latest [1]. Looks like the deploy guide needs some more conditional wording. I've raised a bug [2], feel free to comment if I've missed

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

I think one might be a bug in the deploy guide then. It states: "In order for nodes to be available for deploying workloads on them, nodes must be in the available provision state. To do this, nodes created with API version 1.11 and above must be moved from the enroll state to the manageable

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

Ahhh yes. The default (null) value of ironic_log_dir doesn't do quite what the author thought it did. https://review.openstack.org/549650 is a patch to correct that. Michael On Mon, Mar 5, 2018 at 8:42 AM, Mark Goddard wrote: > Try setting the ironic_log_dir variable to

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

On the enroll state, you can move it to available via manageable by setting the provision state to manage, then provide. Try an ironic node-validate to diagnose the issue, and make sure the ipmi credentials given can be used to query the nodes power state using ipmitool. Mark On 4 Mar 2018 9:42

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

Try setting the ironic_log_dir variable to /var/log/ironic, or setting [default] log_dir to the same in ironic.conf. I'm surprised it's not logging to a file by default. Mark On 4 Mar 2018 8:33 p.m., "Michael Still" wrote: > Ok, so I applied your patch and redeployed. I now

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

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).

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

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" wrote: Replying to a single email

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

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

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

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.,

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

> 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

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

Hi Michael So what does ironic driver-list say? May it be pxe_ipmitool? It would also be useful if you provide the conductor logs. On Sun, Mar 4, 2018 at 11:06 AM, Michael Still wrote: > Heya, > > I've been playing with bifrost to help me manage some lab machines. I must >

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

Heya, I've been playing with bifrost to help me manage some lab machines. I must say the install process was well documented and smooth, so that was a pleasure. Thanks! That said, I am struggling to get a working node enrolment. I'm resisting using the JSON file / ansible playbook approach,