Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-5952

PTP operator failed to upgrade because "Policy rule not satisfied for service account"

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      While upgrading both platform and operators of 3423 SNOs, 1 cluster failed to upgrade the ptp operator because the csv reported "Policy rule not satisfied for service account"

      Version-Release number of selected component (if applicable):

      SNO OCP 4.10.32 (Clusters with issue) attempting to be upgraded to 4.11.5
      Hub OCP 4.11.19
      ACM Version - 2.7.0-DOWNSTREAM-2023-01-12-20-55-01
      Operators being upgraded from the v4.10 to the v4.11 operators catalog
      ptp upgraded to ptp-operator.4.11.0-202301031954 from ptp-operator.4.10.0-202212072254

      How reproducible:

      Extremely rare 1 out of 3423
      1 out of 84 failures encountered during the upgrade

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

       

      Expected results:

       

      Additional info:

      # oc --kubeconfig=/root/hv-vm/sno/manifests/sno03065/kubeconfig get csvs -n openshift-ptp 
      NAME                               DISPLAY        VERSION               REPLACES                           PHASE
      ptp-operator.4.11.0-202301031954   PTP Operator   4.11.0-202301031954   ptp-operator.4.10.0-202212072254   Pending
      # oc --kubeconfig=/root/hv-vm/sno/manifests/sno03065/kubeconfig get installplans -n openshift-ptp 
      NAME            CSV                                APPROVAL   APPROVED
      install-gzg2c   ptp-operator.4.11.0-202301031954   Manual     true
      install-vj46r   ptp-operator.4.10.0-202212072254   Manual     true

              vgrinber@redhat.com Vitaly Grinberg
              akrzos@redhat.com Alex Krzos
              Ofer Bochan Ofer Bochan
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: