Bug 1946095
Summary: | "No valid network interface has been found" when starting HE deployment via cockpit | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Asaf Rachmani <arachman> | ||||
Component: | cockpit-ovirt | Assignee: | Scott Dickerson <sdickers> | ||||
Status: | CLOSED ERRATA | QA Contact: | Wei Wang <weiwang> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 4.4.6 | CC: | arachman, cshao, dfediuck, dfodor, lsvaty, lveyde, mavital, michal.skrivanek, mjurasek, peyu, sasundar, sbonazzo, sdickers, sgratch, shlei, spiros.mouzakitis, theophanis_kontogiannis, weiwang, yaniwang | ||||
Target Milestone: | ovirt-4.4.6-1 | Keywords: | Regression, TestBlocker, ZStream | ||||
Target Release: | 4.4.6 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | cockpit-ovirt-0.15.0-1 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2021-06-03 10:24:42 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | UX | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1954623 | ||||||
Attachments: |
|
Description
Asaf Rachmani
2021-04-04 11:32:30 UTC
Created attachment 1769041 [details]
No_valid_network_screenshot
*** Bug 1943567 has been marked as a duplicate of this bug. *** Test with rhvh-4.4.6.1-0.20210402.0, QE can reproduce this bug. ACK+ moving back to high since it works with ansible/cli installation that's alternative to GUI *** Bug 1948492 has been marked as a duplicate of this bug. *** (In reply to Michal Skrivanek from comment #4) > moving back to high since it works with ansible/cli installation that's > alternative to GUI Hi Michal, For RHHI-V use case, we do not expect the admins to use the hosted-engine CLI interface. Gluster deployment is initiated from cockpit and that allows users to decide on the disks, volumes and other options pertaining to gluster volumes. Then after the gluster volume is deployed, users will continue to 'Hosted Engine' deployment from GUI. This issue will affect the RHHI-V users. It break the usability and UX feature for RHHI-V customers So bumping up the severity of the bug (In reply to SATHEESARAN from comment #6) > (In reply to Michal Skrivanek from comment #4) > > moving back to high since it works with ansible/cli installation that's > > alternative to GUI > > Hi Michal, > > For RHHI-V use case, we do not expect the admins to use the hosted-engine > CLI interface. > Gluster deployment is initiated from cockpit and that allows users to decide > on the > disks, volumes and other options pertaining to gluster volumes. > > Then after the gluster volume is deployed, users will continue to 'Hosted > Engine' deployment > from GUI. This issue will affect the RHHI-V users. It break the usability > and UX feature for > RHHI-V customers > > So bumping up the severity of the bug usability is one thing, but I was curious about gluster-related screens, whether they work at all, can you take a look at that? (In reply to Michal Skrivanek from comment #7) > (In reply to SATHEESARAN from comment #6) > > (In reply to Michal Skrivanek from comment #4) > > > moving back to high since it works with ansible/cli installation that's > > > alternative to GUI > > > > Hi Michal, > > > > For RHHI-V use case, we do not expect the admins to use the hosted-engine > > CLI interface. > > Gluster deployment is initiated from cockpit and that allows users to decide > > on the > > disks, volumes and other options pertaining to gluster volumes. > > > > Then after the gluster volume is deployed, users will continue to 'Hosted > > Engine' deployment > > from GUI. This issue will affect the RHHI-V users. It break the usability > > and UX feature for > > RHHI-V customers > > > > So bumping up the severity of the bug > > usability is one thing, but I was curious about gluster-related screens, > whether they work at all, can you take a look at that? Hi Michal, I find that the gluster deployment too fails with the latest RHVH 4.4.6 [ RHVH-4.4-20210426.1-RHVH-x86_64-dvd1.iso ] Even the HE deployment wizard fails to open up. I have raised a bug - https://bugzilla.redhat.com/show_bug.cgi?id=1954629 for the same Investigation notes: - Cockpit on 4.4.5 bundles jquery in the "base1" package. - Cockpit on >=4.4.6 no longer bundles jquery in the "base1" package. Hopefully all it will take is to package jquery with cockpit-ovirt itself and the problem will be solved. back to assigned, merged patches are not solving. Still having: System data could not be retrieved! No valid network interface has been found If you are using Bonds or VLANs Use the following naming conventions: - VLAN interfaces: physical_device.VLAN_ID (for example, eth0.23, eth1.128, enp3s0.50) - Bond interfaces: bond*number* (for example, bond0, bond1) - VLANs on bond interfaces: bond*number*.VLAN_ID (for example, bond0.50, bond1.128) * Supported bond modes: active-backup, balance-xor, broadcast, 802.3ad * Networking teaming is not supported and will cause errors Console shows: Execution of /usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml with tags get_network_interfaces started DefaultValueProvider.js:138 Network interfaces retrieval failed PlaybookUtil.js:156 Ansible output file directory created successfully. PlaybookUtil.js:30 Execution of /usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml with tags validate_hostnames started Validation.js:184 ReferenceError: $ is not defined at PlaybookUtil.js:52 at new Promise (<anonymous>) at at._runPlaybook (PlaybookUtil.js:29) at PlaybookUtil.js:22 Validation.js:185 Validation of host FQDN, node0.lab, failed PlaybookUtil.js:122 Error: Unable to read file /var/tmp/ovirt-hosted-engine-setup/cockpit/validate_hostnames-202143132659-od3nms.json (anonymous) @ PlaybookUtil.js:122 Validation.js:195 Unable to read output file: /var/tmp/ovirt-hosted-engine-setup/cockpit/validate_hostnames-202143132659-od3nms.json. Error: Unable to read file DefaultValueProvider.js:98 General system data retrieved successfully. @Sandro - The rpm installed on your VM was from [1] (build/ci refactoring) but needed to be from [2] (embed jquery in cockpit-ovirt). [2] is the same one as currently provided by [3]. [1] - https://gerrit.ovirt.org/c/cockpit-ovirt/+/114580 [2] - https://gerrit.ovirt.org/c/cockpit-ovirt/+/114581 [3] - https://jenkins.ovirt.org/job/cockpit-ovirt_standard-on-merge/lastSuccessfulBuild/artifact/ *** Bug 1954629 has been marked as a duplicate of this bug. *** bug is fixed with the latest 4.4.6 build. move it 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 (Moderate: Red Hat Virtualization Host security update [ovirt-4.4.6]), 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://access.redhat.com/errata/RHSA-2021:2239 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |