Carry degrade reasons on the remaining extension errors - #5166
Merged
caseydavenport merged 2 commits intoAug 13, 2026
Conversation
Restores the per-error status reasons the enterprise controllers used before the extension split.
Brian-McM
approved these changes
Aug 13, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follow-on to #4871, for CORE-13340.
Errors returned from the enterprise extensions came back unclassified, so the controllers degraded with a generic create-error reason no matter what actually failed. Each error site now carries the same status reason the controller reported for it before the extension split, and the tests assert the reason per failed read.