[Komal Thareja]

Hi,

I was able to run the notebook .

Could you please share your Slice ID?

Additionally, could you post your inquiries in the FABRIC General Questions and Discussion forum?

Thanks,

Komal

[Komal Thareja]

Hi Yuanjun,

Could you please try SSH into your VMs now? We were able to successfully SSH to the VMs.

Additionally, could you post your inquiry in the FABRIC General Questions and Discussion forum?

Thanks,

Komal

[Komal Thareja]

Hi Yuanjun,

Unfortunately, the STAR resources you’re requesting are currently in use. Please try again later or consider scheduling your slices in advance using the notebook.

Additionally, could you post your inquiry in the FABRIC General Questions and Discussion forum?

Thanks,
Komal

[Komal Thareja]

Hi Yuanjun,

Unfortunately, the MAX resources you’re requesting are currently in use. Please try again later or consider scheduling your slices in advance using the notebook.

Additionally, could you post your inquiry in the FABRIC General Questions and Discussion forum?

Thanks,
Komal

[Komal Thareja]

Glad to hear that worked! We will work to address this and add support to interrupt/return meaningful error in such cases.

Thanks,

Komal

[Komal Thareja]

Hi Kriti,

Could you please re-run this notebook: jupyter-examples-rel1.8.1/configure_and_validate/configure_and_validate.ipynb ?
This shall renew any expired keys. Please try your slice again after this. I want to rule out any SSH errors. If you continue to see the error, please share /tmp/fablib/fablib.log

Thanks,
Komal

[Komal Thareja]

Authentication failed would explain the SSH errors you are observing. Could you please re-run this notebook: jupyter-examples-rel1.8.1/configure_and_validate/configure_and_validate.ipynb ?
This shall renew any expired keys. Please try your slice again after this.

Thanks,
Komal

[Komal Thareja]

Hi,

Please try the following snippet. Please note that list_sites() should be invoked before show_site().

We will fix this to return a more meaningful error in the next version.


from fabrictestbed_extensions.fablib.fablib import FablibManager as fablib_manager
fablib = fablib_manager()
fablib.list_sites()
fablib.get_resources().show_site("HAWI")


Thanks,
Komal

[Komal Thareja]

Thank you Justas! I haven’t been able to reproduce this even on JH Stable 1.8 container. Could you please share /tmp/fablib/fablib.log file from your container?

Also, please share the sliceid of your new slice.

Thanks,

Komal

[Komal Thareja]

Could you please try this with Beyond Bleeding Edge Container? I wasn’t able to reproduce this issue there. Trying it with 1.8 Stable container now.

Thanks,

Komal

[Komal Thareja]

Hey Kriti,

Could you please share which JH container were you using when you noticed this issue?

Thanks,

Komal

[Komal Thareja]

Also, could you please share which JH container are you using?

Thanks,

Komal

[Komal Thareja]

Hi,

Both your slices  are in Stable State. It seems like a bug in fablib or a race condition which is causing fablib to think the slice is still Configuring.

As a workaround, could you please do the following?

I am trying to reproduce this at my end and would work to fix this. Apologies for the inconvenience!


slice=fablib.get_slice(slice_name)
slice.post_boot_config()
slice.list_nodes();
slice.list_interfaces();



Slice Name: FRR-losa Slice ID: 0367f6f3-1331-49dc-9399-722616237a5b Project ID: a57c7715-d871-4369-82e6-408c9a57a6e7 Project Name: UCSD-FABRIC test
Graph ID: 071abcd4-f292-449d-a69a-da4768780546
Slice owner: { name: orchestrator, guid: orchestrator-guid, oidc_sub_claim: 91f5ecc3-16ff-4f09-95ac-dfeee0c3b1e3, email: jbalcas@es.net}
Slice state: StableOK
Lease time: 2025-02-07 14:24:38+00:00


Thanks,

Komal

[Komal Thareja]

Hi Raghav,

Please set up your JH environment by running the notebook: jupyter-examples-rel1.8.1/configure_and_validate/configure_and_validate.ipynb

This shall setup all the required configuration files and SSH keys. Please try the Wide Area Link notebook or Hello Fabric after that to ensure your configuration works. Please let us know if you run into issues.

Thanks,

Komal

[Komal Thareja]

Issue resolved over zoom meeting, the issue was the token.

Token file only had id_token instead of the entire token contents. Downloading the token file and using that resolved the issue.

Please let us know if you run into any other issues. I have taken a note to return a more user friendly error. We will address this in the next release.

Thanks,

Komal

[Author]

Posts