Your message dated Fri, 21 Jun 2013 14:25:17 +0200
with message-id <87hagrk5w2....@turbotape.w.bitbit.net>
and subject line Re: [Pkg-puppet-devel] Bug#712963: Puppet agent fails with
"Could not intern_multiple from yaml: Invalid parameter ftype"
has caused the Debian Bug report #712963,
regarding Puppet agent fails with "Could not intern_multiple from yaml: Invalid
parameter ftype"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
712963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Package: puppet
Version: 3.2.2-1
Severity: grave
The current puppet package startes failing with the following message:
...
[1;31mWarning: Unable to fetch my node definition, but the agent run will
continue:[0m
[1;31mWarning: Could not intern from yaml: undefined method `name' for
nil:NilClass[0m
[0;32mInfo: Retrieving plugin[0m
[0;36mDebug: file_metadata supports formats: b64_zlib_yaml pson raw yaml;
using yaml[0m
[1;31mError: /File[/var/lib/puppet/lib]: Failed to generate additional
resources using 'eval_generate: Could not intern_multiple from yaml: Invalid
parameter ftype to object class Puppet::FileServing::Metadata[0m
[0;36mDebug: file_metadata supports formats: b64_zlib_yaml pson raw yaml;
using yaml[0m
[1;31mError: /File[/var/lib/puppet/lib]: Could not evaluate: Could not
intern from yaml: Invalid parameter ftype to object class
Puppet::FileServing::Metadata Could not retrieve file metadata for
puppet://puppet/plugins: Could not intern from yaml: Invalid parameter ftype to
object class Puppet::FileServing::Metadata[0m
...
[1;31mError: Could not retrieve catalog from remote server: Could not
intern from yaml: Could not convert from pson: Could not find relationship
source {"catalog"=>{"aliases"=>{}, "applying"=>false, [very long line] ain",
"type"=>"Stage", "virtual"=>nil}[0m
...
- -- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (800, 'unstable'), (600, 'oldstable'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.9.4 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to
de_DE)
Shell: /bin/sh linked to /bin/dash
Versions of packages puppet depends on:
ii puppet-common 3.2.2-1
ii ruby 1:1.9.3
ii ruby1.8 [ruby-interpreter] 1.8.7.358-7
ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-8.1+b1
Versions of packages puppet recommends:
ii ruby [rdoc] 1:1.9.3
Versions of packages puppet suggests:
ii etckeeper 1.4
pn puppet-el <none>
ii vim-puppet 3.2.2-1
- -- Configuration Files:
/etc/default/puppet changed:
START=yes
DAEMON_OPTS="--fqdn ikki.ket"
- -- no debconf information
- --
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <kl...@ethgen.de>
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQGcBAEBCgAGBQJRxBsuAAoJEKZ8CrGAGfas0hML/3DQiXFWGbRcutbjha4av2hm
W7IdUnmQ9r8bhUiq+0xXPKbBKMuMBOvyFCgRcXdh3WzvJo0PP26vuQpfuMrEDz0J
h3HHCIPZPTFYw67XajyHWPiJ5iRFL41IBdcUNjkVL6IKZhFH48v5VrUuiRSUgXek
JvZzuEn2YeddH4hHLeppgYyX3CIM4ar/GmYMidyH7n2Zcj/0zp6Og1bU28REZmHu
yiDd4xTLmb20bOvPoJ/bR0eLYMQEYmVBqHJmfyz4YWIH8aDBd4bEujo1axzQ076R
S1VaBjS6s4/C5e0zeUebkVLNqV/0BI72FnPaiNgksW+UpHMaFNByoQ1zfbia6Prd
ZUFRVXDO9BOkIjIh+yw7msidf4jSUtsrLVreEToAaqn3WjgNjbkrbmy5/nkNgWFB
NkgTxLoIsfVkWl6/0mc7LPszTXcFAZceSOU8knjqpOznyeCc92g8gz7XgtdG+fvf
B5AbThK0xs9JA2CNWG1lttZRO/mlJaNakF3hPtGYtA==
=fv9R
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Klaus Ethgen <kl...@ethgen.de> writes:
> Until version 3.2.1-1, it worked fine.
Yes. The 3.2.2 security release involved a hardening of the YAML loader
in response to "http://puppetlabs.com/security/cve/cve-2013-3567/";.
From the error message (and the 3.2.2 changelog), it looks like a likely
cause.
> There is some interoperatibility.
>
> Unfortunatelly you might have clients that have unstable or testing
> but on the server you want to have stable distribution.
Puppet Labs says:
,----[
http://docs.puppetlabs.com/guides/faq.html#should-i-upgrade-the-client-or-server-first
]
| Should I upgrade the client or server first?
|
| When upgrading to a new version of Puppet, always upgrade the server
| first. Old clients can point at a new server but you may have problems
| when pointing a new client at an old server.
`----
It would be nice to have this, but I do not want to promise more
interoperability in the package than our upstream does.
--
Stig Sandbeck Mathisen <s...@debian.org>
pgp2stMIm0QPH.pgp
Description: PGP signature
--- End Message ---
