You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously (prior to I'd say main.2847 but I am not 100%) upgrades via the KOTS dashboard worked without issue. They are however failing at the moment. From the kots-installer pod logs:
Error: UPGRADE FAILED: release gitpod failed, and has been rolled back due to atomic being set: cannot patch "openvsx-proxy" with kind StatefulSet: StatefulSet.apps "openvsx-proxy" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', 'updateStrategy' and 'minReadySeconds' are forbidden
I'm wondering if this may be a regression of #8657?
Steps to reproduce
Spin up a new instance of Gitpod via the KOTS installer.
Await a new version of Gitpod to be deployed.
Use the lovely upgrade functionality within KOTS in order to attempt to upgrade your instance.
Follow the installer pod logs - ex. kubectl logs -f pod/installer-abcdef.
After about 10 minutes observe the error regarding StatefulSet on openvsx-proxy.
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Uh oh!
There was an error while loading. Please reload this page.
Bug description
Previously (prior to I'd say
main.2847
but I am not 100%) upgrades via the KOTS dashboard worked without issue. They are however failing at the moment. From thekots-installer
pod logs:I'm wondering if this may be a regression of #8657?
Steps to reproduce
kubectl logs -f pod/installer-abcdef
.StatefulSet
onopenvsx-proxy
.Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: