Call stacks were included in the error of keymanagementprovider resource

[yizha1]

What happened in your environment?

I specified a non-existing tenantID or clientID for accessing AKV, and then used the command kubectl get keymanagementprovider to check the status. The ISSUCCESS was false which was as expected. However, when I described the specific keymanagementprovider resource, the error field included a lengthy call stack, most users don’t need to deal with those messages.

What did you expect to happen?

The error field should include concise and precise messages about error description, the reason and possible mitigation methods.

What version of Kubernetes are you running?

AKS

What version of Ratify are you running?

0-dev (dev.20240505.6163b7e)

Anything else you would like to add?

No response

Are you willing to submit PRs to contribute to this bug fix?

• Yes, I am willing to implement it.

[susanshi]

HI @yizha1 , would you be able to include the customer scenario and detailed error log? thanks

[yizha1]

@susanshi It seems that I did not save the original log, so I cannot provide it. But it is easy to reproduce, the scenarios are related to configuration of azurekeyvault KMP, users specify a wrong value for tenantID or ClientID that is required for the KMP resource. Then you follow the description of this issue to check the error, you will find a lengthy call stack is shown.