Project

General

Profile

Actions

Bug #30089

closed

Capsule upgrade playbook does not return all stdout in case of failure

Added by Vladimir Sedmik almost 4 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

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.

Actions #1

Updated by Vladimir Sedmik almost 4 years ago

Actions #2

Updated by Tomer Brisker over 3 years ago

  • Project changed from Foreman Remote Execution to Ansible
  • Bugzilla link set to 1874103
Actions #3

Updated by Suraj Patil over 3 years ago

  • Bugzilla link deleted (1874103)
Actions #4

Updated by Suraj Patil over 3 years ago

A new issue is opened under foreman-maintain component - https://projects.theforeman.org/issues/30810
This issue can be closed or marked as duplicate.

Actions #5

Updated by Suraj Patil over 3 years ago

  • Related to deleted (Tracker #29643: Capsule upgrade playbook tracker)
Actions #6

Updated by Ondřej Ezr almost 3 years ago

  • Status changed from New to Rejected

Thanks, the main issue should be in foreman-maintain.

Actions

Also available in: Atom PDF