Created attachment 1218799 [details] production.log(filename: errors.log) Description of problem: Locations are disabled in satellite-answers.yaml(locations_enabled: false) Not able to publish a Content-View with a puppet module. Version-Release number of selected component (if applicable): All versions How reproducible: Always Steps to Reproduce: 1. Setup a satellite server with location disabled 2. Create and publish content-view. Actual results: Exception raised. Request completed with 500 error. 2016-10-26 07:57:06 [foreman-tasks/action] [E] undefined method `id' for nil:NilClass (NoMethodError) Expected results: Content-view should be published. Additional Info: From customer : Attached production.log(filename: errors.log)
Note: It is reasonable to update the software to improve the behavior (error messaging) in this configuration (Locations disabled); however, it should be noted that Satellite 6 does not officially support having locations disabled. If that is desired, a separate RFE should be requested to ensure proper QE coverage.
Moving to assigned, since there is currently a PR associated with the upstream issue.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17281 has been resolved.
Verified with Satellite 6.3 SNAP 11: satellite-6.3.0-16.0.beta.el7sat.noarch, tfm-rubygem-katello-3.4.4-1.el7sat.noarch Installed and configured a Satellite 6.3 with locations disabled (--foreman-locations-enabled=false). Imported several puppet modules in to a repository, added them to a content view and successfully published the CV. No errors were observed.
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-2018:0336
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-2018:0336