Bug 1112674
| Summary: | It is not possible to create VLAN on top of bond interface in the NM GUI | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ladislav Jozsa <ljozsa> |
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | CC: | dcbw, jikortus, jkonecny, jstodola, lrintel, rbarry, rvykydal, sbueno, ycui |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | 1112672 | Environment: | |
| Last Closed: | 2016-06-30 18:47:49 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: | |||
| Bug Depends On: | 1045203, 1112672, 1255735 | ||
| Bug Blocks: | 1112660, 1205794 | ||
|
Description
Ladislav Jozsa
2014-06-24 13:04:07 UTC
We should check that when support is added to NM, anaconda doesn't stumble upon configuration created in Connection Editor. 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. Lubomir, any idea why we are hitting the issue in comment #4? (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? 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). (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. (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. 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? 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. Based on comment #10, comment #11, comment #12 I propose to close this bug as CURRENTRELEASE. (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. |