Opened 5 years ago

Closed 5 years ago

#1274 closed (fixed)

AL2S OESS aggregate createsliver request fails with Unable to find path error

Reported by: lnevers@bbn.com Owned by: luke@grnoc.iu.edu
Priority: major Milestone:
Component: STITCHING Version: SPIRAL6
Keywords: GENI Network Stitching Cc:
Dependencies:

Description

Writing ticket to capture current test issue.

In a scenario where this topology was tested:

GPO <-ION-> Missouri <-AL2S-> Stanford:

OESS reports the following error:

'Exception: Unable to find two endpoints in my domain in this request.'

No resolution yet for the error below - waiting on fix.

Attachments (1)

3linear-createsliver-request-31-al2s-internet2-edu.xml (8.1 KB) - added by lnevers@bbn.com 5 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 Changed 5 years ago by lnevers@bbn.com

This problem was also seen in one cross connect test:

Stanford <-AL2S->NEWYX-connect<-ION-> GPO

Working on reproducing this failure.

comment:2 Changed 5 years ago by lnevers@bbn.com

Problem is not resolved, the scenario "GPO <-ION-> Missouri <-AL2S-> Stanford" (2014-08-14 13:17) still reports the same failure:

13:17:52 INFO : Stitcher doing createsliver at <Aggregate oess>... 13:17:52 ERROR : {'output': 'Exception: Unable to find two endpoints in my domain in this request.', 'code': {'geni_code': 2}}

comment:3 Changed 5 years ago by luke@grnoc.iu.edu

ugh. that's unexpected. super. i'll take a look and report back...

comment:4 Changed 5 years ago by lnevers@bbn.com

Re-ran topology: GPO <-ION-> Missouri <-AL2S-> Stanford

and got this error:

14:18:30 INFO    : Stitcher doing createsliver at <Aggregate oess>...
14:18:31 ERROR   :  {'output': 'Exception: Unable to find a suitable path for this request.', 'code': {'geni_code': 2}}
14:18:31 WARNING : Stitching failed but will retry: Circuit reservation failed at <Aggregate oess> (AMAPIError: Error from Aggregate: code 2: Exception: Unable to find a suitable path for this request..). Try again from the SCS

comment:5 Changed 5 years ago by luke@grnoc.iu.edu

A new error... progress. Can you send me the rspec as submitted to AL2S AM for this one as well?

Changed 5 years ago by lnevers@bbn.com

comment:6 Changed 5 years ago by lnevers@bbn.com

RSpec attached

comment:7 Changed 5 years ago by luke@grnoc.iu.edu

Give this one a go again. Overly aggressive error handling meant that it was failing if an AL2S circuit wasn't included in the first link element.

comment:8 Changed 5 years ago by lnevers@bbn.com

Resolution: fixed
Status: newclosed

re-ran topology and did not get the last error and was able to exchange traffic between all end-points. Issue is resolved, closing ticket.

Note: See TracTickets for help on using tickets.