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

TestCertRotationTimeUpgradeable failing consistently in kube-apiserver-operator

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.12
    • kube-apiserver
    • Important
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • NA

      Description of problem:

      https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-kube-apiserver-operator/1382/pull-ci-openshift-cluster-kube-apiserver-operator-master-e2e-gcp-operator/1577508664229498880
      
      After closer look at kube-apiserver-operator logs, the reason the cluster is not upgradeable is that the installer pods are failing to talk to API server:
      
      <snippet from installer log>
      cmd.go:418] unable to get owner reference (falling back to namespace): Unauthorized
      </snippet>
      
      This seems to be regression after rebase and has to be investigated before we release 4.12 to make sure the cert rotation works as expected and not brick clusters.
      
      

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

      4.12 / master branch

      How reproducible:

      https://prow.ci.openshift.org/job-history/gs/origin-ci-test/pr-logs/directory/pull-ci-openshift-cluster-kube-apiserver-operator-master-e2e-gcp-operator

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

       

      Expected results:

       

      Additional info:

       

            Unassigned Unassigned
            mfojtik@redhat.com Michal Fojtik
            Ke Wang Ke Wang
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: