Bug 1679412 - Gateway address unreachable error displays on VM settings during hosted engine deployment.
Summary: Gateway address unreachable error displays on VM settings during hosted engin...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Hosted Engine
Version: 0.12.2
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-4.3.1
: ---
Assignee: Ido Rosenzwig
QA Contact: Wei Wang
URL:
Whiteboard:
Depends On:
Blocks: 1670492
TreeView+ depends on / blocked
 
Reported: 2019-02-21 06:14 UTC by Wei Wang
Modified: 2019-03-01 10:20 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-01 10:20:18 UTC
oVirt Team: Node
Embargoed:
sbonazzo: ovirt-4.3?
mtessun: blocker+
mtessun: planning_ack+
sbonazzo: devel_ack+
cshao: testing_ack+


Attachments (Terms of Use)
Gateway address is unreachable (64.07 KB, image/png)
2019-02-21 06:14 UTC, Wei Wang
no flags Details
Log files (517.25 KB, application/gzip)
2019-02-21 06:15 UTC, Wei Wang
no flags Details
ipv6 environment screenshot (102.52 KB, image/png)
2019-02-21 07:44 UTC, Wei Wang
no flags Details
ipv6 log files (510.03 KB, application/gzip)
2019-02-26 14:56 UTC, Wei Wang
no flags Details
page1 (132.96 KB, image/png)
2019-02-26 16:54 UTC, Simone Tiraboschi
no flags Details
page3 (136.33 KB, image/png)
2019-02-26 16:54 UTC, Simone Tiraboschi
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 98024 0 master MERGED Fix gateway validation on HE wizard 2019-02-25 12:26:15 UTC
oVirt gerrit 98025 0 ovirt-4.3 MERGED Fix gateway validation on HE wizard 2019-02-25 12:27:24 UTC

Description Wei Wang 2019-02-21 06:14:58 UTC
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):
rhvh-4.3.0.4-0.20190220.0
cockpit-system-176-4.el7.noarch
cockpit-176-4.el7.x86_64
cockpit-machines-ovirt-176-4.el7.noarch
cockpit-storaged-176-4.el7.noarch
cockpit-ovirt-dashboard-0.12.2-1.el7ev.noarch
cockpit-dashboard-176-4.el7.x86_64
cockpit-bridge-176-4.el7.x86_64
cockpit-ws-176-4.el7.x86_64
ovirt-hosted-engine-setup-2.3.5-1.el7ev.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch

How reproducible:
100%


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"

Actual results:
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"

Expected results:
No error message displays in VM settings during hosted engine deployment.

Additional info:
There is not this issue with build rhvh-4.3.0.2-0.20190129.0. So it is a regression bug.

Comment 1 Wei Wang 2019-02-21 06:15:41 UTC
Created attachment 1536896 [details]
Log files

Comment 2 Wei Wang 2019-02-21 07:44:11 UTC
Created attachment 1536912 [details]
ipv6 environment screenshot

The issue also exists with IPV6 environment. The screenshot is attached.

Comment 3 Wei Wang 2019-02-26 05:59:11 UTC
Test Version
rhvh-4.3.0.5-0.20190225.0
cockpit-system-176-4.el7.noarch
cockpit-ws-176-4.el7.x86_64
cockpit-bridge-176-4.el7.x86_64
cockpit-storaged-176-4.el7.noarch
cockpit-machines-ovirt-176-4.el7.noarch
cockpit-176-4.el7.x86_64
cockpit-ovirt-dashboard-0.12.3-1.el7ev.noarch
cockpit-dashboard-176-4.el7.x86_64
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch
ovirt-hosted-engine-setup-2.3.5-1.el7ev.noarch

Test Steps:
According to comment 0

Result:
No error message displays in VM settings during hosted engine deployment, and Hosted engine deploys successfully.

bug is fixed, change status to "VERIFIED"

Comment 4 Wei Wang 2019-02-26 14:43:30 UTC
Test with rhvh-4.3.0.5-0.20190225.0, hosted hosted deployment on only static ipv6 environment, the bug can be reproduced.

Change the status to "ASSIGNED"

Comment 5 Wei Wang 2019-02-26 14:56:55 UTC
Created attachment 1538844 [details]
ipv6 log files

Comment 6 Ido Rosenzwig 2019-02-26 15:51:17 UTC
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 ?

Comment 7 Simone Tiraboschi 2019-02-26 16:54:09 UTC
Created attachment 1538909 [details]
page1

Comment 8 Simone Tiraboschi 2019-02-26 16:54:56 UTC
Created attachment 1538910 [details]
page3

Comment 9 Simone Tiraboschi 2019-02-26 16:57:05 UTC
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.

Comment 11 Ying Cui 2019-02-27 07:29:00 UTC
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.

Comment 13 Sandro Bonazzola 2019-03-01 10:20:18 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.