Fix MCV resource retrieval error conversion #873
Merged
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.
Previously, there was an issue where the conversion of MCV retrieval errors was not handled properly, leading to unexpected behavior in certain cases.
This PR fixes the issue by parsing the
MCV.Status.Conditions[0].Message
field for known error strings, Specificallynot found
andthe server could not find the requested resource
error messages. While this approach is effective for identifying errors in the short term, it is not a sustainable solution.As a next step, an issue should be opened against the ACM View Controller to fix and improve the MCV status,
potentially by adding the last error to the
MCV.Status
field. This would allow for more comprehensive and accurateerror reporting, and reduce the need for temporary workarounds.
Fixes: bz:2138855 and bz:2170684
Multicloud-operators-foundation
for preserving original error inview_controller
resource retrievalissue: here