Custom Query (98 matches)
Results (46 - 48 of 98)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#51 | fixed | Cannot log in to some InstaGENI nodes | ||
Description |
I have created several slivers in the last couple of weeks where one or more of the four nodes (VMs) have not had their SSH keys configured correctly. IOW, I get a password prompt when attempting to log in to the node. I ran into the same problem today and left the slice up in case someone wants to troubleshoot. The slice is johGEM1209261101. I can only log into node PCA (pc1.utah.geniracks.net -p 31035). The rest present the password prompt. Luisa has reproduced the same problem in two of her slices today. |
|||
#52 | fixed | Failing to create a four-node InstaGENI sliver during GEMINI testing | ||
Description |
I have been trying to create a four-node slice for testing GEMINI. This slice contains three VMs in a mesh network configuration and one stand-alone VM. When I try to create this sliver, I am getting at least one node failure most of the time. This morning I have tried at least 12 slivers so far and all but two have had at least one node fail. The sliverstatus output does not give any geni_error indication as to what caused the failure.
I have left slice johGEM1209261119 up in case someone wants to take a look at one of the failures. |
|||
#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 |