Created attachment 1536895 [details]
Gateway address is unreachable
Description of problem:
Gateway address unreachable error displays on VM settings during hosted engine deployment.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Clean install redhat-virtualization-host-4.3-20190220.2.el7_6.x86_64.liveimg.squashfs
2. Login to cockpit with root account
3. Go to hosted engine page, click "Start" under "Hosted Engine"
4. Check the VM setting in "Hosted Engine Deployment"
5. Click "Advanced"
After step 4: error message "Please correct errors before moving to the next step" displays.
After step 5: error message "Unable to ping address, Please enter a pingable address" displays below "Gateway Address"
No error message displays in VM settings during hosted engine deployment.
There is not this issue with build rhvh-126.96.36.199-0.20190129.0. So it is a regression bug.
Created attachment 1536896 [details]
Created attachment 1536912 [details]
ipv6 environment screenshot
The issue also exists with IPV6 environment. The screenshot is attached.
According to comment 0
No error message displays in VM settings during hosted engine deployment, and Hosted engine deploys successfully.
bug is fixed, change status to "VERIFIED"
Test with rhvh-188.8.131.52-0.20190225.0, hosted hosted deployment on only static ipv6 environment, the bug can be reproduced.
Change the status to "ASSIGNED"
Created attachment 1538844 [details]
ipv6 log files
I don't understand, can you please explain what has failed ?
Does the ipv6 validation on the gateway on the cockpit-ovirt's he-wizard failed ?
or the deployment on ipv6 has failed ?
Created attachment 1538909 [details]
Created attachment 1538910 [details]
I'm not able to reproduce it on my side or at least I didn't really understood where the issue is: see attached screenshots.
According to comment #3 and comment #10, changed the status to 'VERIFIED'. For any other new issues, let's report new bug for trace.Thanks.
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.
Since the problem described in this bug report should be
resolved in oVirt 4.3.1 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.