[UX/AWS] When SSO expired, `sky status` shows a lot SSO error
When AWS SSO session expired, sky status can show a lot of SSO error if the catalog needs to be updated or is removed (reached the update frequency).
File "/opt/conda/envs/sky-dev/lib/python3.10/site-packages/botocore/tokens.py", line 95, in _refresh
self._protected_refresh()
File "/opt/conda/envs/sky-dev/lib/python3.10/site-packages/botocore/tokens.py", line 122, in _protected_refresh
raise TokenRetrievalError(
botocore.exceptions.TokenRetrievalError: Error when retrieving token from sso: Token has expired and refresh failed
D 09-20 08:16:38 aws_catalog.py:146] Failed to get AWS user identity. Using the latest mapping file for user 'b710cff4'.
Version & Commit info:
-
sky -v: PLEASE_FILL_IN -
sky -c: PLEASE_FILL_IN
For record from #3754
A user reported that, even with sky status, it requires AWS SSO login once the authentication is expired. This is unexpected, as the sky status should be considered to be not needing to connect to the clouds.
isn't it the expected behavior?) there is a command to just refresh the token for sso - aws sso login --profile <aws_sso_profile>
It is expected when we are running operations that need to access clouds, but sky status conceptually should only check the local status, and it is bothering for seeing those error message. :)
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 10 days.
I ran into this error when my credentials expired after my jobs had been launched. most status works, but "managed jobs" does not.
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 10 days.
This issue was closed because it has been stalled for 10 days with no activity.