Description of problem: Version-Release number of selected component (if applicable): rhev-hypervisor7-7.2-20151117.0.iso ovirt-node-3.2.3-28.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Install rhev-hypervisor7-7.2-20151117 and configure network with DHCP mode. 2. Register to RHEV-M3.5.6 3. Reboot RHEV-H7.2 Actual results: After step3, RHEV-H7.2 cannot be up on RHEV-M3.5.6 Expected results: After step3, RHEV-H7.2 can be up on RHEV-M3.5.6 Additional info: The RHEV-H can be up after register to RHEV-3.5.6, but if you reboot RHEV-H, the RHEV-H status is always down on RHEV-M even the RHEV-H already boot up successful.
Created attachment 1095981 [details] /var/log and sosreport
This did not happen on rhev-hypervisor7-7.2-20151112.0, so we marked as regression.
Check with the build rhev-hypervisor7-7.2-20151118.0.iso. Version: rhev-hypervisor7-7.2-20151118.0.iso ovirt-node-3.2.3-29.el7.noarch Steps: 1. Install rhev-hypervisor7-7.2-20151118 and configure network with DHCP mode. 2. Register to RHEV-M3.5.6, reboot RHEV-H several times. Result: After step2, RHEV-H7.2 can be up on RHEV-M3.5.6 This bug has been fixed, so change the status to VERIFIED
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-2015-2526.html
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days