Skip to content

Bug-fix for fetching region from AWS cluster obj in GetAWSRegion()#1483

Merged
aayushchouhan09 merged 1 commit intonoobaa:masterfrom
aayushchouhan09:region-fix
Dec 11, 2024
Merged

Bug-fix for fetching region from AWS cluster obj in GetAWSRegion()#1483
aayushchouhan09 merged 1 commit intonoobaa:masterfrom
aayushchouhan09:region-fix

Conversation

@aayushchouhan09
Copy link
Member

@aayushchouhan09 aayushchouhan09 commented Dec 3, 2024

Explain the changes

  1. Root Cause: The problem arises when the AWS cluster region cannot be determined from node names, especially in cases where the node naming convention does not include the region or when the DHCP option modifies DNS settings, causing standard parsing methods to fail.

  2. Solution: To resolve this, the solution first attempts to fetch the region directly from the cluster configuration, which is the most reliable source. If this fails, it falls back to parsing the region from the node name.

Issues: Fixed #xxx / Gap #xxx

  1. Bug: https://issues.redhat.com/browse/DFBUGS-747

Testing Instructions:

  1. Install noobaa operator on AWS cluster and check for default backingstore creation with DHCP option set and not set.

Signed-off-by: Aayush Chouhan <achouhan@redhat.com>
@aayushchouhan09 aayushchouhan09 merged commit 1fd00fb into noobaa:master Dec 11, 2024
vh05 pushed a commit to vh05/noobaa-operator that referenced this pull request Dec 11, 2024
Bug-fix for fetching region from AWS cluster obj in GetAWSRegion()

Signed-off-by: Vinayak Hariharmath <vinayak.hariharmath@gmail.com>
@aayushchouhan09 aayushchouhan09 deleted the region-fix branch May 6, 2025 07:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants