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.

Bug 953123

Summary: can't set Cloned MAC Address for VLAN
Product: Red Hat Enterprise Linux 6 Reporter: Tomas Pelka <tpelka>
Component: NetworkManagerAssignee: Jirka Klimes <jklimes>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4CC: dcbw, jklimes, rkhan
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 21:50:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
[PATCH] editor: correcly save VLAN MAC address and MTU none

Description Tomas Pelka 2013-04-17 12:12:59 UTC
Description of problem:
Not able to set Cloned MAC Address for VLAN connection, filed goes empty after apply and reopen in nm-connection-manager. The Cloned MAC Address value does not write to ifcfg file as well. 

Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-43.el6

How reproducible:
100%

Steps to Reproduce:
1. Create VLAN profile
2. try to set up Cloned MAC Address
3.
  
Actual results:
MAC will not save and change

Expected results:
should be saved and changed

Additional info:
cat /etc/sysconfig/network-scripts/ifcfg-VLAN_connection_1 
VLAN=yes
TYPE=Vlan
DEVICE=vlan100
PHYSDEV=eth1
VLAN_ID=100
REORDER_HDR=0
BOOTPROTO=none
IPADDR=192.168.122.177
PREFIX=24
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="VLAN connection 1"
UUID=87fc8fac-49a3-49f2-8fec-0c2820cabe1a
ONBOOT=yes

Comment 1 Jirka Klimes 2013-07-11 14:46:13 UTC
This is the problem in nm-connection-editor.
The "parent interface" combo box doesn't set active item when initialized. It causes Cloned MAC and MTU not being saved when "Parent interface" was not re-selected (touched).

Comment 2 Jirka Klimes 2013-07-11 14:50:48 UTC
Created attachment 772263 [details]
[PATCH] editor: correcly save VLAN MAC address and MTU

This patch for RHEL6 fixes the issue. It is based on an upstream commit, however the commit had to be edited a bit for RHEL 6.5.

Comment 7 errata-xmlrpc 2013-11-21 21:50:08 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/RHBA-2013-1670.html