1. Slice Renewal Stuck in Configuring State

Slice Renewal Stuck in Configuring State

Home Forums FABRIC General Questions and Discussion Slice Renewal Stuck in Configuring State

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #9600

    Hi FABRIC Team,

    I hope you are doing well. Today, I attempted to extend my slice through the FABRIC portal, but it became stuck in the Configuring state. After checking the slice notices, I observed multiple resource allocation errors, including:

    Insufficient resources: [ram]

    Insufficient resources: ncsa-w1.fabric-testbed.net cannot serve the requested sliver (RAM)

    Insufficient resources: No path available with the requested QoS

    Could you please check whether there is an issue with this slice modification and whether the slice can be recovered?

    Slice ID: 698e8e21-3926-451f-ad94-24ea5db4a822

    Thank you very much for your help.

    Best regards,

    Fatih Berkay Sarpkaya

    #9602
    Komal Thareja
    Participant

      Hi Fatih,

      I looked into your slice (698e8e21). During the renewal attempt, several VMs failed to renew due to insufficient resources on the target workers. These closed on 2026-03-16 initial end date.

      – 4 VMs failed due to insufficient RAM (on ncsa-w1 and other workers)
      – 2 VMs failed due to insufficient cores (on mich-w2, mich-w3)

      These VM failures caused a cascade: their dependent network services (L2Bridge, L2PTP) were also closed on expiry i.e. function without the underlying VMs. In total, 85 out of 129 reservations were closed and 3 additional network services were cleaned up.

      The slice was stuck in Configuring because some network reservations were waiting indefinitely for their dead predecessor VMs. I have deployed a fix that now properly detects this condition and closes those stuck reservations, which is why the slice has transitioned out of the Configuring state.

      Unfortunately, this slice cannot be recovered in its current state — too many VMs and their dependent network services have been closed. I recommend deleting this slice and creating a new one. To avoid resource contention, you may want to check site availability before submitting and consider spreading your VMs across sites with more available capacity, or using smaller VM flavors.

      Please let us know if you need any further assistance.

      NOTE: Please note that with advanced reservations in play, renew/extend is not always guaranteed as the resources may have been acquired by someone else.

      Best regards,
      Komal

      • This reply was modified 11 hours, 5 minutes ago by Komal Thareja.
    Viewing 2 posts - 1 through 2 (of 2 total)
    • You must be logged in to reply to this topic.