RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
I have host with eth2 that ifcfg-eth2 cfg is:
DEVICE=eth2
ONBOOT=no
BOOTPROTO=dhcp
HWADDR=00:10:18:24:47:F2

I have add the host to RHEVM and install it.
The newly created RHEVM ifcfg file look like this:
DEVICE=rhevm
TYPE=Bridge
ONBOOT=yes
DELAY=0
BOOTPROTO=dhcp
ONBOOT=no

The RHEVM cfg file have two onboot one with yes and one with no, After reboot RHEVM bridge is down.


Version-Release number of selected component (if applicable):
vdsm-4.9-113.2.el6_3.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Host with ethX that have onboot=off
2.Add the host to RHEVM and install it.

  
Actual results:
After reboot RHEVM bridge not up, The hosty is non-operational

Expected results:
After reboot RHEVM bridge is up, shouldn't be onboot=no on RHEVM cfg file.

In the bootstrap process the management bridge parameters are copied from the nic the bridge is connected to (in this case the ONBOOT=no).

In addition the bootstrap is adding a few parameter of it own (ONBOOT=yes).

We are missing the logic to skip copying the ONBOOT property from the bridge.

I believe that the root cause for this is that ONBOOT is passed as-is to the internal functions, and not converted to lowercase - just as in bug 847733.
Thus, I think that this should be solved by

http://gerrit.ovirt.org/7390

*** This bug has been marked as a duplicate of bug 847733 ***