Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-2358

keycloak and server pods do not restart automatically after adding a ConfigMap

    XMLWordPrintable

Details

    • False
    • False
    • +
    • Hide
      = `keycloak` and `codeready` pods do not restart automatically after adding a ConfigMap

      After adding a ConfigMap to a {prod-short} instance, the `keycloak` and `codeready` Pods do not restart automatically.

      .Workaround

      * Manually restart the `keycloak` and `codeready` pods after adding a ConfigMap.
      Show
      = `keycloak` and `codeready` pods do not restart automatically after adding a ConfigMap After adding a ConfigMap to a {prod-short} instance, the `keycloak` and `codeready` Pods do not restart automatically. .Workaround * Manually restart the `keycloak` and `codeready` pods after adding a ConfigMap.
    • Workaround Exists
    • Hide

      Manually restart 'keycloak' and 'codeready' pods consequently after adding required ConfigMap.

      Show
      Manually restart ' keycloak ' and ' codeready ' pods consequently after adding required ConfigMap.
    • Hide
      • There should be several CRW instances on the OCP cluster
      • Install new CRW instance
      • Add new 'ConfigMap' using commands below:
      $ oc create configmap my-ca-cert --from-file=<path-to-file-ca.crt> -n=<crw-namespace-name>
$ oc label configmap my-ca-cert app.kubernetes.io/part-of=che.eclipse.org app.kubernetes.io/component=ca-bundle -n=<crw-namespace-name>
      • Pods of 'keycloak and 'codeready' do not restart automatically
      Show
      There should be several CRW instances on the OCP cluster Install new CRW instance Add new 'ConfigMap' using commands below: $ oc create configmap my-ca-cert --from-file=<path-to-file-ca.crt> -n=<crw-namespace-name> $ oc label configmap my-ca-cert app.kubernetes.io/part-of=che.eclipse.org app.kubernetes.io/component=ca-bundle -n=<crw-namespace-name> Pods of 'keycloak and 'codeready' do not restart automatically

    Description

      When a ConfigMap is added to a CRW 2.12.0 instance, 'keycloak-pod' and 'codeready-pod' do not restart automatically.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. CRW-2653 `Test propagation of the trusted certificates` automation step fails because codeready pod doesn't restart after patching CheCluster

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Closed
          links to

          GitHub eclipse-che/che-operator#1135: fix: import ca-bundle even if there are several checluster CR (non all…

          Activity

            People

              abazko Anatolii Bazko
              oshmarai Shmaraiev Oleksandr
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: