New module classes not showing in cosole

[Ali]

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 (???)
/etc/puppetlabs/code/modules (no modules installed)
/opt/puppetlabs/puppet/modules
├── puppetlabs-pe_accounts (v2.0.2-6-gd2f698c)
├── puppetlabs-pe_concat (v1.1.2-7-g77ec55b)
├── puppetlabs-pe_console_prune (v0.1.1-9-gfc256c0)
├── puppetlabs-pe_hocon (v2015.3.0)
├── puppetlabs-pe_inifile (v1.1.4-16-gcb39966)
├── puppetlabs-pe_java_ks (v1.2.4-37-g2d86015)
├── puppetlabs-pe_nginx (v2016.1.0)
├── puppetlabs-pe_postgresql (v2015.3.0)
├── puppetlabs-pe_puppet_authorization (v2016.1.0)
├── puppetlabs-pe_r10k (v2015.2.2-2-g21c67b9)
├── puppetlabs-pe_razor (v0.2.1-85-g6e105cf)
├── puppetlabs-pe_repo (v2016.1.0)
├── puppetlabs-pe_staging (v2015.3.0)
└── puppetlabs-puppet_enterprise (v2016.1.1-2-gb24975d)

# cat puppet.conf
[main]
    certname =template.plug.com
    server = template.plug.com
    user  = pe-puppet
    group = pe-puppet
    archive_files = true
    archive_file_server = template.plug.com
    app_management = false
    module_groups = base+pe_only
    environmentpath = /etc/puppetlabs/code/environments

[agent]
    graph = true

[master]
node_terminus = classifier
storeconfigs = true
storeconfigs_backend = puppetdb
reports = puppetdb
certname = template.plug.com
always_cache_features = true

[Andrew Grimberg]

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-

[Ali]

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 .

[Andrew Grimberg]

On 05/10/2016 08:25 AM, Ali 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 .

Someone else will have to answer then. I don't have any experience with
PE only the OSS version of Puppet.

-Andy-

[Lindsey Smith]

On Tue, May 10, 2016 at 8:25 AM, Ali <ali.ja...@gmail.com> 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 puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/03fcbb7b-a190-47dc-a756-413c851e66a1%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Ali]

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