Bug 1540616

Summary: On redeployment attempts on the ansible flow the logs entries got multiplied
Product: [oVirt] cockpit-ovirt Reporter: Simone Tiraboschi <stirabos>
Component: Hosted EngineAssignee: Phillip Bailey <phbailey>
Status: CLOSED CURRENTRELEASE QA Contact: Yihui Zhao <yzhao>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 0.11.6CC: bugs, cshao, huzhao, qiyuan, rbarry, sbonazzo, weiwang, yaniwang, ycui, yturgema, yzhao
Target Milestone: ovirt-4.2.2Flags: rule-engine: ovirt-4.2+
cshao: testing_plan_complete?
sbonazzo: devel_ack+
yzhao: 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 11:10:59 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
Screenshot of the issue
none
issue1 none

Description Simone Tiraboschi 2018-01-31 14:29:16 UTC
Description of problem:
On redeployment attempts on the ansible flow the logs entries got multiplied.
See the attached screenshot.

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

How reproducible:
100%

Steps to Reproduce:
1. start hosted-engine deployment from cockpit and make it failing somehow
2. restart the deployment
3. check logs field

Actual results:
Logs entries are multiplied

Expected results:
Logs entries on single lines

Additional info:
See attached screenshot

Comment 1 Simone Tiraboschi 2018-01-31 14:29:48 UTC
Created attachment 1388989 [details]
Screenshot of the issue

Comment 2 Yihui Zhao 2018-02-02 13:16:42 UTC
Created attachment 1390146 [details]
issue1

Comment 3 Yihui Zhao 2018-02-02 13:18:00 UTC
Can reproduce.

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.9-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.20180201.0+1
rhvm-appliance-4.2-20180125.0.el7.noarch

Test steps:
Redeploy HE based ansible deployment


Test results:
https://bugzilla.redhat.com/attachment.cgi?id=1390146

Comment 4 Yihui Zhao 2018-03-16 06:41:44 UTC
Cannot meet this issue with redeployment.


Test version:
cockpit-dashboard-160-3.el7.x86_64
cockpit-system-160-3.el7.noarch
cockpit-ovirt-dashboard-0.11.17-1.el7ev.noarch
cockpit-bridge-160-3.el7.x86_64
cockpit-ws-160-3.el7.x86_64
cockpit-storaged-160-3.el7.noarch
cockpit-160-3.el7.x86_64
ovirt-hosted-engine-ha-2.2.7-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.13-1.el7ev.noarch

vdsm-http-4.20.22-1.el7ev.noarch
vdsm-hook-ethtool-options-4.20.22-1.el7ev.noarch
vdsm-network-4.20.22-1.el7ev.x86_64
vdsm-api-4.20.22-1.el7ev.noarch
vdsm-python-4.20.22-1.el7ev.noarch
vdsm-hook-vmfex-dev-4.20.22-1.el7ev.noarch
vdsm-hook-vhostmd-4.20.22-1.el7ev.noarch
vdsm-yajsonrpc-4.20.22-1.el7ev.noarch
vdsm-client-4.20.22-1.el7ev.noarch
vdsm-4.20.22-1.el7ev.x86_64
vdsm-gluster-4.20.22-1.el7ev.noarch
vdsm-hook-vfio-mdev-4.20.22-1.el7ev.noarch
vdsm-common-4.20.22-1.el7ev.noarch
vdsm-hook-openstacknet-4.20.22-1.el7ev.noarch
vdsm-jsonrpc-4.20.22-1.el7ev.noarch
vdsm-hook-fcoe-4.20.22-1.el7ev.noarch

rhvm-appliance-4.2-20180202.0.el7.noarch
rhvh-4.2.1.4-0.20180305.0+1

Test steps:
1. Re-deploy HE via cockpit with ansible.

Test result:
On redeployment attempts on the ansible flow the logs entries didn't get multiplied

So, change the bug's status to verified.

Comment 5 Sandro Bonazzola 2018-03-29 11:10:59 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.