Skip to content

fix: Return correct non-interactive session state when pod is gone #1153

Merged
eikek merged 6 commits into
mainfrom
fix/job-status-when-pod-missing
Jun 25, 2026
Merged

fix: Return correct non-interactive session state when pod is gone #1153
eikek merged 6 commits into
mainfrom
fix/job-status-when-pod-missing

Conversation

@eikek

@eikek eikek commented Jun 19, 2026

Copy link
Copy Markdown
Member

It happens that the pod is gone, but the job and amalthea session still exists. In this case the status of the amalthea session needs to be derived from the job.

/deploy

@eikek eikek marked this pull request as ready for review June 19, 2026 06:55
@eikek eikek requested review from a team and olevski as code owners June 19, 2026 06:55
@eikek eikek requested a review from leafty June 19, 2026 06:56

@sgaist sgaist left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some small things otherwise looks good

Comment thread internal/controller/children.go Outdated
Comment thread internal/controller/children.go
@RenkuBot

Copy link
Copy Markdown
Contributor

You can access the deployment of this PR at https://renku-ci-am-1153.dev.renku.ch

@eikek eikek requested a review from sgaist June 19, 2026 11:55
sgaist
sgaist previously approved these changes Jun 19, 2026
Comment thread internal/controller/status.go Outdated
Comment thread internal/controller/children.go Outdated
sgaist
sgaist previously approved these changes Jun 23, 2026
@eikek eikek requested a review from leafty June 24, 2026 12:21
leafty
leafty previously approved these changes Jun 24, 2026
eikek added 6 commits June 24, 2026 17:30
A pod might be missing for a renku job. Then it must not fall through
"not ready".
Also re-use the `failureMessage` method to early determine failure state
This has already been taken care of. The bug only involves successful
jobs that have no pods anymore.
failure message should be taken from the fetched job object
@eikek eikek dismissed stale reviews from leafty and sgaist via 91da796 June 24, 2026 15:31
@eikek eikek force-pushed the fix/job-status-when-pod-missing branch from b1c9bce to 91da796 Compare June 24, 2026 15:31
@eikek eikek requested a review from leafty June 24, 2026 15:32
@eikek eikek force-pushed the fix/job-status-when-pod-missing branch from 91da796 to 620e341 Compare June 25, 2026 09:18
@eikek

eikek commented Jun 25, 2026

Copy link
Copy Markdown
Member Author

I tested it on a data services pr. The deployment was successful when using the what-da-heck branch of renku-actions

@eikek eikek merged commit 473a212 into main Jun 25, 2026
7 of 8 checks passed
@eikek eikek deleted the fix/job-status-when-pod-missing branch June 25, 2026 10:44
@RenkuBot

Copy link
Copy Markdown
Contributor

Tearing down the temporary RenkuLab deplyoment for this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants