Custom Query (98 matches)
Results (13 - 15 of 98)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #8 | fixed | creating a sliver with one vm at Utah InstaGENi and one VM other site results in incomplete manifest | ||
| Description |
This experiment was run twice with following resources:
In both scenarios the createsliver operation only showed login information only for the InstaGENI rack, subsequent attempt to get sliver status failed with "resource is busy; try again later" for approximately 10 minutes. Once was able to collect sliverstatus, in both runs there was no login information for either remote rack (GPO PG or Utah PG). Waited up to 30 minutes and sliverstatus did not change to include remote details, Following are details for each of the two runs. Run 1: Using an RSpec that includes 2 nodes (1 @ Utah InstaGENI, 1@ GPO PG) was able to create a sliver without any errors. The createsliver generated an incomplete manifest RSpec which was missing login details for the GPO node. Followed up by checking the Manifest RSpec for the sliver, up to 30 minutes late, showed no node for the GPO VM. The request RSpec and the manifest are attached at run1-*. Run 2: Using an RSpec that includes 2 nodes (1 @ Utah InstaGENI, 1@ Utah PG) was able to create a sliver without any errors. The initial sliver creation showed only InstaGENI rack login information. After approximately 10 minutes of "resource busy was able to get a sliver status to run, but no login information was available for the Utah PG VM. The request RSpec and the manifest are attached at run2-*. |
|||
| #9 | fixed | creating 4 node linear sliver fails with <Fault -32600: 'Internal Error executing CreateSliver'> | ||
| Description |
Created a 4 VMs linear topology which failed with the following error: ERROR:omni.protogeni:Call for Create Sliver urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+pglinear at https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0 failed. Server says: <Fault -32600: 'Internal Error executing CreateSliver'> The sliver failed around 9:40 and the slice was named "pglinear". The rspec used is attached. |
|||
| #10 | fixed | A 2 VM sliver (1@InstaGENI & 1@PG Utah) shows pg_status 'notready' 40 minutes after slivercreate | ||
| Description |
The slice used for this experiment is urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+1nsta-1pg and was created at around 4:21 pm eastern. Twenty minutes after the two sliver were created at InstaGENI AM and PG Utah AM, the pg_status' was still 'notready'. |
|||
