You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As stated by @alexjfisher in #53subscription-manager might lead to long puppet runs and - in case RHSM/Satellite 6 is down - might lead to issues when relying on the resulting facts:
If the Satellite server (or RHSM) is not accessible or sends http errorcodes.
Not accessible: Puppet runs are stale until subscription-manager times out (default timeout is 180s per http request and subscription-manager repos --list-enabled triggers ~7 requests)
Satellite/RHSM frontend answers with http errorcode: fact returns empty array -> if someone (like we do) evaluates this fact to enable repos, Puppet tries to enable all repos (again - not a big issue but def. not a nice behaviour).
We were thinking about a caching mechanism which addresses these two issues.
Instead of calling subscription-manager or yum the file /etc/yum.repos.d/redhat.repo should be evaluated
".. or search for enabled = 1 and all sections without enabled
This should also address both issues.
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: >=4
Ruby: generic
Distribution: RHEL
Module version: 3.2.1-rc0/master
How to reproduce (e.g Puppet code you use)
As described in README.md
What are you seeing
Slow puppet runs (>10s for subscription-manager), issues when Satellite 6 is not available or - even worse - partially available.
The text was updated successfully, but these errors were encountered:
As stated by @alexjfisher in #53
subscription-manager
might lead to long puppet runs and - in case RHSM/Satellite 6 is down - might lead to issues when relying on the resulting facts:If the Satellite server (or RHSM) is not accessible or sends http errorcodes.
subscription-manager
times out (default timeout is 180s per http request andsubscription-manager repos --list-enabled
triggers ~7 requests)We were thinking about a caching mechanism which addresses these two issues.
Instead of calling
subscription-manager
oryum
the file/etc/yum.repos.d/redhat.repo
should be evaluated".. or search for
enabled = 1
and all sections withoutenabled
This should also address both issues.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
As described in README.md
What are you seeing
Slow puppet runs (>10s for
subscription-manager
), issues when Satellite 6 is not available or - even worse - partially available.The text was updated successfully, but these errors were encountered: