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.

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:

Please try to reproduce this on RHEL. You will need to enable RHEL extras to retrieve cockpit.

Since this issue is move to cockpit part, I would like to wait cockpit guys to debug this issue.

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.

> 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.

> 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?

This bug will be fixed in cockpit 0.113

https://github.com/cockpit-project/cockpit/pull/4640

Reassigning to Dominik for inclusion in next RHEL release of Cockpit.

Cockpit integration test here: https://github.com/cockpit-project/cockpit/pull/4640/files#diff-b7a8b7371f34d5364bc2f57a5d9c812aR224

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