Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1329956 - vlan can not click to on after created through cockpit and the original nic still can be configured
vlan can not click to on after created through cockpit and the original nic s...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit (Show other bugs)
7.2
Unspecified Unspecified
urgent Severity high
: pre-dev-freeze
: 7.2
Assigned To: Dominik Perpeet
Jan Ščotka
: Extras
Depends On:
Blocks: ovirt-node-ng-platform
  Show dependency treegraph
 
Reported: 2016-04-25 04:10 EDT by wanghui
Modified: 2016-08-16 22:32 EDT (History)
12 users (show)

See Also:
Fixed In Version: cockpit-0.114-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-08-04 09:47:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Node
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1442 normal SHIPPED_LIVE cockpit bug fix and enhancement update 2016-08-04 13:45:50 EDT

  None (edit)
Description wanghui 2016-04-25 04:10:45 EDT
Description of problem:
vlan can not click to on after created through cockpit and the original nic still can be configured

Version-Release number of selected component (if applicable):
ovirt-node-ng-installer-ovirt-3.6-2016042323.iso 
cockpit-0.103-1.el7.centos.x86_64
cockpit-ovirt-0.5.1-0.0.master.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1. Anaconda install NGN 4.0.
2. Start cockpit service.
3. Add a vlan in p3p1
4. Check "On" button for p3p1.20 in cockpit.
5. Check the 'General' field to enable connect automatically.
6. Check the networking field.

Actual results:
1. After step4, the 'On' button can not be checked.
2. After step5, miss save button to save the changes in "General" field. 
3. After create vlan, p3p1 still in interfaces list and can be configured also.

Expected results:
1. After step4, the "on" button can be checked.
2. After step5, the changes can be saved in "General" field.
3. p3p1 can not be configured.

Additional info:
Comment 1 Fabian Deutsch 2016-04-25 04:25:23 EDT
Please try to reproduce this on RHEL. You will need to enable RHEL extras to retrieve cockpit.
Comment 2 wanghui 2016-04-26 05:52:48 EDT
Since this issue is move to cockpit part, I would like to wait cockpit guys to debug this issue.
Comment 4 Marius Vollmer 2016-06-27 09:30:24 EDT
https://github.com/cockpit-project/cockpit/pull/4640

This is fixed by the same fix as bug 1329954.

VLAN devices also had a disabled on/off switch in their off state because the actual kernel interface does not exist then.
Comment 5 Marius Vollmer 2016-06-28 08:35:21 EDT
> After step5, miss save button to save the changes in "General" field. 

There is no need to save this explicitly, it will be saved when you change it.
Comment 6 Marius Vollmer 2016-06-28 08:36:50 EDT
> After create vlan, p3p1 still in interfaces list and can be configured also.

Could you file a new bug for this separate issue?

Could you also explain why the parent of a vlan should not be configured individually?
Comment 8 Stef Walter 2016-07-05 15:19:19 EDT
This bug will be fixed in cockpit 0.113

https://github.com/cockpit-project/cockpit/pull/4640
Comment 9 Stef Walter 2016-07-05 15:19:56 EDT
Reassigning to Dominik for inclusion in next RHEL release of Cockpit.
Comment 14 errata-xmlrpc 2016-08-04 09:47:01 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-1442.html

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