Add AzureKeyBasedAuthenticationNotPermitted to Hive error handling #4539
+60
−0
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
kimorris27
requested review from
bennerv,
cadenmarchese,
hawkowl,
hlipsig,
jharrington22,
mociarain,
mrWinston,
pepedocs,
rogbas,
sankur-codes,
tiguelu,
tsatam,
wanghaoran1988 and
yjst2012
as code owners
tsatam
approved these changes
Jan 6, 2026
shubhadapaithankar
approved these changes
Jan 6, 2026
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.
Which issue this PR addresses:
https://issues.redhat.com/browse/ARO-23318
What this PR does / why we need it:
There have been more and more of these Hive cluster install failures in the queue recently for some reason. The issue is always customer-inflicted by an Azure Policy that modifies a CSP cluster's storage account to disable key based authentication, so we should be returning the failure cause directly to the customer rather than responding to alerts and sending AzComms.
To get this going in prod, there are two more things I'll need to follow up with once this PR merges:
Test plan for issue:
Pushed additional install log regexes to eastus shared dev Hive and tested with a local dev cluster where I set up a policy just like a customer would; my local dev RP returned the
KeyBasedAuthenticationNotPermittedissue back to me.Is there any documentation that needs to be updated for this PR?
No
How do you know this will function as expected in production?
Tested thoroughly in local dev, which is close enough to prod in this case