Hide Forgot
Created attachment 565324 [details] katello-debug output Description of problem: I've registered a system with katello that has some errata outstanding. When I run "yum check-update" on the commandline, I see the following updates available: [root@localhost ~]# yum check-update Loaded plugins: product-id, security, subscription-manager Updating certificate-based repositories. rhel-6-server-rpms | 3.8 kB 00:00 libpng.x86_64 2:1.2.46-2.el6_2 rhel-6-server-rpms libxml2.x86_64 2.7.6-4.el6_2.4 rhel-6-server-rpms libxml2-python.x86_64 2.7.6-4.el6_2.4 rhel-6-server-rpms passwd.x86_64 0.77-4.el6_2.2 rhel-6-server-rpms No errata show up in the "Errata" tab under the system in Katello, though. Version-Release number of selected component (if applicable): subscription-manager-0.96.17-1.el6.x86_64 (client) katello-0.1.238-4.el6.noarch (server) How reproducible: Not sure Steps to Reproduce: 1. Register a system to katello using "subscription-manager register" 2. Find the system in the katello UI and navigate to errata. 3. Compare the results of a "yum check-update" on the client with the errata listed in the UI. Actual results: No errata appear in the UI Expected results: Applicable errata should be available. Additional info: This might just be a registration issue - there are no products showing up in the subscription-manager list output. But, if there are no products, why does yum show available updates?
Created attachment 565325 [details] output of "subscription-manager list" on the client
It is possible that this is an issue with the version of katello-agent installed on the client. The agent is responsible for sending updates to System Engine when the redhat.repo is updated to inform it of the repos the client is using. System Engine will use this info to bind the system to the repo, enabling the UI to properly display the list of errata associated with that system. To support the above, katello-agent-0.15-1.el6.noarch or later is needed. Can you confirm what version of katello-agent is installed on the system?
Well, I was running katello-agent-0.13-2.el6.noarch, but I've updated to katello-agent-0.15-1.el6.noarch, unregistered and reregistered and I'm still having the same issue.
I've reproduced on a second client and a freshly reinstalled katello instance using the latest build. Let me know if there's any more information I can provide. Michael.
Michael, thanks for letting me log in and look over the client. It appears that the issue was that the goferd service was not running on the client. After installing the katello-agent, this service needs to be started. One of the responsibilities of the agent is to inform the server of the repos that are enabled (in redhat.repo). This allows the server to determine which errata apply to the client.
For now, going to close this one as 'not a bug', since the issue appeared to be related to goferd not running. If needed, it can be reopened.
getting rid of 6.0.0 version since that doesn't exist