Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionVladimir Vasilev
2014-09-22 15:44:53 UTC
Description of problem:
When I try to create new Host Group and add some puppet classes to it I'm always getting "Warning. Please select an environment first" although I selected puppet environment.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Go to Configure -> Host Groups -> New Host Group
2. Put some name, select puppet environment
3. Go to "Puppet Classes"
Actual results:
Warning. Please select an environment first.
Expected results:
Display available puppet classes.
Additional info:
As a work-around I did an empty "Content View" assigned to "Library", then in the New Host Group page I choose the Lifecycle Environment with the Content View, then click on "Puppet Classes" to "unlock" it, then go back to the main tab and switch back to empty Lifecycle Environment, choose desired Puppet Environment and go to Puppet Classes.
Also the message is misleading, it could be Lifecycle Environment or Puppet Environment.
Comment 1RHEL Program Management
2014-09-22 15:53:22 UTC
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.
Created attachment 992160[details]
Works as expected...
This worked as expected in my test. Could be that the original test used a DB which doesn't have any puppet classes or that there were no classes associated with the selected environments?
I used foreman_scap_client puppet-module to test this.
a) Installed the puppet-foreman_scap_client rpm
b) Installing this would make foreman_scap_client module get added to '/usr/share/puppet/modules/'
c) Now added 'foreman_scap_client' to 'example_env' via the puppet-class via the import button.
d) Now when creating a Host-Group, I selected the puppet-environment as "example-env", this does show up 'foreman_scap_client' under the "puppet-classes" tab.
VERIFIED with Satellite-6.1.0-RHEL-7-20150320.1
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, 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-2015:1592