Custom Query (138 matches)
Results (43 - 45 of 138)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#117 | fixed | listreources for sliver hangs | ||
Description |
Created a sliver named "EG-EXP-6-exp1" which was successfully created and is ready according to sliverstatus: INFO:omni:Sliver status for Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+EG-EXP-6-exp1 at AM URL https://bbn-hn.exogeni.net:11443/orca/xmlrpc INFO:omni:{ "geni_status": "ready", "geni_urn": "urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+EG-EXP-6-exp1", "geni_resources": [ { "orca_expires": "Fri Oct 12 17:56:27 UTC 2012", "geni_urn": "urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+c0505466-19dd-4e18-8426-ae7727d61598#VM", "geni_error": "", "geni_status": "Active" But, attempts to get listresources on this sliver hang every time: omni.py -a https://bbn-hn.exogeni.net:11443/orca/xmlrpc listresources EG-EXP-6-exp1 Waited as long as 10 minutes for this sliver listresources to return sliver details. Leaving the sliver running.
|
|||
#115 | fixed | Requesting a resource that is being allocation to some other sliver causes other sliver to fail | ||
Description |
Ran a test case which requested the 1 bare metal resource while it was being allocated to a separate sliver. This request caused for the other existing sliver request to fail. Here is an outline for this failure:
Results: The 2nd sliver request never failed, it quickly reported success and a sliver manifest. The sliver status showed the bare metal as "Ticketed" and remained in this state. The 1st sliver creation continued to run for about 5 more minutes and then failed with the following error: Result Summary: Failed CreateSliver for slice errors at https://geni.renci.org:11443/orca/xmlrpc. Error from Aggregate: code 2: Request id: null Embedding workflow ERROR: 1:Insufficient resources or Unknown domain: http://geni-orca.renci.org/owl/bbnvmsite.rdf#bbnvmsite/Domain/baremetalce:baremetalce:0! Requested: baremetalce:1. Shouldn't the bare metal be unavailable, while the 1st sliver is being created? |
|||
#114 | fixed | Unable to SSH into bare metal nodes | ||
Description |
Created a sliver via the ExoSM named "lnexo", which requested one bare metal node at BBN and 1 bare metal node at RENCI. Sliver was created successfully, and sliverstatus reported the sliver "ready" 10 minutes after creation time, as expected. Tried to login to each of the bare metal nodes but attempts fail with "Connection timed out". This failure is still occurring 30 minutes after the sliver was deemed "ready": BBN bare metal node connection: $ ssh -i ~/.ssh/id_rsa root@192.1.242.111 ssh: connect to host 192.1.242.111 port 22: Connection timed out RENCI bare meta node connection: $ ssh -i ~/.ssh/id_rsa root@152.54.14.201 ssh: connect to host 152.54.14.201 port 22: Connection timed out |