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 2230459 - Recalculate button for Errata is not available on Satellite 6.13/ Satellite 6.14 if no errata is present
Summary: Recalculate button for Errata is not available on Satellite 6.13/ Satellite 6...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 6.15.0
Assignee: Jeremy Lenz
QA Contact: David Moore
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-09 13:45 UTC by Amit Agarwal
Modified: 2024-04-23 17:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2250352 (view as bug list)
Environment:
Last Closed: 2024-04-23 17:12:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36790 0 Normal New Recalculate button for Errata is not available on Satellite 6.13/ Satellite 6.14 if no errata is present 2023-09-28 20:13:35 UTC
Red Hat Issue Tracker SAT-19935 0 None None None 2023-09-07 14:10:07 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:12:11 UTC

Description Amit Agarwal 2023-08-09 13:45:06 UTC 
Description of problem:
Recalculate button for Errata is not available on Satellite 6.13/ Satellite 6.14
if no errata is present.


However Recalculate button for Errata is  available on Satellite 6.11 even if no errata is present

Version-Release number of selected component (if applicable):
Satellite 6.13/ Satellite 6.14

How reproducible:

To update the Installable Errata count click on the Recalculate button in the Satellite's web UI under:

 	Hosts -> Content Hosts -> content_host -> Errata -> recalculate

Steps to Reproduce:
1. For Satellite 6.11 , Hosts -> Content Hosts -> content_host -> Errata -> recalculate // Recalculate option is present


2.  For Satellite 6.13/6.14 , Hosts -> Content Hosts -> content_host -> Errata -> recalculate // Recalculate option is present only if errata is available.


Actual results:

Recalculate button for Errata should be available on Satellite 6.13/ Satellite 6.14 even if no errata is present as it is available on Satellite 6.11
Comment 1 Brad Buckingham 2023-08-10 16:23:50 UTC 
Hello Amit,

Thanks for raising the bugzilla.

Does the same behavior exist if using the new host details page?  (This should be the default as of Satellite 6.13).
Comment 2 Amit Agarwal 2023-09-05 07:18:33 UTC 
Recalculate option is available on the Legacy UI (even if no errata is present for Satellite 6.13 / 6.14 )



Host --> Content Host --> Click on Content Host --> Switch to Legacy UI --> Content --> Errata  / Here Recalculate button for Errata is available on Satellite 6.13/ Satellite 6.14 even if no errata is present.
Comment 4 Jeremy Lenz 2023-09-28 20:13:34 UTC 
Created redmine issue https://projects.theforeman.org/issues/36790 from this bug
Comment 5 Bryan Kearney 2023-09-29 00:02:58 UTC 
Upstream bug assigned to jlenz
Comment 6 Bryan Kearney 2023-09-29 00:03:00 UTC 
Upstream bug assigned to jlenz
Comment 8 Brad Buckingham 2023-10-30 11:29:29 UTC 
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.
Comment 9 David Moore 2024-01-22 19:05:39 UTC 
Verified 6.15.0 snap 6.0

Original Issue: If no errata were available, the recalculate button was not available in UI host>content>errata tab.

Resolution: Recalculate button should be present as long as some repos are enabled, in case we want to manually check for changes.

Steps:
    1. Create product and repo, sync.
    2. Create a content-view, add repository, publish/promote.
    3. Register a new host, select the content-view as the content source.
    4. Enable the repositories in UI host>content>repository sets, or with: 
      > subscription-manager repos --enable {repository_label}
    5. Navigate to host>content>errata tab.

Expected and Actual results:
    3. Unknown errata status, the recalculate button is not present, since no repositories are enabled.
   """
   Unknown errata status
   No installed packages and/or enabled repositories have been reported by subscription-manager.
   {Clear Filters (link)} 
   """

    5. No errata are present from enabled repos, but just below we have the option to recalculate again manually.
   """
   All up to date
   No action is needed because there are no applicable errata for this host.
   {Refresh errata applicability (link)}
   """
Comment 12 errata-xmlrpc 2024-04-23 17:12:10 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.15.0 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-2024:2010
Note You need to log in before you can comment on or make changes to this bug.