Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-8806

3scale operator doesn't start on OCP 4.12

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Blocker
    • None
    • 2.13.0 GA, 2.12.1 GA
    • 3scale Operator
    • None
    • False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

    Description

      Since PodDisruptionBudget was moved from v1beta1 to v1 the deprecated version v1beta1 was removed in OCP 4.12. This prevents 3scale operator to start in OCP 4.12.
      The error message from operator follows:

      {"level":"error","ts":1665574491.4701285,"logger":"setup","msg":"problem running manager","error":"no matches for kind \"PodDisruptionBudget\" in version \"policy/v1beta1\"","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/remote-source/deps/gomod/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\nmain.main\n\t/remote-source/app/main.go:321\nruntime.main\n\t/opt/rh/go-toolset-1.13/root/usr/lib/go-toolset-1.13-golang/src/runtime/proc.go:203"}
      

      We are considering this bug as a blocker, because the release of 2.13 will happen before release of 4.12 and will affect all customers who would upgrade their cluster.

      Attachments

        Activity

          People

            Unassigned Unassigned
            mjaros@redhat.com Miroslav Jaroš
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: