Bug 1541850 - There are the excess steps about iscsi configuration while deploying HE via cockpit based otopi.
Summary: There are the excess steps about iscsi configuration while deploying HE via c...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Hosted Engine
Version: ---
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Phillip Bailey
QA Contact: Yihui Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-05 04:27 UTC by Yihui Zhao
Modified: 2022-02-25 08:26 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-03-09 12:55:38 UTC
oVirt Team: Integration
Embargoed:
rule-engine: blocker+

Attachments (Terms of Use)
issue1 (28.77 KB, image/png)
2018-02-05 04:27 UTC, Yihui Zhao 		no flags Details
issue2 (8.15 KB, image/png)
2018-02-05 04:29 UTC, Yihui Zhao 		no flags Details
issue3 (7.74 KB, image/png)
2018-02-05 04:29 UTC, Yihui Zhao 		no flags Details
issue4 (18.02 KB, image/png)
2018-02-05 04:30 UTC, Yihui Zhao 		no flags Details
issue5 (18.55 KB, image/png)
2018-02-05 04:31 UTC, Yihui Zhao 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44917 0 None None None 2022-02-25 08:26:49 UTC
oVirt gerrit 87141 0 None None None 2018-02-05 14:19:00 UTC

Description Yihui Zhao 2018-02-05 04:27:54 UTC 
Created attachment 1391323 [details]
issue1

Description of problem: 
There are the excess steps about iscsi configurations while deploying HE via cockpit based otopi.


Version-Release number of selected component (if applicable): 
cockpit-ws-157-1.el7.x86_64
cockpit-bridge-157-1.el7.x86_64
cockpit-storaged-157-1.el7.noarch
cockpit-dashboard-157-1.el7.x86_64
cockpit-157-1.el7.x86_64
cockpit-ovirt-dashboard-0.11.10-0.1.el7ev.noarch
cockpit-system-157-1.el7.noarch
ovirt-hosted-engine-setup-2.2.9-1.el7ev.noarch
ovirt-hosted-engine-ha-2.2.4-1.el7ev.noarch
rhvh-4.2.1.2-0.20180202.0+1
rhvm-appliance-4.2-20180202.0.el7.noarch


How reproducible: 
100%

Keywords:
Regression

Steps to Reproduce: 
1. Clean install latest RHVH4.2.1 with ks(rhvh-4.2.1.2-0.20180202.0+1)
2. Deploy HE with iscsi storage via cockpit

Actual results: 
There are the excess steps about iscsi configuration while deploying HE via cockpit based otopi.


Expected results: 
There are no excess steps about iscsi configuration while deploying HE via cockpit based otopi.


Additional info:
Comment 1 Yihui Zhao 2018-02-05 04:29:29 UTC 
Created attachment 1391324 [details]
issue2
Comment 2 Yihui Zhao 2018-02-05 04:29:59 UTC 
Created attachment 1391325 [details]
issue3
Comment 3 Yihui Zhao 2018-02-05 04:30:31 UTC 
Created attachment 1391326 [details]
issue4
Comment 4 Yihui Zhao 2018-02-05 04:31:05 UTC 
Created attachment 1391327 [details]
issue5
Comment 5 Red Hat Bugzilla Rules Engine 2018-02-05 06:19:41 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 6 Simone Tiraboschi 2018-02-05 14:19:01 UTC 
Moving to MODIFIED as for https://gerrit.ovirt.org/#/c/87141/
Comment 7 Ryan Barry 2018-02-07 20:03:34 UTC 
Just to verify expectations, are these excess because they're already part of the wizard, or is there another reason?

Exactly steps to reproduce the excess would be helpful.
Comment 8 Yihui Zhao 2018-02-08 05:31:14 UTC 
(In reply to Ryan Barry from comment #7)
> Just to verify expectations, are these excess because they're already part
> of the wizard, or is there another reason?
> 
> Exactly steps to reproduce the excess would be helpful.

Due to the bug comment :https://bugzilla.redhat.com/show_bug.cgi?id=1539598#c19
if just input the target address, other iscsi configuration steps are needed.
Also, it is helpful for user to deploy.
Comment 9 Simone Tiraboschi 2018-03-09 12:55:38 UTC 
We are going to completely remove support for otopi deployment from cockpit.
Note You need to log in before you can comment on or make changes to this bug.