RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 845634 - Subscriptions for a registered and subscribed system are not correctly updated if rhsmcertd is bounced
Summary: Subscriptions for a registered and subscribed system are not correctly update...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: 7.0
Assignee: candlepin-bugs
QA Contact: Entitlement Bugs
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel70
TreeView+ depends on / blocked
 
Reported: 2012-08-03 16:35 UTC by Og Maciel
Modified: 2013-01-30 15:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-30 15:41:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Katello ui showing system is not compliant (70.45 KB, image/png)
2012-08-03 16:35 UTC, Og Maciel
no flags Details

Description Og Maciel 2012-08-03 16:35:19 UTC
Created attachment 602169 [details]
Katello ui showing system is not compliant

Description of problem:

Assuming that you have the correct amount and type of subscriptions available for your organization, when you register and autosubscribe a system to that organization, this system should be displayed as being compliant in katello's web ui (which displays a green icon next to the system name). However, the web ui displays that system as being non-compliant with a red icon next to it. It isn't until rhsmcertd run (or bounced) that the system is properly displayed in the ui.

The default refresh rate for checking/posting the system "health" is 1 day, which means that the true state for a just recently system won't reflect in Katello's web ui until much later. Could we post the system's information back to katello upon successful subscription?

Version-Release number of selected component (if applicable):

*subscription-manager-0.96.17-1.el6.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 RHEL Program Management 2012-12-14 08:47:18 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 William Poteat 2013-01-30 15:41:57 UTC
The status in Katello is derived from Candlepin exclusively.

The running of rhsmcertd will change the status in the Subscription Manager only. It is far too expensive for every request for subscription or installed product status to refresh from the server. 

The status update will need to wait for rhsmcertd unless we put a 'refresh from server' action in the GUI. The CLI has a 'refresh' command, but it must be explicitly run to pull down or remove certs that will change installed product status.


This needs to be rewritten as an RFE.


Note You need to log in before you can comment on or make changes to this bug.