Bug 1658544 - Add logging to of failed check-for-upgrade command
Summary: Add logging to of failed check-for-upgrade command
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ovirt-4.3.1
: ---
Assignee: Ondra Machacek
QA Contact: Petr Matyáš
URL:
Whiteboard:
: 1459019 1662637 1662639 (view as bug list)
Depends On:
Blocks: 1459019
TreeView+ depends on / blocked
 
Reported: 2018-12-12 11:57 UTC by Ondra Machacek
Modified: 2019-03-01 10:17 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.3.1.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-01 10:17:49 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.3+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 96766 0 master MERGED ansible: Load stderr for failed tasks 2019-02-14 12:36:06 UTC

Description Ondra Machacek 2018-12-12 11:57:07 UTC 
Currently when running check-for-upgrade and it fails, it's hard to debug the reason. Please add logging.
Comment 1 Martin Perina 2019-01-21 12:38:26 UTC 
*** Bug 1662639 has been marked as a duplicate of this bug. ***
Comment 2 Martin Perina 2019-01-21 12:39:14 UTC 
*** Bug 1662637 has been marked as a duplicate of this bug. ***
Comment 3 Ondra Machacek 2019-02-04 12:30:32 UTC 
As testing please try to also check if there is reasonable error message when package is missing, as described in bug 1658544.
Comment 4 Ondra Machacek 2019-02-04 12:31:07 UTC 
*** Bug 1459019 has been marked as a duplicate of this bug. ***
Comment 5 Petr Matyáš 2019-02-22 13:38:06 UTC 
Verified on ovirt-engine-4.3.1.1-0.1.el7.noarch
Comment 6 Sandro Bonazzola 2019-03-01 10:17:49 UTC 
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.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.
Note You need to log in before you can comment on or make changes to this bug.