Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1186644[details]
kickstart file
Description of problem:
Add bond1 on two NICs, after delete bond1, the two slave NICs can not be up or enable, there is error report:
Unexpected error
Master connection not found or invalid
Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.0-20160727.1.x86_64
imgbased-0.7.3-0.1.el7ev.noarch
cockpit-0.114-2.el7.x86_64
cockpit-ovirt-dashboard-0.10.6-1.3.3.el7ev.noarch
libvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64
glib-networking-2.42.0-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Install redhat-virtualization-host-4.0-20160727.1.x86_64 with kickstart file in attachment
2. Login RHVH via cockpit, change to Networking page
3. Add bond1 (Active-backup mode) on two NICs p3p1 and p4p1
4. Delete bond1
5. Enter p3p1 or p4p1, click "on"
Actual results:
1. After step5, enable p3p1 and p4p1 failed, there is error report:
Unexpected error
Master connection not found or invalid
Expected results:
1. After step5, should enable p3p1 and p4p1 successful without error.
Additional info:
(In reply to Dominik Perpeet from comment #7)
> What state are the two NICs in before a bond is added? I can't reproduce the
> issue here.
The two NICs are up before a bond is added
> Does the process work if you run all the steps via nmcli?
If I write ifcfg file via nmcli same as cockpit produced, also encounter this issue.
But after I remove "MASTER=XXXXXX" from ifcfg-p3p1, "ifup p3p1" works well, so I guess the issue maybe the "MASTER=XXXXXX" in NICs ifcfg file.
Created attachment 1186644 [details] kickstart file Description of problem: Add bond1 on two NICs, after delete bond1, the two slave NICs can not be up or enable, there is error report: Unexpected error Master connection not found or invalid Version-Release number of selected component (if applicable): redhat-virtualization-host-4.0-20160727.1.x86_64 imgbased-0.7.3-0.1.el7ev.noarch cockpit-0.114-2.el7.x86_64 cockpit-ovirt-dashboard-0.10.6-1.3.3.el7ev.noarch libvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64 glib-networking-2.42.0-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install redhat-virtualization-host-4.0-20160727.1.x86_64 with kickstart file in attachment 2. Login RHVH via cockpit, change to Networking page 3. Add bond1 (Active-backup mode) on two NICs p3p1 and p4p1 4. Delete bond1 5. Enter p3p1 or p4p1, click "on" Actual results: 1. After step5, enable p3p1 and p4p1 failed, there is error report: Unexpected error Master connection not found or invalid Expected results: 1. After step5, should enable p3p1 and p4p1 successful without error. Additional info: