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.
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.
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
Comment 7Satellite Program
2018-02-21 16:51:07 UTC
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
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)