Bug 1400792 - Setup network with vlan over bond via Cockpit failed.
Summary: Setup network with vlan over bond via Cockpit failed.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.2
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: pre-dev-freeze
: ---
Assignee: Dominik Perpeet
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-02 05:50 UTC by Yihui Zhao
Modified: 2016-12-07 09:42 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-07 08:23:24 UTC
Target Upstream Version:


Attachments (Terms of Use)
sosreport,/var/log/*,network-scripts/* (8.41 MB, application/x-bzip)
2016-12-02 05:50 UTC, Yihui Zhao
no flags Details
NIC_info (22.96 KB, image/png)
2016-12-02 05:51 UTC, Yihui Zhao
no flags Details
Screenshot_static_bond_vlan.png (118.77 KB, image/png)
2016-12-02 06:15 UTC, Huijuan Zhao
no flags Details

Description Yihui Zhao 2016-12-02 05:50:07 UTC
Created attachment 1227154 [details]
sosreport,/var/log/*,network-scripts/*

Description of problem:
When set network with vlan over bond, that's failed.

Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.0-20161130.0
imgbased-0.8.10-0.1.el7ev.noarch
cockpit-ws-122-3.el7.x86_64
cockpit-ovirt-dashboard-0.10.6-1.4.2.el7ev.noarch

How reproducible:
100%


Steps to Reproduce:
1. Install RHVH 
2. Login cockpit
3. Set network with vlan over bond (such as bond0.50),
   Click "on" to enable the network bond0.50


Actual results:
After step3, enable the vlan over bond network(bond0.50) failed. Sometimes can enable it, but can not get IP from dhcp server.

Expected results:
After step3, should enable the vlan over bond network(bond0.50) successful, and can get IP from dhcp server.

Additional info:

I try to use the command nmtui to setup vlan over bond,that's also failed.

Comment 1 Red Hat Bugzilla Rules Engine 2016-12-02 05:50:20 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Yihui Zhao 2016-12-02 05:51:50 UTC
Created attachment 1227155 [details]
NIC_info

Comment 3 Huijuan Zhao 2016-12-02 06:14:53 UTC
Configure static IP for vlan over bond network (such as bond0.50), also encounter this issue.

We have to enable slave NICs, bond0, and bond0.50 at the same time, then the static IP of bond0.50 is effective. But bond0 is "Configuring IP", it will fail in several minutes, then the bond0.50 changes to Inactive.

See attachment "Screenshot_static_bond_vlan.png"

Comment 4 Huijuan Zhao 2016-12-02 06:15:32 UTC
Created attachment 1227156 [details]
Screenshot_static_bond_vlan.png

Comment 6 Marius Vollmer 2016-12-05 14:51:07 UTC
So the problem is that "bond0" doesn't stay up?  Does it work to set IPv4 to "disabled" and IPv6 to "ignored"?

Comment 7 Yihui Zhao 2016-12-06 04:18:31 UTC
(In reply to Marius Vollmer from comment #6)
> So the problem is that "bond0" doesn't stay up?  Does it work to set IPv4 to
> "disabled" and IPv6 to "ignored"?

Hi,Marius
   Thank you for your advice.It work to set IPv4 to "disabled" and IPv6 to "ignored" with bond0.
   And i have a problem about it.Why need to set IPv4 to "disabled" and IPv6 to "ignored" with bond0? Does it has some rules about network with cockpit?


Thanks,
Yihui

Comment 8 Marius Vollmer 2016-12-07 08:23:24 UTC
(In reply to Yihui Zhao from comment #7)
> (In reply to Marius Vollmer from comment #6)
> > So the problem is that "bond0" doesn't stay up?  Does it work to set IPv4 to
> > "disabled" and IPv6 to "ignored"?
> 
> Hi,Marius
>    Thank you for your advice.It work to set IPv4 to "disabled" and IPv6 to
> "ignored" with bond0.

Great!

>    And i have a problem about it.Why need to set IPv4 to "disabled" and IPv6
> to "ignored" with bond0? Does it has some rules about network with cockpit?

This is really a question for the NetworkManager people.

How would you configure the VLAN using nmcli?

My theory is that NM brings bond0 down after a while when it can get a IP address for it.  When bond0 is down, any VLAN on top of it will stop working.

If you tell NM that you don't want any IP address for bond0, then it will stay up without one.


A possible improvement might be to change NM so that it brings the parent interface of a VLAN up and down more 'intelligently'.  It'd be up if any VLAN is up or if it is directly activated, and down otherwise.


I close this as NOTABUG since I think this works as designed.  Please reopen if you think we need to improve the user experience here.

Comment 9 Huijuan Zhao 2016-12-07 09:42:28 UTC
According to Comment6, Comment7 and Comment8,  I think we'd better add these detail steps of setting vlan over bond to Doc, in order to prevent customers are confused.


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