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

[ALBO] Appliacation Load Balancer (ALB) is not accessible in Local Zone cluster

XMLWordPrintable

    • Important
    • No
    • 1
    • Sprint 239
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      The ALB is not reachable in OSD cluster with Local zone

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

      4.13.4

      How reproducible:

      100%

      Steps to Reproduce:

      1. Create OSD cluster
      2. Create Local zone and add two worker nodes
      
      $ oc -n openshift-machine-api get machine
      NAME                                               PHASE     TYPE         REGION      ZONE               AGE
      sdq-ccs-jkvab-8zgjk-infra-us-east-1a-gwgwf         Running   r5.xlarge    us-east-1   us-east-1a         4h53m
      sdq-ccs-jkvab-8zgjk-infra-us-east-1b-stfj4         Running   r5.xlarge    us-east-1   us-east-1b         4h53m
      sdq-ccs-jkvab-8zgjk-infra-us-east-1c-qtvgl         Running   r5.xlarge    us-east-1   us-east-1c         4h53m
      sdq-ccs-jkvab-8zgjk-master-0                       Running   m5.2xlarge   us-east-1   us-east-1a         5h18m
      sdq-ccs-jkvab-8zgjk-master-1                       Running   m5.2xlarge   us-east-1   us-east-1b         5h18m
      sdq-ccs-jkvab-8zgjk-master-2                       Running   m5.2xlarge   us-east-1   us-east-1c         5h17m
      sdq-ccs-jkvab-8zgjk-mp-lz-us-east-1-bos-1a-l26mv   Running   t3.xlarge    us-east-1   us-east-1-bos-1a   3h53m
      sdq-ccs-jkvab-8zgjk-mp-lz-us-east-1-bos-1a-pr2bc   Running   t3.xlarge    us-east-1   us-east-1-bos-1a   3h53m
      sdq-ccs-jkvab-8zgjk-worker-us-east-1a-jk8md        Running   m5.xlarge    us-east-1   us-east-1a         5h15m
      sdq-ccs-jkvab-8zgjk-worker-us-east-1b-mhq56        Running   m5.xlarge    us-east-1   us-east-1b         5h15m
      sdq-ccs-jkvab-8zgjk-worker-us-east-1c-lq827        Running   m5.xlarge    us-east-1   us-east-1c         5h15m
      
       
      3. Install ALBO and Controller
      kind: AWSLoadBalancerController
      apiVersion: networking.olm.openshift.io/v1
      metadata:
        name: cluster
      spec:
        ingressClass: alb
        subnetTagging: Auto
        additionalResourceTags:
        - key: albo-test
          value: tags
      
      
      4. Create test pod,svc and ingress
      apiVersion: networking.k8s.io/v1
      kind: Ingress
      metadata:
        name: ingress-test
        annotations:
          alb.ingress.kubernetes.io/scheme: internet-facing
          alb.ingress.kubernetes.io/target-type: instance
      spec:
        ingressClassName: alb
        rules:
        - host: foo.bar.com
          http:
            paths:
            - backend:
                service:
                  name: service-unsecure
                  port:
                    number: 27017
              path: /
              pathType: Exact
      
      
      
      5. Check the ingress and if ALB provisioned
      
      $ oc get ingress
      NAME           CLASS   HOSTS         ADDRESS                                                                PORTS   AGE
      ingress-test   alb     foo.bar.com   k8s-hongli-ingresst-90ec2debaf-947179752.us-east-1.elb.amazonaws.com   80      37m
      
      6. Access the ALB
      $ curl k8s-hongli-ingresst-90ec2debaf-947179752.us-east-1.elb.amazonaws.com -H "Host: foo.bar.com"
      curl: (28) Failed to connect to k8s-hongli-ingresst-90ec2debaf-947179752.us-east-1.elb.amazonaws.com port 80 after 214905 ms: Connection timed out
      
      
      
      

      Actual results:

      Connection timed out when accessing the ALB

      Expected results:

      Should access the ALB

      Additional info:

       

              alebedev@redhat.com Andrey Lebedev
              rhn-support-hongli Hongan Li
              Hongan Li Hongan Li
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: