and i defined a couple of environments and modules thats already used by
clients, yet every time when i tried to import environments or classes in
web interface, it said no change detected.
when importing environments, only 1 'production' env was loaded.
i had /etc/puppet/puppet.conf in foreman config(settings.yml.)
:puppet_conf: /etc/puppet/puppet.conf
and if you go check the URLs of foreman-proxy, it showed the right info.
https://<hostname>:8443/puppet/environments/
["common","production","development"]
you see all the modules defined in puppet, so i believe foreman proxy is
getting the info right.
just foreman fails to update it and theres no error msg at all.
each time, you try to import, it said no change detected. only production
environment shown in foreman and no modules can be loaded in foreman :443
web interface.
Seems there's some misbehaviour in foreman itself…
···
On Friday, 5 July 2013 13:12:37 UTC+2, Xin Ma wrote:
>
> I'm running foreman with puppet.
>
> and i defined a couple of environments and modules thats already used by
> clients, yet every time when i tried to import environments or classes in
> web interface, it said no change detected.
> when importing environments, only 1 'production' env was loaded.
> i had /etc/puppet/puppet.conf in foreman config(settings.yml.)
> :puppet_conf: /etc/puppet/puppet.conf
>
> and if you go check the URLs of foreman-proxy, it showed the right info.
> https://:8443/puppet/environments/
>
> ["common","production","development"]
>
>
> you see all the modules defined in puppet, so i believe foreman proxy is
> getting the info right.
> just foreman fails to update it and theres no error msg at all.
>
> each time, you try to import, it said no change detected. only production
> environment shown in foreman and no modules can be loaded in foreman :443
> web interface.
>
> any help is appreciated.
>
> thanks!
>
Should also note that the same behaviour is present when trying to import
existing classes.
Attempting to use the rake task also fails but with an authentication error
(user: foreman). I'll remove authentication here and see if that makes a
difference.
···
On Monday, 8 July 2013 08:49:45 UTC+2, Andy Edmonds wrote:
>
> I'm seeing this issue too.
>
> However foreman-proxy is reporting back the correct and expected
> environments. You can verify this by:
>
> curl -k -X GET https://localhost:8443/puppet/environments
>
> Seems there's some misbehaviour in foreman itself...
>
> On Friday, 5 July 2013 13:12:37 UTC+2, Xin Ma wrote:
>>
>> I'm running foreman with puppet.
>>
>> and i defined a couple of environments and modules thats already used by
>> clients, yet every time when i tried to import environments or classes in
>> web interface, it said no change detected.
>> when importing environments, only 1 'production' env was loaded.
>> i had /etc/puppet/puppet.conf in foreman config(settings.yml.)
>> :puppet_conf: /etc/puppet/puppet.conf
>>
>> and if you go check the URLs of foreman-proxy, it showed the right info.
>> https://:8443/puppet/environments/
>>
>> ["common","production","development"]
>>
>>
>> you see all the modules defined in puppet, so i believe foreman proxy is
>> getting the info right.
>> just foreman fails to update it and theres no error msg at all.
>>
>> each time, you try to import, it said no change detected. only production
>> environment shown in foreman and no modules can be loaded in foreman :443
>> web interface.
>>
>> any help is appreciated.
>>
>> thanks!
>>
>
So I've removed authentication (and SSL to be sure) and I'm still faced
with the same issues. Will dig about in the logs and see what I can see.
···
On Monday, 8 July 2013 09:22:00 UTC+2, Andy Edmonds wrote:
>
> Should also note that the same behaviour is present when trying to import
> existing classes.
> Attempting to use the rake task also fails but with an authentication
> error (user: foreman). I'll remove authentication here and see if that
> makes a difference.
>
> On Monday, 8 July 2013 08:49:45 UTC+2, Andy Edmonds wrote:
>>
>> I'm seeing this issue too.
>>
>> However foreman-proxy is reporting back the correct and expected
>> environments. You can verify this by:
>>
>> curl -k -X GET https://localhost:8443/puppet/environments
>>
>> Seems there's some misbehaviour in foreman itself...
>>
>> On Friday, 5 July 2013 13:12:37 UTC+2, Xin Ma wrote:
>>>
>>> I'm running foreman with puppet.
>>>
>>> and i defined a couple of environments and modules thats already used by
>>> clients, yet every time when i tried to import environments or classes in
>>> web interface, it said no change detected.
>>> when importing environments, only 1 'production' env was loaded.
>>> i had /etc/puppet/puppet.conf in foreman config(settings.yml.)
>>> :puppet_conf: /etc/puppet/puppet.conf
>>>
>>> and if you go check the URLs of foreman-proxy, it showed the right info.
>>> https://:8443/puppet/environments/
>>>
>>> ["common","production","development"]
>>>
>>>
>>> you see all the modules defined in puppet, so i believe foreman proxy is
>>> getting the info right.
>>> just foreman fails to update it and theres no error msg at all.
>>>
>>> each time, you try to import, it said no change detected. only
>>> production environment shown in foreman and no modules can be loaded in
>>> foreman :443 web interface.
>>>
>>> any help is appreciated.
>>>
>>> thanks!
>>>
>>
···
On Monday, 8 July 2013 10:07:55 UTC+2, Andy Edmonds wrote:
>
> So I've removed authentication (and SSL to be sure) and I'm still faced
> with the same issues. Will dig about in the logs and see what I can see.
>
> On Monday, 8 July 2013 09:22:00 UTC+2, Andy Edmonds wrote:
>>
>> Should also note that the same behaviour is present when trying to import
>> existing classes.
>> Attempting to use the rake task also fails but with an authentication
>> error (user: foreman). I'll remove authentication here and see if that
>> makes a difference.
>>
>> On Monday, 8 July 2013 08:49:45 UTC+2, Andy Edmonds wrote:
>>>
>>> I'm seeing this issue too.
>>>
>>> However foreman-proxy is reporting back the correct and expected
>>> environments. You can verify this by:
>>>
>>> curl -k -X GET https://localhost:8443/puppet/environments
>>>
>>> Seems there's some misbehaviour in foreman itself...
>>>
>>> On Friday, 5 July 2013 13:12:37 UTC+2, Xin Ma wrote:
>>>>
>>>> I'm running foreman with puppet.
>>>>
>>>> and i defined a couple of environments and modules thats already used
>>>> by clients, yet every time when i tried to import environments or classes
>>>> in web interface, it said no change detected.
>>>> when importing environments, only 1 'production' env was loaded.
>>>> i had /etc/puppet/puppet.conf in foreman config(settings.yml.)
>>>> :puppet_conf: /etc/puppet/puppet.conf
>>>>
>>>> and if you go check the URLs of foreman-proxy, it showed the right info.
>>>> https://:8443/puppet/environments/
>>>>
>>>> ["common","production","development"]
>>>>
>>>>
>>>> you see all the modules defined in puppet, so i believe foreman proxy
>>>> is getting the info right.
>>>> just foreman fails to update it and theres no error msg at all.
>>>>
>>>> each time, you try to import, it said no change detected. only
>>>> production environment shown in foreman and no modules can be loaded in
>>>> foreman :443 web interface.
>>>>
>>>> any help is appreciated.
>>>>
>>>> thanks!
>>>>
>>>
···
On Monday, 8 July 2013 11:43:26 UTC+2, Greg Sutcliffe wrote:
>
>
> On 8 July 2013 10:41, Andy Edmonds <andy.e...@gmail.com >wrote:
>
>> From what I can tell from my very basic ruby skills, there seems to be an
>> issue in /usr/share/foreman/app/models/puppet_class_importer.rb
>>
>> Although the correct values are returned from the call to the smart-proxy
>> there seems to be an issue with parsing the code.
>>
>> Anyone out there fancy taking a look at the code? My foreman environment
>> is here as a vagrant project: https://github.com/dizz/vagrant-foreman
>>
>
> What proxy version are you testing against, out of interest?
> Greg
>
I.e if you specify a hash, drop the 'true' line. Same for each other block.
That doesn't help me troubleshoot the problem though - we should have
tests that cover the problem in 1.2.0. I don't see any actual modules in
the link (I'm not a Vagrant user though), but it seems like you're saying no classes are found in the listed environments. You say
/puppet/environments is correct - do you get a list of classes from
/puppet/environments/<env>/classes ?
Thanks for the heads up on the config file - changes now committed.
So currently this is what I see when I curl foreman-proxy Environments:
curl -k -X GET https://localhost:8443/puppet/environments
["development","production"]
That matches my puppet configuration
···
On Monday, 8 July 2013 13:05:39 UTC+2, Greg Sutcliffe wrote:
>
>
> On 8 July 2013 10:46, Andy Edmonds <andy.e...@gmail.com >wrote:
>
>> Hey Greg - foreman-proxy is: 1.2.0+ubuntu1
>>
>
> That answers file looks odd, you shouldn't be specifying
> foreman/puppet/etc twice. It should be just:
>
> #foreman: true
> foreman:
> authentication: false
> ssl: false
> organizations_enabled: true
> locations_enabled: true
>
> I.e if you specify a hash, drop the 'true' line. Same for each other block.
>
> That doesn't help me troubleshoot the problem though - we _should_ have
> tests that cover the problem in 1.2.0. I don't see any actual modules in
> the link (I'm not a Vagrant user though), but it seems like you're saying
> _no_ classes are found in the listed environments. You say
> /puppet/environments is correct - do you get a list of classes from
> /puppet/environments//classes ?
>
> Cheers,
> Greg
>
Although foreman-proxy returns what I'm expecting, the environment importer
fails to pick up development and production environments
···
On Monday, 8 July 2013 13:41:40 UTC+2, Andy Edmonds wrote:
>
> Thanks for the heads up on the config file - changes now committed. :-)
>
> So currently this is what I see when I curl foreman-proxy
> *Environments*:
> curl -k -X GET https://localhost:8443/puppet/environments
> ["development","production"]
> That matches my puppet configuration
>
> *Classes*:
> curl -k -X GET
> https://localhost:8443/puppet/environments/development/classes
> []
> curl -k -X GET
> https://localhost:8443/puppet/environments/production/classes
> []
> That too matches the content of my directories under
> /etc/puppet/{environments,modules}
>
>
>
> Andy
>
> On Monday, 8 July 2013 13:05:39 UTC+2, Greg Sutcliffe wrote:
>>
>>
>> On 8 July 2013 10:46, Andy Edmonds wrote:
>>
>>> Hey Greg - foreman-proxy is: 1.2.0+ubuntu1
>>>
>>
>> That answers file looks odd, you shouldn't be specifying
>> foreman/puppet/etc twice. It should be just:
>>
>> #foreman: true
>> foreman:
>> authentication: false
>> ssl: false
>> organizations_enabled: true
>> locations_enabled: true
>>
>> I.e if you specify a hash, drop the 'true' line. Same for each other
>> block.
>>
>> That doesn't help me troubleshoot the problem though - we _should_ have
>> tests that cover the problem in 1.2.0. I don't see any actual modules in
>> the link (I'm not a Vagrant user though), but it seems like you're saying
>> _no_ classes are found in the listed environments. You say
>> /puppet/environments is correct - do you get a list of classes from
>> /puppet/environments//classes ?
>>
>> Cheers,
>> Greg
>>
>
display. I bet if you manually create a production env and a class, Foreman
would offer to delete the env, as it's empty, according to the proxy. No
need to test that unless you want to
So the real question is why does the proxy not list some classes? Can you
supply your puppet.conf and the full system path to the init.pp of one of
your modules, so I can see what the proxy should be trying to find?
Cheers,
Greg
···
On 8 July 2013 12:56, Andy Edmonds wrote:
Forgot to add the last line…
Although foreman-proxy returns what I’m expecting, the environment
importer fails to pick up development and production environments
Well no - the proxy says there’s no classes, so Foreman has nothing to
Ah! So if foreman see there are no classes associated to an environment,
although there are environments defined, it will not create the
environments?
Let me throw some classes in and ping back…
···
On Monday, 8 July 2013 14:02:37 UTC+2, Greg Sutcliffe wrote:
>
> On 8 July 2013 12:56, Andy Edmonds <andy.e...@gmail.com >wrote:
>
>> Forgot to add the last line...
>>
>> Although foreman-proxy returns what I'm expecting, the environment
>> importer fails to pick up development and production environments
>>
>> Well no - the proxy says there's no classes, so Foreman has nothing to
> display. I bet if you manually create a production env and a class, Foreman
> would offer to delete the env, as it's empty, according to the proxy. No
> need to test that unless you want to ;)
>
> So the real question is why does the proxy not list some classes? Can you
> supply your puppet.conf and the full system path to the init.pp of one of
> your modules, so I can see what the proxy should be trying to find?
>
> Cheers,
> Greg
>
Weird… didn't mean to delete my own post but anyways…
I've added classes to where puppet is expecting them to be (both in
production and development and still foreman-proxy does not see the
classes. It does see the environments however.
Andy
···
On Monday, 8 July 2013 14:19:12 UTC+2, Andy Edmonds wrote:
>
> Ah! So if foreman see there are no classes associated to an environment,
> although there are environments defined, it will not create the
> environments?
>
> Let me throw some classes in and ping back...
>
> On Monday, 8 July 2013 14:02:37 UTC+2, Greg Sutcliffe wrote:
>>
>> On 8 July 2013 12:56, Andy Edmonds wrote:
>>
>>> Forgot to add the last line...
>>>
>>> Although foreman-proxy returns what I'm expecting, the environment
>>> importer fails to pick up development and production environments
>>>
>>> Well no - the proxy says there's no classes, so Foreman has nothing to
>> display. I bet if you manually create a production env and a class, Foreman
>> would offer to delete the env, as it's empty, according to the proxy. No
>> need to test that unless you want to ;)
>>
>> So the real question is why does the proxy not list some classes? Can you
>> supply your puppet.conf and the full system path to the init.pp of one of
>> your modules, so I can see what the proxy should be trying to find?
>>
>> Cheers,
>> Greg
>>
>
So then I re-iterate this request - without seeing what it's trying to
load, I can't see if it should work.
Greg
···
On 8 July 2013 15:15, Andy Edmonds wrote:
Weird… didn’t mean to delete my own post but anyways…
I’ve added classes to where puppet is expecting them to be (both in
production and development and still foreman-proxy does not see the
classes. It does see the environments however.
Andy
On Monday, 8 July 2013 14:19:12 UTC+2, Andy Edmonds wrote:
Ah! So if foreman see there are no classes associated to an environment,
although there are environments defined, it will not create the
environments?
Let me throw some classes in and ping back…
On Monday, 8 July 2013 14:02:37 UTC+2, Greg Sutcliffe wrote:
Although foreman-proxy returns what I’m expecting, the environment
importer fails to pick up development and production environments
Well no - the proxy says there’s no classes, so Foreman has nothing to
display. I bet if you manually create a production env and a class, Foreman
would offer to delete the env, as it’s empty, according to the proxy. No
need to test that unless you want to
So the real question is why does the proxy not list some classes? Can
you supply your puppet.conf and the full system path to the init.pp of one
of your modules, so I can see what the proxy should be trying to find?
···
On Monday, July 8, 2013 10:15:40 PM UTC+8, Andy Edmonds wrote:
>
> Weird... didn't mean to delete my own post but anyways...
>
> I've added classes to where puppet is expecting them to be (both in
> production and development and still foreman-proxy does not see the
> classes. It does see the environments however.
>
> Andy
>
> On Monday, 8 July 2013 14:19:12 UTC+2, Andy Edmonds wrote:
>>
>> Ah! So if foreman see there are no classes associated to an environment,
>> although there are environments defined, it will not create the
>> environments?
>>
>> Let me throw some classes in and ping back...
>>
>> On Monday, 8 July 2013 14:02:37 UTC+2, Greg Sutcliffe wrote:
>>>
>>> On 8 July 2013 12:56, Andy Edmonds wrote:
>>>
>>>> Forgot to add the last line...
>>>>
>>>> Although foreman-proxy returns what I'm expecting, the environment
>>>> importer fails to pick up development and production environments
>>>>
>>>> Well no - the proxy says there's no classes, so Foreman has nothing to
>>> display. I bet if you manually create a production env and a class, Foreman
>>> would offer to delete the env, as it's empty, according to the proxy. No
>>> need to test that unless you want to ;)
>>>
>>> So the real question is why does the proxy not list some classes? Can
>>> you supply your puppet.conf and the full system path to the init.pp of one
>>> of your modules, so I can see what the proxy should be trying to find?
>>>
>>> Cheers,
>>> Greg
>>>
>>
···
On Monday, 8 July 2013 16:40:21 UTC+2, Greg Sutcliffe wrote:
>
> On 8 July 2013 15:15, Andy Edmonds <andy.e...@gmail.com >wrote:
>
>> Weird... didn't mean to delete my own post but anyways...
>>
>> I've added classes to where puppet is expecting them to be (both in
>> production and development and still foreman-proxy does not see the
>> classes. It does see the environments however.
>>
>> Andy
>>
>> On Monday, 8 July 2013 14:19:12 UTC+2, Andy Edmonds wrote:
>>>
>>> Ah! So if foreman see there are no classes associated to an environment,
>>> although there are environments defined, it will not create the
>>> environments?
>>>
>>> Let me throw some classes in and ping back...
>>>
>>> On Monday, 8 July 2013 14:02:37 UTC+2, Greg Sutcliffe wrote:
>>>>
>>>> On 8 July 2013 12:56, Andy Edmonds wrote:
>>>>
>>>>> Forgot to add the last line...
>>>>>
>>>>> Although foreman-proxy returns what I'm expecting, the environment
>>>>> importer fails to pick up development and production environments
>>>>>
>>>>> Well no - the proxy says there's no classes, so Foreman has nothing to
>>>> display. I bet if you manually create a production env and a class, Foreman
>>>> would offer to delete the env, as it's empty, according to the proxy. No
>>>> need to test that unless you want to ;)
>>>>
>>>> So the real question is why does the proxy not list some classes? Can
>>>> you supply your puppet.conf and the full system path to the init.pp of one
>>>> of your modules, so I can see what the proxy should be trying to find?
>>>>
>>>
> So then I re-iterate this request - without seeing what it's trying to
> load, I can't see if it should work.
> Greg
>
and the module i deployed is already running well against all the clients.
just foreman failed to import any class.
the [] result.
···
On Tuesday, July 9, 2013 11:09:08 AM UTC+8, Xin Ma wrote:
>
> sorry i was sick for a couple of days. back to the thread.
>
> im seeing exactly the same thing as andy...
> (i do have the classes.)
>
> *Environments*:
> curl -k -X GET https://localhost:8443/puppet/environments
>
> ["development","production","common"]
>
> That matches my puppet configuration
>
> *Classes*:
> curl -k -X GET
> https://localhost:8443/puppet/environments/development/classes
> []
> curl -k -X GET
> https://localhost:8443/puppet/environments/production/classes
> []
>
> thanks!
>
> On Monday, July 8, 2013 10:15:40 PM UTC+8, Andy Edmonds wrote:
>>
>> Weird... didn't mean to delete my own post but anyways...
>>
>> I've added classes to where puppet is expecting them to be (both in
>> production and development and still foreman-proxy does not see the
>> classes. It does see the environments however.
>>
>> Andy
>>
>> On Monday, 8 July 2013 14:19:12 UTC+2, Andy Edmonds wrote:
>>>
>>> Ah! So if foreman see there are no classes associated to an environment,
>>> although there are environments defined, it will not create the
>>> environments?
>>>
>>> Let me throw some classes in and ping back...
>>>
>>> On Monday, 8 July 2013 14:02:37 UTC+2, Greg Sutcliffe wrote:
>>>>
>>>> On 8 July 2013 12:56, Andy Edmonds wrote:
>>>>
>>>>> Forgot to add the last line...
>>>>>
>>>>> Although foreman-proxy returns what I'm expecting, the environment
>>>>> importer fails to pick up development and production environments
>>>>>
>>>>> Well no - the proxy says there's no classes, so Foreman has nothing to
>>>> display. I bet if you manually create a production env and a class, Foreman
>>>> would offer to delete the env, as it's empty, according to the proxy. No
>>>> need to test that unless you want to ;)
>>>>
>>>> So the real question is why does the proxy not list some classes? Can
>>>> you supply your puppet.conf and the full system path to the init.pp of one
>>>> of your modules, so I can see what the proxy should be trying to find?
>>>>
>>>> Cheers,
>>>> Greg
>>>>
>>>
···
On Tuesday, 9 July 2013 05:16:30 UTC+2, Xin Ma wrote:
>
> and the module i deployed is already running well against all the clients.
> just foreman failed to import any class.
> the [] result.
>
> On Tuesday, July 9, 2013 11:09:08 AM UTC+8, Xin Ma wrote:
>>
>> sorry i was sick for a couple of days. back to the thread.
>>
>> im seeing exactly the same thing as andy...
>> (i do have the classes.)
>>
>> *Environments*:
>> curl -k -X GET https://localhost:8443/puppet/environments
>>
>> ["development","production","common"]
>>
>> That matches my puppet configuration
>>
>> *Classes*:
>> curl -k -X GET
>> https://localhost:8443/puppet/environments/development/classes
>> []
>> curl -k -X GET
>> https://localhost:8443/puppet/environments/production/classes
>> []
>>
>> thanks!
>>
>> On Monday, July 8, 2013 10:15:40 PM UTC+8, Andy Edmonds wrote:
>>>
>>> Weird... didn't mean to delete my own post but anyways...
>>>
>>> I've added classes to where puppet is expecting them to be (both in
>>> production and development and still foreman-proxy does not see the
>>> classes. It does see the environments however.
>>>
>>> Andy
>>>
>>> On Monday, 8 July 2013 14:19:12 UTC+2, Andy Edmonds wrote:
>>>>
>>>> Ah! So if foreman see there are no classes associated to an
>>>> environment, although there are environments defined, it will not create
>>>> the environments?
>>>>
>>>> Let me throw some classes in and ping back...
>>>>
>>>> On Monday, 8 July 2013 14:02:37 UTC+2, Greg Sutcliffe wrote:
>>>>>
>>>>> On 8 July 2013 12:56, Andy Edmonds wrote:
>>>>>
>>>>>> Forgot to add the last line...
>>>>>>
>>>>>> Although foreman-proxy returns what I'm expecting, the environment
>>>>>> importer fails to pick up development and production environments
>>>>>>
>>>>>> Well no - the proxy says there's no classes, so Foreman has nothing
>>>>> to display. I bet if you manually create a production env and a class,
>>>>> Foreman would offer to delete the env, as it's empty, according to the
>>>>> proxy. No need to test that unless you want to ;)
>>>>>
>>>>> So the real question is why does the proxy not list some classes? Can
>>>>> you supply your puppet.conf and the full system path to the init.pp of one
>>>>> of your modules, so I can see what the proxy should be trying to find?
>>>>>
>>>>> Cheers,
>>>>> Greg
>>>>>
>>>>
thank you Andy. could you share me the link so i can add to my watch-list
too. appreciated
···
On Tuesday, July 9, 2013 8:34:56 PM UTC+8, Andy Edmonds wrote:
>
> I'll open a bug on the issue tracker today...
>
> On Tuesday, 9 July 2013 05:16:30 UTC+2, Xin Ma wrote:
>>
>> and the module i deployed is already running well against all the clients.
>> just foreman failed to import any class.
>> the [] result.
>>
>> On Tuesday, July 9, 2013 11:09:08 AM UTC+8, Xin Ma wrote:
>>>
>>> sorry i was sick for a couple of days. back to the thread.
>>>
>>> im seeing exactly the same thing as andy...
>>> (i do have the classes.)
>>>
>>> *Environments*:
>>> curl -k -X GET https://localhost:8443/puppet/environments
>>>
>>> ["development","production","common"]
>>>
>>> That matches my puppet configuration
>>>
>>> *Classes*:
>>> curl -k -X GET
>>> https://localhost:8443/puppet/environments/development/classes
>>> []
>>> curl -k -X GET
>>> https://localhost:8443/puppet/environments/production/classes
>>> []
>>>
>>> thanks!
>>>
>>> On Monday, July 8, 2013 10:15:40 PM UTC+8, Andy Edmonds wrote:
>>>>
>>>> Weird... didn't mean to delete my own post but anyways...
>>>>
>>>> I've added classes to where puppet is expecting them to be (both in
>>>> production and development and still foreman-proxy does not see the
>>>> classes. It does see the environments however.
>>>>
>>>> Andy
>>>>
>>>> On Monday, 8 July 2013 14:19:12 UTC+2, Andy Edmonds wrote:
>>>>>
>>>>> Ah! So if foreman see there are no classes associated to an
>>>>> environment, although there are environments defined, it will not create
>>>>> the environments?
>>>>>
>>>>> Let me throw some classes in and ping back...
>>>>>
>>>>> On Monday, 8 July 2013 14:02:37 UTC+2, Greg Sutcliffe wrote:
>>>>>>
>>>>>> On 8 July 2013 12:56, Andy Edmonds wrote:
>>>>>>
>>>>>>> Forgot to add the last line...
>>>>>>>
>>>>>>> Although foreman-proxy returns what I'm expecting, the environment
>>>>>>> importer fails to pick up development and production environments
>>>>>>>
>>>>>>> Well no - the proxy says there's no classes, so Foreman has nothing
>>>>>> to display. I bet if you manually create a production env and a class,
>>>>>> Foreman would offer to delete the env, as it's empty, according to the
>>>>>> proxy. No need to test that unless you want to ;)
>>>>>>
>>>>>> So the real question is why does the proxy not list some classes? Can
>>>>>> you supply your puppet.conf and the full system path to the init.pp of one
>>>>>> of your modules, so I can see what the proxy should be trying to find?
>>>>>>
>>>>>> Cheers,
>>>>>> Greg
>>>>>>
>>>>>
···
On Wednesday, 10 July 2013 09:22:13 UTC+2, Xin Ma wrote:
>
> thank you Andy. could you share me the link so i can add to my watch-list
> too. appreciated
>
> On Tuesday, July 9, 2013 8:34:56 PM UTC+8, Andy Edmonds wrote:
>>
>> I'll open a bug on the issue tracker today...
>>
>> On Tuesday, 9 July 2013 05:16:30 UTC+2, Xin Ma wrote:
>>>
>>> and the module i deployed is already running well against all the
>>> clients.
>>> just foreman failed to import any class.
>>> the [] result.
>>>
>>> On Tuesday, July 9, 2013 11:09:08 AM UTC+8, Xin Ma wrote:
>>>>
>>>> sorry i was sick for a couple of days. back to the thread.
>>>>
>>>> im seeing exactly the same thing as andy...
>>>> (i do have the classes.)
>>>>
>>>> *Environments*:
>>>> curl -k -X GET https://localhost:8443/puppet/environments
>>>>
>>>> ["development","production","common"]
>>>>
>>>> That matches my puppet configuration
>>>>
>>>> *Classes*:
>>>> curl -k -X GET
>>>> https://localhost:8443/puppet/environments/development/classes
>>>> []
>>>> curl -k -X GET
>>>> https://localhost:8443/puppet/environments/production/classes
>>>> []
>>>>
>>>> thanks!
>>>>
>>>> On Monday, July 8, 2013 10:15:40 PM UTC+8, Andy Edmonds wrote:
>>>>>
>>>>> Weird... didn't mean to delete my own post but anyways...
>>>>>
>>>>> I've added classes to where puppet is expecting them to be (both in
>>>>> production and development and still foreman-proxy does not see the
>>>>> classes. It does see the environments however.
>>>>>
>>>>> Andy
>>>>>
>>>>> On Monday, 8 July 2013 14:19:12 UTC+2, Andy Edmonds wrote:
>>>>>>
>>>>>> Ah! So if foreman see there are no classes associated to an
>>>>>> environment, although there are environments defined, it will not create
>>>>>> the environments?
>>>>>>
>>>>>> Let me throw some classes in and ping back...
>>>>>>
>>>>>> On Monday, 8 July 2013 14:02:37 UTC+2, Greg Sutcliffe wrote:
>>>>>>>
>>>>>>> On 8 July 2013 12:56, Andy Edmonds wrote:
>>>>>>>
>>>>>>>> Forgot to add the last line...
>>>>>>>>
>>>>>>>> Although foreman-proxy returns what I'm expecting, the environment
>>>>>>>> importer fails to pick up development and production environments
>>>>>>>>
>>>>>>>> Well no - the proxy says there's no classes, so Foreman has nothing
>>>>>>> to display. I bet if you manually create a production env and a class,
>>>>>>> Foreman would offer to delete the env, as it's empty, according to the
>>>>>>> proxy. No need to test that unless you want to ;)
>>>>>>>
>>>>>>> So the real question is why does the proxy not list some classes?
>>>>>>> Can you supply your puppet.conf and the full system path to the init.pp of
>>>>>>> one of your modules, so I can see what the proxy should be trying to find?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Greg
>>>>>>>
>>>>>>
