Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2069782

Summary: Ingress AWS NLB got provisioned in additional AZ
Product: OpenShift Container Platform Reporter: Bharat <bbabbar>
Component: NetworkingAssignee: Miciah Dashiel Butler Masters <mmasters>
Networking sub component: router QA Contact: Arvind iyengar <aiyengar>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, apaladug, hongli, mmasters
Version: 4.8   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-11 14:17:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bharat 2022-03-29 16:49:12 UTC
Description of problem:
Ingress AWS NLB got provisioned in additional AZ which was not even provided to the installer during OCP deployment

OpenShift release version:
4.8.10


Cluster Platform:
AWS IPI

How reproducible:
100%

Steps to Reproduce (in detail):
1. create install-config.yaml like below:


apiVersion: v1
baseDomain: lab.example.com
credentialsMode: Mint
controlPlane:
  hyperthreading: Enabled
  name: master
  platform:
    aws:
      zones:
      - us-east-1a
      - us-east-1b
      - us-east-1c
      rootVolume:
        iops: 4000
        size: 500
        type: io1
      type: c5.2xlarge
  replicas: 3
compute:
- hyperthreading: Enabled
  name: worker
  platform:
    aws:
      rootVolume:
        iops: 2000
        size: 500
        type: io1
      type: c5.4xlarge
      zones:
      - us-east-1a
      - us-east-1b
      - us-east-1c
  replicas: 3
metadata:
  creationTimestamp: null
  name: prd-dr
networking:
  clusterNetwork:
  - cidr: 10.155.0.0/17
    hostPrefix: 24
  machineNetwork:
  - cidr: 10.156.136.0/21
  networkType: OpenShiftSDN
  serviceNetwork:
  - 10.157.0.0/20
platform:
  aws:
    region: us-east-1
    subnets:
    - subnet-XXX
    - subnet-XXX
    - subnet-XXX
fips: false
publish: Internal
sshkey: ssh-rsa


2. Install using the above install-config.yaml 

3. Replace CLB with AWS NLB

$ oc get ingresscontroller  default -o yaml
spec:
  endpointPublishingStrategy:
    loadBalancer:
      providerParameters:
        aws:
          type: NLB
        type: AWS
      scope: Internal
    type: LoadBalancerService
  httpErrorCodePages:
    name: ''
  replicas: 3
  tuningOptions: {}
  unsupportedConfigOverrides: null


Actual results:
AWS NLB observed to be added to additional AZ
that is us-east-1d

Expected results:

The ingress NLB should only be provisioned on   
      - us-east-1a
      - us-east-1b
      - us-east-1c

Impact of the problem:


Additional info:



** Please do not disregard the report template; filling the template out as much as possible will allow us to help you. Please consider attaching a must-gather archive (via `oc adm must-gather`). Please review must-gather contents for sensitive information before attaching any must-gathers to a bugzilla report.  You may also mark the bug private if you wish.

Comment 2 Miciah Dashiel Butler Masters 2022-03-31 16:42:50 UTC
Possible duplicate of bug 2027137.

Comment 3 Anand Paladugu 2022-04-08 14:25:00 UTC
@bbabbar 

Have you checked to see if the cause/workaround as mentioned in BZ 2027137  apply in this case ?

Comment 16 Miciah Dashiel Butler Masters 2022-05-11 14:17:33 UTC
It appears that the service.beta.kubernetes.io/aws-load-balancer-subnets annotation was not set when the logs were gathered, and comment 15 indicates we won't be getting further logs.  I'll have to assume that the annotation was not set correctly and that this is in fact the same issue as bug 2027137.

*** This bug has been marked as a duplicate of bug 2027137 ***