Updating from 3.2.4 to 3.7.4 problem with exported resources

45 views
Skip to first unread message

Marc

unread,
Feb 26, 2015, 9:18:22 AM2/26/15
to puppet...@googlegroups.com
Hi all,

This is my current situation:

Master A has:
 - port 8140
 - puppet server 3.2.4
 - puppetdb terminus 1.6.2

Master B has:
 - port 8141
 - puppet server 3.7.4
 - puppetdb terminus 1.6.2

PuppetDB has:
 - puppetdb 1.6.2

Client has:
 - puppet client 3.2.4

And my node manifest is:

node 'marc-test.demo.lan' {

    @@file { '/tmp/foo/bar':
        ensure => present,
    }   
}

Where '/tmp/foo' does not exist.

So, given the above information, if I issue the following command in the client, everything works as expected:

[ro...@marc-test.demo ~]# puppet agent -t --environment marc_villacorta --masterport 8140
...
Info: Applying configuration version '1424959728'
Notice: Finished catalog run in 19.06 seconds

But when I try the same against the 3.7.4 master the managed node attempts to realize the exported resource:

[ro...@marc-test.demo ~]# puppet agent -t --environment marc_villacorta --masterport 8141
...
Info: Applying configuration version '1424959869'
Error: Could not set 'present' on ensure: No such file or directory - /tmp/foo/bar at 5:/etc/puppet/environments/marc_villacorta/manifests/nodes/marc-test.demo.lan.pp
Error: Could not set 'present' on ensure: No such file or directory - /tmp/foo/bar at 5:/etc/puppet/environments/marc_villacorta/manifests/nodes/marc-test.demo.lan.pp
Wrapped exception:
No such file or directory - /tmp/foo/bar
Error: /Stage[main]//Node[marc-test.demo.lan]/File[/tmp/foo/bar]/ensure: change from absent to present failed: Could not set 'present' on ensure: No such file or directory - /tmp/foo/bar at 5:/etc/puppet/environments/marc_villacorta/manifests/nodes/marc-test.demo.lan.pp
Notice: Finished catalog run in 98.65 seconds

I have tried to update the client to 3.7.4 but I get the same result.
My puppet infrastructure is about 4 years old maybe I have configs with deprecated stuff ...

Any idea? A bug perhaps?

Cheers
Marc

Marc

unread,
Feb 26, 2015, 11:28:12 AM2/26/15
to puppet...@googlegroups.com
Update:

Looks like whatever is affecting me was introduced in puppet server 3.6.2

3.2.4 Works
3.3.2 Works
3.4.3 Works
3.5.1 Works
3.6.0 Works
3.6.1 Works
3.6.2 Fails
3.7.3 Fails
3.7.4 Fails

The release notes for 3.6.2:

Puppet 3.6.2
Security Fixes
Feature: Disabling Deprecation Warnings
Fix for Directory Environments Under Webrick
Fixes to purge_ssh_keys
Default environment_timeout increased
General Bug Fixes

Not sure where to start looking but we use config-files environments ...
I think I will update to 3.6.1 and start hunting deprecation warnings from there.

Thanks,
Marc
Reply all
Reply to author
Forward
0 new messages