OD-3129: Pod never becomes ready after upgrading to OneDev 16.7.0

Pod never becomes ready after upgrading to OneDev 16.7.0 #3129

christoffers opened 1 month ago

I upgraded OneDev from 16.6.3 to 16.7.0 in Kubernetes. The upgrade itself completed without errors, but the pod never reaches a ready state — it appears to hang after JVM startup and stays there indefinitely.

Pod logs stop here:

Launching a JVM...
WrapperManager: Initializing...
20:00:50 INFO  i.onedev.commons.bootstrap.Bootstrap - Launching application from '/opt/onedev'...
20:00:50 INFO  i.onedev.commons.bootstrap.Bootstrap - Cleaning temp directory...
20:00:52 INFO  io.onedev.commons.loader.AppLoader - Starting application...

No further log lines appear, no error is thrown, and the readiness probe never succeeds. The pod just stays in 0/1 Running.

Copy

Robin Shen commented 1 month ago

While investigating this issue, please restart both pods and it should be working after restarted.

Copy
OneDev commented 1 month ago

State changed as build OD-8492 is successful

Copy
OneDev changed state to 'Closed' 1 month ago
Previous Value Current Value
Open

Closed
christoffers commented 1 month ago

Does this change imply that, when running with multiple replicas, we need to scale the StatefulSet down to 1 replica before performing an upgrade?

Copy
Robin Shen commented 1 month ago

It will be scaled to 0 to make sure all pods are stopped before upgrade, the scaled back to previous number. If scale down policy is to delete storage, it will refuse to scale down and exit the upgrade.

Copy
Login to comment

Previous Value	Current Value
Open	Closed

Type	Bug
Priority	Critical
Assignee	Robin Shen
Affected Versions	16.7.0
Labels	No labels

Issue Votes (0)

Watchers (4)

Reference

OD-3129