Opened 12 years ago
Closed 12 years ago
#2 closed (fixed)
Unable to use OpenVZ resources in slivers
| Reported by: | lnevers@bbn.com | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | AM | Version: | SPIRAL4 |
| Keywords: | openvz | Cc: | |
| Dependencies: |
Description
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.
Change History (3)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
This comment is a test of an e-mail configuration change; please ignore.
comment:3 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This problem no longer occurs, closing ticket.
Version information for this ticket.
$ ./src/omni.py -a https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0 getversion 2>&1 | grep code_tag 'value': { 'code_tag': 'cc7e165660730a4aafa878e5d617c2aaadf38a2e',