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

Private router not deployed in HCP namespace on a 4.13 mgmt cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.14.0
    • 4.13, 4.14
    • HyperShift
    • None
    • Important
    • No
    • Hypershift Sprint 234, Hypershift Sprint 235, Hypershift Sprint 236
    • 3
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Cluster does not finish rolling out on a 4.13 management cluster because of pod security constraints.

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

      4.14

      How reproducible:

      Always

      Steps to Reproduce:

      1.Install 4.14 hypershift operator on a recent 4.13 mgmt cluster
2.Create an AWS PublicAndPrivate hosted cluster on that hypershift cluster

      Actual results:

      Hosted cluster stalls rollout because the private router never gets created

      Expected results:

      Hosted cluster comes up successfully

      Additional info:

      Pod security enforcement is preventing the private router from getting created.

              cewong@redhat.com Cesar Wong
              cewong@redhat.com Cesar Wong
              Jie Zhao Jie Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: