Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1542426

Summary: [cockpit][otopi][iscsi] cockpit over vintage otopi flow should not let the user enter an iSCSI lun uuid
Product: [oVirt] cockpit-ovirt Reporter: Simone Tiraboschi <stirabos>
Component: Hosted EngineAssignee: Ryan Barry <rbarry>
Status: CLOSED CURRENTRELEASE QA Contact: Yihui Zhao <yzhao>
Severity: high Docs Contact:
Priority: unspecified    
Version: 0.11.7CC: bugs, cshao, huzhao, phbailey, qiyuan, rbarry, sbonazzo, stirabos, weiwang, yaniwang, ycui, yturgema, yzhao
Target Milestone: ovirt-4.2.2Flags: rule-engine: ovirt-4.2+
cshao: testing_plan_complete?
cshao: testing_ack+
Target Release: 0.11.12   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.11.12-0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 10:55:18 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:
Bug Depends On: 1548958    
Bug Blocks:    
Attachments:
Description Flags
lun field none

Description Simone Tiraboschi 2018-02-06 10:56:41 UTC
Created attachment 1391994 [details]
lun field

Description of problem:
cockpit over vintage otopi flow let the user enter an iSCSI lun uuid but doesn't validate it at all.
The user can enter a random number and the setup will fail.
See the attached screenshot.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Try to deploy hosted-engine on iSCSI from cockpit
2. Enter a random value as LUN uuid
3.

Actual results:
cockpit page doesn't validate at all the lun uuid

Expected results:
cockpit page validates the lun uuid or it doesn't show thew LUN filed let otopi code validating it

Additional info:

Comment 1 Yihui Zhao 2018-02-06 11:03:01 UTC
(In reply to Simone Tiraboschi from comment #0)
> Created attachment 1391994 [details]
> lun field
> 
> Description of problem:
> cockpit over vintage otopi flow let the user enter an iSCSI lun uuid but
> doesn't validate it at all.
> The user can enter a random number and the setup will fail.
> See the attached screenshot.
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1. Try to deploy hosted-engine on iSCSI from cockpit
> 2. Enter a random value as LUN uuid
> 3.
> 
> Actual results:
> cockpit page doesn't validate at all the lun uuid
> 
> Expected results:
> cockpit page validates the lun uuid or it doesn't show thew LUN filed let
> otopi code validating it
> 
> Additional info:

Add the Version-Release number of selected component:
cockpit-system-157-1.el7.noarch
cockpit-dashboard-157-1.el7.x86_64
cockpit-ovirt-dashboard-0.11.11-0.1.el7ev.noarch
cockpit-bridge-157-1.el7.x86_64
cockpit-storaged-157-1.el7.noarch
cockpit-157-1.el7.x86_64
cockpit-ws-157-1.el7.x86_64
ovirt-hosted-engine-ha-2.2.4-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.9-1.el7ev.noarch
rhvm-appliance-4.2-20180202.0.el7.noarch
rhvh-4.2.1.2-0.20180205.0+1

Comment 2 cshao 2018-02-07 02:40:27 UTC
Give qa_ack+ according #c22 of bug 1539598

Comment 3 Yihui Zhao 2018-03-02 05:17:56 UTC
Tested cockpit-ovirt-0.11.14-0.1 on RHEL7.4, now cockpit don't let the user enter an iSCSI lun uuid, so can deploy HE with iscsi successfully.

Test version:
Red Hat Enterprise Linux Server 7.4 Beta (Maipo)
ovirt-hosted-engine-ha-2.2.6-1.el7ev.noarch
cockpit-ovirt-dashboard-0.11.14-0.1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.11-1.el7ev.noarch
cockpit-storaged-158-1.el7.noarch
cockpit-bridge-157-1.el7.x86_64
cockpit-157-1.el7.x86_64
cockpit-dashboard-158-1.el7.x86_64
cockpit-ws-157-1.el7.x86_64
cockpit-system-157-1.el7.noarch
rhvm-appliance-4.2-20180202.0.el7.noarch

So, change this bug's status to verified.

Comment 4 Sandro Bonazzola 2018-03-29 10:55:18 UTC
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

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