Hi all,
I am in the final steps of bringing the OpenStack modules and foreman
(0.4.2) together however I've run into a blocker (for me).
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
$concat_basedir not defined. Try running again with pluginsync enabled at
/etc/puppet/modules/iaas/concat/manifests/setup.pp:25 on node
fman-os-aio.cloudcomplab.ch
Now I've enabled pluginsync = true yet I still receive the error.
concat_basedir is a facter fact, yet calling facter, I do not see it in the
listing. I have a puppet environment defined as:
[iaas]
modulepath = /etc/puppet/modules/iaas:/etc/puppet/modules/common
What puzzles me is that I have setup OpenStack with puppet (without the '
iaas' environment) already outside of foreman and have not seen is error.
Does anyone have an idea what might be the issue?
Andy
Do you have an environment "production" ? What's the modulepath for
"production" ?
Is the module(s) you are using in the "iaas" also present in the
"production" modulepath ?
It could be you are hitting puppetbug #3910.
To be able to list custom facts with "facter" via commandline use
"FACTERLIB" environment variable, e.g.::
export FACTERLIB=/var/lib/puppet/lib/facter
Maybe that helps.
Cheers,
Marcello
···
From: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com]
On Behalf Of Andy Edmonds
Sent: maandag 2 juli 2012 22:56
To: foreman-users@googlegroups.com
Subject: [foreman-users] Concat & Foreman
Hi all,
I am in the final steps of bringing the OpenStack modules and foreman
(0.4.2) together however I’ve run into a blocker (for me).
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
$concat_basedir not defined. Try running again with pluginsync enabled at
/etc/puppet/modules/iaas/concat/manifests/setup.pp:25 on node
fman-os-aio.cloudcomplab.ch
Now I’ve enabled pluginsync = true yet I still receive the error.
concat_basedir is a facter fact, yet calling facter, I do not see it in the
listing. I have a puppet environment defined as:
[iaas]
modulepath = /etc/puppet/modules/iaas:/etc/puppet/modules/common
What puzzles me is that I have setup OpenStack with puppet (without the
’iaas’ environment) already outside of foreman and have not seen is error.
Does anyone have an idea what might be the issue?
Andy
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/Lu12dVPNu_gJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
So from what I can tell, this is related to puppets handling of
environments: bug 4409.
http://projects.puppetlabs.com/issues/4409
Andy
···
On Tuesday, 3 July 2012 10:48:58 UTC+2, marcellods wrote:
>
> Do you have an environment “production” ? What’s the modulepath for
> “production” ?
>
> Is the module(s) you are using in the “iaas” also present in the
> “production” modulepath ?
>
> It could be you are hitting puppetbug #3910…
>
>
>
> To be able to list custom facts with "facter" via commandline use
> "FACTERLIB" environment variable, e.g.::
>
> # export FACTERLIB=/var/lib/puppet/lib/facter
>
>
>
> Maybe that helps.
>
>
>
> Cheers,
>
> Marcello
>
>
>
> *From:* foreman-users@googlegroups.com [mailto:
> foreman-users@googlegroups.com] *On Behalf Of *Andy Edmonds
> *Sent:* maandag 2 juli 2012 22:56
> *To:* foreman-users@googlegroups.com
> *Subject:* [foreman-users] Concat & Foreman
>
>
>
> Hi all,
>
>
>
> I am in the final steps of bringing the OpenStack modules and foreman
> (0.4.2) together however I've run into a blocker (for me).
>
>
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> $concat_basedir not defined. Try running again with pluginsync enabled at
> /etc/puppet/modules/iaas/concat/manifests/setup.pp:25 on node
> fman-os-aio.cloudcomplab.ch
>
>
>
> Now I've enabled pluginsync = true yet I still receive the error.
> concat_basedir is a facter fact, yet calling facter, I do not see it in
> the listing. I have a puppet environment defined as:
>
>
>
> [iaas]
>
> modulepath = /etc/puppet/modules/iaas:/etc/puppet/modules/common
>
>
>
> What puzzles me is that I have setup OpenStack with puppet (without the '
> iaas' environment) already outside of foreman and have not seen is error.
> Does anyone have an idea what might be the issue?
>
>
>
> Andy
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/foreman-users/-/Lu12dVPNu_gJ.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>
There's a Setting to control whether
$environment-that-Foreman-thinks-a-host-is-in should be present in the
ENC output that is given to Puppet. Might be useful 
Greg
···
On Mon 16 Jul 2012 00:23:05 BST, Andy Edmonds wrote:
> So from what I can tell, this is related to puppets handling of
> environments: bug 4409.
> http://projects.puppetlabs.com/issues/4409
>
> Andy
Hummm - is it the $environment in foreman/manifests/params.pp?
Andy
andy.edmonds.be
···
On Mon, Jul 16, 2012 at 12:05 PM, Greg Sutcliffe wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon 16 Jul 2012 00:23:05 BST, Andy Edmonds wrote:
So from what I can tell, this is related to puppets handling of
environments: bug 4409.
http://projects.puppetlabs.com/issues/4409
Andy
There’s a Setting to control whether
$environment-that-Foreman-thinks-a-host-is-in should be present in the
ENC output that is given to Puppet. Might be useful
Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAD51kACgkQ8O7RN8oK65MxPgCgyPhz8juC8TURG8oGDh29iLEw
HUcAnjwBjlPhQub1NkduySRf7lFETzJV
=PMrl
-----END PGP SIGNATURE-----
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
No, it's in the UI - More -> Seetings -> enc_environment
Greg
···
On 17/07/12 13:47, Andy Edmonds wrote:
> Hummm - is it the $environment in foreman/manifests/params.pp?
The only setting related to environment are:
default_puppet_environment
module_path
Is enc_environment something in puppet 1.0.x?
Andy
andy.edmonds.be
···
On Tue, Jul 17, 2012 at 2:49 PM, Greg Sutcliffe wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17/07/12 13:47, Andy Edmonds wrote:
Hummm - is it the $environment in foreman/manifests/params.pp?
No, it’s in the UI - More -> Seetings -> enc_environment
Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAFXzwACgkQ8O7RN8oK65MSxgCgkPg2fWRknrwHKwZV3JwRwgE7
YLIAoIumctUCfCpZ33/lVGaAV92pYLTt
=dZ7q
-----END PGP SIGNATURE-----
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
Oops, thought I'd replied to this 
Yeah, must be a 1.0 thing. It's easy enough to patch the ENC script to
drop the environment though. I used to use something like this:
result=/usr/share/foreman/extras/puppet/foreman/files/external_node.rb #{ARGV[0]}
if $? == 0
yml=YAML::load(result)
yml.delete('environment')
puts YAML::dump(yml)
exit 0
end
HTH,
Greg
···
On 17 July 2012 14:21, Andy Edmonds wrote:
> The only setting related to environment are:
> default_puppet_environment
> module_path
>
> Is enc_environment something in puppet 1.0.x?
Thanks Greg! I'll give it a go sometime this week.
Andy
andy.edmonds.be
···
On Sun, Jul 22, 2012 at 5:36 PM, Greg Sutcliffe wrote:
On 17 July 2012 14:21, Andy Edmonds andy@edmonds.be wrote:
The only setting related to environment are:
default_puppet_environment
module_path
Is enc_environment something in puppet 1.0.x?
Oops, thought I’d replied to this
Yeah, must be a 1.0 thing. It’s easy enough to patch the ENC script to
drop the environment though. I used to use something like this:
result=/usr/share/foreman/extras/puppet/foreman/files/external_node.rb #{ARGV[0]}
if $? == 0
yml=YAML::load(result)
yml.delete(‘environment’)
puts YAML::dump(yml)
exit 0
end
HTH,
Greg
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
