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.

Description of problem:
some rhsm commands get the information from the server (up to date), some rely on local data (which could be out of date), so one command's result is not consistent with another.

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


How reproducible:
always

Steps to Reproduce:
1. Register a system to katello
2. Suscribe the system to a product in the katello UI
3. sm refresh (now subscribed)
4. Unsubscribe in the katello UI
5. sm list --available (sm goes to server and sees it's available now)
6. sm list --consumed (sm only looks locally, shows subscription still consumed)

Actual results:
conflicting data shown

Expected results:
sm should *always* ask the server unless otherwise specified (say, via a command line switch to use local data only).  It's way too easy to get into an inconsistent state.  The same thing can happen if you unregister the system from the server side, and there's probably other ways to get inconsistent data.  

It's true the daemon would eventually sync things up, but that isn't good enough - sm should always show the right data when it's requested.

Additional info:

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.

This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

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.

subscription-manager refresh should be called to re-sync to the Candlepin server. It is too expensive to update the certs every time list --consumed or list --installed is called.