New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update rhsm.conf template #85
Comments
Hi @kallies, thanks for reporting this. Are you able to provide a PR for it? |
kallies
added a commit
to kallies/puppet-rhsm
that referenced
this issue
Feb 21, 2019
…oxpupuli#85) Add defaults from subscription-manager 1.21.10
kallies
added a commit
to kallies/puppet-rhsm
that referenced
this issue
Feb 22, 2019
…oxpupuli#85) Add defaults from subscription-manager 1.21.10
kallies
added a commit
to kallies/puppet-rhsm
that referenced
this issue
Feb 25, 2019
…oxpupuli#85) Add defaults from subscription-manager 1.21.10
kallies
added a commit
to kallies/puppet-rhsm
that referenced
this issue
Sep 11, 2019
…oxpupuli#85) Add defaults from subscription-manager 1.21.10
kallies
added a commit
to kallies/puppet-rhsm
that referenced
this issue
Oct 10, 2019
…oxpupuli#85) Add defaults from subscription-manager 1.21.10
kallies
added a commit
to kallies/puppet-rhsm
that referenced
this issue
Oct 25, 2019
…oxpupuli#85) Add defaults from subscription-manager 1.21.10
kallies
added a commit
to kallies/puppet-rhsm
that referenced
this issue
Oct 25, 2019
…oxpupuli#85) Add defaults from subscription-manager 1.21.10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current subscription-manager packages (e.g. 1.21.10-3.el7_6) deliver an updated
rhsm.conf
. Therefore the template should be updated. New values are:See also https://github.com/candlepin/subscription-manager/blob/master/etc-conf/rhsm.conf#L86
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
Removal of default parameters
What behaviour did you expect instead
Keeping defaults.
Output log
The text was updated successfully, but these errors were encountered: