Bug 1669928 - Hosted engine Wizard loading failed with static IPv6 network environment.
Summary: Hosted engine Wizard loading failed with static IPv6 network environment.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Hosted Engine
Version: 0.12.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-4.3.1
: ---
Assignee: Simone Tiraboschi
QA Contact: Wei Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-28 03:47 UTC by Wei Wang
Modified: 2019-03-01 10:21 UTC (History)
10 users (show)

Fixed In Version: cockpit-ovirt-0.12.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-01 10:21:28 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.3+
rule-engine: blocker+
cshao: testing_ack+


Attachments (Terms of Use)
Wizard loading failed (82.75 KB, image/png)
2019-01-28 03:47 UTC, Wei Wang
no flags Details
Log files (763.73 KB, application/gzip)
2019-01-28 03:48 UTC, Wei Wang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 97729 0 master MERGED IPv6 fixes 2019-02-18 09:20:42 UTC
oVirt gerrit 97823 0 ovirt-4.3 MERGED IPv6 fixes 2019-02-18 09:44:49 UTC

Description Wei Wang 2019-01-28 03:47:02 UTC
Created attachment 1524144 [details]
Wizard loading failed

Description of problem:
Hosted engine Wizard loading failed with static IPv6 network environment.


Version-Release number of selected component (if applicable):
RHVH-4.3-20190124.0-RHVH-x86_64-dvd1.iso
cockpit-176-4.el7.x86_64
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-ovirt-dashboard-0.12.1-1.el7ev.noarch
cockpit-machines-ovirt-176-4.el7.noarch
cockpit-dashboard-176-4.el7.x86_64
ovirt-hosted-engine-setup-2.3.2-1.el7ev.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch
rhvm-appliance-4.3-20190124.0.el7.x86_64
firefox-60.4.0-1.el7.x86_64
google-chrome-stable-71.0.3578.98-1.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Clean install RHVH-4.3-20190124.0-RHVH-x86_64-dvd1.iso
2. Configure the host with static IPv6 network
3. Login to cockpit webUI with root account in ipv6 network env.
4. Deploy Hosted-engine with clicking "Start" button under "Hosted Engine".
5. Wizard is loading, check.

Actual results:
Hosted engine Wizard loading failed with static IPv6 network environment.

Expected results:
Hosted engine Wizard should load successful with static IPv6 network environment.

Additional info:
The Wizard can be loaded successful with ipv4 network using the same version RHVH and Firefox/Chrome.

Comment 1 Wei Wang 2019-01-28 03:48:02 UTC
Created attachment 1524145 [details]
Log files

Comment 2 Red Hat Bugzilla Rules Engine 2019-01-29 09:04:16 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Wei Wang 2019-02-21 07:48:40 UTC
Test Version:
redhat-virtualization-host-4.3-20190220.2.el7_6.x86_64.liveimg.squashfs
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

Test Steps:
According to comment 0 steps.

Result
Hosted engine Wizard load successfully with static IPv6 network environment.

Bug is fixed, change status to "VERIFIED"

Comment 4 Sandro Bonazzola 2019-03-01 10:21:28 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.