#7904 Please kill the Fedora Docs pod builder in OpenShift
Closed: Fixed 4 years ago by kevin. Opened 4 years ago by asamalik.

Fedora Docs is build in OpenShift every hour in a pod that does the job and dies. However, the pod got stuck and runs for 4 days now, preventing other pods to start and build the site.

Could someone please kill it?

https://os.fedoraproject.org/console/project/docsbuilding/browse/pods/build-1560373200-4wm9h?tab=details


Done.

# oc -n docsbuilding delete pod build-1560373200-4wm9h
pod "build-1560373200-4wm9h" deleted

Metadata Update from @mizdebsk:
- Issue assigned to mizdebsk
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
- Issue tagged with: OpenShift

4 years ago

Thank you! 🔥🔥🔥

I'm wondering if something happened — new pods are not getting spawned every hour like they should have. Could that be related to this issue?

Metadata Update from @asamalik:
- Issue status updated to: Open (was: Closed)

4 years ago

This seems to be due to:

Warning FailedNeedsStart 30m (x7329 over 21h) cronjob-controller Cannot determine if job needs to be started: Too many missed start time (> 100). Set or decrease .spec.startingDeadlineSeconds or check clock skew.

So, I set startingDeadlineSeconds: 600 and it started fine the next run at the top of the hour.

Please re-open if there's still any issues.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata