-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR #41 break xNBA DHCP for certain hardware #46
Comments
@ruixingw Have you tried |
Thanks for the update. I'll try it when I get a chance |
@ruixingw Have you had a chance to see if |
oops, this seems to be the last unresolved issue for 2.16.3 milestone.. I’ll try it asap (should be able to get it done in this week) |
Unfortunately the problem still persists with this new version does solve issue xcat2/xcat-core#7036 which I also encountered today with another hardware (Intel X520/DA-2, 82599ES controller). |
@ruixingw Thanks for the feedback. I will move this issue to the next release milestone. |
We have some very cheap motherboards on compute nodes, which may not be that mainstream (HUANANZHI X99 F8D, specs: http://www.huananzhi.com/html/1/184/185/491.html; the NIC is RTL8111H Gigabit Ethernet Card). We previously successfully provisioned OS using these motherboards with xCAT 2.16.1.
Today, I again got some of these machines and was trying to provision them with xCAT 2.16.2 and CentOS 8.4. However, it seems xNBA failed during DHCP, ending with a message like
Configuring (net0 00:90:fb:6b:08:52).................. No configuration methods succeeded
.I also tried the command "dhcp" in xNBA(iPXE) shell. it doesn't work either.
Checking on the management node
/var/log/messages
,dhcpd
receivedDHCPDISCOVER
and sentDHCPOFFER
, but these two repeat several times until timeout. There's noDHCPREQUEST
norDHCPACK
at all. DHCP works fine for onboard PXE (which then chainloads xNBA I guess?) and other nodes.Searching, I found PR #41 which upgraded xnba-undi from 1.0.3-131028 to 1.20.1-0 in xCAT 2.16.2. I downgraded xnba-undi to 1.0.3-131028, and the problem is solved.
xnba-undi-1.0.3 is well enough for us and I can just use it. I just want to let you know about this issue, just in case if there is any unseen bug elsewhere.
Let me know if you need more information or want me to do more tests.
The text was updated successfully, but these errors were encountered: