Code Manager requires coordination between multiple components, including r10k and the file sync service. If you are having problems with Code Manager, this page can help you isolate the problem.
Code Manager logs to the Puppet Server log. By default, this log is in /var/log/puppetlabs/puppetserver/puppetserver.log. For more information about working with Puppet Server logs, see Puppet Server log documentation.
Rule out these common issues before proceeding with more in-depth troubleshooting.
In releases before PE 2016.2, proxies were supported only for Forge modules. To use proxies to access modules from other sources, upgrade to PE 2016.2 or greater.
If your environments are heavily loaded, code deployments can take a long time. If your deployments are timing out too soon, increase your timeouts_deploy key. You might also need to increase timeouts_shutdown and timeouts_wait.
Code Manager code deployment involves accessing many small files. If you store your Puppet code on network-attached storage, slow network or backend hardware can result in poor deployment performance. Tune the network for many small files, or store Puppet code on local or direct-attached storage.
If your code deployment works, but a class you added isn’t in the console:
Check the code management known issues page for additional known issues related to Code Manager, r10k, and file sync.
To troubleshoot Code Manager further, follow these steps:
The control repository controls the creation of Puppet environments, and ensures that the correct versions of all the necessary Puppet modules are installed. The Puppet master server must be able to access and clone the control repo as the pe-puppet user.
To make sure that Code Manager can connect to the control repo, run:
sudo -H -u pe-puppet bash -c \
'/opt/puppetlabs/puppet/bin/r10k deploy display --fetch -c /opt/puppetlabs/server/data/code-manager/r10k.yaml'
This command returns a list of the environments in the control repo.
If the command completes successfully, the SSH key has the correct permissions, the Git URL for the repository is correct, and the pe-puppet user can perform the operations involved.
If the command does not complete successfully, it returns a path that you can use for debugging the SSH key and Git URL.
Check the Puppetfile for syntax errors and verify that every module in the Puppetfile can be installed from the listed source. To do this, you’ll need a copy of the Puppetfile in a temporary directory:
/var/tmp/test-puppetfile on the master for testing purposes.You can then check the syntax and listed sources in your Puppetfile.
To check the Puppetfile syntax, run r10k puppetfile check from within the temporary directory.
If you have Puppetfile syntax errors, correct the syntax and test again. When the syntax is correct, the command prints “Syntax OK”.
To test the configuration of all sources listed in your Puppetfile, perform a test installation. This test installs the modules listed in your Puppetfile into a modules directory in the temporary directory.
In the temporary directory, run the following command:
sudo -H -u pe-puppet bash -c \
'/opt/puppetlabs/puppet/bin/r10k puppetfile install'
This installs all modules listed in your Puppetfile, verifying that you can access all listed sources. Take note of all errors that occur. Issues with individual modules can cause issues for the entire environment. Errors with individual modules (such as Git URL syntax or version issues) show up as general errors for that module.
If you have modules from private Git repositories requiring an SSH key to clone the module, check that you are using the SSH Git URL and not the HTTPS Git URL.
After you’ve fixed errors, test again and fix any further errors, until all errors are fixed.
Manually run a full r10k deployment to check not only the Puppetfile syntax and listed host access, but also whether the deployment will work through r10k.
This command attempts a full r10k deployment based on the r10k.yaml file that Code Manager uses. This test writes to the code-staging directory only. This does not trigger a file sync and should be used only for ad-hoc testing.
Run this deployment test with the following command:
sudo -H -u pe-puppet bash -c \
'/opt/puppetlabs/puppet/bin/r10k deploy environment -c /opt/puppetlabs/server/data/code-manager/r10k.yaml -p -v debug'
If this command completes successfully, the /etc/puppetlabs/code-staging directory is populated with directory-based environments and all of the necessary modules for every environment.
If the command fails, the error is likely in the r10k-specific Code Manager settings. The error messages indicate which settings are failing.
Issues that occur when a Code Manager deployment is triggered by the webhook or the /v1/deploys endpoint can be tricky to isolate. Monitor the logs for the deployment trigger to find the issue.
Deployments triggered by a webhook in Stash/Bitbucket, GitLab, or Github are governed by authentication and hit each service’s /v1/webhook endpoint.
If you are using a GitLab version less than 8.5.0, Code Manager webhook authentication does not work because of the length of the authentication token. To use a Code Manager webhook with GitLab, either disable authentication or update Gitlab.
Note: If you disable webhook authentication, it is disabled only for the
/v1/webhookendpoint. Other endpoints (such as/v1/deploys) are still controlled by authentication. There is no way to disable authentication on any other Code Manager endpoint.
To troubleshoot webhook issues, follow the Code Manager webhook instructions while monitoring the Puppet Server log for successes and errors. To do this, open a terminal window and run:
tail -f /var/log/puppetlabs/puppetserver/puppetserver.log
Watch the log closely for errors and information messages when you trigger the deployment. The puppetserver.log log file is the only location these errors will appear.
If you cannot determine the problem with your webhook in this step, manually deploy to the /v1/deploys endpoint, as described in the next section.
/v1/deploys endpoint log errorsBefore you trigger a deployment to the /v1/deploys endpoint, generate an authentication token. Then deploy one or more environments with the following command:
curl -k -X POST -H 'Content-Type: application/json' \
-H "X-Authentication: `cat ~/.puppetlabs/token`" \
https://<URL.OF.CODE.MANAGER.SERVER>:8170/code-manager/v1/deploys \
-d '{"environments": ["<ENV_NAME>"], "wait": true}'
This request waits for the deployment to complete ("wait": true) and so returns errors from the deployment.
Alternatively, you can deploy all environments with the following curl command:
curl -k -X POST -H 'Content-Type: application/json' \
-H "X-Authentication: `cat ~/.puppetlabs/token`" \
https://<URL.OF.CODE.MANAGER.SERVER>:8170/code-manager/v1/deploys \
-d '{"deploy-all": true, "wait": true}'
Monitor the console-services.log file for any errors that arise from this curl command.
tail -f /var/log/pe-console-services/console-services.log