Hi, I have a issue when I try to deploy, the status is stuck on 'PENDING'.

Hello <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-ur

Deploy status stuck on 'PENDING' about stack-lifecycle-deployment HOT 1 CLOSED

ramazulay commented on July 20, 2024

Deploy status stuck on 'PENDING'

from stack-lifecycle-deployment.

Comments (1)

D10S0VSkY-OSS commented on July 20, 2024

Hello @ramazulay,
I don't see the result in the log at all.
In SLD, pending status can have two meanings:

That you have launched a deployment and the task is pending because there is no available worker that can handle it (when doing a redeployment you should receive an error in the console "The task already exists in pending status waiting to be executed",
Or that task have passed more than three days (it's the default that values are saved) and you don't know what the status of that task is, this last behavior is done intentionally to enforce good practices and apply every 3 days (you can change the behavior by passing the variable to the worker)
vaiable example

          - name: SLD_RESULT_EXPIRE
            value: "604800"

simple example worker for squad1

apiVersion: apps/v1
kind: Deployment
metadata:
  name: sld-worker-squad1
  labels:
    name: sld-worker-squad1
spec:
  replicas: 2
  selector:
    matchLabels:
      name: sld-worker-squad1
  template:
    metadata:
      labels:
        name: sld-worker-squad1
    spec:
      subdomain: primary
      containers:
        - name: sld-worker-squad1
          image: sld-api
          imagePullPolicy: Always
          env:
          - name: SCHEDULE_SERVER
            value: "http://schedule:10000"
          - name: SLD_RESULT_EXPIRE
            value: "604800"
          - name: BROKER_USER
            valueFrom:
              secretKeyRef:
                name: rabbit-default-user
                key: username
          - name: BROKER_PASSWD
            valueFrom:
              secretKeyRef:
                name: rabbit-default-user
                key: password
          resources:
            limits:
              memory: 900Mi
              cpu: 1
            requests:
              memory: 600Mi
              cpu: 200m
          command: ["celery", "--app", "tasks.celery_worker", "worker","--without-heartbeat", "--without-gossip", "--without-mingle", "--loglevel=info", "-c", "1", "-E", "-O", "fair", "-Q", "squad1-nonprod"]

I understand that you are testing the product, it is recommended to exclude the EKS database to an RDS mysql.
If you need more help, don't hesitate to contact me.

from stack-lifecycle-deployment.

Recommend Projects