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.
Bug 857112 - 3.1 - Configuration of network with Boot protocol = DHCP on specific interface will configure that interface with Boot protocl DHCP as well
Summary: 3.1 - Configuration of network with Boot protocol = DHCP on specific interfac...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Igor Lvovsky
QA Contact: GenadiC
URL:
Whiteboard: network
: 856710 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-13 15:24 UTC by GenadiC
Modified: 2022-07-09 05:39 UTC (History)
10 users (show)

Fixed In Version: vdsm-4.9.6-35.0
Doc Type: Bug Fix
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:11:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
vdsm log (12.78 MB, application/octet-stream)
2012-09-13 15:24 UTC, GenadiC 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1508 0 normal SHIPPED_LIVE Important: rhev-3.1.0 vdsm security, bug fix, and enhancement update 2012-12-04 23:48:05 UTC

Description GenadiC 2012-09-13 15:24:11 UTC 
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 2 Antoni 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?
Comment 3 GenadiC 2012-09-19 07:17:18 UTC 
(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 4 Antoni Segura Puimedon 2012-09-19 15:17:36 UTC 
Submitted a patch:
http://gerrit.ovirt.org/#/c/8058
Comment 6 Dan Kenigsberg 2012-09-23 14:48:51 UTC 
*** Bug 856710 has been marked as a duplicate of this bug. ***
Comment 7 GenadiC 2012-09-24 07:02:19 UTC 
(In reply to comment #6)
> *** Bug 856710 has been marked as a duplicate of this bug. ***

When verifying this bug, we should verify the https://bugzilla.redhat.com/show_bug.cgi?id=856710 as well to test that the check connectivity is fixed as well
Comment 8 GenadiC 2012-09-27 15:16:29 UTC 
Verified in SI19
Comment 11 errata-xmlrpc 2012-12-04 19:11:47 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
Note You need to log in before you can comment on or make changes to this bug.