Skip to content
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

puppet enterprise 3.7.0 webhook (no mcollective) ordering problem #138

Closed
jguice opened this issue Feb 24, 2015 · 3 comments
Closed

puppet enterprise 3.7.0 webhook (no mcollective) ordering problem #138

jguice opened this issue Feb 24, 2015 · 3 comments
Labels
bug Something isn't working

Comments

@jguice
Copy link

jguice commented Feb 24, 2015

On a fresh PE 3.7.0 install, applying the 2 webhook classes from the "Running without mcollective" readme example, the peadmin-cert.pem file gets created after the webook.service tries to start.

I see the notify => Service['webhook'] line in r10k/webhook.pp but somehow the final ordering is incorrect:

Notice: Compiled catalog for localhost in environment production in 1.87 seconds
Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
   (at /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/type/package.rb:430:in `block (3 levels) in <module:Puppet>')
Notice: /Stage[main]/R10k::Webhook::Config/File[webhook.yaml]/ensure: defined content as '{md5}56892e29ef349b136bc87a90ac2a03c0'
Notice: /Stage[main]/R10k::Webhook/File[/var/log/webhook]/ensure: created
Notice: /Stage[main]/R10k::Webhook/File[/var/run/webhook]/ensure: created
Notice: /Stage[main]/R10k::Webhook/Package[sinatra]/ensure: created
Notice: /Stage[main]/R10k::Webhook/File[webhook_init_script]/ensure: defined content as '{md5}a00a01080483a584413933000edad83e'
Notice: /Stage[main]/R10k::Webhook/File[webhook_bin]/ensure: defined content as '{md5}4fc99661c62c267609bd9507fbafcd71'
Error: Could not start Service[webhook]: Execution of '/usr/bin/systemctl start webhook' returned 1: Job for webhook.service failed. See 'systemctl status webhook.service' and 'journalctl -xn' for details.
Wrapped exception:
Execution of '/usr/bin/systemctl start webhook' returned 1: Job for webhook.service failed. See 'systemctl status webhook.service' and 'journalctl -xn' for details.
Error: /Stage[main]/R10k::Webhook/Service[webhook]/ensure: change from stopped to running failed: Could not start Service[webhook]: Execution of '/usr/bin/systemctl start webhook' returned 1: Job for webhook.service failed. See 'systemctl status webhook.service' and 'journalctl -xn' for details.
Notice: /Stage[main]/R10k::Webhook/Service[webhook]: Triggered 'refresh' from 2 events
Notice: /Stage[main]/R10k::Webhook/File[peadmin-cert.pem]/ensure: defined content as '{md5}79da222bdd112f5a0fd567be2a4d4dfc'
Notice: Finished catalog run in 13.92 seconds

Applying the classes again of course works since the file is now there ahead of service startup.

@acidprime
Copy link
Collaborator

@jguice did you download the module from the forge, I am about to cut a release that should fix this

@acidprime
Copy link
Collaborator

@acidprime acidprime added the bug Something isn't working label Feb 24, 2015
@jguice
Copy link
Author

jguice commented Feb 24, 2015

Ah, yeah I did (should have specified which version I was using). Thanks!!

acidprime pushed a commit that referenced this issue Feb 25, 2015
Prior to this commit our statement was wrong, this was not noticed
expect for non-upgraded users using the latest versino of the module
Also the spec tests had a typo which let this split through and this
is corrected
@acidprime acidprime reopened this Feb 25, 2015
acidprime pushed a commit that referenced this issue Feb 26, 2015
Prior to this commit I was missing the pe-admin-cert in the specs
and had a typo which was fixed in the previous commit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants