Bug 1538930

Summary: The vintage (based-otopi) deployment didn't use deprecated python flow while deploying HE via cockpit.
Product: [oVirt] cockpit-ovirt Reporter: Yihui Zhao <yzhao>
Component: Hosted EngineAssignee: Ryan Barry <rbarry>
Status: CLOSED CURRENTRELEASE QA Contact: Yihui Zhao <yzhao>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: ---CC: bugs, cshao, dguo, huzhao, phbailey, qiyuan, rbarry, sbonazzo, weiwang, yaniwang, ycui, yisong
Target Milestone: ovirt-4.2.1Keywords: Reopened
Target Release: ---Flags: rule-engine: ovirt-4.2+
rbarry: devel_ack+
cshao: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.11.6-0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 11:57:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
otopi_flow.png none

Description Yihui Zhao 2018-01-26 07:50:42 UTC
Created attachment 1386488 [details]
otopi_flow.png

Description of problem: 
The vintage (based-otopi) deployment with cockpit didn't use deprecated python flow.

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.5-0.1.el7ev.noarch
cockpit-system-157-1.el7.noarch
ovirt-hosted-engine-setup-2.2.8-1.el7ev.noarch
ovirt-hosted-engine-ha-2.2.4-1.el7ev.noarch
rhvm-appliance-4.2-20171219.0.el7.noarch
rhvh-4.2.1.2-0.20180125.0+1

How reproducible: 
100% 


Steps to Reproduce: 
1. Clean install RHVH4.2.1 (rhvh-4.2.1.2-0.20180125.0+1) with ks
2. Deploy HE via cockpit based otopi


Actual results: 
The vintage (based-otopi) deployment didn't use the deprecated python flow. It seems to use the ansible flow.

Expected results: 
The vintage (based-otopi) deployment should use the deprecated python flow to deploy HE via cockpit

Additional info:

Comment 1 Ryan Barry 2018-01-26 09:36:38 UTC
This seems reasonable.

If the engine is not deployed, the status cannot be checked. Please re-open if this persists after a successful deployment.

Comment 2 Yihui Zhao 2018-01-26 10:00:29 UTC
(In reply to Ryan Barry from comment #1)
> This seems reasonable.
> 
> If the engine is not deployed, the status cannot be checked. Please re-open
> if this persists after a successful deployment.

Ryan , I think that your comment is related to the bug :https://bugzilla.redhat.com/show_bug.cgi?id=1538934. 

And this is a real bug:The vintage (based-otopi) deployment didn't use deprecated python flow while deploying HE via cockpit

Comment 3 Ryan Barry 2018-01-26 10:02:23 UTC
Sorry, you're right. Wrong bug :(

Comment 4 Yihui Zhao 2018-01-28 14:19:52 UTC
The bug is fixed on cockpit-ovirt-dashboard-0.11.6-0.1.el7ev.noarch.


Test version:
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.6-0.1.el7ev.noarch
cockpit-system-157-1.el7.noarch
ovirt-hosted-engine-setup-2.2.8-2.el7ev.noarch
ovirt-hosted-engine-ha-2.2.4-1.el7ev.noarch
rhvm-appliance-4.2-20180125.0.el7.noarch
rhvh-4.2.1.2-0.20180126.0+1

Test steps:
1. Clean install RHVH4.2.1 (rhvh-4.2.1.2-0.20180126.0+1)
2. Deploy HE via cockpit based otopi delopyment.

Test results:
After step2, The vintage (based-otopi) deployment  use deprecated python flow while deploying HE via cockpit


So, I will change this bug's status to verified while it changes to ON_QA.

Comment 5 Yihui Zhao 2018-01-29 02:48:35 UTC
According to the comment 4, change the bug's status to verified!

Comment 6 Sandro Bonazzola 2018-02-12 11:57:29 UTC
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

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