Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 5. Known issues
Sometimes a Cryostat release might contain an issue or issues that Red Hat acknowledges and might fix at a later stage during the product’s development. Review each known issue for its description and its resolution.
Cryostat agent cannot accept the ALL event template in recording start requests
- Description
- When creating a JFR recording for a target JVM that is using the Cryostat agent, if you select the ALL event template, the Cryostat agent returns an HTTP 400 error.
- Workaround
Depending on your requirements, you can do either of the following:
- If you want to use the ALL event template, use a JMX connection with your target JVM.
- If you want to use a Cryostat agent connection with your target JVM, use a different event template such as Profiling.
Red Hat Insights integration fails on ARM64 architecture
- Description
-
In the Cryostat Operator’s namespace, a pod whose name begins with
insights-proxy
is in theImagePullBackOff
error state. This is because theAPICast
container used for this pod is not built for the ARM64 architecture. However, Cryostat and all applications that are using the Cryostat agent should still function normally. - Workaround
To disable Red Hat Insights integration:
- Navigate to Operators > Installed Operators.
- Select the Red Hat build of Cryostat operator.
- Select the Subscription tab.
- From the Actions drop-down menu, select Edit Subscription.
Add the
INSIGHTS_ENABLED
environment variable to theSubscription
object:apiVersion: operators.coreos.com/v1alpha1 kind: Subscription metadata: name: cryostat-operator namespace: openshift-operators spec: config: env: - name: INSIGHTS_ENABLED value: “false” channel: stable installPlanApproval: Automatic name: cryostat-operator source: my-operator-catalog sourceNamespace: openshift-marketplace startingCSV: cryostat-operator.v2.4.0
- Click Save.
This workaround disables Red Hat Insights integration in the Cryostat Operator, which removes the
insights-proxy
deployment.