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.
Candlepin has been updated to change reporting around syspurpose status: https://github.com/candlepin/candlepin/pull/2194/files
- Invalid is now Mismatched
- Valid is now Matched
Above two changes affect host search ie "sla_status = invalid" is now "sla_status = mismatched" same for purpose_status, role_status, usage_status, addons_status
- Not Specified (new)
New hosts will no longer show "Matched" on content host details but rather "Not Specified" Hosts without any purpose attributes set will show Not Specified
Summary of what the statuses mean, from Candlepin code:
/*
* The status is 'Matched' if at least one syspurpose attribute (SLA, role, addons, usage) is specified,
* and all of those that are specified are satisfied by the consumer's entitlements.
*
* The status is 'Mismatched' if at least one syspurpose attribute (SLA, role, addons, usage)
* is specified, and from those specified, at least one is not satisfied by the consumer's entitlements.
* (This includes the scenario of multiple addons being specified, where only some but not all of them
* are satisfied)
*
* The status is 'Not Specified' when NONE of the attributes were specified by the consumer at all.
*/