Bug 2150380

Summary: Puppet tab on a Host page on NewUI showing 'Something went wrong'
Product: Red Hat Satellite Reporter: Ashish Patil <ashipati>
Component: HostsAssignee: Ron Lavi <rlavi>
Status: CLOSED ERRATA QA Contact: nalfassi
Severity: medium Docs Contact:
Priority: high    
Version: 6.12.0CC: aruzicka, inecas, nalfassi, osousa, pcreech, peter.vreman, pnovotny, rlavi
Target Milestone: 6.13.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman_puppet-4.0.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2158570 (view as bug list) Environment:
Last Closed: 2023-05-03 13:23:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ashish Patil 2022-12-02 18:13:50 UTC
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.

Comment 3 Ron Lavi 2022-12-13 10:35:56 UTC
Upstream PR is open at https://github.com/theforeman/foreman_puppet/pull/321
once it gets merged I will release foreman_puppet v4.0.4

Comment 5 Brad Buckingham 2022-12-15 15:36:51 UTC
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.

Comment 7 Ron Lavi 2022-12-20 16:42:55 UTC
This has been fixed in foreman_puppet v4.0.4 which is released to https://rubygems.org/gems/foreman_puppet/versions/4.0.4
packaging PR is opened at https://github.com/theforeman/foreman-packaging/pull/8864,
moving to POST

Comment 11 nalfassi 2023-01-19 14:05:00 UTC
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.

Comment 14 errata-xmlrpc 2023-05-03 13:23:27 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 (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