Some of the classes or parameters in this group have been removed from Puppet. These classes and parameters still appear in the list but they are crossed out.

[Vinay Korrapati]

Hi Team,

I have installed the puppet enterprise 2019.8.1 version in my preproduction environment. 

Later i have created a new environment as : preproduction. 

i could observed production (default) got missed  under /etc/puppetlabs/code/environments/ .

Hence often its throwing the below error message in PE Infrastructure node group and respective other PE node groups as well :

Please assist me to address the above issue. 

Note : Before changing the default environment if i ran the puppet agent -t i was able to get the production environment (none of the files got created an empty folder).

Its a temporary workaround. 

Regards

Vinay

[nandha kumar]

Hi ,

Please try restart pe-puppet-server and pe-console services .

Regards,

Nandha

--
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/56305bb1-8bd6-48d6-88e0-aeeb20cffb93n%40googlegroups.com.

[Vinay Korrapati]

Hi Nandha,

THanks for the response. yeah done with that as well.. but no luck. Any other options ?

Thanks & Regards 

Cordially, 

VINAYABABU KORRAPATI
+91-9703333781
vina...@gmail.com

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEzwKcygeyS%2BqY4eBYhH0WpRbtfzvU3bZca_jEE1RLTXmvRPkw%40mail.gmail.com.

[Michael A Riley]

This feels similar to something I saw . The PE server gets confused if it's not running the environment 'production'. Those classes think they belong to that environment. The absence of 'production' essential orphans them which is why they appear to be crossed out. If you're using Code Manager it will remove any environments from /etc/puppetlabs/code/environments that are not defined in your git repo. Which is most likely what happened here.

Oddly enough PE will recreate /etc/puppetlabs/code/environments/production on new JRuby creation:

INFO [clojure-agent-send-pool-1] [p.s.j.i.jruby-internal] Cleaned up old JRubyInstance with id 32.
INFO [clojure-agent-send-pool-1] [p.s.j.i.jruby-internal] Creating JRubyInstance with id 35.
INFO [clojure-agent-send-pool-1] [puppetserver] Puppet Puppet settings initialized; run mode: master
INFO [clojure-agent-send-pool-1] [puppetserver] /File[/etc/puppetlabs/code/environments/production]/ensure created

/etc/puppetlabs/code/environments/production will be deleted next time Code Manager runs however.

There's also usually helpful information in the activity history for the PE Infrastructure node group in web console.

I believe to overcome this you need to install/update your PE server with a pe.conf with the following set to the environment your infrastructure clients will run:

pe_install::install::classification::pe_node_group_environment

per https://puppet.com/docs/pe/2019.8/installing_pe.html#configuration_parameters_and_the_pe.conf_file




Good Luck,




Mike

---

From: puppet...@googlegroups.com <puppet...@googlegroups.com> on behalf of Vinay Korrapati <vina...@gmail.com>
Sent: Wednesday, May 26, 2021 8:15:35 AM
To: Puppet Users
Subject: [Puppet Users] Some of the classes or parameters in this group have been removed from Puppet. These classes and parameters still appear in the list but they are crossed out.

 

--

[Vinay Korrapati]

Hi Mike,

Thanks for the response. Issue got fixed, when i sync the production repo from the control repository. 

Thanks & Regards 

Cordially, 

VINAYABABU KORRAPATI
+91-9703333781
vina...@gmail.com

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/fcc9ba530a124e109768ca7acf6b5c10%40cmu.edu.