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.

Sign up for GitHub

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

Jump to bottom

docker::run ensure=>absent always fails on new nodes #611

Open
jorhett opened this issue Dec 16, 2016 · 2 comments
Open

docker::run ensure=>absent always fails on new nodes #611

jorhett opened this issue Dec 16, 2016 · 2 comments

Comments

@jorhett
Copy link

jorhett commented Dec 16, 2016 •
edited
Loading

#After deploying a change which removes a container, Puppet runs fail on new Trusty nodes that never had the container deployed.

Error: /Stage[main]/Node/Docker::Run[python-github-webhooks]/Service[docker-python-github-webhooks]: Could not evaluate: Could not find init script or upstart conf file for 'docker-python-github-webhooks'

Shouldn't absent quietly do nothing? Seems like it should check for the service and skip the stop step if it doesn't exist...
@twardnw
Copy link

twardnw commented Jan 19, 2017

I too am seeing this same behavior. I would also expect it to quietly do nothing if the resource is already absent

@twardnw
Copy link

twardnw commented Jan 19, 2017

mmm, appears this is an issue with the Service resource and limited to debian

https://projects.puppetlabs.com/issues/17286

cegeka-jenkins pushed a commit to cegeka/puppet-docker that referenced this issue Apr 17, 2024
@sheenaajay
Merge pull request garethr#611 from puppetlabs/pdksync_abs
0031298 
pdksync - Use abs instead of vmpooler to provision test resources
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@twardnw @jorhett