-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added retry if fetching token for SPN auth fails with status code 403 #10447
Conversation
Can u link this with an issue |
@hiyadav I am re-opening your PR as we are seeing increased failures in ARG task getting access token for SPN. |
@Ajay-MS @sachinma @vincentdass please review |
@bishal-pdMSFT did you verify that the issue was indeed while getting token. As per your last observations - it was while talking to ARM? |
If we are actually seeing this while fetching token - the change looks okay to me |
Yes, the error is during fetching taken. There was another similar error which was when talking to ARM - more specifically if user has deleted resource group. last time I was talking about this error which required no fix. |
@Ajay-MS / @vincentdass / @sachinma can you please review and approve? |
d63c92e
to
5fa6ca4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You would probably need to update the task versions.
Yes, I was not aware that we need to update all dependent tasks version now. |
…th status code 403 (#10447)
Fixes #10860
In case of newly created SPN, getting access token can fail with status code 403. This can happen due to SPN replication delay.
Hence, we should add retry if failure status code is 403.