Opened 11 years ago
Closed 11 years ago
#1047 closed (fixed)
ION/I2 Aggregate fails reports error for link that does not go through ION
Reported by: | lnevers@bbn.com | Owned by: | ckotil@grnoc.iu.edu |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | I2AM | Version: | SPIRAL5 |
Keywords: | Network Stitching | Cc: | tlehman@maxgigapop.net, Aaron Helsinger, xyang@maxgigapop.net |
Dependencies: |
Description
In a scenario where the following topology is used:
1VM@IG Utah <-link1->1 VM@PG Utah <- link via ION/I2-> 1 VM@ IG GPO
The ION/I2 aggregate reports and error for link1 which is not in the ION/I2 path:
09:15:07 INFO omni: Creating sliver(s) from rspec file /tmp/stitch-linear-createsliver-request-11-ion-internet2-edu.xml for slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+stitch-linear 09:15:14 ERROR omni: {'output': ': CreateSliver: Internal API error: RspecHandler_GENIv3::parseStitchingResources stitching <path id="link1"> must have at least one <hop> elements.', 'geni_api': 2, 'code': {'am_type': 'sfa', 'geni_code': 5, 'am_code': 5}, 'value': ''} 09:15:14 INFO stitch.Aggregate: Got AMAPIError doing createsliver stitch-linear at <Aggregate urn:publicid:IDN+ion.internet2.edu+authority+cm>: AMAPIError: Error from Aggregate: code 5. sfa AM code: 5: : CreateSliver: Internal API error: RspecHandler_GENIv3::parseStitchingResources stitching <path id="link1"> must have at least one <hop> elements.. 09:15:14 WARNING stitcher: Stitching failed but will retry: Circuit reservation failed at <Aggregate urn:publicid:IDN+ion.internet2.edu+authority+cm> (AMAPIError: Error from Aggregate: code 5. sfa AM code: 5: : CreateSliver: Internal API error: RspecHandler_GENIv3::parseStitchingResources stitching <path id="link1"> must have at least one <hop> elements..). Try again from the SCS
ION/I2 aggregate should not be looking at links that are not part of the ION/I2 path.
Attaching the RSpec stitch-linear-createsliver-request-11-ion-internet2-edu.xml from the example captured above.
Attachments (1)
Change History (8)
Changed 11 years ago by
Attachment: | stitch-linear-createsliver-request-11-ion-internet2-edu.xml added |
---|
comment:1 Changed 11 years ago by
Cc: | tlehman@maxgigapop.net added |
---|---|
Status: | new → assigned |
comment:2 Changed 11 years ago by
Cc: | Aaron Helsinger added |
---|
comment:3 Changed 11 years ago by
Not sure when the new assumptions will be implemented, the problem with a multi-path scenario still occur:
08:50:31 ERROR omni: {'output': ': CreateSliver: Internal API error: RspecHandler_GENIv3::parseStitchingResources stitching <path id="link1"> must have at least one <hop> elements.', 'geni_api': 2, 'code': {'am_type': 'sfa', 'geni_code': 5, 'am_code': 5}, 'value': ''} 08:50:31 WARNING stitcher: Stitching failed but will retry: Circuit reservation failed at <Aggregate urn:publicid:IDN+ion.internet2.edu+authority+cm> (AMAPIError: Error from Aggregate: code 5. sfa AM code: 5: : CreateSliver: Internal API error: RspecHandler_GENIv3::parseStitchingResources stitching <path id="link1"> must have at least one <hop> elements..). Try again from the SCS
comment:5 Changed 11 years ago by
Cc: | xyang@maxgigapop.net added; ckotil@grnoc.iu.edu removed |
---|---|
Owner: | changed from xyang@maxgigapop.net to ckotil@grnoc.iu.edu |
Status: | assigned → new |
Implementation checked in. Assign to Chad to update Java core code.
comment:6 Changed 11 years ago by
Status: | new → assigned |
---|
I've updated the ION AM code and restarted tomcat6.
comment:7 Changed 11 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Ran the 3 nodes linear topology (Utah IG <->Utah PG <-> GPO IG) successfully. Issue is resolved, closing ticket.
Interesting scenario. ION AM assumed all paths in stitching extension in received rspec should go through ION. This looks wrong in multi-path case.
The new assumption will be "at least one path stitching extension in received rspec should go through ION."