puppet 3.8.1 reinstalling downgraded package on ubuntu precise

[Randall Smith]

Greetings,

I'm using puppet 3.8.1 on ubuntu precise. My manifest includes a very simple package to install docker.

  package { $docker::params::docker_package_name:

    ensure => present,

    require => Class["docker::params"],

  }

I recently manually updated the docker package using apt-get on the server. The upgrade caused problems so I rolled it back. This is what dpkg shows for the docker package.

# dpkg -l | grep docker

rc  lxc-docker-1.3.2                 1.3.2                               amd64        Linux container runtime

rc  lxc-docker-1.3.3                 1.3.3                               amd64        Linux container runtime

rc  lxc-docker-1.4.0                 1.4.0                               amd64        Linux container runtime

rc  lxc-docker-1.4.1                 1.4.1                               amd64        Linux container runtime

ii  lxc-docker-1.5.0                 1.5.0                               amd64        Linux container runtime

rc  lxc-docker-1.7.0                 1.7.0                               amd64        Linux container runtime

That's what I want. Unfortunately, puppet sees the docker package as being purged and then re-installs/upgrades it (which I don't want). That would make sense if I had the package configured as 'latest' but it's configured as 'present'. What is going on and how do I prevent this from happening in the future?

[Lowe Schmidt]

Setting the specific version instead of present should be enough.

[...]

ensure => 1.3.2, 

[...]

for example.

--

Lowe Schmidt | +46 723 867 157

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/8fd0fa46-a6c1-4b01-b537-c84a59574763%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Randy Smith]

I'm aware of the version option but I still think "present" should be able see that an older version is installed even if a newer version had been installed and removed. That is the defined behavior of "present", after all.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAC-wWcSh1z0Mz9gvx51dn%2Bk%2BCerrz6z%2B0q4RMU%3DA0aejREy6nw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Randall Smith

Computing Services
Adams State University
http://www.adams.edu/
719-587-7741

[mst3k]

Hi,

I’m trying to set up a new heterogeneous environment with a Puppet 4.2. server running on a 14.04.2 Ubuntu LTS and some *nix and windows clients. Without any changes to the server (except enabling autosigning for my domain and setting the alt_dns_names for the master) I’m trying to connect from another Ubuntu and a Windows 2008 r2 client, but where the ubuntu client will connect without a problem, windows keeps getting an Error:

Error 400 on Server: Invalid byte sequence in UTF-8

I searched the web for a hint and saw, that in an earlier version this could be fixed with a locale-setting in the file „config.ru“, which I don’t seem to have on a 4.2. installation.
I also tried to set the apache charset to utf-8 with the charset-config file with no success.

Can anybody point me to the right direction?

Thank you in advance.

The error-log on the server:

2015-07-13 09:48:00,273 INFO [puppet-server] Puppet Caching node for mynode.mydomain
2015-07-13 09:48:00,736 ERROR [puppet-server] Puppet invalid byte sequence in UTF-8
org/jruby/RubyString.java:6202:in `count'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:248:in `binary?'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:262:in `visit_String'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:128:in `accept'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:324:in `visit_Hash'
org/jruby/RubyHash.java:1341:in `each'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:322:in `visit_Hash'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:128:in `accept'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:467:in `emit_coder'
org/jruby/RubyHash.java:1341:in `each'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:465:in `emit_coder'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:450:in `dump_coder'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:126:in `accept'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:92:in `push'
/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych.rb:244:in `dump'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/yaml.rb:21:in `dump'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:380:in `replace_file'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/yaml.rb:20:in `dump'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/yaml.rb:30:in `save'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:276:in `save'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node/facts.rb:21:in `save'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:39:in `extract_facts_from_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in `profile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in `profile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:20:in `extract_facts_from_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:45:in `find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in `find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:134:in `do_find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:in `call'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:64:in `override'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:223:in `override'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in `call'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:in `process'
org/jruby/RubyArray.java:1613:in `each'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:in `process'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in `process'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in `process'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in `process'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in `profile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in `profile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:in `process'
file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppet-server-lib/puppet/server/master.rb:39:in `handleRequest'
Puppet$$Server$$Master_1527977328.gen:13:in `handleRequest'
request_handler_core.clj:274:in `invoke'
request_handler_service.clj:14:in `handle_request'
request_handler.clj:3:in `invoke'
request_handler.clj:3:in `invoke'
core.clj:626:in `invoke'
core.clj:2468:in `doInvoke'
master_core.clj:47:in `invoke'
ring.clj:22:in `invoke'
ring.clj:13:in `invoke'
comidi.clj:267:in `invoke'
ringutils.clj:106:in `invoke'
ringutils.clj:62:in `invoke'
ringutils.clj:68:in `invoke'
ringutils.clj:118:in `invoke'
jetty9_core.clj:408:in `invoke'

[Rob Reynolds]

Would you mind including some logs from the agent as well? 

I'm looking for 

* facter --trace --debug >facter.log 2>&1

* puppet agent --test --debug --verbose --trace >puppet.log 2>&1

Thanks! 

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/C224994E-EC8F-443C-AC28-C72CC2E214E9%40gt-it.de.

For more options, visit https://groups.google.com/d/optout.

--

Rob Reynolds

Developer, Puppet Labs

PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9.

Register now to take advantage of the Early Bird discount —save $249!

[mst3k]

Hi,

(Sorry for double-posting, the first one captured a foreign topic.)

[mst3k]

Hi,

thx for the answer - and sorry for the weird postings. I may need to create a google-account after all to submit decent requests.. But I got the logs:

puppet.log -> http://pastebin.com/aA6dqK24
facter.log -> http://pastebin.com/f3i8Q6Y9

I hope that helps.

Thank you for your time!

> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMJiBK5gGFbku%3DBZ92kVpBXmvZKdHQhkR__ukm1wv%2BKYtawtkw%40mail.gmail.com.

[Josh Cooper]

On Tue, Jul 14, 2015 at 2:13 PM, mst3k <gro...@gt-it.de> wrote:

Hi,

thx for the answer - and sorry for the weird postings. I may need to create a google-account after all to submit decent requests.. But I got the logs:

puppet.log -> http://pastebin.com/aA6dqK24
facter.log -> http://pastebin.com/f3i8Q6Y9

I believe the timezone fact is giving us trouble:

  timezone => Mitteleurop‰ische Sommerzeit

There have been various tickets filed[1], and I thought it had finally been resolved, but perhaps not or this is a regression in native facter?

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0B8B8EC1-A707-4810-9301-F6D9B09FB98A%40gt-it.de.

For more options, visit https://groups.google.com/d/optout.

[1] https://projects.puppetlabs.com/issues/12702#note-4

--

Josh Cooper

[Peter Huene]

On Wed, Jul 15, 2015 at 9:04 AM, Josh Cooper <jo...@puppetlabs.com> wrote:

On Tue, Jul 14, 2015 at 2:13 PM, mst3k <gro...@gt-it.de> wrote:

Hi,

thx for the answer - and sorry for the weird postings. I may need to create a google-account after all to submit decent requests.. But I got the logs:

puppet.log -> http://pastebin.com/aA6dqK24
facter.log -> http://pastebin.com/f3i8Q6Y9

I believe the timezone fact is giving us trouble:

  timezone => Mitteleurop‰ische Sommerzeit

There have been various tickets filed[1], and I thought it had finally been resolved, but perhaps not or this is a regression in native facter?

This appears to be a regression in Facter 3.0.1.  I've opened a ticket to track this: https://tickets.puppetlabs.com/browse/FACT-1126

 

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA%2Bu97um4c4wgKOJgYi1S908U8E0ndcLSM%2B639-vYf9JP-LibVg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Join us at PuppetConf 2015, October 5-9 in Portland, OR - www.2015.puppetconf.com 

Register early to save 40%!

[Peter Huene]

On Wed, Jul 15, 2015 at 9:08 AM, Peter Huene <peter...@puppetlabs.com> wrote:

On Wed, Jul 15, 2015 at 9:04 AM, Josh Cooper <jo...@puppetlabs.com> wrote:

On Tue, Jul 14, 2015 at 2:13 PM, mst3k <gro...@gt-it.de> wrote:

Hi,

thx for the answer - and sorry for the weird postings. I may need to create a google-account after all to submit decent requests.. But I got the logs:

puppet.log -> http://pastebin.com/aA6dqK24
facter.log -> http://pastebin.com/f3i8Q6Y9

I believe the timezone fact is giving us trouble:

  timezone => Mitteleurop‰ische Sommerzeit

There have been various tickets filed[1], and I thought it had finally been resolved, but perhaps not or this is a regression in native facter?

This appears to be a regression in Facter 3.0.1.  I've opened a ticket to track this: https://tickets.puppetlabs.com/browse/FACT-1126

Closing the loop.  We've fixed this for Facter 3.0.2 and the fix will be in the next release of Puppet agent.  Thanks very much for reporting this issue to us.