Some Puppet Classes are unavailable in the selected environment

How is this a non-issue? It’s producing an error message that needs to be confirmed is not being caused by a real error. So no, it can’t be ignored.

If the message is incorrect, why is it being generated in the first place? What is the criteria that results in this message being generated? For the people receiving this error message and no real error exists, do we have something installed or configured differently than others?

Just read what I wrote before: it’s a bug. It affects everyone. At the moment it always appears, until the bug has been fixed. Thus, all you can do is ignore it. It seems there is a backlog of issues for the puppet module.

We are well aware of the issue but we don’t have much capacity to work on it. We are trying, though, and help is very much appreciated :slight_smile:

We are currently working on the new host details page tab for Puppet and this is something that should be considered during the implementation.
CC @Ron_Lavi @MSinghal

1 Like