OK - I found the issue. Because 2.6.x gives us nice human readable(ish)
catalogs, I compiled mine and the 'random' hits were all for directories.
Re-reading the manifest, I see those directories in the error messages all
had "type => directory", like
file { "/var/empty":
ensure => 'directory',
*type => 'directory',*
mode => 755,
Seems 2.6.5 is being a bit tighter
Anyway - all is well after deleting these types.
John
On 8 February 2011 09:46, John Warburton <jwarbur...@gmail.com> wrote:
> Let me get back to you on this. The server is still 2.6.4!
>
>
> On 7 February 2011 20:19, John Warburton <jwarbur...@gmail.com> wrote:
>
>> Hello All
>>
>> Well, I quickly packaged up puppet-2.6.5-rc1 and dropped it on my test VM
>> (Solaris 10 U9) against my 2.6.4 server, and immediately started getting the
>> same error message, but on different manifests, or the same manifests but
>> different line numbers. These manifests were written in 0.25.5 days and
>> successfully made the transition to 2.6.4 running on a couple of hundred
>> servers
>>
>> John
>>
>>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
