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:
"undefined method `name' for nil:NilClass" while switching organization from template invocation page.
Version-Release number of selected component (if applicable):
- Satellite 6.9.0 snap 4
How reproducible:
- Always
Steps to Reproduce:
1. Run job on a host
2. Once job completed (failed/succeeded) click on hostname of that job to see template invocation(Detailed information about run)
3. Switch to diferent organization from that page.
Actual results:
" Oops, we're sorry but something went wrong undefined method `name' for nil:NilClass"
Expected results:
Proper error message
Additional info:
- Observed same behavior on Satellite 6.8 as well.
Verified
Verified with:
- Satellite 6.9.0 snap 16
Test steps:
1. Run job on a host
2. Once job completed (failed/succeeded) click on hostname of that job to see template invocation(Detailed information about run)
3. Switch to different organization from that page.
Observation:
"Could not display data for job invocation." message.
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 (Moderate: Satellite 6.9 Release), 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-2021:1313