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 1112674 - It is not possible to create VLAN on top of bond interface in the NM GUI
Summary: It is not possible to create VLAN on top of bond interface in the NM GUI
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.1
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Radek Vykydal
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 1045203 1112672 1255735
Blocks: 1112660 1205794
TreeView+ depends on / blocked
 
Reported: 2014-06-24 13:04 UTC by Ladislav Jozsa
Modified: 2016-07-11 09:38 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of: 1112672
Environment:
Last Closed: 2016-06-30 18:47:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ladislav Jozsa 2014-06-24 13:04:07 UTC 
+++ This bug was initially created as a clone of Bug #1112672 +++

Description of problem:
In Network Manager GUI, when setting up a new VLAN it is not possible to select bond interface as a parent one. It is not in the list.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.1-13.git20140326.4dba720.el7
RHEL-7.0 release

How reproducible:
always

Steps to Reproduce:
1. In the NM GUI create bond interface
2. Add some slaves
3. Select 802.3ad mode
4. Add VLAN interface
5. Try to find bond parent

Actual results:
Bond parent interface not found in the list.

Expected results:
It should be possible to configure VLAN on top of the bond

Additional info:
Comment 1 Radek Vykydal 2014-06-24 13:06:02 UTC 
We should check that when support is added to NM, anaconda doesn't stumble upon configuration created in Connection Editor.
Comment 4 Radek Vykydal 2015-08-18 09:16:41 UTC 
I was testing creating vlan over bond in Anaconda on bare metal and hit this issue:

1) create bond over single device (plugged into vlan) in Anaconda GUI ([+] button) - works ok, bond device is created

2) create vlan over the bond device in Anaconda GUI ([+] button) does not work - the bond connection is missing from the list available parent devices in "Editing VLAN connection 1" nm-c-e dialog (there are only physical devices, no 'via' connections). We invoke nm-c-e by running:

nm-connection-editor --create --type=vlan

3) If I switch to terminal in installer and run nm-c-e

export DISPLAY=:1
nm-connection-editor

and Add vlan connection, there is "bond0 (via "Bond connection 1")" item available for choosing.
Creating the vlan this way works, installation finishes successfully, vlan is up after reboot.

If I try the same steps in VM, but with a device (step 1) without any actual vlan present, step 2) works - "bond0 (via "Bond connection 1")" is available for selection as parent.
Comment 5 Radek Vykydal 2015-08-18 09:19:02 UTC 
Lubomir, any idea why we are hitting the issue in comment #4?
Comment 6 Lubomir Rintel 2015-08-18 14:01:22 UTC 
(In reply to Radek Vykydal from comment #5)
> Lubomir, any idea why we are hitting the issue in comment #4?

Yes. I believe only the bridges whose devices actually exist in the system are considered. If you create the bond with "connection.autoconnect = yes" property, then the device will be available immediately.

It shouldn't really do any harm autoconnecting the bond -- it will just create the device and you can reactivate it again in case you do changes to the configuration. Is that a plausible solution for you?
Comment 7 Radek Vykydal 2015-08-18 14:29:27 UTC 
We are setting connection.autoconnect-slaves=1 in global NM config for anaconda and bond device is actually created and configured in both cases before we are trying to add vlan connection (note that they are seen if we try to add vlan connection in the way 3).

For some reason, when populating parents list in case 2) by calling nm-c-e with --create --type=vlan options the connections (ie bond) are not listed whereas when adding it from nm-connection-editor they are. But what seems really strange to me is that in VM, the connections are listed even in case 2).
Comment 8 Radek Vykydal 2015-08-21 12:30:39 UTC 
(In reply to Radek Vykydal from comment #5)
> Lubomir, any idea why we are hitting the issue in comment #4?

I created bug 1255735 for the issue.
Comment 10 Radek Vykydal 2016-01-25 15:16:32 UTC 
(In reply to Radek Vykydal from comment #8)
> (In reply to Radek Vykydal from comment #5)
> > Lubomir, any idea why we are hitting the issue in comment #4?
> 
> I created bug 1255735 for the issue.

This seems to be fixed in 7.2.

I was able to create vlan with static IP on top of bond device with ipv4 configured with dhcp.

If I create bond device with ipv4 configuration Disabled, keeping ipv6 set to Automatic, nm-c-e exits with status 11 when trying to create vlan with bond parent device. Trying to run it as in comment #4 3), I can see some error messages (and nm-c-e segfaults.
If I change ipv6 config of the bond connection to Ignore, I can create vlan on top of the bond connection successfuly.
Comment 11 Jiri Kortus 2016-02-05 14:12:49 UTC 
I was not able to reproduce this bug on RHEL-7.2 using instructions in bug description, so it seems like this issue has been fixed -- after creating the bond interface, I can see it in the interfaces list when creating a new VLAN device.

However when I turn the bond device off, it is not available in the devices list for VLAN creation anymore. I'm not sure if this is correct, one one hand it is clear that the bond device must exist prior to creating a VLAN device, on the other hand it should be possible to create a VLAN on top of a bond device without creating/activating it during installation when it is not needed immediately, so maybe this should be fixed.

Radek, what is your opinion on this matter?
Comment 12 Radek Vykydal 2016-02-19 14:53:10 UTC 
IMO this is something out of scope of this BZ which was opened to check that functionality added to nm-c-e works also in installer. And I think nm-c-e on installed system behaves the same way (requires existing bond device to be able to configure vlan on top of it). As for creating connections / configurations we are limited to what nm-c-e allows, in Anaconda.

I am not sure how well kickstart works in this respect (vlan over bond) but maybe this would be the way to create connections without activating them in installer. Or using nmcli in tty2 shell.
Comment 13 Radek Vykydal 2016-06-21 08:51:59 UTC 
Based on comment #10, comment #11, comment #12 I propose to close this bug as CURRENTRELEASE.
Comment 14 Samantha N. Bueno 2016-06-30 18:47:49 UTC 
(In reply to Radek Vykydal from comment #13)
> Based on comment #10, comment #11, comment #12 I propose to close this bug
> as CURRENTRELEASE.

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