Bug 1685738

Summary: Provide a template for handling yum check-update always exiting with code 100, making the jobs appear as 'failed'
Product: Red Hat Satellite Reporter: Paul Dudley <pdudley>
Component: Remote ExecutionAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.2CC: aruzicka, ehelms, inecas, jalviso, jhanley, onerleka, susalvi
Target Milestone: 6.10.0Keywords: Triaged
Target Release: Unused   
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: 2021-11-16 14:08:28 UTC 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:

Description Paul Dudley 2019-03-05 23:05:17 UTC
Version-Release number of selected component (if applicable):
Satellite 6.4.2

Whenever a remote execution job runs the 'yum check-update' command the job will result in a 'failed' status

Here is an example job (take from the webui of the failed job):
---
   1: Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id,
   2: : search-disabled-repos, subscription-manager
   3: Not using downloaded rhel-7-server-optional-rpms/repomd.xml because it is older than what we have:
   4: Current : Mon Mar 4 03:54:07 2019
   5: Downloaded: Fri Mar 1 23:17:20 2019
   6: Not using downloaded rhel-7-server-rpms/repomd.xml because it is older than what we have:
   7: Current : Sun Mar 3 05:22:38 2019
   8: Downloaded: Fri Mar 1 23:41:28 2019
   9: java-1.8.0-openjdk.x86_64 1:1.8.0.201.b09-0.el7_6 rhel-7-server-rpms
  10: java-1.8.0-openjdk-headless.x86_64 1:1.8.0.201.b09-0.el7_6 rhel-7-server-rpms
  11: mesa-libwayland-egl.x86_64 18.0.5-4.el7_6 rhel-7-server-optional-rpms
  12: Uploading Enabled Repositories Report
  13: Loaded plugins: langpacks, product-id, subscription-manager
  14: Exit status: 100
---

The command is seen here:
---
{"ssh_user"=>"root", "effective_user"=>"root", "effective_user_method"=>"sudo", "cleanup_working_dirs"=>true, "sudo_password"=>"", "ssh_port"=>22, "hostname"=>"10.12.212.64", "script"=>"yum check-update", "execution_timeout_interval"=>nil, "connection_options"=>{"retry_interval"=>15, "retry_count"=>4}, "proxy_url"=>"https://iridium.usersys.redhat.com:9090", "proxy_action_name"=>"ForemanRemoteExecutionCore::Actions::RunScript", "locale"=>"en", "current_user_id"=>4}
---

'yum check-update' reliably reproduces this exit code every time and it would be great to not see this action as a failure in the Satellite when the command actually succeeds.

Comment 8 Adam Ruzicka 2019-07-30 13:38:07 UTC
Created redmine issue https://projects.theforeman.org/issues/27470 from this bug

Comment 9 Bryan Kearney 2019-07-30 14:02:58 UTC
Upstream bug assigned to aruzicka

Comment 10 Bryan Kearney 2019-07-30 14:03:00 UTC
Upstream bug assigned to aruzicka

Comment 11 Adam Ruzicka 2019-11-07 14:58:34 UTC
*** Bug 1769821 has been marked as a duplicate of this bug. ***

Comment 12 Surjeet Salvi 2019-11-07 16:28:42 UTC
Hello Team,

I have a customer (Case - 02509118) who has reported the same issue. 

Please confirm if we have any KCS article for this issue which can be shared with the CU

Regards
Surjeet Salvi

Comment 13 Bryan Kearney 2021-03-29 21:00:13 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/27470 has been resolved.

Comment 14 Peter Ondrejka 2021-06-01 09:20:24 UTC
Verified on Satellite 6.10 sn 1 on a rhel host, Check Update template succeeds and returns the expected info

Comment 17 errata-xmlrpc 2021-11-16 14:08:28 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 (Moderate: Satellite 6.10 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/RHSA-2021:4702

Comment 18 Adam Ruzicka 2024-03-04 12:27:20 UTC
*** Bug 2267682 has been marked as a duplicate of this bug. ***