rollover failure when editing deployment on compreview-apps

[Thien01]

Hi i have this issue where whenever i try to either:

oc edit deployment/beeper-api # mounting volume
#or
oc set volume deployment/beeper-api --type secret --secret-name beeper-api-certs --mountpath /etc/pki/beeper-api

The beeper-api pod wont rollout with new configuration. But how come when I use the suggested method from answer section by applying new changes on deployment.yaml, then i works?

I also have tried to delete the pod to force creation of new pod, but the pod still inherit old configurations.

[rhnoname · Accepted solution]

Hello,

From what I recall, I used to edit the manifest files and then run the "oc apply deployment.yaml", then the rollout should be trigger automatically.

I would suggest try first getting the current deployment configuration and look if everything is fine:

oc get deployment beeper-api -o yaml

then I would try the following:

1. Scale replicas to 0 and then 1
2. Check the events by oc get events, you might find what is wrong
3. Re-create the deployment from scratch

As a last resort cleanup the lab and restart the lab from scratch or delete the entire lab env

Hope it helps

[Thien01]

thanks, it worked by scaling it down and up again

But i still cant wrap around to why the deployment wont automatically rollover. In practice it should automatically rollover. I have tried following:

1. mounting volume (oc set volumes deploy/beeper-api --type secret --secret-name...)
2. edit deployment (oc edit deploy/beeper-api)
3. update manifest and update deployment (oc apply -f deployment.yaml)

I know recreating manifest works and so do scaling.