Grepping conductor log [1] for the failed node `04e86289-e615-47c2-ab77-d790a5c0aa5e` does not reveal any IPMI errors any more. So this is likely not the libvirt issue any more.
From the inspector log [2] it looks like the node has never come up for introspection. Hooking on VM's console may probably shed some light on what's happening.
Grepping conductor log [1] for the failed node `04e86289- e615-47c2- ab77-d790a5c0aa 5e` does not reveal any IPMI errors any more. So this is likely not the libvirt issue any more.
From the inspector log [2] it looks like the node has never come up for introspection. Hooking on VM's console may probably shed some light on what's happening.
1. https:/ /ci.centos. org/artifacts/ rdo/jenkins- tripleo- quickstart- promote- master- current- tripleo- delorean- minimal- 379/undercloud/ var/log/ containers/ ironic/ ironic- conductor. log.gz /ci.centos. org/artifacts/ rdo/jenkins- tripleo- quickstart- promote- master- current- tripleo- delorean- minimal- 379/undercloud/ var/log/ containers/ ironic- inspector/ ironic- inspector. log.gz
2. https:/