Bug 2184742
| Summary: | [RFE] Requesting a quiet mode for leapp to report only failures or if we're ok to reboot | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | jcastran |
| Component: | leapp | Assignee: | Leapp Notifications Bot <leapp-notifications-bot> |
| Status: | NEW --- | QA Contact: | upgrades-and-conversions |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 7.9 | CC: | pstodulk |
| Target Milestone: | rc | ||
| 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: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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?