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:
Customer reports a situation where it looks like the Web UI is saying katello-agent is not installed while the CLI/API report that katello-agent is not installed. It looks like the problem is that one uses katello's db to check for katello-agent while the other checks Pulp.
Version-Release number of selected component (if applicable):
6.2.0
How reproducible:
Once the state is reached where katello says the system does not have package and pulp says it does, 100%.
Steps to Reproduce:
This is a bit tricky. Not sure how we reached the initial state where pulp and katello got out of sync for the package info but this would reproduce the state:
1. Register a system that has katello-agent installed
2. Go into Katello db/console and remove the katello-agent package
3. Check the Web UI content host page and run "hammer content-host info --id 1"
Actual results:
The Web UI does not agree with the CLI.
Expected results:
The Web UI and CLI have the same info regarding whether katello-agent is installed.
Additional info:
Somewhat related to BZ https://bugzilla.redhat.com/show_bug.cgi?id=1347419. I think 1347419 might be producing the state we're seeing in this bug. If we fix 1347419, that might suffice (and not fix this bug).
Digging a little more, this problem doesn't exist upstream as the systems API has been removed. So this is specific to 6.2. Moreover, I think this bug will no longer be a problem after we fix https://bugzilla.redhat.com/show_bug.cgi?id=1347419.
I recommended that the customer run "rake katello:reindex". Going to wait to hear back if that fixed things and then close this out.