Bug 2037351

Summary: grc pod restarts for each new GET request to the Governance Policy Page
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: mheppler
Component: GRC & PolicyAssignee: Kevin Cormier <kcormier>
Status: CLOSED ERRATA QA Contact: Derek Ho <dho>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhacm-2.4CC: dho, jtalton, juhsu, kcormier, pamela870ander, tuado
Target Milestone: ---Flags: dho: qe_test_coverage?
kcormier: rhacm-2.3.z+
bot-tracker-sync: rhacm-2.4.z+
kcormier: needinfo-
Target Release: rhacm-2.3.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-22 21:58:13 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 mheppler 2022-01-05 13:53:49 UTC 
Description of the problem:

Once accessing the Governance Policy Page, we receive the following error: "502 Bad Gateway"  ​

Upon checking the pods status, we recognized that the pod named: grc-XXXX-grcui-YYYY (which is responsible for the grcuiapi endpoint) has restarted and only once it comes back up we can use the Governance page. 

It happens every time we are going to some other page and then back to the Governance page.

The logs that we see in the restarting pod: 

[INFO] [server] [pid 1] [env production] started.
[INFO] [server] [pid 1] [env production] NODE_ENV=production
[HPM] Proxy created: / -> https://grc-XXX-grcuiapi:4000/grcuiapi
[HPM] Proxy rewrite rule created: "^/multicloud/policies/graphql" ~> "/graphql"
[HPM] Proxy created: / -> https://search-search-api:4010/searchapi
[HPM] Proxy rewrite rule created: "^/multicloud/policies/search/graphql" ~> "/graphql"
[INFO] [grc-ui] [server] Starting express server.
[INFO] [grc-ui] [server] GRC UI is now running on http://localhost:3000/multicloud/policies
/opt/app-root/src/grc-ui/server/lib/server/console-links.js:51
                 var section = link.spec.applicationMenu.section;


TypeError: Cannot read property 'section' of undefined
  at Request._callback (/opt/app-root/src/grc-ui/server/lib/server/console-links.js:45:51)
  at Request.self.callback (/opt/app-root/src/grc-ui/node_modules/request/request.js:185:22)
  at Request.emit (events.js:400:28)
  at Request.<anonymous> (/opt/app-root/src/grc-ui/node_modules/request/request.js:1154:10)
  at Request.emit (events.js:400:28)
  at IncomingMessage.<anonymous> (/opt/app-root/src/grc-ui/node_modules/request/request.js:1076:12)
  at Object.onceWrapper (events.js:519:28)
  at IncomingMessage.emit (events.js:412:35)
  at endReadableNT (internal/streams/readable.js:1317:12)
  at processTicksAndRejections (internal/process/task_queues.js:82:21)


Release version:

 * ACM 2.4

Operator snapshot version:

OCP version:

Browser Info:

Steps to reproduce:
1. Restart POD
2. Reload page
3.

Actual results:

Expected results:

Additional info:
Comment 1 mheppler 2022-01-06 14:06:52 UTC 
Customer cannot provide a full must-gather:

Unfortunately I am not able to provide a full must-gather as it includes sensitive information. I can however provide some specific info regarding the environment / ACM deployment.
We experience the bug in ACM 2.4.1 deployed on a disconnected OpenShift 4.6.27 bare metal cluster.

So, if will need some more info, please specify what...
Comment 2 bot-tracker-sync 2022-01-06 15:19:52 UTC 
G2Bsync 1006663233 comment 
 KevinFCormier Thu, 06 Jan 2022 15:06:56 UTC 
 G2Bsync

The problem appears to be triggered by a ConsoleLink resource that has a `spec.type` value of `ApplicationMenu` but does not include `spec.applicationMenu`. Please check the output of:

oc get consolelinks.console.openshift.io -o yaml

You should see an item in the application menu with no icon, for example:

![image](https://user-images.githubusercontent.com/42188127/148402775-dbc8d159-f872-4ec3-93f1-8d6dc1d8c9f7.png)

We will fix this problem. As a workaround, if you are able to edit the ConsoleLink resource, you can add it to an unnamed section with the following command, substituting in the <console-link-name>:

oc patch consolelinks.console.openshift.io <console-link-name> --type='json' -p '[{"op": "add", "path": "/spec/applicationMenu", "value": {"section": ""}}]'
Comment 3 mheppler 2022-01-10 15:31:59 UTC 
Customer verified that the workaround is working. And is asking for target release.
Comment 4 bot-tracker-sync 2022-01-10 17:19:23 UTC 
G2Bsync 1009023217 comment 
 KevinFCormier Mon, 10 Jan 2022 16:00:11 UTC 
 G2Bsync Target release is 2.4.2
Comment 6 Kevin Cormier 2022-01-11 21:58:32 UTC 
B2Gsync

Please check other ConsoleLink resources on the ACM 2.3.3 system. It may be one other than the one for "Red Hat Advanced Cluster Management for Kubernetes" itself. The fix should be the same and we can fix for 2.3.z as well if needed.
Comment 7 Tuan 2022-01-11 22:23:34 UTC 
Kevin,
     That worked. Work-around works for ACM 2.3.3
Comment 15 errata-xmlrpc 2022-02-22 21:58:13 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: Red Hat Advanced Cluster Management 2.3.6 security updates and bug fixes), 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-2022:0595
Comment 20 pamela 2025-03-27 04:55:14 UTC 
I do believe this is an excellent website. I stumbled upon it I may revisit once again since I saved as a favorite it.  https://www.ezpass-nh.com