Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Previously, configuring a network on a specific interface with the boot protocol "DHCP" caused the underlying interface to be configured with the boot protocol "DHCP". This meant that when (for instance) you moved the DHCP-configured management network from one interface to another, the first interface would remain configured with DHCP. A patch to VDSM makes sure that "Boot proto=dchp" no longer appears in the ifcfg file when the DHCP-configured management network is moved from one interface to another. In those cases, the configured management network has no set boot protocol.
Created attachment 612486[details]
vdsm log
Description of problem:
If you configure network on specific interface with Boot protocol DHCP, it will automatically configure the underlying interface with the Boot protocol DHCP.
For example when moving management network, configured with dhcp from one interface to another will leave the first interface with configuration of dhcp
How reproducible:
Always
Steps to Reproduce:
1. Configure bridged network on host interface with Boot protocol DHCP
2. Run ifcfg-ethx (x is the specific interface on which you configured network)
3.
Actual results:
interface x got Boot proto=dhcp in ifcfg file
Expected results:
Boot proto should be configured an None or should be missing from ifcfg file
Additional info:
Comment 2Antoni Segura Puimedon
2012-09-18 15:57:15 UTC
I would need to know:
1. Which interface (oVirt Web/VdsCli) did you use for configuring the the bridged network.
2. Which is this command ifcfg-ethx where x is the interface previously configured. Do you mean to ifup it?
(In reply to comment #2)
> I would need to know:
>
> 1. Which interface (oVirt Web/VdsCli) did you use for configuring the the
> bridged network.
> 2. Which is this command ifcfg-ethx where x is the interface previously
> configured. Do you mean to ifup it?
1) I was using the WEBADMIN to create Bridged Network and add it to the interface on the host
2) I mean that if you run cat /etc/sysconfig/network-scripts/ifcfg-ethx command to see the configuration on the interface you'll get it configured with DHCP configuration instead of None
Comment 4Antoni Segura Puimedon
2012-09-19 15:17:36 UTC
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.
http://rhn.redhat.com/errata/RHSA-2012-1508.html
Created attachment 612486 [details] vdsm log Description of problem: If you configure network on specific interface with Boot protocol DHCP, it will automatically configure the underlying interface with the Boot protocol DHCP. For example when moving management network, configured with dhcp from one interface to another will leave the first interface with configuration of dhcp How reproducible: Always Steps to Reproduce: 1. Configure bridged network on host interface with Boot protocol DHCP 2. Run ifcfg-ethx (x is the specific interface on which you configured network) 3. Actual results: interface x got Boot proto=dhcp in ifcfg file Expected results: Boot proto should be configured an None or should be missing from ifcfg file Additional info: