Custom Query (98 matches)
Results (28 - 30 of 98)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #53 | fixed | Several slivers have VMs in geni_status "notready" | ||
| 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 |
|||
| #1 | fixed | setup instageni trac instance for InstaGENI testing | ||
| Description |
Set up a dedicated Trac instance for tickets needed during InstaGENI rack testing. |
|||
| #16 | fixed | Resource available is not in synch with information in listresources | ||
| Description |
There are instances of resource information out of synch between listresources and reserved resources. Occurred 05/15 9:00 eastern. According to listresources "pc5" is available, but Chaos checked the reservations on the rack and found pc5 was in a slice I reserved called pgeni-gpolab-bbn-com+slice+image which failed due to lack of resources yesterday afternoon. |
|||
