Bug #4733

Realizing virtual resources fails

Added by R.I. Pienaar over 1 year ago. Updated over 1 year ago.

Status:Duplicate Start date:09/07/2010
Priority:Normal Due date:
Assignee:Markus Roberts % Done:

0%
Category:-
Target version:2.6.1
Affected Puppet version:2.6.1rc4 Branch:
Keywords:
Votes: 0

Description

I do pacakge installs using this pattern:

define pkg() {
        $version = extlookup("${name}_pkg", "present")

        @package{$name: ensure => $version}
}

I then have a class:

class packages::virt {
   pkg{[< a whole lot of packages, 200+ >]: }
}

And then I just realize packages where I need them.

I am testing 2.6.1rc4 and on a node with 66 packages from this setup 2 are failing during compile:

Sep  7 13:44:26 monitor2 puppet-master[17318]: Failed to realize virtual resources Package[perl-XML-Simple], Package[RubyRRDtool] on node

This comes from P::Parser::Compiler#fail_on_unevaluated_resource_collections but how to debug this I have no idea, I can cause this by simply doing:

puppetmasterd --compile monitor2.pinetecltd.net

I am not seeing anything useful in output from above when run with —debug or/and —trace

So I dont know how to reproduce and dont know how to debug further since I know very little about the internals in the compiler class

Related issues

duplicates Puppet - Bug #4736: $name should preserve specified case Closed 09/08/2010

History

#1
Updated by James Turnbull over 1 year ago

  • Target version set to 2.6.1

#2
Updated by Markus Roberts over 1 year ago

  • Status changed from Unreviewed to Investigating
  • Assignee set to Markus Roberts

Is there anything special or even mildly noteworthy about the two resources that fail?

#3
Updated by R.I. Pienaar over 1 year ago

Markus Roberts wrote:

Is there anything special or even mildly noteworthy about the two resources that fail?

nothing. they are created in a big array with 200 others and they’re just packages, i dont even have anything in extlookup for them so they will just be ‘present’.

And since it fails during compile, it’s not related to the actual packages, yum or yum meta data etc.

#4
Updated by R.I. Pienaar over 1 year ago

I was trying to find a way to duplicate this with a simple manifest and noticed that current master works while tag 2.6.1rc4 doesnt.

Might help track it down,

#5
Updated by R.I. Pienaar over 1 year ago

And if I play around with rebase and remove the commit:

763e7cb Minimal fix for #4691 -- class name uppercased in $name

then it doesnt have this issue anymore,

#6
Updated by James Turnbull over 1 year ago

  • Status changed from Investigating to Duplicate

Duplicate of #4736.

Also available in: Atom PDF