Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
PUP 5.3.5, PUP 5.5.0
-
None
-
CentOS 7.4, Puppet Enterprise 2017.3.5 (puppet-agent 5.3.5)
-
-
Coremunity
-
Platform Core KANBAN
-
Needs Assessment
-
Bug Fix
-
The "puppet module" application reported an incorrect URL in error messages if the "module_repository" setting was overridden.
-
Needs Assessment
Description
We had a problem with our artifactory server, where it would return a 404 for the Puppet repository it was providing. This caused an error message to appear, about 404 errors. I tried to install the module manually (or search for it) and also got a 404 error:
[root@puppetmaster ~]# puppet module --debug search saz-sudo |
Debug: Runtime environment: puppet_version=5.3.5, ruby_version=2.4.3, run_mode=user, default_encoding=UTF-8 |
Notice: Searching https://artifactory.domain.com/artifactory/api/puppet/puppet ... |
Debug: HTTP GET https://artifactory.domain.com/artifactory/api/puppet/puppet/artifactory/api/puppet/puppet/v3/modules?query=saz-sudo&module_groups=base%20pe_only |
Error: Request to Puppet Forge failed.
|
The server being queried was https://artifactory.domain.com/v3/modules?query=saz-sudo&module_groups=base%20pe_only |
The HTTP response we received was '404 ' |
Error: Try 'puppet help module search' for usage |
Â
Before adding the debug flag, I thought that the puppet module tool was loosing the "path" part of the "module_repository" configuration when it read it from the puppet.conf, vs when it was specified on the command line. This was not the case, but it led to a lot of pointless troubleshooting. The error message should have the correct URL that failed.
Â
NOTICE the difference between:
Debug: HTTP GET https://artifactory.domain.com/artifactory/api/puppet/puppet/artifactory/api/puppet/puppet/v3/modules?query=saz-sudo&module_groups=base%20pe_only |
... and:
The server being queried was https://artifactory.domain.com/v3/modules?query=saz-sudo&module_groups=base%20pe_only |
Â
Attachments
Issue Links
- relates to
-
-
- Closed
-
