Either of the 2 fixes, on the Katello server or the container_gateway plugin on smart proxy will resolve the issue. Let us know if you’re still seeing any issues.
Hi can you confirm these fixes were added to the repo please? I upgraded to 3.16 w/katello yesterday and need to know if a manual fix is needed on top. thanks. I also presume no sync issues were found at all during the testing phase?
Thanks for asking..Looks like the 2 fixes are still in flight release-wise..I will see if we can get those out of the door quickly.
Okay this shows a few dozens of hosts in our system. How should we fix the records for:
- Hosts that don’t subscribe to content.
- Hosts that are consuming content (register?)
For unregistered hosts, a null subscription_uuid is expected. For hosts that need content, reregistering should resolve it, yes.
At this point, I too am seeing these failed sync’s on a couple of my proxy servers since upgrading to 3.16.2. What exactly is the solution to this issue? I’ve read through this thread, but I’m not 100% clear on how to resolve the issue. Thanks in advance for any clarification and solution.
On one of my proxies, I see the following ERROR msg in the /var/log/foreman-proxy/proxy.log file:
2026-01-26T17:06:14 fc199c5b [W] Error processing request 'fc199c5b-b727-457f-ba7b-2dc3f929d90d: Sequel::NotNullConstraintViolation: PG::NotNullViolation: ERROR: null value in column “uuid” of relation “hosts” violates not-null constraint
DETAIL: Failing row contains (53, null).
How would I determine which host this culprit is?
When I search in the Foreman UI for any hosts that have a null subscription_uuid, I get no results. Some of the searches I use are:
subscription_uuid = “null”
subscription_uuid = null
subscription_uuid = “”
subscription_uuid =
If I understand this correctly there is a fix in Fixes #38862 - Handle nil host UUIDs properly by sjha4 · Pull Request #60 · Katello/smart_proxy_container_gateway · GitHub due to be released in the next release of Katello 4.18.2.
Looking forward to it.
1 Like
I wonder if updating Foreman to 3.17 and Katello to 4.19 would resolve the issue?
I don’t know how the smart_proxy_container_gateway repo gets included in the Katello release (dev please enlighten us) so I can’t answer that question. I have yet to upgrade in my setup to test.
I have just ran into the same exception, caused by a host which has been created and configured in foreman, but hasn’t been built, yet. Changing the content source for this host allowed me to get the sync working again…