1. Slice stuck in ‘Configuring’ on extend

Slice stuck in ‘Configuring’ on extend

Home Forums FABRIC General Questions and Discussion Slice stuck in ‘Configuring’ on extend

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #7892
    Ilya Baldin
    Participant

      Hello,

      I have a slice e2706941-6c42-4fd5-a446-56f6b448ec66 stuck in ‘Configuring’ on extend. The resources underneath I believe have expired and been released, it’s just the slice name occupying the namespace. I’ve recreated it with another name, so this isn’t urgent, but it is still there in ‘Configuring’ state.

      #7893
      Komal Thareja
      Participant

        Hi Ilya,

        Thank you for reporting this issue. It seems to be a bug, and I’m in the process of debugging it. In the meantime, I’ve closed your slice, so it should no longer show up as “Configuring.”

        Best regards,
        Komal

        #7900
        Komal Thareja
        Participant

          Hi Ilya,

          I looked into your slice and found that it was partially renewed, with the VM on STAR not renewing completely.

          This appears to be a side effect of the Kafka maintenance we conducted yesterday, which impacted STAR. During this time, renewal messages were not processed because the Kafka consumer had stopped. I’ve resolved the issue, and future renewals should now work as expected.

          Thank you for bringing this to our attention and helping us identify and fix the problem.

          Best regards,
          Komal

          P.S: Another user also ran into this: https://learn.fabric-testbed.net/forums/topic/not-able-to-renew-the-slice/

          #7903
          Ilya Baldin
          Participant

            Komal,

            Thank you. My recollection of events though is that I tried to renew it some days ago and it stayed in that ‘Configuring’ state, never updating to the new deadline. It’s possible I did it during another Kafka event.

          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.