-
Notifications
You must be signed in to change notification settings - Fork 171
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
confignetwork fails when BMC interfaces are defined in the 'nics' table #4538
Comments
PR in #4539 |
Hi @kcgthb. We use |
Hi @kcgthb, We recommend to use |
Well, that's what I used to do in earlier versions of xCAT, until the introduction of the For a time, there was a mention of the deprecation in the Domain Name Resolution page of the documentation:
That mention has been recently removed (in commit 29ff06b) with the following message:
I'll go back to using |
Well, I gave So I'm back with my initial solution of defining the BMC IP address in |
The
confignetwork
postscript returns an error when BMC interfaces are defined in the 'nics` table.For instance, with the following node definition:
The script produces an error for the
bmc
interface:which kind of makes sense, since the OS doesn't really see the BMC interface and can't configure it. Yet
bmc
is a valid interface type in thenics
table, as mentioned in the documentation. So the script should not exit with an error.We need a way to define IP <-> hostname resolution for our BMC interfaces, so they get generated by
makehosts
andmakedns
.So, what's the way to define hostname and IP addresses for BMC interfaces now?
The text was updated successfully, but these errors were encountered: