#1258 waiverdb: Update command for the new container image
Merged a year ago by zlopez. Opened a year ago by lholecek.
fedora-infra/ lholecek/ansible update-waiverdb-command  into  main

@@ -1,4 +1,4 @@ 

- 

+ ---

  apiVersion: v1

  kind: DeploymentConfig

  metadata:
@@ -18,7 +18,14 @@ 

          failurePolicy: Abort

          execNewPod:

            containerName: web

-           command: [ /bin/sh, -i, -c, "waiverdb wait-for-db && waiverdb db upgrade" ]

+           command:

+             - /bin/sh

+             - -c

+             - >-

+               if [ -f /app/entrypoint.sh ];

+               then /app/entrypoint.sh waiverdb db upgrade;

+               else waiverdb db upgrade;

+               fi

            volumes:

            - config-volume

            - secret-volume

no initial comment

rebased onto 9a08f786f4d991106b7c1e5e06bacbc04c167a80

a year ago

rebased onto 84b9f9c28ffc55ec45f59ee7add080f4f049a23c

a year ago

rebased onto 84b9f9c28ffc55ec45f59ee7add080f4f049a23c

a year ago

Build succeeded.

rebased onto f7b50f36fd8f230938c822227af64906f64bb17f

a year ago

rebased onto f7b50f36fd8f230938c822227af64906f64bb17f

a year ago

Build succeeded.

rebased onto c3942af

a year ago

rebased onto c3942af

a year ago

Pull-Request has been merged by zlopez

a year ago

Build succeeded.

Was there some issue deploying the new configuration? I still see the old broken command being used in stage (https://console-openshift-console.apps.ocp.stg.fedoraproject.org/k8s/ns/waiverdb/deploymentconfigs/waiverdb-web/yaml).

Sorry, didn't run the deployment, just merged it. It should be deployed now.

Thanks.

Here is another followup to fix high memory consumption: #1261

For now, I fixed and tested it manually in the stage DeploymentConfig: https://console-openshift-console.apps.ocp.stg.fedoraproject.org/k8s/ns/waiverdb/deploymentconfigs/waiverdb-web/yaml

Metadata