thr3ads.net - Puppet users - [Puppet Users] why do I get ensure changed ''purged'' to ''present'' on a package when it is already installed [Feb 2010]

If this information is useful, please help other people find it:
Share via:

tim_schofield

2010-Feb-06 00:24 UTC

[Puppet Users] why do I get ensure changed ''purged'' to ''present'' on a package when it is already installed

Hi all,

I have created a squid class that also installs squidGuard.  When I
run puppetd I always get

notice: //Node[xxxx.xxxxxx.xxx]/squid/squid::install/
Package[squidGuard]/ensure: ensure changed ''purged'' to
''present''

even though the package is already installed - why is this change in
package status happening as it then triggers my exec resource which is
only supposed to run the first time when squidguard is installed
(thereafter it is run as a cron job).  So at the moment it is
triggered every time puppetd is run

exec { "/usr/local/bin/getblacklist.sh":
        subscribe => Package["squidGuard"],
        refreshonly => true
        }


Regards

Tim





-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Dan Bode

2010-Feb-06 03:59 UTC

head link

Re: [Puppet Users] why do I get ensure changed ''purged'' to ''present'' on a package when it is already installed

On Fri, Feb 5, 2010 at 4:24 PM, tim_schofield <tim@scoffer.net> wrote:
> Hi all,
>
> I have created a squid class that also installs squidGuard.  When I
> run puppetd I always get
>
> notice: //Node[xxxx.xxxxxx.xxx]/squid/squid::install/
> Package[squidGuard]/ensure: ensure changed ''purged'' to
''present''
>
> running with --debug will show some useful information about the underlyingsystem calls being made. Run again in debug mode, then post the output (or
just the output that we care about).

also, what version of Puppet are you running? what platform?


> even though the package is already installed - why is this change in
> package status happening as it then triggers my exec resource which is
> only supposed to run the first time when squidguard is installed
> (thereafter it is run as a cron job).  So at the moment it is
> triggered every time puppetd is run
>
> exec { "/usr/local/bin/getblacklist.sh":
>        subscribe => Package["squidGuard"],
>        refreshonly => true
>        }
>
>
> Regards
>
> Tim
>
>
>
>
>
> --
> 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+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Tim Schofield

2010-Feb-06 12:42 UTC

head link

Re: [Puppet Users] why do I get ensure changed ''purged'' to ''present'' on a package when it is already installed

On Fri, 2010-02-05 at 19:59 -0800, Dan Bode wrote:> 
> 
> On Fri, Feb 5, 2010 at 4:24 PM, tim_schofield <tim@scoffer.net>
wrote:
>         Hi all,
>         
>         I have created a squid class that also installs squidGuard.
>          When I
>         run puppetd I always get
>         
>         notice: //Node[xxxx.xxxxxx.xxx]/squid/squid::install/
>         Package[squidGuard]/ensure: ensure changed
''purged'' to
>         ''present''
>         
> running with --debug will show some useful information about the
> underlying system calls being made. Run again in debug mode, then post
> the output (or just the output that we care about).
Ran in debug and the problem was with the

/usr/bin/dpkg-query -W --showformat ''${status} ${Package}
${Version}\n''
squidGuard

when I run this on command line I get
No packages found matching squidGuard

If I run it again using the correct package name of squidguard rather
than squidGuard I get

install ok installed squidguard 1.2.0-8.4

so I changed my manifest file to use squidguard rather than squidGuard
problem solved.  Thanks

So why was squidGuard installed in first place so I apt-get remove
squidguard, set my manifest back to squidGuard and it reinstalled, did
the same again with -debug to find the system call which was

/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install
squidGuard

ran this on the command line and it install squidguard

also ran the lowercase version

/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install
squidguard

and this installed as well.

> 
> also, what version of Puppet are you running? what platform?
> puppet 0.24.5-3
Debian lenny 

>         even though the package is already installed - why is this
>         change in
>         package status happening as it then triggers my exec resource
>         which is
>         only supposed to run the first time when squidguard is
>         installed
>         (thereafter it is run as a cron job).  So at the moment it is
>         triggered every time puppetd is run
>         
>         exec { "/usr/local/bin/getblacklist.sh":
>                subscribe => Package["squidGuard"],
>                refreshonly => true
>                }
>         
>         
>         Regards
>         
>         Tim
>         
>         
>         
>         
>         
>         --
>         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
>         +unsubscribe@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
> +unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Andrey Kouznetsov

2013-Jan-17 14:46 UTC

head link

[Puppet Users] Re: why do I get ensure changed ''purged'' to ''present'' on a package when it is already installed

I have exactly the same problem on Ubuntu 12.04

On Saturday, February 6, 2010 4:24:58 AM UTC+4, tim_schofield
wrote:>
> Hi all,
>
> I have created a squid class that also installs squidGuard.  When I
> run puppetd I always get
>
> notice: //Node[xxxx.xxxxxx.xxx]/squid/squid::install/
> Package[squidGuard]/ensure: ensure changed ''purged'' to
''present''
>
> even though the package is already installed - why is this change in
> package status happening as it then triggers my exec resource which is
> only supposed to run the first time when squidguard is installed
> (thereafter it is run as a cron job).  So at the moment it is
> triggered every time puppetd is run
>
> exec { "/usr/local/bin/getblacklist.sh":
>         subscribe => Package["squidGuard"],
>         refreshonly => true
>         }
>
>
> Regards
>
> Tim
>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/-CTgFSYbeqYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

jcbollinger

2013-Jan-18 14:31 UTC

head link

[Puppet Users] Re: why do I get ensure changed ''purged'' to ''present'' on a package when it is already installed

On Thursday, January 17, 2013 8:46:25 AM UTC-6, Andrey Kouznetsov
wrote:>
> I have exactly the same problem on Ubuntu 12.04


Then likely the underlying cause and solution are also the same as the OP 
already posted.


John

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/iZHUmyA0njAJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Maybe Matching Threads

Search for more possibly parallel threads

Puppet users - Feb 2010 - why do I get ensure changed 'purged' to 'present' on a package when it is already installed

[Puppet Users] why do I get ensure changed ''purged'' to ''present'' on a package when it is already installed

Re: [Puppet Users] why do I get ensure changed ''purged'' to ''present'' on a package when it is already installed

Re: [Puppet Users] why do I get ensure changed ''purged'' to ''present'' on a package when it is already installed

[Puppet Users] Re: why do I get ensure changed ''purged'' to ''present'' on a package when it is already installed

[Puppet Users] Re: why do I get ensure changed ''purged'' to ''present'' on a package when it is already installed

Maybe Matching Threads