Forman environments not importing

Support
1

I have the following in my puppet.conf

[master]
autosign = $confdir/autosign.conf { mode = 664 }
reports = foreman
external_nodes = /etc/puppet/node.rb
node_terminus = exec
ca = true
ssldir = /var/lib/puppet/ssl
certname = <MY_MACHINE_FQDN>
strict_variables = false

environmentpath  = /etc/puppet/environments
basemodulepath   =

/etc/puppet/environments/$environment/modules/forge:/etc/puppet/environments/$environment/modules/local

When I curl the puppet foreman proxy I get environments reported

curl -k -sS https://<MY_MACHINE_FQDN>:8140/v2.0/environments --cert
/var/lib/puppet/ssl/certs/<MY_MACHINE_FQDN>.pem --key
/var/lib/puppet/ssl/private_keys/<MY_MACHINE_FQDN>.pem -X GET
http://localhost:8443/puppet/environments

My understanding from this is that the proxy has correctly found the
environments

I am running Forman 1.6.1-1
on CentOS release 6.5
It was installed with installer defaults

Any input welcome

2

puppet version is 3.7.2 (community)

3

I'm afraid I don't see any output from your curl command there, i'd expect
an array. Did the mailing list just mangle that part of your mail, or did
it really return nothing?

Greg

4

The json output had the search path in it for both the module sub paths <environment>/modules/forge
and <environment>/modules/local unfortunately Foreman only parses
<environment>/modules and does not seem to honor the search paths returned
by puppet. As a work around I have moved my modules into <environment>/modules
and all works as expected

··· On Tuesday, 28 October 2014 11:11:00 UTC, Greg Sutcliffe wrote: > > I'm afraid I don't see any output from your curl command there, i'd expect > an array. Did the mailing list just mangle that part of your mail, or did > it really return nothing? > > Greg >
5

I am attempting to raise this as a bug but not having a lot of luck with
redmine.

Can newly created users raise bug or do I need to send them to a mailing
list?

6

Any user registered to Redmine should be able to create a bug.

http://projects.theforeman.org/projects/foreman/issues/new

If not, please say exactly what problem you're having.

Incidentally, regarding the problem, I think it's probably that the
smart proxy isn't interpolating $environment in a modulepath returned
from Puppet. I had expected Puppet to do that, evidently not.

··· On 29/10/14 10:02, Robert Mortimer wrote: > I am attempting to raise this as a bug but not having a lot of luck with > redmine. > > Can newly created users raise bug or do I need to send them to a mailing > list?

–
Dominic Cleal
Red Hat Engineering

7

Bug #8162 raised
Thank you I just could not see navigation to get a new bug

··· On Wednesday, 29 October 2014 10:58:44 UTC, Dominic Cleal wrote: > > On 29/10/14 10:02, Robert Mortimer wrote: > > I am attempting to raise this as a bug but not having a lot of luck with > > redmine. > > > > Can newly created users raise bug or do I need to send them to a mailing > > list? > > Any user registered to Redmine should be able to create a bug. > > http://projects.theforeman.org/projects/foreman/issues/new > > If not, please say exactly what problem you're having. > > Incidentally, regarding the problem, I think it's probably that the > smart proxy isn't interpolating $environment in a modulepath returned > from Puppet. I had expected Puppet to do that, evidently not. > > -- > Dominic Cleal > Red Hat Engineering >
8

Had to choose a project before getting a new issue tab

··· On Wednesday, 29 October 2014 16:55:46 UTC, Robert Mortimer wrote: > > Bug #8162 raised > Thank you I just could not see navigation to get a new bug > > On Wednesday, 29 October 2014 10:58:44 UTC, Dominic Cleal wrote: >> >> On 29/10/14 10:02, Robert Mortimer wrote: >> > I am attempting to raise this as a bug but not having a lot of luck >> with >> > redmine. >> > >> > Can newly created users raise bug or do I need to send them to a >> mailing >> > list? >> >> Any user registered to Redmine should be able to create a bug. >> >> http://projects.theforeman.org/projects/foreman/issues/new >> >> If not, please say exactly what problem you're having. >> >> Incidentally, regarding the problem, I think it's probably that the >> smart proxy isn't interpolating $environment in a modulepath returned >> from Puppet. I had expected Puppet to do that, evidently not. >> >> -- >> Dominic Cleal >> Red Hat Engineering >> >