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.
Description of problem:
When one updates a Content View or Lifecycle Environment of a Content Host, errata applicability calculation is not run so the user still sees all past errata applicable.
Ideally, such a change should trigger Actions::Katello::Host::GenerateApplicability task (followed by update_applicability_counts that is missing there in general).
However, that change might not be welcomed, since until the Content Host runs "subscription-manager refresh", it has old certs and yum repos thus it can't get a new packages, I think. And such a command on client does trigger RegApp task (but STILL not update_applicability_counts, so _old_ counts of security/bugfix/enhancement errata will be shown, like in bz1699786).
Version-Release number of selected component (if applicable):
Sat 6.4, also 6.5 HTB
How reproducible:
100%
Steps to Reproduce:
1. Have a big CV with few repos, some of the content promoted to Dev LE, some new content additionally in Library LE
2. Have another CV with just smaller content
3. Have a Content Host with some old versions of packages, such that sets of applicable errata are mutually exclusive in "big CV in Dev LE" and "big CV in Library" and "small CV"
4. Update CV or LE of the C.Host in WebUI.
5. Check applicable errata (both in Content Host "Details" tab and listed errata in "Errata" tab).
Actual results:
5. stays the same, regardless of any update of CV or LE in 4.
Expected results:
5. to be updated (after a while as some async task can be triggered) accordingly to the change made in 4.
Additional info:
If it will be decided RegApp task is meaningless to be triggered by the change in 4., then please add to the task itself calling:
host.content_facet.update_applicability_counts
such that RegApp task (invoked e.g. by subscription-manager refresh or otherwise) will update also the errata applicability _counts_ (cf. bz1699786 again).
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in approximately a month. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact your Red Hat Account Team. Thank you.