Bug 2184742 - [RFE] Requesting a quiet mode for leapp to report only failures or if we're ok to reboot
Summary: [RFE] Requesting a quiet mode for leapp to report only failures or if we're o...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: leapp
Version: 7.9
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Leapp Notifications Bot
QA Contact: upgrades-and-conversions
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-05 14:46 UTC by jcastran
Modified: 2023-07-31 07:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OAMG-8814 0 None None None 2023-04-05 14:48:10 UTC
Red Hat Issue Tracker RHELPLAN-154093 0 None None None 2023-04-05 14:48:01 UTC

Comment 3 Petr Stodulka 2023-04-05 16:32:51 UTC
Hi John. Thank you for the report. If I understand right what's the main problem in this particular case,
the asked result should be possible to achieve easily by command like:

    # leapp upgrade >/dev/null 2>/dev/null && grep -q '"inhibitor"' /var/log/leapp/leapp-report.json || echo "Cannot upgrade"

The last echo could be dropped in case the exit code is the only thing that matters.

Expecting that ansible playbook does not consume content from the serial console during the phases inside the upgrade environment
and the last phase (first boot to the upgraded system) also does not produce too much data.

Could this be sufficient solution for the customer?


Note You need to log in before you can comment on or make changes to this bug.