Investigate "could not set 'file' on ensure" issues

[rmccue]

I've heard this one a couple of times now. Let's try and track it down:

==> default: Error: Could not set 'file' on ensure: No such file or directory - /etc/nginx/sites-available/hm-vip.local20161201-2324-iydb4v.lock at 22:/vagrant/puppet/modules/chassis/manifests/network.pp
==> default:
==> default: Error: Could not set 'file' on ensure: No such file or directory - /etc/nginx/sites-available/hm-vip.local20161201-2324-iydb4v.lock at 22:/vagrant/puppet/modules/chassis/manifests/network.pp
==> default: Wrapped exception:
==> default: No such file or directory - /etc/nginx/sites-available/hm-vip.local20161201-2324-iydb4v.lock
==> default: Error: /Stage[main]/Main/Chassis::Wp[hm-vip.local]/Chassis::Network[hm-vip.local]/File[/etc/nginx/sites-available/hm-vip.local]/ensure: change from absent to file failed: Could not set 'file' on ensure: No such file or directory - /etc/nginx/sites-available/hm-vip.local20161201-2324-iydb4v.lock at 22:/vagrant/puppet/modules/chassis/manifests/network.pp

[rmccue]

Seems to be fixed per @mattheu's testing, but reopen this if it pops back up again.