fix extraction of EBS volume id when there's no region prefix #2351
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jopadi
requested review from
FxKu,
Jan-M,
hughcapet,
idanovinda and
sdudoladov
as code owners
FxKu
changed the title
FxKu
changed the title
Jan-M
reviewed
Jun 9, 2023
|
👍 |
|
👍 |
1 similar comment
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
Users encountered an error when trying to modify the IOPS and throughput of an existing and new EBS volume. The error message displayed:
populating EBS meta data failed, skippinq potential adiustements: MissinqParameter: The request must contain the parameter volumes status code: 400.Cause:
This problem occurs because AWS does not presenting the
awsElasticBlockStore.volumeIDin Kubernetes such asaws://eu-central-1c/vol-0432294a5a7e57939, as it was before now it's being show asvol-0432294a5a7e57939. Consequently, the Postgres operator is unable to locate the correct volume ID for modifying the IOPS and throughput.Solution:
To resolve this problem, the Postgres operator should still recognize the previous volume ID format while also being able to identify the new formatting. One method is to ensure the volume ID retains the same prefix
/vol-as it did before.