Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-2610

Quay upgrade from 3.3.4 to 3.6.0 report error "unexpected error updating component conditions"

XMLWordPrintable

      Description:

      This is an issue found when use Quay 3.6.0 Operator to upgrade quay from 3.3.4 to 3.6.0, after the upgrade completed successfully, check Quay Operator POD Logs, get error message "unexpected error updating component conditions", this will confuse Quay Customers, pls remove this invalid error message.

      2021-09-29T03:28:51.018Z	INFO	controllers.QuayRegistry	Quay upgrade complete, updating `status.currentVersion`	{"quayregistry": "quay334/quay33"}
      2021-09-29T03:28:51.024Z	DEBUG	controller-runtime.manager.events	Normal	{"object": {"kind":"QuayRegistry","namespace":"quay334","name":"quay33","uid":"76258a27-a75b-4cad-928d-1e7d48eb9fd7","apiVersion":"quay.redhat.com/v1","resourceVersion":"8788688"}, "reason": "HealthChecksPassing", "message": "all registry component healthchecks passing"}
      2021-09-29T03:28:51.043Z	INFO	controllers.QuayRegistry	successfully updated `status` after Quay upgrade	{"quayregistry": "quay334/quay33"}
      2021-09-29T03:28:51.047Z	ERROR	controllers.QuayRegistryStatus	unexpected error updating component conditions	{"quayregistrystatus": "quay334/quay33", "error": "Operation cannot be fulfilled on quayregistries.quay.redhat.com \"quay33\": the object has been modified; please apply your changes to the latest version and try again"}
      github.com/go-logr/zapr.(*zapLogger).Error
      	/workspace/vendor/github.com/go-logr/zapr/zapr.go:132
      github.com/quay/quay-operator/controllers/quay.(*QuayRegistryStatusReconciler).Reconcile
      	/workspace/controllers/quay/quayregistry_status_controller.go:114
      sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
      	/workspace/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:297
      sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
      	/workspace/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:252
      sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1.2
      	/workspace/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:215
      k8s.io/apimachinery/pkg/util/wait.JitterUntilWithContext.func1
      	/workspace/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:185
      k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1
      	/workspace/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:155
      k8s.io/apimachinery/pkg/util/wait.BackoffUntil
      	/workspace/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:156
      k8s.io/apimachinery/pkg/util/wait.JitterUntil
      	/workspace/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133
      k8s.io/apimachinery/pkg/util/wait.JitterUntilWithContext
      	/workspace/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:185
      k8s.io/apimachinery/pkg/util/wait.UntilWithContext
      	/workspace/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:99
      

       

              rmarasch@redhat.com Ricardo Maraschini (Inactive)
              lzha1981 luffy zhang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: