Actions
Bug #34813
closed
Investigation: `bound_repositories` not getting updated outside of client profile uploads
Description
I've been seeing a number of user issues lately that point to bound repositories not being updated properly for hosts. I noticed that the only way to have a host's bound repositories update is via a profile upload from the host. When a host is first registered or if it changes CV/LCE, applicability can be out of date due to incorrect bound repositories.
Here's a related user case: https://community.theforeman.org/t/foreman-centos7-errata-processing/26925/11
The user reported having no trouble on Katello 4.1, so perhaps a bug was introduced relating to bound repositories after that.
Updated by Chris Roberts almost 2 years ago
- Status changed from New to Closed
- Target version set to Katello Recycle Bin
- Triaged changed from No to Yes
After discussion with the community user, it was determined this was a workflow issue.
Actions