diff --git a/TroubleshootReadme.md b/TroubleshootReadme.md new file mode 100644 index 00000000..5fa90548 --- /dev/null +++ b/TroubleshootReadme.md @@ -0,0 +1,45 @@ +# Known Issues and Troubleshooting steps: + +## 1) Startup probe failed on OCP 4.6.34, 4.6.36 and 4.7.18 + +In the recent version of the openshift (4.6.34, 4.6.36 and 4.7.18) we have noticed the below issue on db2u pods. + +### Issue: + +```bash +Error: Pods c-db2oltp-wkc-db2u-0  & c-db2oltp-iis-db2u-0 pods will have  Startup probe failed with bellow error message +``` +```bash +Warning  Unhealthy       101m                    kubelet            Startup probe failed: time="2021-07-09T03:05:48-05:00" level=error msg="exec failed: open /dev/tty: no such device or address" +  Normal   Pulled          34m (x4 over 87m)       kubelet            Container image "cp.icr.io/cp/db2u.restricted@sha256:c1aaa5dc86b01c7706ee0bf5d46da51cee628c77758b955385325a574e451372" already present on machine +  Warning  Unhealthy       5m24s (x249 over 101m)  kubelet            (combined from similar events): Startup probe failed: time="2021-07-09T04:42:08-05:00" level=error msg="exec failed: open /dev/tty: no such device or address" +``` +### Workaround: + +We have added the patch recommended by DB2 team to patch the db2 sts, this will restart the db2u pod and allow the service to be proceed further. + +Patch example for wkc: +```bash + +oc patch sts c-db2oltp-wkc-db2u -p='{"spec":{"template":{"spec":{"containers":[{"name":"db2u","tty":false}]}}}}}' + +Once the db2u pod is up: + +oc rsh c-db2oltp-wkc-db2u-0  + +bash +ipclean -a && sleep 5 +db2start +db2 -v activate db LINEAGE + +``` + +For IIS, the below patch should make the install proceed further. + +``` bash +oc patch sts c-db2oltp-iis-db2u -p='{"spec":{"template":{"spec":{"containers":[{"name":"db2u","tty":false}]}}}}}' +``` + +For db2 instance creation in CP4D services like db2wh, db2oltp, dv ... that might be in progress for long time,if you see db2u pods in 0/1 state, describe pod for the respective db2u pod shows /dev/tty: no such device or address error + +Run the similar patch as above for the db2u sts that is in 0/1 state. diff --git a/managed-openshift/ibmcloud/cpd_install/cpd.tf b/managed-openshift/ibmcloud/cpd_install/cpd.tf index f096bca0..66d6bd45 100644 --- a/managed-openshift/ibmcloud/cpd_install/cpd.tf +++ b/managed-openshift/ibmcloud/cpd_install/cpd.tf @@ -20,7 +20,7 @@ resource "null_resource" "bedrock_zen_operator" { working_dir = "${path.module}/scripts/" interpreter = ["/bin/bash", "-c"] - command = "./install-bedrock-zen-operator.sh" + command = "./install_bedrock_zen_operator.sh" } depends_on = [ @@ -41,7 +41,7 @@ resource "null_resource" "install_ccs" { working_dir = "${path.module}/scripts/" interpreter = ["/bin/bash", "-c"] - command = "./install-ccs.sh" + command = "./install_ccs.sh" } depends_on = [ @@ -161,7 +161,7 @@ resource "null_resource" "install_wsl" { working_dir = "${path.module}/scripts/" interpreter = ["/bin/bash", "-c"] - command = "./install-wsl.sh" + command = "./install_wsl.sh" } depends_on = [ diff --git a/managed-openshift/ibmcloud/cpd_install/scripts/dmc-cr.yaml b/managed-openshift/ibmcloud/cpd_install/scripts/dmc-cr.yaml index d18704d0..b19f8f16 100644 --- a/managed-openshift/ibmcloud/cpd_install/scripts/dmc-cr.yaml +++ b/managed-openshift/ibmcloud/cpd_install/scripts/dmc-cr.yaml @@ -9,4 +9,4 @@ spec: version: "4.0.0" license: accept: true - license: Enterprise \ No newline at end of file + license: Enterprise \ No newline at end of file diff --git a/managed-openshift/ibmcloud/cpd_install/scripts/install-wkc.sh b/managed-openshift/ibmcloud/cpd_install/scripts/install-wkc.sh index 663d050b..183785fd 100755 --- a/managed-openshift/ibmcloud/cpd_install/scripts/install-wkc.sh +++ b/managed-openshift/ibmcloud/cpd_install/scripts/install-wkc.sh @@ -30,7 +30,7 @@ cloudctl case launch --case ${CASE_PACKAGE_NAME} \ # switch to zen namespace -oc project zen +oc project ${NAMESPACE} # # Install wkc Customer Resource diff --git a/managed-openshift/ibmcloud/cpd_install/scripts/install-bedrock-zen-operator.sh b/managed-openshift/ibmcloud/cpd_install/scripts/install_bedrock_zen_operator.sh similarity index 100% rename from managed-openshift/ibmcloud/cpd_install/scripts/install-bedrock-zen-operator.sh rename to managed-openshift/ibmcloud/cpd_install/scripts/install_bedrock_zen_operator.sh diff --git a/managed-openshift/ibmcloud/cpd_install/scripts/install-ccs.sh b/managed-openshift/ibmcloud/cpd_install/scripts/install_ccs.sh similarity index 100% rename from managed-openshift/ibmcloud/cpd_install/scripts/install-ccs.sh rename to managed-openshift/ibmcloud/cpd_install/scripts/install_ccs.sh diff --git a/managed-openshift/ibmcloud/cpd_install/scripts/install-wsl.sh b/managed-openshift/ibmcloud/cpd_install/scripts/install_wsl.sh similarity index 100% rename from managed-openshift/ibmcloud/cpd_install/scripts/install-wsl.sh rename to managed-openshift/ibmcloud/cpd_install/scripts/install_wsl.sh diff --git a/selfmanaged-openshift/azure/ocs_module/deploy-with-olm.yaml b/selfmanaged-openshift/azure/ocs_module/deploy-with-olm.yaml index b27f2c07..df6a1db0 100644 --- a/selfmanaged-openshift/azure/ocs_module/deploy-with-olm.yaml +++ b/selfmanaged-openshift/azure/ocs_module/deploy-with-olm.yaml @@ -27,4 +27,3 @@ spec: name: ocs-operator source: redhat-operators sourceNamespace: openshift-marketplace - startingCSV: ocs-operator.v4.6.4 diff --git a/selfmanaged-openshift/azure/portworx_module/px-install.yaml b/selfmanaged-openshift/azure/portworx_module/px-install.yaml index 7ec06a3b..4e9279fd 100644 --- a/selfmanaged-openshift/azure/portworx_module/px-install.yaml +++ b/selfmanaged-openshift/azure/portworx_module/px-install.yaml @@ -23,4 +23,3 @@ spec: name: portworx-certified source: certified-operators sourceNamespace: openshift-marketplace - startingCSV: portworx-operator.v1.4.4