Problem: Host is forever complaining about “Could not calculate errata status, ensure host is registered and the katello-host-tools package is installed”
Expected outcome: Should go to green after the Katello Agent (which is installed) does its thing
**Foreman and Proxy versions:**2.1 dont tknow what a proxy is, I just have a single test server
**Foreman and Proxy plugin versions:**with everything installed with foreman-install
**Distribution and version:**cent OS CentOS Linux 7.8.2003
Other relevant data:
So on three occasions with test clients I get a orange status. Leaving it for > 24 hours does nothing. Yet when I sync a single repo the staus turns green. However the repo will then then show zero packages and errata available.
Is there a link between the OS Kattelo thinks the client is, and the repo packages/content view, or whatever it is called?
I should add that I have updated packages using katello and it works but did not fix the status problem.
Also I am now using remote execute, and wondering if it may be an option to use that instead, but does it check the errata and stuff?
Hello,
I’ve seen a few other posts such as yours which points out some of the confusion around the errata status messaging. I opened a PR to help clarify it, and your input is welcome: https://github.com/Katello/katello/pull/8845
To get errata status showing properly you need
- your content host to be registered (subscription-manager register)
- your content host to have 1+ repositories enabled
- your content host to be submitting its enabled repo and installed package data (this is done in newer installations by subscription-manager itself, whereas katello-host-tools took care of it in the past and still does on very old clients)
2 Likes
Okay I bring a “solution”, not a question. The solution may be a workaround or a demonstration of my misunderstanding of foreman/katello (I wish I knew where one started and the other one ended).
setup: Virgin install of centOS7. Followed by 3.16 instructions on client install (Kattello server install also 3.16rc4).
Issue: client status is “forever” at “Could not calculate errata status, ensure host is registered and the katello-host-tools package is installed””
"Solution"???:. If I go to “sync all” repositories and the process takes several seconds, the host turns green with “Errata–All errata applied” . If the sync takes mere seconds it says “orange”, however if I go to Products-> “Advanced Sync”-> “Complete Sync” (and wait), it turns green. I think it is obvious why certain syncs take longer than others, however what I don’t understand is why this “syncing” needs to be done to get it to work.
I have now done this with 7 test host servers and it worked every-time. (“complete sync” had to be done twice). If this is an issue it could be the foreman server but it is a fairly clean build.
By the way, the reason some repo contents showed “0” on sync (see OP) was low disk space on my server (the sync did not report errors though).
Hello to the historians of the future.
1 Like
To be clear
“If this is an issue it could be the foreman server but it is a fairly clean build.”
meant
“If this is an issue it could be MY foreman server but it is a fairly clean build.”
