We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After updating to Puppet 3.5.0, I get this error message.
Error: Failed to apply catalog: Parameter proxy failed on Yumrepo[epel-testing]: Must be a valid URL at /etc/puppet/modules/epel/manifests/init.pp:24
This might be a regression in puppet, because the docs say that absent is acceptable, instead of a well formed URL. http://docs.puppetlabs.com/references/latest/type.html#yumrepo-attribute-proxy
absent
As a workaround, I have commented out the "proxy" lines in the EPEL module in my installation, and that allows the puppet run to succeed.
The text was updated successfully, but these errors were encountered:
I'm nearly certain it's a regression introduced in Puppet 3.5. https://github.com/puppetlabs/puppet/blob/3.5.0/lib/puppet/type/yumrepo.rb#L206
Here's a related issue already logged in the Puppet tracker: https://tickets.puppetlabs.com/browse/PUP-2162
So I'm going to close this issue now.
Sorry, something went wrong.
No branches or pull requests
After updating to Puppet 3.5.0, I get this error message.
Error: Failed to apply catalog: Parameter proxy failed on Yumrepo[epel-testing]: Must be a valid URL at /etc/puppet/modules/epel/manifests/init.pp:24
This might be a regression in puppet, because the docs say that
absent
is acceptable, instead of a well formed URL. http://docs.puppetlabs.com/references/latest/type.html#yumrepo-attribute-proxyAs a workaround, I have commented out the "proxy" lines in the EPEL module in my installation, and that allows the puppet run to succeed.
The text was updated successfully, but these errors were encountered: