Hi,
Just a quick query about some things that crop up when I run ''puppetd
--test''. Every time I run this command I always see the following
output, which I think is strange as the ''man'' package has been
installed
previously and the firewall service is definitely running. Has anybody
got any suggestions as to why puppet thinks it needs to install the man
package and restart the firewall when it doesn''t need to ?
notice: Starting configuration run
notice: //basenode/core-firewall/Service[firewall]/ensure: ensure
changed ''stopped'' to ''running''
notice: //basenode/os-ubuntu/Package[man]/ensure: created
notice: Finished configuration run in 52.47 seconds
The relevant config elements are :
file { "/etc/init.d/firewall":
owner => "root",
group => "root",
mode => 755,
source => "puppet://$puppet_server/files/init.d/firewall",
before => service["firewall"]
}
service { "firewall":
ensure => true,
enable => true
}
and ...
package { "man": ensure => installed }
Thanks,
Rob
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 21 July 2007, robl wrote:> Hi, > > Just a quick query about some things that crop up when I run ''puppetd > --test''. Every time I run this command I always see the following > output, which I think is strange as the ''man'' package has been installed > previously and the firewall service is definitely running. Has anybody > got any suggestions as to why puppet thinks it needs to install the man > package and restart the firewall when it doesn''t need to ? > > notice: Starting configuration run > notice: //basenode/core-firewall/Service[firewall]/ensure: ensure > changed ''stopped'' to ''running'' > notice: //basenode/os-ubuntu/Package[man]/ensure: created > notice: Finished configuration run in 52.47 seconds > > > The relevant config elements are : > > file { "/etc/init.d/firewall": > owner => "root", > group => "root", > mode => 755, > source => "puppet://$puppet_server/files/init.d/firewall", > before => service["firewall"] > } > > service { "firewall": > ensure => true, > enable => true > } > > and ... > > package { "man": ensure => installed }Which provider (dpkg, apt, rpm, etc) are you using? Which versions of puppet are you using? Use --debug to see what commands are actually run. Regards, David - -- - - hallo... wie gehts heute? - - *hust* gut *rotz* *keuch* - - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGoevz/Pp1N6Uzh0URAgPRAKChfjs3gaqlDyVxXVKBtn7N20baYwCffDwl d0i3uTC0gbe9zsNa9ivORCw=vEMf -----END PGP SIGNATURE-----
Thanks, that helped me to fix the firewall issues. However the
re-installation of the man package is still occurring :
Relevant parts from puppetd --test --debug
debug: package provider apt: Executing ''/usr/bin/dpkg-query -W
--showformat ${Status} ${Package} ${Version}\n man''
debug: //basenode/os-ubuntu/Package[man]: Changing ensure
debug: //basenode/os-ubuntu/Package[man]: 1 change(s)
debug: //basenode/os-ubuntu/Package[man]/ensure: setting present
(currently absent)
debug: package provider apt: Executing ''/usr/bin/apt-get -q -y -o
DPkg::Options::=--force-confold install man''
notice: //basenode/os-ubuntu/Package[man]/ensure: created
I''m running puppet 0.22.1 on Ubuntu Dapper (backported from Feisty).
Running the dpkg-query command gives (a slightly strange output ?):
me@ops:~# /usr/bin/dpkg-query -W --showformat ${Status} ${Package}
${Version}\n man
nme@ops:~#
Any ideas ?
David Schmitt wrote:> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Saturday 21 July 2007, robl wrote:
>
>> Hi,
>>
>> Just a quick query about some things that crop up when I run
''puppetd
>> --test''. Every time I run this command I always see the
following
>> output, which I think is strange as the ''man'' package
has been installed
>> previously and the firewall service is definitely running. Has anybody
>> got any suggestions as to why puppet thinks it needs to install the man
>> package and restart the firewall when it doesn''t need to ?
>>
>> notice: Starting configuration run
>> notice: //basenode/core-firewall/Service[firewall]/ensure: ensure
>> changed ''stopped'' to ''running''
>> notice: //basenode/os-ubuntu/Package[man]/ensure: created
>> notice: Finished configuration run in 52.47 seconds
>>
>>
>> The relevant config elements are :
>>
>> file { "/etc/init.d/firewall":
>> owner => "root",
>> group => "root",
>> mode => 755,
>> source =>
"puppet://$puppet_server/files/init.d/firewall",
>> before => service["firewall"]
>> }
>>
>> service { "firewall":
>> ensure => true,
>> enable => true
>> }
>>
>> and ...
>>
>> package { "man": ensure => installed }
>>
>
>
> Which provider (dpkg, apt, rpm, etc) are you using?
>
> Which versions of puppet are you using?
>
> Use --debug to see what commands are actually run.
>
> Regards, David
> - --
> - - hallo... wie gehts heute?
> - - *hust* gut *rotz* *keuch*
> - - gott sei dank kommunizieren wir über ein septisches medium ;)
> -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGoevz/Pp1N6Uzh0URAgPRAKChfjs3gaqlDyVxXVKBtn7N20baYwCffDwl
> d0i3uTC0gbe9zsNa9ivORCw> =vEMf
> -----END PGP SIGNATURE-----
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users
>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 22 July 2007, robl wrote:> Thanks, that helped me to fix the firewall issues. However the > re-installation of the man package is still occurring : > > Relevant parts from puppetd --test --debug > > debug: package provider apt: Executing ''/usr/bin/dpkg-query -W > --showformat ${Status} ${Package} ${Version}\n man'' > debug: //basenode/os-ubuntu/Package[man]: Changing ensure > debug: //basenode/os-ubuntu/Package[man]: 1 change(s) > debug: //basenode/os-ubuntu/Package[man]/ensure: setting present > (currently absent) > debug: package provider apt: Executing ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install man'' > notice: //basenode/os-ubuntu/Package[man]/ensure: created > > I''m running puppet 0.22.1 on Ubuntu Dapper (backported from Feisty). > > Running the dpkg-query command gives (a slightly strange output ?): > > me@ops:~# /usr/bin/dpkg-query -W --showformat ${Status} ${Package} > ${Version}\n man > nme@ops:~# > > Any ideas ?To test this correctly, you need to add quotes like this: /usr/bin/dpkg-query -W --showformat ''${Status} ${Package} ${Version}\n'' man Do you have set any defaults on the package type or are there any relations between other resources and Package[man] ? Regards, David - -- - - hallo... wie gehts heute? - - *hust* gut *rotz* *keuch* - - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGowFW/Pp1N6Uzh0URAor6AJ9Lf05yjriXMvHbdWEQVpqvH6whJwCfclAx 0Jk0gL5SLJOQNzAE9lHbdzc=Hspj -----END PGP SIGNATURE-----
> To test this correctly, you need to add quotes like this: > > /usr/bin/dpkg-query -W --showformat ''${Status} ${Package} ${Version}\n'' man > > Do you have set any defaults on the package type or are there any relations > between other resources and Package[man] ? > >It would appear there is some kind of alias lookup within apt that installs the man-db package when you apt-get install man (there is no ''man'' package). This explains why the about dpkg-query command then cannot find the man package. Thanks for the help.
On 7/22/2007 6:45 AM, robl wrote:> It would appear there is some kind of alias lookup within apt that > installs the man-db package when you apt-get install man (there is no > ''man'' package). This explains why the about dpkg-query command then > cannot find the man package.In Debian terms, the man-db package "provides" man. So apt-get install man would actually install man-db: # apt-get install man Reading Package Lists... Done Building Dependency Tree... Done Note, selecting man-db instead of man man-db is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. It may be worth adding a note into the TypeReference that folks on Debian-derived distributions should make sure that their package namevars need to evaluate down to literal package names, not meta-packages created via Provides. -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu