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:
If you have a content host registered to a satellite 6.1 machine with katello-agent running, the "installed" status of katello agent will turn to "not installed" after upgrading to 6.2.0.
Version-Release number of selected component (if applicable): snap 16.0
How reproducible: every time
Steps to Reproduce:
1. register content host to 6.1, ensure katello agent is installed and sat says that katello agent is installed in the host details page
2. upgrade
3. restart goferd on content host, view host details status
Actual results: katello-agent is marked as not installed
If you run "rm /var/lib/rhsm/packages/packages.json && katello-package-upload" on the host, katello-agent will be marked as being installed again.
NOTE: this field is purely informational, and will eventually fix itself the next time a yum operation occurs on the content host.