이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 7. Known issues
This section lists the known issues for AMQ Streams 1.8.
7.1. SMTP appender for log4j 링크 복사링크가 클립보드에 복사되었습니다!
AMQ Streams ships with a potentially vulnerable version of log4j (log4j-1.2.17.redhat-3). The vulnerability lies with the SMTP appender functionality, which is not used by AMQ Streams in its default configuration.
| Issue Number | Description |
|---|---|
| CVE-2020-9488 log4j: improper validation of certificate with host mismatch in SMTP appender [amq-st-1]. |
Workaround
If you are using the SMTP appender, ensure that mail.smtp.ssl.checkserveridentity is set to true.
7.2. AMQ Streams Cluster Operator on IPv6 clusters 링크 복사링크가 클립보드에 복사되었습니다!
The AMQ Streams Cluster Operator does not start on Internet Protocol version 6 (IPv6) clusters.
Workaround
There are two workarounds for this issue.
Workaround one: Set the KUBERNETES_MASTER environment variable
Display the address of the Kubernetes master node of your OpenShift Container Platform cluster:
oc cluster-info Kubernetes master is running at MASTER-ADDRESS # ...
oc cluster-info Kubernetes master is running at MASTER-ADDRESS # ...Copy to Clipboard Copied! Toggle word wrap Toggle overflow Copy the address of the master node.
List all Operator subscriptions:
oc get subs -n OPERATOR-NAMESPACE
oc get subs -n OPERATOR-NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow Edit the
Subscriptionresource for AMQ Streams:oc edit sub amq-streams -n OPERATOR_NAMESPACE
oc edit sub amq-streams -n OPERATOR_NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow In
spec.config.env, add theKUBERNETES_MASTERenvironment variable, set to the address of the Kubernetes master node. For example:Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Save and exit the editor.
Check that the
Subscriptionwas updated:oc get sub amq-streams -n OPERATOR-NAMESPACE
oc get sub amq-streams -n OPERATOR-NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow Check that the Cluster Operator
Deploymentwas updated to use the new environment variable:oc get deployment CLUSTER-OPERATOR-DEPLOYMENT-NAME
oc get deployment CLUSTER-OPERATOR-DEPLOYMENT-NAMECopy to Clipboard Copied! Toggle word wrap Toggle overflow
Workaround two: Disable hostname verification
List all Operator subscriptions:
oc get subs -n OPERATOR-NAMESPACE
oc get subs -n OPERATOR-NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow Edit the
Subscriptionresource for AMQ Streams:oc edit sub amq-streams -n OPERATOR_NAMESPACE
oc edit sub amq-streams -n OPERATOR_NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow In
spec.config.env, add theKUBERNETES_DISABLE_HOSTNAME_VERIFICATIONenvironment variable, set totrue. For example:Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Save and exit the editor.
Check that the
Subscriptionwas updated:oc get sub amq-streams -n OPERATOR-NAMESPACE
oc get sub amq-streams -n OPERATOR-NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow Check that the Cluster Operator
Deploymentwas updated to use the new environment variable:oc get deployment CLUSTER-OPERATOR-DEPLOYMENT-NAME
oc get deployment CLUSTER-OPERATOR-DEPLOYMENT-NAMECopy to Clipboard Copied! Toggle word wrap Toggle overflow