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 807544

Summary: Kernel: VLAN interface can't change MAC addrs when the interface below it changed
Product: Red Hat Enterprise Linux 6 Reporter: Liang Zheng <lzheng>
Component: kernelAssignee: Weiping Pan <wpan>
Status: CLOSED NOTABUG QA Contact: Network QE <network-qe>
Severity: high Docs Contact:
Priority: high    
Version: 6.2CC: kzhang, rkhan, ruyang, wpan
Target Milestone: beta   
Target Release: 6.4   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-22 07:29:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 846704    

Description Liang Zheng 2012-03-28 06:07:47 UTC
Description of problem:
When QE testing bz800231, add a vlan on top of the bond, set fail_over_mac=active,change the active slave, the bond0 and the slaves are all changed the MAC addr except the VLAN interface.

Version-Release number of selected component (if applicable):
kernel-2.6.32.257.el6

How reproducible:
100%

Steps to Reproduce:
1.vconfig add eth0 3
2.ifconfig eth0.3 up
3.ifconfig eth0 hw ether 22:22:22:22:22:22
4.check the MAC addr of eth0.3
ifconfig eth0.3
  
Actual results:
the vlan interface doesnot change the MAC addr.

Expected results:


Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=800231

Comment 1 Weiping Pan 2012-04-11 07:01:32 UTC
Hi, Liang Zheng,

IMHO, this is not a bug. 
I think eth0.3 has a loose relationship with eth0, they can have different settings.
It is not like bonding, that bonding device has a close relationship with its slaves.

P.S.
The behaviour is the same in upstream.

thanks
Weiping Pan

Comment 3 Rashid Khan 2012-04-30 21:06:41 UTC
Hi, Liang Zheng,
Can you please reply to Weiping's comments below. I tend to agree with him on his assessment. Please let us know if you think otherwise. 
Thanks

Comment 4 Liang Zheng 2012-05-02 03:27:29 UTC
(In reply to comment #3)
> Hi, Liang Zheng,
> Can you please reply to Weiping's comments below. I tend to agree with him on
> his assessment. Please let us know if you think otherwise. 
> Thanks
I have discussed with Weiping before,but I donet agree him.
There is some discussion on upstream, you can refer it :
http://patchwork.ozlabs.org/patch/153551/

Comment 6 Weiping Pan 2012-05-04 02:02:02 UTC
The suggested patch has not been accepted in upstream.
I will pay attention to the discussion and then decide whether it is a bug and how to handle it.

Comment 10 Weiping Pan 2013-09-22 07:29:37 UTC
Hi,

From the comments in [1], the maintainers do not think this is a bug,
so I will close it.

[1] http://patchwork.ozlabs.org/patch/118525/

thanks
Weiping Pan