Slice showing as StableOK but is actually closed

[Anthony Ulloa]

Hello all,

I encountered an issue where I cannot SSH into my node after initiating a Globus node transfer. I didn’t work on anything else prior relating to the slice, or the configuration. I reprovisioned the slice but the same issue is present where it is not reachable:

fabric@winter:work-17%$ ssh -F /home/fabric/work/fabric_config/ssh_config -i /home/fabric/work/fabric_config/slice_key rocky@131.94.57.34 Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts. channel 0: open failed: connect failed: Connection timed out stdio forwarding failed kex_exchange_identification: Connection closed by remote host Connection closed by UNKNOWN port 65535 fabric@winter:work-17%$

I checked the slice status and it’s showing “StableOK” on the slice dashboard. However after asking a FABRIC member to take a closer look, the following error was shown on the back-end:

“notices”: “Reservation 052a7159-0741-4347-b8e4-5de38308c6d0 (Slice AmLight-L3-FacilityPort(a5d2fff2-84fc-48d9-8d67-5ff96e120273) Graph Id:da197621-2208-4851-83d5-decaf52c50f4 Owner:anulloa@fiu.edu) is in state (Closed,None_) (Last ticket update: Insufficient resources : [‘core’])”,

My SSH keys should be valid and the slice had no issue before the attempted transfer. Attached are the details of the slice:

Slice ID: a5d2fff2-84fc-48d9-8d67-5ff96e120273
IP Address: 131.94.57.34
JupyterLab Server Used: (default) FABRIC Examples v1.8.0, FABlib v1.8.0: released: 01/10/2025, stable: Winter 2025

If anyone could help me on regaining access to the server without recreating, that would be of help. If that is the last resort, I will go ahead and do that, but I would just like to avoid this in the future or find a fix. Thank you so much!

 

[Komal Thareja]

Hi Anthony,

Regarding your slice: a5d2fff2-84fc-48d9-8d67-5ff96e120273
Start: 2025-04-18 14:53:43 +0000
End: 2025-05-02 14:53:42 +0000

A renew operation was attempted for this slice, but it failed for the VM due to insufficient resources: ['core'].

Please note that we now support advance reservations, which allow users to reserve resources ahead of time. As a result, a renew request may fail if it conflicts with an existing advance reservation — which appears to be the case here.

It’s unclear how the renew was initiated, but if it was done through JupyterHub, the error would have been reported to the user. We suspect there may be a bug on the portal side where this error is not being surfaced correctly, and we will investigate and address that.

Unfortunately, the only available option at this point is to re-create the slice. We apologize for the inconvenience.

Thanks,

Komal

[Author]

Posts