Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionVladimí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
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
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