Synchrony pod is not moving into ready state using Helm Chart installation

Infra Core
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 28, 2024

I have enabled synchrony in helm charts and provided all the required deatils butmy synchrony pod doesnt move to Ready state .Here are the details of the POD:

k describe pod/wiki-stage-synchrony-0

Name:                 wiki-stage-synchrony-0

Namespace:            infra-core

Priority:             200000000

Priority Class Name:  odc-default

Service Account:      wiki-stage

Node:                 10.197.58.219/10.197.58.219

Start Time:           Tue, 28 May 2024 12:01:06 +0530

Labels:               app.kubernetes.io/instance=wiki-stage

                      app.kubernetes.io/name=confluence-synchrony

                      controller-revision-hash=wiki-stage-synchrony-68f58556f7

                      statefulset.kubernetes.io/pod-name=wiki-stage-synchrony-0

Annotations:          checksum/config-jvm: 9791eadf10943562b37eff41c58bd5927fdbc5a20708080521e89b8c90d5db71

                      cni.projectcalico.org/containerID: d942476ac00603192d071776c712383bf29ee6f886941ed7de9e585ed77b23aa

                      cni.projectcalico.org/podIP: 10.244.3.192/32

                      cni.projectcalico.org/podIPs: 10.244.3.192/32

Status:               Running

SeccompProfile:       RuntimeDefault

IP:                   10.244.3.192

IPs:

  IP:           10.244.3.192

Controlled By:  StatefulSet/wiki-stage-synchrony

Containers:

  synchrony:

    Container ID:  cri-o://a4c476ee96c4525fb87666747503b5832fd031f040da5e2995710e063ced37b9

    Image:         containers.oracledatacloud.com/atlassian/confluence:7.19.17

    Image ID:      containers.oracledatacloud.com/atlassian/confluence@sha256:d3f39161a3ba7a76e58502055d2c4f3a382ca9a084d89de43487a42afdfc0eef

    Ports:         8091/TCP, 5701/TCP

    Host Ports:    0/TCP, 0/TCP

    Command:

      /scripts/start-synchrony.sh

    State:          Running

      Started:      Tue, 28 May 2024 17:45:39 +0530

    Last State:     Terminated

      Reason:       Error

      Exit Code:    1

      Started:      Tue, 28 May 2024 17:19:10 +0530

      Finished:     Tue, 28 May 2024 17:45:39 +0530

    Ready:          False

    Restart Count:  13

    Limits:

      cpu:     4

      memory:  6G

    Requests:

      cpu:      4

      memory:   6G

    Readiness:  http-get http://:8091/synchrony/heartbeat delay=5s timeout=1s period=1s #success=1 #failure=10

    Environment:

      SET_PERMISSIONS:                    true

      SYNCHRONY_BIND:                      (v1:status.podIP)

      SYNCHRONY_SERVICE_URL:              https:///synchrony

      SYNCHRONY_DATABASE_URL:             jdbc:mysql://10.197.31.237:3306/confluence_stage?sessionVariables=transaction_isolation='READ-COMMITTED'

      SYNCHRONY_DATABASE_USERNAME:        <set to the key 'username' in secret 'dblogin'>  Optional: false

      SYNCHRONY_DATABASE_PASSWORD:        <set to the key 'password' in secret 'dblogin'>  Optional: false

      KUBERNETES_NAMESPACE:               infra-core (v1:metadata.namespace)

      HAZELCAST_KUBERNETES_SERVICE_NAME:  wiki-stage-synchrony

      HAZELCAST_KUBERNETES_SERVICE_PORT:  5701

      CLUSTER_JOIN_TYPE:                  kubernetes

    Mounts:

      /scripts from entrypoint-script (rw)

      /var/atlassian/application-data/confluence from synchrony-home (rw)

      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-swhk8 (ro)

Conditions:

  Type              Status

  Initialized       True

  Ready             False

  ContainersReady   False

  PodScheduled      True

Volumes:

  synchrony-home:

    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)

    ClaimName:  synchrony-home-wiki-stage-synchrony-0

    ReadOnly:   false

  entrypoint-script:

    Type:      ConfigMap (a volume populated by a ConfigMap)

    Name:      wiki-stage-synchrony-entrypoint

    Optional:  false

  shared-home:

    Type:      NFS (an NFS mount that lasts the lifetime of a pod)

    Server:    confluence-fss-mt-stage.wh2n1.iad1.oraclevcn.com

    Path:      /export/confluence-stage

    ReadOnly:  false

  kube-api-access-swhk8:

    Type:                    Projected (a volume that contains injected data from multiple sources)

    TokenExpirationSeconds:  3607

    ConfigMapName:           kube-root-ca.crt

    ConfigMapOptional:       <nil>

    DownwardAPI:             true

QoS Class:                   Guaranteed

Node-Selectors:              <none>

Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s

                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s

Events:

  Type     Reason     Age                        From     Message

  ----     ------     ----                       ----     -------

  Warning  Unhealthy  4m29s (x21217 over 5h54m)  kubelet  Readiness probe failed: Get "http://10.244.3.192:8091/synchrony/heartbeat": dial tcp 10.244.3.192:8091: connect: connection refused

 
Warning  Unhealthy  4m29s (x21217 over 5h54m)  kubelet  Readiness probe failed: Get "http://10.244.3.192:8091/synchrony/heartbeat": dial tcp 10.244.3.192:8091: connect: connection refused

1 answer

0 votes
Ruben Khachaturov
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 31, 2024

Same issue 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events