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:
After installing Puppet on Satellite 6.12 or after upgrading Satellite 6.11 to 6.12 with puppet enabled, on a host in the NEWUI, the 'Puppet' tab shows the error 'Something went wrong'.
Version-Release number of selected component (if applicable):
Satellite 6.12
How reproducible:
After installing Puppet.
Steps to Reproduce:
1. Install Puppet on the Satellite 6.12
2. Login to the Satellite WebUI and go to Hosts > All Hosts page.
3. Click on a host, on the NEWUI page of the host, click on the 'Puppet' tab, and the page with the error opens:
=====================
Something went wrong
There was a problem processing the request. Please try again.
To report an issue click here
TypeError: Cannot read properties of undefined (reading 'Puppet details'),
in d
in d
in div
in GridItem
in div
in Grid
in div
in l
in t
in t
in d
in d
in component
in d
in C
in t
in t
in t
in t
in d
in section
in PageSection
in M
in t
in t
in u
in f
in d
in div
in c
in p
in y
in t
in n
in a
in C
in s
in div
in b
in IntlProvider
in I18nProviderWrapper(b)
in d
in StoreProvider(I18nProviderWrapper(b))
in DataProvider(StoreProvider(I18nProviderWrapper(b)))
=====================
Actual results:
NA
Expected results:
The page should show information related to Puppet.
Additional info:
- The error is not observed on the Legacy UI page.
- No logs are generated in the production.log after clicking on the 'Puppet' tab.
We are removing the 6.13 flag as it has been confirmed that this issue is not present in 6.13. That said, the bugzilla remains proposed for an upcoming 6.12.z. The target milestone will be set once the solution is available and it is aligned to a specific zstream.
Verified.
Version Tested: Satellite 6.13 Snap 7.0
Verification Steps:
1. Install Puppet 5.0.0 on the Satellite 6.13
2. Login to the Satellite WebUI and go to Hosts > All Hosts page.
3. Click on a host, on the NEWUI page of the host, click on the 'Puppet' tab.
Result:
The page shows information related to Puppet.
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 (Important: Satellite 6.13 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-2023:2097
Description of problem: After installing Puppet on Satellite 6.12 or after upgrading Satellite 6.11 to 6.12 with puppet enabled, on a host in the NEWUI, the 'Puppet' tab shows the error 'Something went wrong'. Version-Release number of selected component (if applicable): Satellite 6.12 How reproducible: After installing Puppet. Steps to Reproduce: 1. Install Puppet on the Satellite 6.12 2. Login to the Satellite WebUI and go to Hosts > All Hosts page. 3. Click on a host, on the NEWUI page of the host, click on the 'Puppet' tab, and the page with the error opens: ===================== Something went wrong There was a problem processing the request. Please try again. To report an issue click here TypeError: Cannot read properties of undefined (reading 'Puppet details'), in d in d in div in GridItem in div in Grid in div in l in t in t in d in d in component in d in C in t in t in t in t in d in section in PageSection in M in t in t in u in f in d in div in c in p in y in t in n in a in C in s in div in b in IntlProvider in I18nProviderWrapper(b) in d in StoreProvider(I18nProviderWrapper(b)) in DataProvider(StoreProvider(I18nProviderWrapper(b))) ===================== Actual results: NA Expected results: The page should show information related to Puppet. Additional info: - The error is not observed on the Legacy UI page. - No logs are generated in the production.log after clicking on the 'Puppet' tab.