token error – while reserving a slice

[Vidushi Mishra]

Hello I am  new to  Fabric. I have set up the bastion keys and executed the config_validate. I was trying to reserve a slice. and got the following error

Submitting the new slice, "CLOS_MTP"...

Auto-refresh on load failed: Token refresh failed: 500: HTTP request failed
{"errors":[{"message":"Internal Server Error","details":"An internal error occurred. Please try again or contact support."}],"type":"error","size":1,"status":500}

Slice Fail: Token refresh failed: 500: HTTP request failed
{"errors":[{"message":"Internal Server Error","details":"An internal error occurred. Please try again or contact support."}],"type":"error","size":1,"status":500}

[GG]

Hello,

Was this problem solved? My newly registered students cannot reserve the slices properly, even if they follow FABRIC’s “Start here” notebook and configuration instructions. Looks like those ipynb files have not been updated for at least a year, while FABRIC’s API has been changed since my old ipynb setup commands do not work anymore.

Thank you

[Komal Thareja]

Hi Garegin,

Could you please share the error they are encountering?

I verified that the configure_and_validate.ipynb notebook works without any issues with the latest API.

We also recommend using loomai.net as the new interface for accessing FABRIC. LoomAI is an AI-assisted graphical interface that also provides access to the existing JupyterHub environment.

Also, please try File -> Hub Control Panel -> Stop My Server, followed by Start My Server. This shall restart your Jupyter Hub container and refresh your tokens.

Please let me know if that resolves the issues.

Best,

Komal

• This reply was modified 1 week, 6 days ago by Komal Thareja.

[GG]

Thank you,

I think I identified the error. The ProjectID was incorrect and fixing it helped another student.

The problem was after fablib.verify_and_configure(). The error message was:

“FabricManagerException: No id_token available. Provide id_token parameter, set token_location, or pass tokens during init.”.

[Komal Thareja]

I’m glad to hear the issue has been resolved! Thank you for sharing the error message. We’ll work on making it clearer and more helpful.

Best,
Komal

[Author]

Posts