I am trying puppet version 4.4.1 .
puppet --version
4.4.1
Everything with module and class looks good .
#puppet apply
--modulepath=/etc/puppetlabs/code/environments/production/modules -e
"include critical_policy"
Notice: Compiled catalog for template.plug.com in environment production in
0.14 seconds
Notice: Welcome from puppet.
Notice: /Stage[main]/Critical_policy/Notify[Welcome from puppet.]/message:
defined 'message' as 'Welcome from puppet.'
Notice: Applied catalog in 0.52 seconds
# pwd
/etc/puppetlabs/code/environments/production/modules/critical_policy/manifests
#puppet apply init.pp
Notice: Compiled catalog for template.plug.com in environment production in
0.08 seconds
Notice: Applied catalog in 0.48 seconds
# cat init.pp
class critical_policy {
notify { "Welcome from puppet.": }
}
# puppet parser validate init.pp
> On Tue, May 10, 2016 at 8:25 AM, Ali <[email protected] <javascript:>>
> wrote:
>
>> thanks for quick reply.
>>
>> Problem is its not showing in enterprise console under classification -
>> node group - classes - add new class drop down list .
>>
>> Not sure if I am missing some configuration or need to add new module to
>> somewhere else so it can show up in class drop down list in enterprise
>> console .
>>
>
> What version of PE are you using?
>
> It could be that there is an error with the class and therefore is
> filtered out of the available class list. Can you puppet apply the class
> successfully?
>
>
>>
>>
>> On Tuesday, May 10, 2016 at 11:03:29 AM UTC-4, Andrew Grimberg wrote:
>>
>>> On 05/10/2016 07:43 AM, Ali wrote:
>>> > Hi ,
>>> >
>>> > My new test module critical_policy class in not showing in console . I
>>> > restarted all pe-services , rebooted node but no luck . Any help will
>>> be
>>> > appreciated .
>>> >
>>> > # puppet --version
>>> > 4.4.1
>>> >
>>> > # puppet module list
>>> > /etc/puppetlabs/code/environments/production/modules
>>> > └── critical_policy (???)
>>>
>>> Greetings Ali,
>>>
>>> Looks like it's being found no problems. The (???) would be because you
>>> likely don't have a metadata.json file in the root of the module that
>>> has a version number. Or, if you do, it can't be parsed for some reason.
>>>
>>> -Andy-
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/03fcbb7b-a190-47dc-a756-413c851e66a1%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/puppet-users/03fcbb7b-a190-47dc-a756-413c851e66a1%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/7166e1b8-3b59-485a-bf67-afbbe43755d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
