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.
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.
Setting to Katello as it might be an interaction with the additional combo boxes.
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?
AFAIU this happens due to defacing katello does on the form, changing back to katello.
This should be resolved in 6.1 builds already.
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
This bug is slated to be released with Satellite 6.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