Jobs cloud run execution modification on the fly

[lucg]

Hello,

I have encountered what looks like a bug on jobs cloud run. A job "Execution" image can be modified on the fly so that tasks inside job "Execution" don't all use the same image. The image displayed in the configuration pane of the "Execution" is not modified though.

Steps to reproduce:

- Create a "Job" in "Jobs Cloud Run"

- Create an "Execution" with a given container image (say image "container image 1"), 2 tasks and a parallelism limit of 1. The two tasks will be run sequentially.

- Run the execution

- During the first task, modify the "Execution" configuration to use an other image (say image "container image 2")

- After the first task is finished. The second task will be run with "container image 2". However, the configuration pane of the "Execution" will show that "container image 1" is used.

I believe editing an "Execution" on the fly could be considered a feature. However, it should be made clear that the currently running "Executions " are affected by the changes. At least, by updating the configuration pane.

Thoughts?

[knet]

Thank you for raising this! I've raised this issue with our engineering team, we'll look into it.

[knet]

lucg, Can you please give us more information on what you're editing? Job executions are not editable. Are you editing the Job while an execution is running, and finding that new taks of the running execution are picking up the modified job configuration?

[lucg]

Yes, that's it!

[knet · Accepted solution]

A few of us tried to reproduce this and weren't able to. If I run a job with many tasks, limiting parallelism so that the job doesn't run all at once, and then modify the job itself half-way using the "edit" button in the UI, all my tasks still run using the original configuration.

Are there any more details that could point at what's going on?

[lucg]

I was puzzled by your answer and dug a little bit more. The problem wasn't on google cloud end but mine. I am sorry for the waste of time.

If you're curious, long story short:

The script executed in my containers pull some code from github before executing it. Pushing new code on github triggers a new image creation on artifact registry, but also changes the code that will be pulled by new tasks of currently executed job. Hence leading me to believe the new image was used when in fact, it was the old image pulling the new code.

Thank you for your replies

[knet]

Thanks for sharing the outcome! It's interesting that you pull code to execute as part of your script. Glad you were able to figure out the issue!