Opened 10 years ago

Closed 10 years ago

#1153 closed (fixed)

Request for 3 node linear stitched sliver results in "no edge hop" error at Utah IG

Reported by: Owned by: somebody
Priority: major Milestone:
Component: STITCHING Version: SPIRAL6
Keywords: Network Stitching Cc:,


Creating a 3 node linear with the following path:

GPO IG<-> Missouri IG <-> Utah IG

Results in the following failure:

09:19:14 INFO     stitch.Aggregate: Writing to '/tmp/IG-ST-3-createsliver-request-11-utah-geniracks-net.xml'
09:19:14 INFO     stitch.Aggregate: 
	Stitcher doing createsliver at
09:19:15 WARNING  omni: Requested API version 2, but AM uses version 1. Same aggregate talks API v2 at a different URL:
09:19:26 ERROR    omni:  {'output': 'link1: no edge hop', 'code': {'protogeni_error_log': '', 'am_type': 'protogeni', 'geni_code': 2, 'am_code': 2, 'protogeni_error_url': ''}, 'value': 0}
09:19:26 INFO     stitch.Aggregate: Got AMAPIError doing createsliver IG-ST-3 at <Aggregate>: AMAPIError: Error from Aggregate: code 2. protogeni AM code: 2: link1: no edge hop.
09:19:26 WARNING  stitcher: Stitching failed but will retry: Circuit reservation failed at <Aggregate> (AMAPIError: Error from Aggregate: code 2. protogeni AM code: 2: link1: no edge hop.). Try again from the SCS
09:19:26 WARNING  stitcher: Had reservation at
09:19:26 INFO     stitch.Aggregate: Doing deletesliver at
09:19:53 ERROR    omni:  {'output': 'resource is busy; try again later', 'code': {'protogeni_error_log': '', 'am_type': 'protogeni', 'geni_code': 14, 'am_code': 14, 'protogeni_error_url': ''}, 'value': 0}

Attaching the request RSpec IG-ST-3-createsliver-request-11-utah-geniracks-net.xml'

Attachments (1)

IG-ST-3-createsliver-request-11-utah-geniracks-net.xml (8.8 KB) - added by 10 years ago.

Download all attachments as: .zip

Change History (2)

Changed 10 years ago by

comment:1 Changed 10 years ago by

Resolution: fixed
Status: newclosed

Closing ticket, this was user error. There was an RSPec definition problem with the link:

  <link client_id="link1">
    <component_manager name=""/>
    <component_manager name=""/>
    <interface_ref client_id="ig-gpo:if0"/>   <<<<=====SHOULD HAVE BEEN ig-utah ====|
    <interface_ref client_id="miss:if0"/>
    <property source_id="miss:if0" dest_id="ig-utah:if0" />
    <property source_id="ig-utah:if0" dest_id="miss:if0" />
Note: See TracTickets for help on using tickets.