1. failed lease update- all units failed priming: Exception during create for unit:
Searching...

failed lease update- all units failed priming: Exception during create for unit:

Home › Forums › FABRIC General Questions and Discussion › failed lease update- all units failed priming: Exception during create for unit:

Log In Register Lost Password

Tagged: 

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • April 4, 2023 at 3:56 pm #4032
    Nagmat Nazarov
    Participant

      Dear Community

       

      I am getting below error 3-4 times today.

      ” failed lease update- all units failed priming: Exception during create for unit: b8271e81-1216-44fb-b6d8-b9338cbc3b47 Playbook has failed tasks: Error in creating the server (no further information available)#all units failed priming: Exception during create for unit: b8271e81-1216-44fb-b6d8-b9338cbc3b47 Playbook has failed tasks: Error in creating the server (no further information available)# ”

      What may be the issue?

      Kind regards,

      Nagmat

      April 4, 2023 at 4:26 pm #4033
      Komal Thareja
      Participant

        Hi Nagmat,

        Thank you for sharing your observation! The requested slice asks for a VM with 2000GB disk on FIU rack (fiu-w4.fabric-testbed.net). However, the disk isn’t available and hence VM provisioning fails. We have a known issue that there is a mismatch in the disk availability as seen by software and the actual infrastructure. We are working to address that. But for now, I would request to create a slice with smaller disk.

        Also, was this issue only observed on FIU rack? If not, Could you please share the other sites where you observed this error?

        Thanks,
        Komal

        1 user thanked author for this post.
        Nagmat Nazarov
        April 4, 2023 at 4:35 pm #4035
        Nagmat Nazarov
        Participant

          It was observed in :

          #site1 = “FIU”
          #site2 = “UCSD”
          #site3 = “MASS”

          The storage size wasn’t 2000GB but it was 1000G.

          Kind regards,

          Nagmat

          April 4, 2023 at 4:56 pm #4037
          Komal Thareja
          Participant

            I can confirm it’s the same issue on MASS and UCSD as well based on the logs. Also, I noticed the slice request was for 1000G disk but it gets mapped to a flavor with 2000G as we don’t have any 1000G flavor. None of the sites/workers mentioned have that much disk available and hence the provisioning fails. Unfortunately, the error message returned by openstack is not specific and not very helpful.

            Thanks again for letting us know. We will work on fixing the mismatch and address this.

            Thanks,
            Komal

            May 26, 2023 at 2:49 pm #4322
            Nagmat Nazarov
            Participant

              Closed.

            • Author
              Posts
            Viewing 5 posts - 1 through 5 (of 5 total)
            • The topic ‘failed lease update- all units failed priming: Exception during create for unit:’ is closed to new replies.