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.

Description of problem:
When trying to create a build for a new host with a Content View that does not have a Puppet Environment, the host cannot be saved with this message: "can't be blank"

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

Steps to Reproduce:
1. Create and Publish a Content View that has no Puppet Module
2. Create a new host and associate the Content View
3. Try to let the Puppet Environment blank, you will get an error

Actual results:
Can't create a host build

Expected results:
As the Puppet Environment are no more created automatically if the Content View does not contain a Puppet Module, we would expect that this field can be blank at the host creation.

Additional info:
[app] [I] Failed to save: Environment can't be blank

The validator for this was changed in Satellite 6.2 to:
  validates :environment_id, :presence => true, :unless => Proc.new { |host| host.puppet_proxy_id.blank? }

Which means a puppet environment should NOT be required unless you've selected a puppet master (proxy).  Did you select one?

Actually waiting from customer feedback to confirm that the bug is no more required.

Regarding the actual linked case, this was simply corrected by making sure that no Puppet Ca and not Puppet Master were selected, I am closing this bug.