Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:


Version-Release number of selected component (if applicable):
Satellite 6.14.0 Snap 9.0

How reproducible:
Always

Steps to Reproduce:
1. Enable puppet on Satellite 6.14
2. Create config group with some puppet_classes assigned
3. Click on the config group created from all page.

Actual results:
Oops, we're sorry but something went wrong undefined method "environment' for #‹ForemanPuppet:ConfigGroup:0x0000555d6a93b90

Expected results:
ConfigGroup Edit page should be visible

Additional info:
Same works for 6.13, so adding a `Regression` keyword

Fix available here: https://github.com/theforeman/foreman_puppet/pull/366

Can you verify the fix + check that the styling is the same as before?
I did small refactoring, it should behave the same but want to be 100% sure.

@lstejska Thanks for the quick fix, I've tested the patch above, and it fixes the issue. Also Ack'd the PR.

Verified.

Tested on Satellite 6.14.0 Snap 12.0 with rubygem-foreman_puppet-6.0.1-1.el8sat.noarch and used above steps from comment 0 to validate this fix.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.14 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6818