Opened 13 years ago
Closed 13 years ago
#44 closed (fixed)
Several VMs are not accessible after their sliver is shown as ready
Reported by: | lnevers@bbn.com | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | IG-EXP-3 |
Component: | Experiment | Version: | SPIRAL4 |
Keywords: | vm support | Cc: | |
Dependencies: |
Description
Set up 10 experiments but some of the hosts are not accessible even though the slivers status reports that the slivers are ready.
Scenario:
- 10 slices created, each slice contains one sliver with 2 VMs.
- Slice names are 2vmslice1 through 2vmslice10.
- All slivers are ready according to the sliver status.
There are 3 VMs on which I am prompted for a password, below are the sliver name, the hostname and ports for the VMs not allowing login.
SliceName: 2vmslice4 'hostname': 'pc3.utah.geniracks.net', 'port': 31803, SliceName: 2vmslice8 'hostname': 'pc1.utah.geniracks.net', 'port': 32826, SliceName: 2vmslice9 'hostname': 'pc1.utah.geniracks.net', 'port': 33082,
Attaching the sliver status to the ticket.
Attachments (3)
Change History (5)
Changed 13 years ago by
Attachment: | 2vmslice4-sliverstatus-utah-geniracks-net-protogeni.json added |
---|
Changed 13 years ago by
Attachment: | 2vmslice8-sliverstatus-utah-geniracks-net-protogeni.json added |
---|
Changed 13 years ago by
Attachment: | 2vmslice9-sliverstatus-utah-geniracks-net-protogeni.json added |
---|
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Significant improvements have been made in this area. Numerous experiments have been run with multiple VMs, none of which showed the node access failures encountered in ticket. Closing ticket, no longer an issue.
Note: See
TracTickets for help on using
tickets.
On 7/19/12 2:26 PM, Leigh Stoller wrote:
Can I delete the slivers?
Also, if I run into this again, I will let you know.