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

Bug 1662639

Summary: Missing ansible logs for "check for upgrade"
Product: [oVirt] ovirt-engine Reporter: Liran Rotenberg <lrotenbe>
Component: GeneralAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact: Lukas Svaty <lsvaty>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: bugs, mperina
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-21 12:38:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine-sosreport none

Description Liran Rotenberg 2018-12-31 09:13:25 UTC
Created attachment 1517569 [details]
engine-sosreport

Description of problem:
Using web UI - check for upgrade on host have no logs, making it difficult to understand in case of failure.

2018-12-30 14:39:37,577+02 INFO  [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-hostUpdatesChecker-Thread-5) [] Executing Ansible command: ANSIBLE_STDOUT_CALLBACK=hostupgradeplugin [/usr/bin/ansible-playbook, --ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config, --check, --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa, --inventory=/tmp/ansible-inventory7099874618505348174
, /usr/share/ovirt-engine/playbooks/ovirt-host-upgrade.yml] [Logfile: null]

As you can see: "Logfile: null".

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.0-0.6.alpha2.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Try to run check for upgrade from the web UI.

Actual results:
No logs for the ansible operation.

Expected results:
Logs for the operation.

Comment 1 Martin Perina 2019-01-21 12:38:26 UTC

*** This bug has been marked as a duplicate of bug 1658544 ***