Custom Query (98 matches)

Using version ??? on 04/25/2012, sent email to ​instageni-ops@flux.utah.edu:

Created a sliver with 2 OpenVZ hosts, the sliver was created successfully, but the sliverstatus shows that the 'pg_status' is 'not ready'. Attempts to login to the 2 nodes fail with a timeout. Connections were attempted over 40 minutes after sliver creation. This problem is reproducible

Response to the email:

On 4/25/12 11:15 PM, Robert Ricci wrote:

At this point, we are still debugging some problems in our OpenVZ image - our older Fedora 10 based image has trouble booting on the machines in these racks, and so we've had to move to a newer Fedora 15 image. We've resolved several obstacles with that image, but there are still a few kinks to iron out. We will keep you updated.

New Site Confirmation Test include on test to verify that administrative user can ssh from the boss node to each of the VM servers.

On the Kansas rack I am able to login to the 2 OpenVZ servers, but I am not able to login to the Xen server host:

LNM:~$ ssh boss.instageni.ku.gpeni.net
 ....
[lnevers@boss ~]$ ssh pc1
Last login: Wed Nov 13 13:03:28 2013 from boss.instageni.ku.gpeni.net
[lnevers@vhost1 ~]$ exit
logout
Connection to pc1.instageni.ku.gpeni.net closed.
[lnevers@boss ~]$ ssh pc2
Last login: Wed Nov 13 13:03:35 2013 from boss.instageni.ku.gpeni.net
[lnevers@vhost2 ~]$ exit
logout
Connection to pc2.instageni.ku.gpeni.net closed.
[lnevers@boss ~]$ ssh pc5
lnevers@pc5.instageni.ku.gpeni.net's password: 
Permission denied, please try again.
lnevers@pc5.instageni.ku.gpeni.net's password: 
Permission denied, please try again.
lnevers@pc5.instageni.ku.gpeni.net's password: 
Permission denied (publickey,password).
[lnevers@boss ~]$ 

In a scenario where 4 VMs are requested, I am not able to login to one of the VMs.

I have ran into this problem on two separate instances of a 4 VMs sliver. The most current failure occurred on a sliver named IG-CT-1, where I am not able to login to the VM associated with port 30780 on pc3.utah.geniracks.net even though the VM is listed as "ready".