Custom Query (98 matches)

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.

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.

{'geni_error': ,

'geni_status': 'failed', 'geni_urn': 'urn:publicid:IDN+utah.geniracks.net+sliver+10467', 'pg_manifest': {'attributes': {'client_id': 'PCC',

'component_id': 'urn:publicid:IDN+utah.geniracks.net+node+pc1', 'component_manager_id': 'urn:publicid:IDN+utah.geniracks.net+authority+cm', 'exclusive': 'false', 'sliver_id': 'urn:publicid:IDN+utah.geniracks.net+sliver+10467', 'xmlns': 'http://www.geni.net/resources/rspec/3', 'xmlns:gemini': '​http://geni.net/resources/rspec/ext/gemini/1'},

...

I have left slice johGEM1209261119 up in case someone wants to take a look at one of the failures.

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.