| Type |
Bug
|
| Priority |
Critical
|
| Assignee | |
| Affected Versions |
16.7.0
|
| Labels |
No labels
|
Issue Votes (0)
| Type |
Bug
|
| Priority |
Critical
|
| Assignee | |
| Affected Versions |
16.7.0
|
| Labels |
No labels
|
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:
No further log lines appear, no error is thrown, and the readiness probe never succeeds. The pod just stays in 0/1 Running.