Thank you for the reply R I Pienaar , while executing the command "mco 
inventory nodename" , we are able to find agent_specified_environment for 
one node but not for another . 

Can you please let me know how can I set an agent specified environment for 
a node which by default doesn't have one.

The node2 which doesn't show up the agent specified environment is added to 
the Dev environment group from the PE Console. Is it the reason for not 
showing the agent_specified_environment?

As you have mentioned environment is special and not a fact anymore , can 
you please let us know how can we filter based on these special values. Our 
requirement is to categorize nodes based on environments and execute 
manifests across the required environment.



On Thursday, October 27, 2016 at 8:47:29 PM UTC+5:30, [email protected] 
wrote:
>
> Hi,
>
>     I'm trying to trigger puppet agent specific to environment using 
> mcollective. I'm using the command *"mco puppet runonce --environment 
> <environment name>"*, but it's not able to filter the node specific to 
> the mentioned environment instead triggers all the nodes configured under 
> Puppet server. I have created a group 'Dev environment' with 'Production 
> environment' as a parent group in PE console, have added a node under 'Dev 
> environment'. I'm running the command* "**puppet config print modulepath 
> --section master --environment <environment name>"* to cross check if the 
> child group exists & it works fine. 
>
>      When we try to run the command *"** mco puppet runonce -W 
> environment=production"* it's returning the message *"**No request sent, 
> we did not discover any nodes"*.
>
>  
>     Can anyone please help me with the correct method to accomplish it, or 
> help me with the required configuration to be done in  any of the conf 
> files.
>
> Thanks,
> Rakshatha
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"mcollective-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to