Bug 1874103 - Capsule upgrade playbook does not return all stdout in case of failure
Summary: Capsule upgrade playbook does not return all stdout in case of failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.8.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: 6.8.0
Assignee: Suraj Patil
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-31 15:10 UTC by Vladimír Sedmík
Modified: 2020-10-27 12:39 UTC (History)
8 users (show)

Fixed In Version: rubygem-foreman_maintain-0.6.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:38:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30810 0 Normal Closed Capsule upgrade playbook does not return all stdout in case of failure 2020-11-11 08:44:42 UTC
Red Hat Product Errata RHBA-2020:4365 0 None None None 2020-10-27 12:38:59 UTC

Description Vladimír Sedmík 2020-08-31 15:10:19 UTC
Description of problem:
When I run the Capsule upgrade playbook with wrong target version (like 6.8 on 6.8 capsule, instead of 6.8.z), I get only first part of the stdout, which mentions another INFO/WARNING unrelated to the cause of failure. This might be a bit confusing for the user, making him to run the upgrade manually.

Job output:
19:TASK [Print satellite-maintain output] *********************************
20:ok: [dhcp-3-111.vms.sat.rdu2.redhat.com] => {
21: "result": {
22: "changed": true,
23: "cmd": "satellite-maintain upgrade run --assumeyes --target-version=6.8 --whitelist=\"repositories-validate,repositories-setup,disk-performance\"",
24: "delta": "0:00:06.087094",
25: "end": "2020-06-10 03:26:01.743619",
26: "failed": true,
27: "msg": "non-zero return code",
28: "rc": 1,
29: "start": "2020-06-10 03:25:55.656525",
30: "stderr": "",
31: "stderr_lines": [],
32: "stdout": "Checking for new version of satellite-maintain...\nNothing to update, can't find new version of satellite-maintain.",
33: "stdout_lines": [
34: "Checking for new version of satellite-maintain...",
35: "Nothing to update, can't find new version of satellite-maintain."
36: ]
37: }
38:}

Output when running the same command manually:
[root@dhcp-3-111 ~]# satellite-maintain upgrade run --assumeyes --target-version=6.8 --whitelist="repositories-validate,repositories-setup,disk-performance"
Checking for new version of satellite-maintain...
Nothing to update, can't find new version of satellite-maintain.
Can't upgrade to 6.8
Possible target versions are:
6.8.z

There is a ~3 sec delay between "Nothing to update, can't find.." and the rest. Not sure if it relates, just saying.


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


How reproducible:
always

Steps to Reproduce:
1. Have a Satellite and a Capsule registered to it
2. Monitor > Jobs > Run Job > 
3. Fill the following fileds, leave 'whitelist_options' blank
   Job category : Ansible Playbook
   Job template : Capsule Upgrade Playbook
   Search Query : name ~ <caps-fqdn>
   target_version : 6.8
4. Submit


Actual results:
only first part of the stdout is shown


Expected results:
all output being shown

Comment 4 Suraj Patil 2020-09-10 06:38:39 UTC
Created redmine issue https://projects.theforeman.org/issues/30810 from this bug

Comment 11 errata-xmlrpc 2020-10-27 12:38:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.8 Satellite Maintenance Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4365


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