Code Manager queued environments

[Jonathan Gazeley]

I'm dabbling with a new PE 2016.4 installation as I'm hoping to finally
migrate away from Puppet 3.

We're using code manager rather than r10k to deploy environments from
git using a commit hook from GitLab. This was all working fine until
about a week ago when it stopped deploying code and started saying that
each environment was "queued".

[root@puppet4-dev ~]# puppet-code deploy --all
Deploying all environments.
[{"environment":"242_mod_suexec","id":1,"status":"queued"},{"environment":"249_postfix_message_size_limit","id":2,"status":"queued"},{"environment":"avoid_uob_dc10","id":3,"status":"queued"},{"environment":"f5_ipv6_dns","id":4,"status":"queued"},{"environment":"gitlab_ci","id":5,"status":"queued"},{"environment":"logwatch_ignore","id":6,"status":"queued"},{"environment":"nagios_api","id":7,"status":"queued"},{"environment":"pe","id":8,"status":"queued"},{"environment":"production","id":9,"status":"queued"},{"environment":"sauron","id":10,"status":"queued"},{"environment":"splay","id":11,"status":"queued"}]

Anyone know what this means or how to fix it? I couldn't find any
documentation to explain about queued environments, but this is
currently a blocker on my project :(

Thanks,
Jonathan

--
Jonathan Gazeley
Senior Systems Administrator
IT Services
University of Bristol

[Anderson Mills]

Jonathan,

What happens if you use

puppet-code deploy --all --wait

???

[Alex Dreyer]

By default the `puppet code deploy` command starts the deploy but doesn't wait for it to finish so it's normal for the command to return with all environments queued.  If deploys are not completing you can run `puppet-code deploy --all --wait` to wait for the deploy to finish and see any errors or look errors logged in /var/log/puppetlabs/puppetserver/puppetserver.log on the puppetmaster

[Jonathan Gazeley]

On 29/11/16 23:01, Anderson Mills wrote:
>
> What happens if you use
>
> puppet-code deploy --all --wait

This worked. Apparently it was taking quite a long time to deploy and I
was too impatient before checking to see what had been deployed, and I
didn't release that it didn't wait unless you specified --wait.