1. Issues with MASS

Issues with MASS

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #5858
    Bruce Hartpence
    Participant

      Morning – Second time getting provisioning errors

      failed lease update- all units failed priming: Exception during create for unit: adc30d20-13bd-4c15-9386-b2009af352ee Playbook has failed tasks: Error in creating the server (no further information available)#all units failed priming: Exception during create for unit: adc30d20-13bd-4c15-9386-b2009af352ee Playbook has failed tasks: Error in creating the server (no further information available)#

      #5859
      Komal Thareja
      Participant

        Good morning Bruce,

        Thank you for sharing your observations. VM provisioning to the worker (mass-w1.fabric-testbed.net) to which the VM was allocated is not working. We are working to resolve it. In the meanwhile, Please consider creating a slice on a different site or a different worker.

        Node can be requested on a specific worker by passing in the host field as below:

        node1 = slice.add_node(name="Node1", cores=16, ram=32, site="MASS", image='docker_rocky_8', host="mass-w2.fabric-testbed.net")

        Thanks,

        Komal

        #5860
        Bruce Hartpence
        Participant

          OK thanks. I moved the affected nodes to MAX.

        Viewing 3 posts - 1 through 3 (of 3 total)
        • The topic ‘Issues with MASS’ is closed to new replies.