Created attachment 1041777 [details]
no bootable device for one of the nodes
Description of problem:
I am constantly getting failures for virtual machines introspection. THe percentage is about 75 % of success. The rest of the nodes are not able to get discovered and are returning "No bootable device." (screenshot attached). Few minutes ago I was able to discover 15 nodes of 20.
Version-Release number of selected component (if applicable):
75 % of time
Steps to Reproduce:
1. trigger introspection on multiple nodes
75 % of success
100 % of success
A couple of questions: is it always the same node? does the same thing happen with deploy?
Also please attach $ sudo journalctl -u openstack-ironic-discoverd-dnsmasq
CC'ing Lucas as he may know more about iPXE.
is it always the same node?
-- no, various nodes, not always the same ones
does the same thing happen with deploy?
-- no, deploy never got stuck with similar issue
I don't have the machine available anymore, so I cannot provide any other logs.
Ok, I will try to reproduce it myself. In the meanwhile, if someone has the same issue, I'm in bad need of logs, please provide some!
Created attachment 1042800 [details]
dnsmasq log output
This is the openstack-ironic-discoverd-dnsmasq log output from a failing run. The MAC address of the failed node is fa:16:3e:4e:ee:38, and it looks like it's the same address in use problem you had mentioned to me before.
Exactly. Do you think it's a good time to redirect this bug to kvm or whatever manages the PXE firmware? I think everybody here reproduced this bug at least once...
Oh btw, we had a sleep in our scripts:
which is no longer in a new CLI:
We have to bring it back, I'll submit a patch.
And here's the patch: https://review.gerrithub.io/#/c/237591/
heh dmitry its like deja vu. I was having issues with vm introspection last 2 days, especially yesterday lots of poking. I remember when this happened the first time round and the sleep was added ;)
Glad I came across this, will try out since am refreshing envs today for poodle. (I can only do vm envs)
Patch merged, I believe it will work around the problem.
*** Bug 1234956 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.