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

APIServer service isn't selected correctly for PublicAndPrivate cluster when external-dns is not configured

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • 4.12.z
    • 4.14
    • HyperShift
    • None
    • No
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-10864. The following is the description of the original issue:

      Description of problem:

      APIServer service not selected correctly for PublicAndPrivate when external-dns isn't configured. 
      Image: 4.14 Hypershift operator + OCP 4.14.0-0.nightly-2023-03-23-050449
      
      jiezhao-mac:hypershift jiezhao$ oc get hostedcluster/jz-test -n clusters -ojsonpath='{.spec.platform.aws.endpointAccess}{"\n"}'
      PublicAndPrivate
      
          - lastTransitionTime: "2023-03-24T15:13:15Z"
            message: Cluster operators console, dns, image-registry, ingress, insights,
              kube-storage-version-migrator, monitoring, openshift-samples, service-ca are
              not available
            observedGeneration: 3
            reason: ClusterOperatorsNotAvailable
            status: "False"
            type: ClusterVersionSucceeding
      
      services:
        - service: APIServer
         servicePublishingStrategy:
          type: LoadBalancer
        - service: OAuthServer
         servicePublishingStrategy:
          type: Route
        - service: Konnectivity
         servicePublishingStrategy:
          type: Route
        - service: Ignition
         servicePublishingStrategy:
          type: Route
        - service: OVNSbDb
         servicePublishingStrategy:
          type: Route
      
      jiezhao-mac:hypershift jiezhao$ oc get service -n clusters-jz-test | grep kube-apiserver
      kube-apiserver            LoadBalancer  172.30.211.131  aa029c422933444139fb738257aedb86-9e9709e3fa1b594e.elb.us-east-2.amazonaws.com  6443:32562/TCP         34m
      kube-apiserver-private        LoadBalancer  172.30.161.79  ab8434aa316e845c59690ca0035332f0-d818b9434f506178.elb.us-east-2.amazonaws.com  6443:32100/TCP         34m
      jiezhao-mac:hypershift jiezhao$
      
      jiezhao-mac:hypershift jiezhao$ cat hostedcluster.kubeconfig | grep server
        server: https://ab8434aa316e845c59690ca0035332f0-d818b9434f506178.elb.us-east-2.amazonaws.com:6443
      jiezhao-mac:hypershift jiezhao$
      
      jiezhao-mac:hypershift jiezhao$ oc get node --kubeconfig=hostedcluster.kubeconfig 
      E0324 11:17:44.003589   95300 memcache.go:238] couldn't get current server API group list: Get "https://ab8434aa316e845c59690ca0035332f0-d818b9434f506178.elb.us-east-2.amazonaws.com:6443/api?timeout=32s": dial tcp 10.0.129.24:6443: i/o timeout

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

       

      How reproducible:

      Always

      Steps to Reproduce:

      1.Create a PublicAndPrivate cluster without external-dns
      2.access the guest cluster (it should fail)
      3.
      

      Actual results:

      unable to access the guest cluster via 'oc get node --kubeconfig=<guest cluster kubeconfig>', some guest cluster co are not available

      Expected results:

      The cluster is up and running, the guest cluster can be accessed via 'oc get node --kubeconfig=<guest cluster kubeconfig>'

      Additional info:

       

       

            sjenning Seth Jennings
            openshift-crt-jira-prow OpenShift Prow Bot
            Liangquan Li Liangquan Li
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: