Bug 1903567

Summary: cockpit cant discover iscsi and fc luns
Product: [oVirt] cockpit-ovirt Reporter: Aviv Turgeman <aturgema>
Component: Hosted EngineAssignee: Asaf Rachmani <arachman>
Status: CLOSED CURRENTRELEASE QA Contact: Wei Wang <weiwang>
Severity: high Docs Contact:
Priority: unspecified    
Version: 0.14.15CC: arachman, bugs, cshao, gofaizen, lsvaty, mavital, nlevy, peyu, sbonazzo, shlei, weiwang, yaniwang
Target Milestone: ovirt-4.4.4Flags: pm-rhel: ovirt-4.4+
weiwang: testing_plan_complete+
pm-rhel: planning_ack+
sbonazzo: devel_ack+
weiwang: testing_ack+
Target Release: 0.14.16   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.14.16-1.el8ev Doc Type: Bug Fix
Doc Text:
Cause: Ansible changed the module's behavior in the 2.9.14 version and the module no longer returns 'ansible_facts' in variables. Consequence: During hosted-Engine deployment, Cockpit can't discover iscsi and fc luns Fix: Parse the variable correctly. Result: Cockpit can discover iscsi and fc luns, during hosted-Engine deployment.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-21 12:36:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
iscsi luns error
none
fc luns error
none
fc-log-file
none
iscsi-log-file none

Description Aviv Turgeman 2020-12-02 11:58:11 UTC 
Created attachment 1735577 [details]
iscsi luns error

Description of problem:
when reaching "storage" phase, Fibre Channel and ISCSI luns are not retrieved by cockpit.

Version-Release number of selected component (if applicable):
cockpit-ovirt-dashboard-0.14.15-1.el8.noarch

How reproducible:
100%

Steps to Reproduce:
1. Deploy HE with cockpit dashboard
2. Reach to Step 4 "Storage" and choose iSCSI or Fibre Channel
3. if chosen iscsi enter portal IP address and retrieve luns, else just retrieve luns
4. wait until received massaged for no luns discovered

Actual results:
receiving an error that can't finish installation until a lun is selected.

Expected results:
lun list should appear and should be able to choose from that list

Additional info:
This bug is similar to bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1891521
Comment 1 Aviv Turgeman 2020-12-02 12:11:22 UTC 
Created attachment 1735590 [details]
fc luns error
Comment 2 Aviv Turgeman 2020-12-02 12:12:30 UTC 
Created attachment 1735591 [details]
fc-log-file
Comment 3 Aviv Turgeman 2020-12-02 12:13:24 UTC 
Created attachment 1735592 [details]
iscsi-log-file
Comment 4 Wei Wang 2020-12-04 04:06:56 UTC 
Test with rhvh-4.4.3.2-0.20201130.0, QE can reproduce this bug, ack+
Comment 5 Aviv Turgeman 2020-12-09 12:14:22 UTC 
*** Bug 1905955 has been marked as a duplicate of this bug. ***
Comment 6 Wei Wang 2020-12-11 03:19:30 UTC 
The latest RHVH build, cockpit-ovirt-dashboard-0.14.15-1.el8ev.noarch. QE will verify this bug when dev added the fixed version to RHVH build.
Comment 7 Sandro Bonazzola 2020-12-11 15:33:57 UTC 
This can be tested also on plain RHEL, there's no real need to wait for a RHV-H build including cockpit-ovirt
Comment 8 Sandro Bonazzola 2020-12-11 15:34:49 UTC 
You can also just install cockpit-ovirt on top of RHV-H by disabling yum versionlock plugin and yum upgrade cockpit-ovirt there.
Comment 9 Ilia Molchadsky 2020-12-14 11:21:35 UTC 
cockpit-ovirt-dashboard-0.14.16-1.el8 - works as expected. FC LUNs were detected by HA setup.
Comment 10 Wei Wang 2020-12-17 04:17:34 UTC 
Test with cockpit-ovirt-dashboard-0.14.16-1 on RHEL8, works as expected, iscsi luns are retrieved successfully.

And according to comment 9, this bug is fixed, move it to "VERIFIED"
Comment 11 Sandro Bonazzola 2020-12-21 12:36:51 UTC 
This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.4 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.