Puppet

Ohad —

So it appears that a resource is getting serialized without a type, but it’s not clear which resource, or why, and most especially, how. I’ve tried reproducing with a variety of resource types but haven’t been able to get this result. So it’s question time:

1) How repeatable is the problem? 2) How pervasive is the problem? 3) Do you know (or suspect) what resource is causing it? 4) Do you know what catalog serialization format is being used?
5) Does the problem persist if you try a different format? 6) Is either machine running ruby 1.8.1? 7) Is the manifest in question small enough and non-sensitive enough that you could share it? 8) Can you think of anything else that might give us a handle on the problem?

— Markus

1) How repeatable is the problem?

afaik on every run

3) Do you know (or suspect) what resource is causing it?

so far I was unable to find the exact manifest which causes it.

4) Do you know what catalog serialization format is being used?

5) Does the problem persist if you try a different format?

yaml, switching to marshel on the client solves the problem

6) Is either machine running ruby 1.8.1?

yes, but that was observed on newer versions of ruby too(1.8.5 RH5)

7) Is the manifest in question small enough and non-sensitive enough that you could share it?

I didn’t find it yet :(

8) Can you think of anything else that might give us a handle on the problem?

• it does work against a 0.25.4 master.
• could it be that the default serialization was marshel, and with the introduction of zaml the order was changed?

Ohad —

Can you try it with this patch on the client:

diff --git a/lib/puppet/transportable.rb b/lib/puppet/transportable.rb
index 41c51fd..7afded1 100644
--- a/lib/puppet/transportable.rb
+++ b/lib/puppet/transportable.rb
@@ -87,6 +87,7 @@ module Puppet
         end
 
         def to_type
+            p [:to_type,type,name,file,line]
             if typeklass = Puppet::Type.type(self.type)
                 return typeklass.create(self)
             else

which will spew a lot of diagnostics, and should provide enough information to figure out which resource it’s choking on?

— Markus

bingo :)

[:to_type, nil, "addons", "/etc/puppet/modules/development/services/redhat/manifests/yum.pp", 26]

and the file content is:

# adds http://puppet as source to the yum repository and enable the addons repo
class redhat::yum {
  $nfsgold=$gi ? { "2" => "goldenimage_2.0", "4" => "goldenimage_4.0", "5" => "goldenimage_5" }
  $webgold="gold_$gi"
  $gipath=$gi ? { "2" => "_ws", default => ""}

  yumrepo { 'base':
    enabled => '1',
    baseurl => "file:///opt/$nfsgold/\$basearch$gipath/
              http://puppet/opt/$nfsgold/\$basearch$gipath/
              http://yum.klu.infineon.com/yum/$webgold/base/\$basearch$gipath/",
    failovermethod => 'priority'
  }
  yumrepo { 'stable':
     baseurl => "file:///opt/$nfsgold/repo/\$basearch/stable/
              http://puppet/opt/$nfsgold/repo/\$basearch/stable/
              http://yum.klu.infineon.com/yum/$webgold/repo/\$basearch/stable/",
    failovermethod => 'priority'
  }
  yumrepo { 'addons':
    enabled => '1',
    baseurl => "file:///opt/$nfsgold/repo/\$basearch/addons/
              http://puppet/opt/$nfsgold/repo/\$basearch/addons/
              http://yum.klu.infineon.com/yum/$webgold/repo/\$basearch/addons/",
    failovermethod => 'priority'
  }
}