Skip to content

KOTS Performing Automatic Updates Even When Not Configured Too #10353

Closed
@jimmybrancaccio

Description

@jimmybrancaccio

Bug description

KOTS appears to be performing automatic updates to my Gitpod instance even when it is not configured too. This results in a broken install since I use ClusterIP and not LoadBalancer. This in turn results in an "infinite loop" of attempted rollbacks.

Screen Shot 2022-05-30 at 08 25 43AM

18      	Fri May 27 12:45:09 2022	deployed        	gitpod-kots-1.0.0	main.3384  	Upgrade complete
19      	Sun May 29 15:10:29 2022	failed          	gitpod-kots-1.0.0	main.3384  	Upgrade "gitpod" failed: timed out waiting for the condition
20      	Sun May 29 15:16:26 2022	failed          	gitpod-kots-1.0.0	main.3384  	Release "gitpod" failed: timed out waiting for the condition
21      	Sun May 29 15:22:12 2022	pending-rollback	gitpod-kots-1.0.0	main.3384  	Rollback to 19

Revision 18 was a manual update I performed on Friday, then on Sunday something seems to have happened where it tried updating itself? I ran a manual rollback to 18 myself this morning to resolve the issue.

I faintly remember this happening last Sunday too, is there some sort of automation we have in place to run on Sundays?

Steps to reproduce

  1. Spin up a KOTS instance of Gitpod.
  2. You may need to wait until Sunday (afternoon) for you to observe that some sort of automation attempted to take place.
  3. You can review the helm history - helm history gitpod --namespace gitpod.

Workspace affected

No response

Expected behavior

No response

Example repository

No response

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    meta: staleThis issue/PR is stale and will be closed soontype: bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions