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:
hammer full-help fails with "Error: uninitialized constant HammerCLIForeman::CommandExtensions::PuppetEnvironment"

Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli_foreman-3.1.0-1.el7sat.noarch
tfm-rubygem-hammer_cli-3.1.0-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. # hammer full-help
2.
3.

Actual results:
Should list all available help options

Expected results:
Error: uninitialized constant HammerCLIForeman::CommandExtensions::PuppetEnvironment

Additional info:

Hi, closing this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2035195. In case it's not, feel free to re-open.

*** This bug has been marked as a duplicate of bug 2035195 ***