<div dir="ltr">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 something.<div>Mark</div><div><br></div><div>[1] <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><a href="https://docs.openstack.org/releasenotes/python-ironicclient/queens.html">https://docs.openstack.org/releasenotes/python-ironicclient/queens.html</a></span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">[2] <a href="https://bugs.launchpad.net/ironic/+bug/1753435">https://bugs.launchpad.net/ironic/+bug/1753435</a></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 4 March 2018 at 23:32, Michael Still <span dir="ltr"><<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I think one might be a bug in the deploy guide then. It states:<div><br></div><div>"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 state and then to the available state. This section can be safely skipped, if API version 1.10 or earlier is used (which is the case by default)."</div><div><br></div><div>Whereas I definitely had to move the node to the manage provision state manually to get the node to be managed. For reference, this is the set of command lines I ended up using to manually enroll a node (in case its of use to someone else):</div><div><br></div><div><span class=""><div>ironic node-create -d agent_ipmitool \</div><div> -i ipmi_username=root \</div><div> -i ipmi_password=superuser \</div><div> -i ipmi_address=192.168.50.31 \</div><div> -i deploy_kernel=<a href="http://192.168.50.209:8080/ipa.vmlinuz" target="_blank">http://192.168.<wbr>50.209:8080/ipa.vmlinuz</a> \</div><div> -i deploy_ramdisk=<a href="http://192.168.50.209:8080/ipa.initramfs" target="_blank">http://192.168.<wbr>50.209:8080/ipa.initramfs</a> \</div><div> -p cpus=16 \</div><div> -p memory_mb=12288 \</div><div> -p local_gb=750 \</div><div> -p cpu_arch=x86_64 \</div></span><div> -p capabilities=boot_option:local \</div><div> -n lab8</div><div>ironic port-create -n ${UUID} -a ${DHCP_MAC}</div><div>ironic node-validate lab8</div><div>ironic --ironic-api-version 1.11 node-set-provision-state lab8 manage</div></div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Michael</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 5, 2018 at 9:05 AM, Mark Goddard <span dir="ltr"><<a href="mailto:mark@stackhpc.com" target="_blank">mark@stackhpc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">On the enroll state, you can move it to available via manageable by setting the provision state to manage, then provide.<div dir="auto"><br></div><div dir="auto">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.</div><span class="m_-1102971249007353079HOEnZb"><font color="#888888"><div dir="auto"><br></div><div dir="auto">Mark</div></font></span></div><div class="m_-1102971249007353079HOEnZb"><div class="m_-1102971249007353079h5"><div class="gmail_extra"><br><div class="gmail_quote">On 4 Mar 2018 9:42 p.m., "Mark Goddard" <<a href="mailto:mark@stackhpc.com" target="_blank">mark@stackhpc.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Try setting the ironic_log_dir variable to /var/log/ironic, or setting [default] log_dir to the same in ironic.conf.<div dir="auto"><br></div><div dir="auto">I'm surprised it's not logging to a file by default.</div><div dir="auto"><br></div><div dir="auto">Mark</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 4 Mar 2018 8:33 p.m., "Michael Still" <<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.<div><br></div><div>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.</div><div><br></div><div>Your thoughts?</div><div><br></div><div>Michael</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 5, 2018 at 7:04 AM, Mark Goddard <span dir="ltr"><<a href="mailto:mark@stackhpc.com" target="_blank">mark@stackhpc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>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.</div><div dir="auto"><span class="m_-1102971249007353079m_-4084617025678643300m_-5501300547542997358m_4450719190559359970HOEnZb"><font color="#888888">Mark</font></span><div><div class="m_-1102971249007353079m_-4084617025678643300m_-5501300547542997358m_4450719190559359970h5"><br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On 4 Mar 2018 7:59 p.m., "Michael Still" <<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a>> wrote:<br type="attribution"><blockquote class="m_-1102971249007353079m_-4084617025678643300m_-5501300547542997358m_4450719190559359970m_-4437375923044245668quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Replying to a single email because I am lazier than you.<div><br></div><div>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).</div><div><br></div><div>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 <a href="https://review.openstack.org/#/c/549318/3" target="_blank">https://review.opensta<wbr>ck.org/#/c/549318/3</a> is more subtle than that. I will patch in that change and see if I can get things to work after a redeploy.</div><font color="#888888"><div><br></div><div>Michael</div><div><br></div><div><br></div></font></div><div class="m_-1102971249007353079m_-4084617025678643300m_-5501300547542997358m_4450719190559359970m_-4437375923044245668elided-text"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 5, 2018 at 5:45 AM, Mark Goddard <span dir="ltr"><<a href="mailto:mark@stackhpc.com" target="_blank">mark@stackhpc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Hi Michael,<div dir="auto"><br></div><div dir="auto">If you're using the latest release of biifrost I suspect you're hitting <a href="https://bugs.launchpad.net/bifrost/+bug/1752975" target="_blank">https://bugs.launchpad<wbr>.net/bifrost/+bug/1752975</a>. I've submitted anfox for review.</div><div dir="auto"><br></div><div dir="auto">For a workaround, modify /etc/ironic/ironic.conf, and set enabled_hardware_types=ipmi.</div><div dir="auto"><br></div><div dir="auto">Cheers,</div><div dir="auto">Mark</div></div><div class="m_-1102971249007353079m_-4084617025678643300m_-5501300547542997358m_4450719190559359970m_-4437375923044245668m_8810066551044548932HOEnZb"><div class="m_-1102971249007353079m_-4084617025678643300m_-5501300547542997358m_4450719190559359970m_-4437375923044245668m_8810066551044548932h5"><div class="gmail_extra"><br><div class="gmail_quote">On 4 Mar 2018 5:50 p.m., "Julia Kreger" <<a href="mailto:juliaashleykreger@gmail.com" target="_blank">juliaashleykreger@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> No valid host was found. Reason: No conductor service registered which<br>
> supports driver agent_ipmitool. (HTTP 400)<br>
><br>
> I can't see anything helpful in the logs. What driver should I be using for<br>
> bifrost? agent_ipmitool seems to be enabled in ironic.conf.<br>
<br>
Weird, I'm wondering what the error is in the conductor log. You can<br>
try using "ipmi" for the hardware type that replaces<br>
agent_ipmitool/pxe_ipmitool.<br>
<br>
-Julia<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote></div></div>
</div></div><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br></blockquote></div><br></div>
</div><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br></blockquote></div><br></div></div></div></div></div>
<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br></blockquote></div><br></div>
<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br></blockquote></div></div>
</blockquote></div></div>
</div></div><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div>