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:
If we edit the "Lifecycle Environment" of a Host Group, the label of the "Puppet Environment" field, changes to "Content View"

Version-Release number of selected component (if applicable):
6.0.4

How reproducible:
Always

Steps to Reproduce:
1.Edit a hostgroup
2.Note that the field below "Lifecycle Environment" is labelled "Puppet Environment"
3.Click on the "Lifecycle Environment" select box and select a different entry

Actual results:
The label "Puppet Environment" changes to "Content View"


Expected results:
consistency!

Additional info:

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Can be closed is fixed in Sat6.1.1.
The WebUI is changed and has a separate Content View box

As mentioned in comment #3, as of Satellite 6.1.1, there are 3 separate fields to represent Lifecycle Environment, Content View and Puppet Environment; therefore, the behavior describe no longer exists.