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:
When creating VM with URL and change the source of network interface to another network(delete the network interface whose source is 'default'), then install the VM. After a few moments, the installation has been started, the source of network interface is changed to default

Version-Release number of selected component (if applicable):
cockpit-machines-208-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create a VM with URL and uncheck 'Immediately Start VM'
2. Delete the network interface whose source is 'default', then add a new network interface which is not 'default'
3. Click 'Install' button of the VM

Actual results:
The source of network interface is changed to 'default'.

Expected results:
The source of network interface should be unchanged

Additional info:

*** Bug 1780450 has been marked as a duplicate of this bug. ***

This was fixed in https://github.com/cockpit-project/cockpit/pull/13312 and released in 210.

Verified with packages:
cockpit-machines-210-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64

Steps:
1. Prepare 2 networks on Networks page.
2. Create a VM with URL and uncheck 'Immediately Start VM'
3. Delete the network interface whose source is 'default', then add a new network interface which is not 'default'
4. Click 'Install' button of the VM

The source of network interface is not changed to default.
So verified.

*** Bug 1778071 has been marked as a duplicate of this bug. ***

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://access.redhat.com/errata/RHBA-2020:1639