Puppet users - Oct 2011 - Problems with exported resources after upgrade to 2.7.5

Hi all,

I use a number of exported resources, some of which are exported custom 
definitions.Since
upgrading to 2.7.5, I''ve seen an issue which is driving me up the wall 
trying to debug it. Hopefully
someone can help :)

Consider the following three snippets of code:

*$modulepath/ntp/manifests/ntp_register.pp:*
define basics::ntp_register ($content="", $order=10) {

  concat::fragment{"ntp_conf_$name":
    target  => "/etc/ntp.conf",
    content => "$content",
    order => "$order"      
  }
}

$modulepath/servers/manifests/ntp_server.pp
class servers::ntp_server {
  @@basics::ntp_register { "Server Ntp $domain": content =>
"stuff here\n" }
}

*$modulepath/servers/manifests/ntp_client.pp*
class servers::ntp {
  Basics::Ntp_register <<| title == "Server Ntp $domain"
|>>
}

So we have a defined resource, an export of that resource, and a collection 
of it. In 2.7.3, this worked fine,
however, in 2.7.4 and 2.7.5 I get

err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Could not find type 
Basics::Ntp_register on node client.foo.bar

I''m not sure what''s changed that''s causing this.
I''ve read some stuff about
loading order, but they seem
to be old bugs that were fixed ages ago. I can see that rewriting this as a 
local definition containing an
exported resource might work, but I''d rather understand what''s
wrong with my
approach first.

Thanks in advance,
Greg

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/D2Ou_f59FIoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

This is definitely busted for me too. I think it''s just broken when
custom defines are exported, as exported classes seem to be working OK
(witness nagios::service for example).

Any word on a fix?

Thanks,
Robin

On Oct 3, 7:51 am, Greg Sutcliffe <greg.sutcli...@gmail.com>
wrote:
> Hi all,
>
> I use a number of exported resources, some of which are exported custom
> definitions.Since
> upgrading to 2.7.5, I''ve seen an issue which is driving me up the
wall
> trying to debug it. Hopefully
> someone can help :)
>
> Consider the following three snippets of code:
>
> *$modulepath/ntp/manifests/ntp_register.pp:*
> define basics::ntp_register ($content="", $order=10) {
>
>   concat::fragment{"ntp_conf_$name":
>     target  => "/etc/ntp.conf",
>     content => "$content",
>     order => "$order"      
>   }
>
> }
>
> $modulepath/servers/manifests/ntp_server.pp
> class servers::ntp_server {
>   @@basics::ntp_register { "Server Ntp $domain": content =>
"stuff here\n" }
>
> }
>
> *$modulepath/servers/manifests/ntp_client.pp*
> class servers::ntp {
>   Basics::Ntp_register <<| title == "Server Ntp $domain"
|>>
>
> }
>
> So we have a defined resource, an export of that resource, and a collection
> of it. In 2.7.3, this worked fine,
> however, in 2.7.4 and 2.7.5 I get
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Could not find type
> Basics::Ntp_register on node client.foo.bar
>
> I''m not sure what''s changed that''s causing this.
I''ve read some stuff about
> loading order, but they seem
> to be old bugs that were fixed ages ago. I can see that rewriting this as a
> local definition containing an
> exported resource might work, but I''d rather understand
what''s wrong with my
> approach first.
>
> Thanks in advance,
> Greg
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Thu, Oct 6, 2011 at 11:50 AM, Rob Walsh <rob.walsh@gmail.com> wrote:
> This is definitely busted for me too. I think it''s just broken
when
> custom defines are exported, as exported classes seem to be working OK
> (witness nagios::service for example).
>
> Any word on a fix?
>
Anecdotes have piled up to become data, and we''re looking at it now.



-- 
Nigel Kersten
Product Manager, Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Thu, Oct 6, 2011 at 16:01, Nigel Kersten <nigel@puppetlabs.com>
wrote:
> On Thu, Oct 6, 2011 at 11:50 AM, Rob Walsh <rob.walsh@gmail.com>
wrote:
>>
>> This is definitely busted for me too. I think it''s just broken
when
>> custom defines are exported, as exported classes seem to be working OK
>> (witness nagios::service for example).
>>
>> Any word on a fix?
>
> Anecdotes have piled up to become data, and we''re looking at it
now.
It would be helpful if folks hit by this could let me know:

* what DBMS are you using?
* what version of ActiveRecord is in use?

Also, if possible, a query that tries to collect something that is
being missed would be useful.

That should be selecting from resources where "type =
''File''" and a
few other criteria.

Daniel
-- 
⎋ Puppet Labs Developer – http://puppetlabs.com
♲ Made with 100 percent post-consumer electrons

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

This should be fixed in 2.7.6rc2.  Please test.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.