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 1366298 - Prevent creation of a bond with vlan slaves
Summary: Prevent creation of a bond with vlan slaves
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-11 14:36 UTC by Fabian Deutsch
Modified: 2016-10-06 09:36 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-06 09:36:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Fabian Deutsch 2016-08-11 14:36:24 UTC 
Description of problem:
It is currently possible to create a bond which has vlan slaves,
But this is not working.

network manager should prevent this setup.

See:
https://bugzilla.redhat.com/show_bug.cgi?id=1356635
https://access.redhat.com/solutions/483803


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


How reproducible:


Steps to Reproduce:
1. Create bond with vlan slaves
2. Try to get an IP over DHCP
3.

Actual results:
After 2: Fails to retrieve IP.

Expected results:


Additional info:
Comment 1 Fabian Deutsch 2016-08-11 14:37:56 UTC 
We've seen this a couple of times in RHEV, up to now we prevented this in high-level tools, but it should actually be prevented by NetworkManager to create unsupported/non-working setups.
Comment 3 Fabian Deutsch 2016-08-12 18:30:21 UTC 
I do see there are combinations that do work - so we might not want to prevent this setp completely.

OTOH there are combinations which don't work, and we should prevent that a user is setting them up.

As said, we do see users trying this in the real world, and they do run into issues.

We could block it on the high-level, but I'd rather like to see it fixed at the root - so either NM/legacy initscripts or even in kernel land.
Comment 4 Beniamino Galvani 2016-09-01 14:18:06 UTC 
(In reply to Fabian Deutsch from comment #3)
> I do see there are combinations that do work - so we might not want to
> prevent this setp completely.
>
> OTOH there are combinations which don't work, and we should prevent that a
> user is setting them up.
>
> As said, we do see users trying this in the real world, and they do run into
> issues.
>
> We could block it on the high-level, but I'd rather like to see it fixed at
> the root - so either NM/legacy initscripts or even in kernel land.

After a bit of research, I don't think there aren't any technical
reasons why a bond over VLANs should not work. We don't support this
configuration in RHEL [1], and instead favor the use of VLAN over
bond. Nevertheless the setup is legitimate and NetworkManager should
not prevent it.

Do you have more details about which configurations have caused
issues?

[1] https://bugzilla.redhat.com/show_bug.cgi?id=952719
Comment 5 Fabian Deutsch 2016-09-01 15:44:26 UTC 
Well, in bug 1356635 we see that a bond over VLANs leads to issues.

In our experience this setup is _never_ stable (having a bond over vlan devices [slaves]).

Dan or Ying might recall more bugs.
Comment 6 Dan Kenigsberg 2016-09-13 06:15:09 UTC 
I'm afraid I do not recall. But unrelated to this, oVirt does not support (nor even recognizes) bond-over-vlan, and I'm not aware of anybody asking us to add this. For our use case, it would be cool if Cockpit had a way to block it.
Comment 7 Fabian Deutsch 2016-09-14 09:48:49 UTC 
Okay, so let's see if Ying has a good example for failures.

Otherwise it seems that we don't agree to prevent this setups, and thus we can then close this bug.
Comment 8 Ying Cui 2016-09-18 10:00:40 UTC 
Huijuan, See this bug, could you provide our thoughts for comment 5 and comment 7 based on our testing?
Comment 9 Huijuan Zhao 2016-09-20 02:33:48 UTC 
(In reply to Fabian Deutsch from comment #5)
> Well, in bug 1356635 we see that a bond over VLANs leads to issues.
> 
> In our experience this setup is _never_ stable (having a bond over vlan
> devices [slaves]).
> 
> Dan or Ying might recall more bugs.

In my test, can not setup bond over VLANs via Cockpit, in other word, it is blocked by Cockpit.
Comment 10 Beniamino Galvani 2016-10-06 09:36:58 UTC 
Blocking the creation of unwanted configurations from upper layers, as cockpit does, makes more sense to me. I'm closing this for now, please reopen if there are any updates or more specific requests.
Note You need to log in before you can comment on or make changes to this bug.