Investigate Deployment crash loop

When deploying GitLab in !101 (merged), I saw these errors in the Operator logs:

2021-03-04T02:06:10.017Z ERROR controller Reconciler error {"reconcilerGroup": "apps.gitlab.com", "reconcilerKind": "GitLab", "controller": "gitlab", "name": "gitlab", "namespace": "gitlab-system", "error": "Operation cannot be fulfilled on deployments.apps "gitlab-sidekiq-all-in-1-v1": the object has been modified; please apply your changes to the latest version and try again"}

│ manager 2021-03-04T18:52:58.306Z ERROR controller Reconciler error {"reconcilerGroup": "apps.gitlab.com", "reconcilerKind": "GitLab", "controller": "gitlab", "name": "gitlab", "namespace": "gitlab-system", "error": "Operation cannot be fulfilled on deployments.apps "gitlab-webservice-default": the object has been modified; please apply your changes to the latest version and try again"}

│ manager 2021-03-04T18:53:29.338Z ERROR controller Reconciler error {"reconcilerGroup": "apps.gitlab.com", "reconcilerKind": "GitLab", "controller": "gitlab", "name": "gitlab", "namespace": "gitlab-system", "error": "Operation cannot be fulfilled on deployments.apps "gitlab-registry": the object has been modified; please apply your changes to the latest version and try again"}

The first pod(s) related to these deployments stay running indefinitely, but new ones are periodically created and then disappear within just a few seconds.

We should follow up to ensure this is fixed. When trying to log into the GitLab instance via the browser (port-forwarded the service), I got an error (422). Not sure if this is related but the only other pod with issues was registry (addressed in !90 (merged)).

Edited Mar 04, 2021 by Mitchell Nielsen
Assignee Loading
Time tracking Loading