Jira (PUP-9728) `puppet device --apply` no such file, state.yaml.lock

[David Armstrong (JIRA)]

David Armstrong created an issue

Puppet / PUP-9728 `puppet device --apply` no such file, state.yaml.lock Issue Type: Bug Assignee: Unassigned Created: 2019/06/04 8:00 AM Priority: Normal Reporter: David Armstrong Puppet Version: 6.0.x **** This issue appears to be linked to https://tickets.puppetlabs.com/browse/PUP-8632 and https://tickets.puppetlabs.com/browse/PUP-9047   `Failed to apply catalog: No such file or directory @ dir_s_mkdir - /var/lib/jenkins/.puppetlabs/opt/puppet/cache/devices/sut/state/state.yaml20190604-1254-pmanfh.lock`   The following error can be found here: https://travis-ci.org/puppetlabs/puppet-resource_api/jobs/539161320 +Notice: Compiled catalog for the_node in environment production in 0.01 seconds +Info: Applying configuration version '1559214109' +Info: Creating state file /home/travis/.puppetlabs/opt/puppet/cache/devices/the_node/state/state.yaml +Error: Failed to apply catalog: No such file or directory @ dir_s_mkdir - /home/travis/.puppetlabs/opt/puppet/cache/devices/the_node/state/state.yaml20190530-11941-ex9ryg.lock +/home/travis/build/puppetlabs/puppet-resource_api/vendor/bundle/ruby/2.5.0/bundler/gems/puppet-441b417f69d4/lib/puppet/file_system/uniquefile.rb:182:in `mkdir' +/home/travis/build/puppetlabs/puppet-resource_api/vendor/bundle/ruby/2.5.0/bundler/gems/puppet-441b417f69d4/lib/puppet/file_system/uniquefile.rb:182:in `mkdir' +/home/travis/build/puppetlabs/puppet-resource_api/vendor/bundle/ruby/2.5.0/bundler/gems/puppet-441b417f69d4/lib/puppet/file_system/uniquefile.rb:175:in `locking' +/home/travis/build/puppetlabs/puppet-resource_api/vendor/bundle/ruby/2.5.0/bundler/gems/puppet-441b417f69d4/lib/puppet/file_system/uniquefile.rb:38:in `block in initialize' +/home/travis/build/puppetlabs/puppet-resource_api/vendor/bundle/ruby/2.5.0/bundler/gems/puppet-441b417f69d4/lib/puppet/file_system/uniquefile.rb:134:in `create_tmpname' +/home/travis/build/puppetlabs/puppet-resource_api/vendor/bundle/ruby/2.5.0/bundler/gems/puppet-441b417f69d4/lib/puppet/file_system/uniquefile.rb:28:in `initialize'   Also observed https://jenkins-platform.delivery.puppetlabs.net/job/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM=panos71-64,WORKER_LABEL=beaker/87/console 15:06:15 +Notice: panos_commit[commit]: Updating: Finished in 22.55 seconds 15:06:15 +Debug: /Stage[main]/Main/Panos_commit[commit]: The container Class[Main] will propagate my refresh event 15:06:15 +Debug: Class[Main]: Skipping host resources because running on a device 15:06:15 +Debug: Class[Main]: Resource is being skipped, unscheduling all events 15:06:15 +Info: Class[Main]: Unscheduling all events on Class[Main] 15:06:15 +Debug: Stage[main]: Skipping host resources because running on a device 15:06:15 +Debug: Stage[main]: Resource is being skipped, unscheduling all events 15:06:15 +Debug: /Filebucket[puppet]: Skipping host resources because running on a device 15:06:15 +Debug: /Filebucket[puppet]: Resource is being skipped, unscheduling all events 15:06:15 +Debug: Storing state 15:06:15 +Info: Creating state file /var/lib/jenkins/.puppetlabs/opt/puppet/cache/devices/sut/state/state.yaml 15:06:15 +Debug: Pruned old state cache entries in 0.00 seconds 15:06:15 +Error: Failed to apply catalog: No such file or directory @ dir_s_mkdir - /var/lib/jenkins/.puppetlabs/opt/puppet/cache/devices/sut/state/state.yaml20190604-1254-pmanfh.lock 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/file_system/uniquefile.rb:182:in `mkdir' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/file_system/uniquefile.rb:182:in `mkdir' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/file_system/uniquefile.rb:175:in `locking' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/file_system/uniquefile.rb:38:in `block in initialize' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/file_system/uniquefile.rb:134:in `create_tmpname' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/file_system/uniquefile.rb:28:in `initialize' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/util.rb:586:in `new' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/util.rb:586:in `replace_file' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/util/yaml.rb:68:in `dump' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/util/storage.rb:98:in `block in store' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/util.rb:231:in `block in benchmark' 15:06:15 +/usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/benchmark.rb:308:in `realtime' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/util.rb:230:in `benchmark' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/util/storage.rb:97:in `store' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/resource/catalog.rb:246:in `ensure in apply' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/resource/catalog.rb:246:in `apply' 15:06:15 +/tmp/jenkins/workspace/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/PLATFORM/panos71-64/WORKER_LABEL/beaker/.bundle/gems/bundler/gems/puppet-a5f7e82537cd/lib/puppet/configurer.rb:192:in `block (2 levels) in apply_catalog' Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Josh Cooper (JIRA)]

Josh Cooper commented on PUP-9728

Re: `puppet device --apply` no such file, state.yaml.lock This should be fixed by https://github.com/puppetlabs/puppet/pull/7550 We can probably close this since we haven't released a version of puppet with the regression. But we can keep it open until CI is green.

Add Comment

[David Mallon (JIRA)]

David Mallon updated an issue

Puppet / PUP-9728

`puppet device --apply` no such file, state.yaml.lock

Change By: David Mallon Team: Network Automation

Add Comment

[David Mallon (JIRA)]

David Mallon commented on PUP-9728

Re: `puppet device --apply` no such file, state.yaml.lock Hey Josh Cooper does that PR need merged up anywhere else? We are still seeing this failure on nightly builds

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper commented on PUP-9728

Re: `puppet device --apply` no such file, state.yaml.lock

Hey David Mallon the linked jenkins job used: 07:01:38 Using puppet 6.0.10 from https://github.com/puppetlabs/puppet.git (at 6.0.x@a5f7e82) but the device change wasn't merged to 6.0.x until 809606160d. So I'd expect future runs to pass. Let me know if that's not the case!

Add Comment