Opened 10 years ago

Closed 10 years ago

#53 closed (fixed)

Several slivers have VMs in geni_status "notready"

Reported by: lnevers@bbn.com Owned by: somebody
Priority: major Milestone: IG-EXP-2
Component: AM Version: SPIRAL4
Keywords: sliver creation Cc:
Dependencies:

Description

The sliver named "lninsta" was created to request 4 VMs. Two of the requested VMs have been in geni_status "notready" for over 1 hour. The two nodes are:

pc3.utah.geniracks.net port 32826 
pc3.utah.geniracks.net -p 32827

A second sliver named "lninsta-3" was created to request 3 VMs. One of the VMs has also been in geni_status "notready" for over 1 hour. The node is:

pc1.utah.geniracks.net -p 33340

Change History (1)

comment:1 Changed 10 years ago by lnevers@bbn.com

Resolution: fixed
Status: newclosed

Recently have set up as many as 25 slivers each with 4 VM and all node became ready and were accessible via SSH. Also set up 10 slivers, each with 3 VMs without problem.

I believe this is no longer a problem, closing ticket.

Note: See TracTickets for help on using tickets.