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 846016 - [vdsm] [Setup Host Networks] After changing nics for network, both ifcfg files are left with BRIDGE=<networkName>
Summary: [vdsm] [Setup Host Networks] After changing nics for network, both ifcfg file...
Keywords:
Status: CLOSED DUPLICATE of bug 845193
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-06 14:01 UTC by Muli Salem
Modified: 2012-08-07 06:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 06:37:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Muli Salem 2012-08-06 14:01:18 UTC
Description of problem:
When changing interfaces for a network, ifcfg file in old interface is left with BRIDGE=<networkName>.

Version-Release number of selected component (if applicable):
4.10.0-0.254

How reproducible:
always

Steps to Reproduce:
From WebAdmin:
1. Add host with more than 1 NIC to setup.
2. Add a network which is defined as a vm network.
3. In Setup Host Networks, assign this network to a nic and click OK.
4. In Setup Host Networks, drag the network to another nic and click OK.
  
Actual results:
Both /etc/sysconfig/network-scripts/ifcfg-<originalNicName>
and /etc/sysconfig/network-scripts/ifcfg-<newNicName>
have BRIDGE=<networkName>

Expected results:
The line should be removed from /etc/sysconfig/network-scripts/ifcfg-<originalNicName>

Additional info:
Also need to make sure the bridge that is up is not connected to both nics.

Comment 1 lpeer 2012-08-07 06:37:19 UTC

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


Note You need to log in before you can comment on or make changes to this bug.