No, it updated all the PHP packages that were mentioned in the manifest. There
were about 20 listed, and no actual install happened.
I'm betting that it uses a default action of Latest, and just updated them all
behind the scenes. But I'd expect a logged action on that, as well as a
comment on the default behavior in the type reference.
( I'm not as worried about the docs - there has to be some default, and latest
isn't a terrible one. )
Matthew Barr
Technical Architect
E: mb...@snap-interactive.com
AIM: matthewbarr1
c: (646) 727-0535
On Jul 26, 2012, at 10:57 AM, Michael Stahnke wrote:
> Did something else pull that package in as a dependency?
>
>
>
> On Thu, Jul 26, 2012 at 7:37 AM, Matthew Barr
> <mb...@snap-interactive.com> wrote:
>> We just saw an interesting scenario:
>> Puppet 2.7.18 updated packages on a RHEL 6.2 box to a newer version without
>> logging that fact.
>>
>> We've already fixed our code so it doesn't happen again, but I'm wondering
>> if this is expected behavior or a bug.
>>
>> * I presume the default "ensure" behavior on package is "latest"? The
>> type reference doesn't say that…
>>
>> * For now, we've switched to using ensure => present… but I'd have liked the
>> logs to reflect that update.
>>
>>
>>
>> Details, if necessary:
>>
>> Now, we had the code as such:
>>
>>
>> package {
>> php:;
>> php-common:;
>> php-xml:;
>> php-domxml;:
>> }
>> and there was a single not present package to install (php-domxml).
>>
>>
>> Interestingly, the package was actually an older package name that's now
>> handled by a new package (php-xml), which meant that the actual message
>> logged was a failure.
>>
>>
>> Jul 25 14:09:43 web01 puppet-agent[1021]:
>> (/Stage[main]/Php/Package[php-domxml]/ensure) change from absent to present
>> failed: Could not find package php-domxml
>>
>> This was the only package message logged, and yet we ended up with newer
>> versions.
>>
>>
>>
>> Matthew Barr
>> Technical Architect
>> E: mb...@snap-interactive.com
>> AIM: matthewbarr1
>> c: (646) 727-0535
>>
>> --
>> 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.
>
> --
> 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.
>
--
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.
