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.
Bug 2218656 - satellite-maintain packages check-update fails when there are no packages to be updated.
Summary: satellite-maintain packages check-update fails when there are no packages to ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.10.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: 6.13.3
Assignee: Sayan Das
QA Contact: Griffin Sullivan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-29 18:30 UTC by Odilon Sousa
Modified: 2023-09-20 16:27 UTC (History)
11 users (show)

Fixed In Version: rubygem-foreman-maintain-1.2.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2073535
Environment:
Last Closed: 2023-08-03 13:30:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36369 0 Normal Closed Consider both 0 and 100 as valid exit codes for check-update yum action 2023-06-29 18:30:54 UTC
Github theforeman foreman_maintain pull 729 0 None Merged Fixes #36369 - Exit code 0 is a valid exit status 2023-06-29 18:30:54 UTC
Red Hat Issue Tracker SAT-17607 0 None None None 2023-06-29 18:30:54 UTC
Red Hat Issue Tracker SAT-18713 0 None None None 2023-06-29 18:33:26 UTC
Red Hat Product Errata RHSA-2023:4466 0 None None None 2023-08-03 13:30:49 UTC

Comment 2 Griffin Sullivan 2023-07-24 20:02:03 UTC 
FailedQA on 6.13.3 snap 1

The change didn't make it into the snap because it seems this was marked for the wrong package. It should be foreman_maintain not foreman_ansible.
Comment 3 Griffin Sullivan 2023-07-27 15:36:18 UTC 
Verified on 6.13.3 snap 2

Packages check-update works when there are no packages to update.

Steps to reproduce:

1) # satellite-maintain packages check-update

2) Ensure there is a list of packages to update

3) # satellite-maintain packages update

4) # reboot

5) # satellite-maintain packages check-update


Results:

Step 5 runs successfully with [OK] status.
Comment 12 errata-xmlrpc 2023-08-03 13:30:19 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 (Important: Satellite 6.13.3 Async Security Update), 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-2023:4466
Note You need to log in before you can comment on or make changes to this bug.