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 594776 [details]
vdsm.log

Description of problem:

Open SetupNetwors > change RHEVM IP to non reachable > apply.
Host stays unreachable until VDSM service is restarted ()

Version-Release number of selected component (if applicable):
vdsm-4.10.0-0.94.git156c30a.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Open SetupNetworks and change RHEVM IP to non reachable
2.Apply

Actual results:
VDSM is unreachable 

Expected results:
After check connectivity time out host should perform rollback of network configuration and became reachable.

After press apply I can see in the vdsm.log that VDSM service restarted - Run and protect: prepareForShutdown
When restarting VDSM service using: /etc/init.d/vdsmd restart then VDSM performe roolback of network configuration
reproduce on HSM host and on SPM host.

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

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

When validating the fix for this bug please also confirm the use case fomr BZ 842662 is also working -

Steps to Reproduce:
1. Create VM Network and attach it to the host's NIC
2. Change the IP of the Network to the static (in the same subnet as rhevm Manager) and press ok button
3. Wait for about 2 minutes(the rolling back time)

http://gerrit.ovirt.org/#/c/6991/

Verified on vdsm-4.9.6-27.0.el6_3.x86_64

(In reply to comment #9)
> Verified on vdsm-4.9.6-27.0.el6_3.x86_64

* vdsm-4.9.6-29.0.el6_3.x86_64

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.

http://rhn.redhat.com/errata/RHSA-2012-1508.html