Red Hat Bugzilla – Bug 857846
Configured a static ip for RHEV-H and registered RHEV-M successful, status page should display "static" not "none".
Last modified: 2016-04-26 10:05:28 EDT
Created attachment 613590 [details]
Description of problem:
If configured a static ip for rhev-h to registered rhev-m, at the status page of rhev-h should display:"static" not "none".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RHEV-H.
2. Configure static ip for the nic ,registered to RHEV-M successful.
3. Check the status page "Networking" display.
Configured a static ip and registered to RHEV-M successful, the status page of RHEV-H display "Networking : rhevm: none 10.66.11.20".
Configured a static ip and regiested to RHEV-M successful, the status page of RHEV-H should display "Networking : rhevm: static 10.66.11.20".
It's right when configured a dhcp ip.No such issue in RHEV-H 6.3-20120815.0.el6_3 , so it is a regression bug.
Created attachment 613621 [details]
could you also provide the vdsm log and the output if ifcfg and brctl show.
vdms is setting BOOTPROTO=static , the UI is just displaying that variable.
According to vdsm static is the correct value for static IP configurations.
In this case we should just replace none with "static".
Tested as follows:
1. Install Node
2. Apply patch
3. Configure static net
4. Change ifcfg-breth0 bootproto to none
5. Re-login into the tui
6. static is displayed on status page
(In reply to comment #5)
> vdms is setting BOOTPROTO=static , the UI is just displaying that
vdsm is setting BOOTPROTO=none
Just to point it out, Node is setting BOOTPROTO=static in ifcfg-breth*, but looking at the docs  'static' is no intended value for BOOTPROTO.
It's noteworthy that looking at the search results of a famous search engine it seems to be common to use BOOTPROTO=static.
So, vdsm is doing the right thing and the TUI just needs to interprete BOOTPROTO=none as a static IP configuration.
There is a existing bug: Bug 867784 - [RHEV-H 6.4] The "DHCP" was marked "*" in network detail page if configured nic by using "static" .
So I will verify this bug after 867784 fixed.
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.