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:
Moving the management network to an unconnected nic when check-connectivity is checked causes losing connection from the host to the engine.


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
Preconditions-
1. The host have at least two nics.
2. One of the nics doesn't have connectivity to the engine.

Steps-
1. Open the SetupNetworks form (Hosts->Network interfaces)
2. Drag the management network to the nic that doesn't have connectivity to the engine.
3. Make sure that the "Verify connectivity between Host and ovirt-engine" (check connectivity) is checked.
4. Make sure "Save Network configuraion" is unchecked.
5. Press ok

  
Actual results:
1. The connectivity from the manager to the host is lost
2. The host keeps the new configuration
3. service vdsmd restart, returns the host to the last saved configuration and the connectivity to the engine returns. 

Expected results:
1. The host rollbacks the change after timeout (60000 ms) and doesn't lose connectivity to the engine.


Additional info:

Created attachment 593254 [details]
vdsm log

*** This bug has been marked as a duplicate of bug 835900 ***