From 631bc25b5adbe014ae1d1da02ecb2c67a76f5263 Mon Sep 17 00:00:00 2001 From: Klesh Wong Date: Mon, 8 Jan 2024 12:56:04 +0800 Subject: [PATCH] docs: go panic in OpenShift k8s (#696) --- docs/Troubleshooting/Installation.md | 6 ++++++ .../version-v0.17/Troubleshooting/Installation.md | 6 ++++++ .../version-v0.18/Troubleshooting/Installation.md | 6 ++++++ .../version-v0.19/Troubleshooting/Installation.md | 6 ++++++ .../version-v0.20/Troubleshooting/Installation.md | 6 ++++++ 5 files changed, 30 insertions(+) diff --git a/docs/Troubleshooting/Installation.md b/docs/Troubleshooting/Installation.md index eb176fc18b0..14037e14cf6 100644 --- a/docs/Troubleshooting/Installation.md +++ b/docs/Troubleshooting/Installation.md @@ -10,6 +10,12 @@ description: > The cause is the `devlake` container trying to decrypt data in the database with the wrong key. Please check the [GettingStarted/Upgrade](../GettingStarted/Upgrade.md) doc for more detail. +### Go Panic in OpenShift Kubernetes + +One of the known root causes of the phonomenon is the Dynatrace agent being injected into the container. +Excluding the namespace from the Dynatrace deployments should fix the problem. +Check [#5612](https://github.com/apache/incubator-devlake/issues/5612) if you needed more detail. + ## None of them solve your problem? Sorry for the inconvenience, please help us improve by [creating an issue](https://github.com/apache/incubator-devlake/issues) diff --git a/versioned_docs/version-v0.17/Troubleshooting/Installation.md b/versioned_docs/version-v0.17/Troubleshooting/Installation.md index eb176fc18b0..14037e14cf6 100644 --- a/versioned_docs/version-v0.17/Troubleshooting/Installation.md +++ b/versioned_docs/version-v0.17/Troubleshooting/Installation.md @@ -10,6 +10,12 @@ description: > The cause is the `devlake` container trying to decrypt data in the database with the wrong key. Please check the [GettingStarted/Upgrade](../GettingStarted/Upgrade.md) doc for more detail. +### Go Panic in OpenShift Kubernetes + +One of the known root causes of the phonomenon is the Dynatrace agent being injected into the container. +Excluding the namespace from the Dynatrace deployments should fix the problem. +Check [#5612](https://github.com/apache/incubator-devlake/issues/5612) if you needed more detail. + ## None of them solve your problem? Sorry for the inconvenience, please help us improve by [creating an issue](https://github.com/apache/incubator-devlake/issues) diff --git a/versioned_docs/version-v0.18/Troubleshooting/Installation.md b/versioned_docs/version-v0.18/Troubleshooting/Installation.md index eb176fc18b0..14037e14cf6 100644 --- a/versioned_docs/version-v0.18/Troubleshooting/Installation.md +++ b/versioned_docs/version-v0.18/Troubleshooting/Installation.md @@ -10,6 +10,12 @@ description: > The cause is the `devlake` container trying to decrypt data in the database with the wrong key. Please check the [GettingStarted/Upgrade](../GettingStarted/Upgrade.md) doc for more detail. +### Go Panic in OpenShift Kubernetes + +One of the known root causes of the phonomenon is the Dynatrace agent being injected into the container. +Excluding the namespace from the Dynatrace deployments should fix the problem. +Check [#5612](https://github.com/apache/incubator-devlake/issues/5612) if you needed more detail. + ## None of them solve your problem? Sorry for the inconvenience, please help us improve by [creating an issue](https://github.com/apache/incubator-devlake/issues) diff --git a/versioned_docs/version-v0.19/Troubleshooting/Installation.md b/versioned_docs/version-v0.19/Troubleshooting/Installation.md index eb176fc18b0..14037e14cf6 100644 --- a/versioned_docs/version-v0.19/Troubleshooting/Installation.md +++ b/versioned_docs/version-v0.19/Troubleshooting/Installation.md @@ -10,6 +10,12 @@ description: > The cause is the `devlake` container trying to decrypt data in the database with the wrong key. Please check the [GettingStarted/Upgrade](../GettingStarted/Upgrade.md) doc for more detail. +### Go Panic in OpenShift Kubernetes + +One of the known root causes of the phonomenon is the Dynatrace agent being injected into the container. +Excluding the namespace from the Dynatrace deployments should fix the problem. +Check [#5612](https://github.com/apache/incubator-devlake/issues/5612) if you needed more detail. + ## None of them solve your problem? Sorry for the inconvenience, please help us improve by [creating an issue](https://github.com/apache/incubator-devlake/issues) diff --git a/versioned_docs/version-v0.20/Troubleshooting/Installation.md b/versioned_docs/version-v0.20/Troubleshooting/Installation.md index eb176fc18b0..14037e14cf6 100644 --- a/versioned_docs/version-v0.20/Troubleshooting/Installation.md +++ b/versioned_docs/version-v0.20/Troubleshooting/Installation.md @@ -10,6 +10,12 @@ description: > The cause is the `devlake` container trying to decrypt data in the database with the wrong key. Please check the [GettingStarted/Upgrade](../GettingStarted/Upgrade.md) doc for more detail. +### Go Panic in OpenShift Kubernetes + +One of the known root causes of the phonomenon is the Dynatrace agent being injected into the container. +Excluding the namespace from the Dynatrace deployments should fix the problem. +Check [#5612](https://github.com/apache/incubator-devlake/issues/5612) if you needed more detail. + ## None of them solve your problem? Sorry for the inconvenience, please help us improve by [creating an issue](https://github.com/apache/incubator-devlake/issues)