Red Hat Bugzilla – Bug 844176
Host is installed with boot protocol "None" on rhevm Network when its management NIC was configured as static
Last modified: 2016-02-10 14:57:51 EST
Created attachment 601043 [details]
Problem shown in GUI
Description of problem:
If you configure management NIC as static on host and then add that host to the system, it will be added with boot protocol None
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure eth0(management IP) of host to have static IP address
2. Add that host to the DC and Cluster
3. When the host become operation check its boot protocol
Boot protocol is None
Boot protocol should be static as was configured on management NIC
On GUI and DB we can see that the management is configured as None and on VDSM we can see that it is static
Created attachment 601044 [details]
It looks similar, but it's not the same.
In 842986 Igor is talking about bridgeless Network only and about absent of cfg field and it is not this case.
In getVdsCaps you can see that the boot protocol is static.
After looking at the code -
We could not locate a place where we add BOOTPROTO=static in our code, this is an illegal value in cfg file.
We did saw that when installing the host the bootstrap code copies the properties of the nic to the management bridge.
Genadi - can you please redo the scenario but validate before the host installation that the cfg file of the nic does not have BOOTPROTO=static to start with
The BOOTPROTO was indeed configured to static on management NIC of the host, but as we spoke it is a legitimate configuration that should be supported.
Verified in SI13