Opened 6 years ago

Closed 6 years ago

#1159 closed (fixed)

Renewing stitched sliver with ION in path may result in OSCARS path modificaiton failure

Reported by: lnevers@bbn.com Owned by: xyang@maxgigapop.net
Priority: major Milestone:
Component: STITCHING Version: SPIRAL6
Keywords: Network Stitching Cc:
Dependencies:

Description

There have been several scenarios where renewing a stitched sliver results in the circuit status for the ION aggregate to go from "ready" to "failed".

There maybe some type of timing issue, this problem does not occur on every attempt. Problem has also been seen with different topologies (IG MAX to IG GPO, and with PG UKY to Missouri IG)

Here is a failure which shows up after the renewsliver: ((( "geni_urn": "urn:publicid:IDN+ch.geni.net:ln-prj+sliver+ig-max-ig-gpo_vlan_ion.internet2.edu-60581", "geni_error": "Coordinator(PATH_MODIFY_FAILED): 'Path modify failed with error from PSS'", "geni_status": "failed" }}}

According to Xi:

On 1/27/14 1:52 PM, Xi Yang wrote:

RenewSliver translates into Modify in Internet2 OSCARS. I have seen it before that Modify succeeded and then circuit transitioned into Failed status. We should ask OSCARS developers to address two issues:

  1. OSCARS does not acknowledge Modify failures properly.
  2. Refusal of Modify request causes circuit failure.

—Xi

Writing this ticket to track problem resolution from OSCARS developement.

Change History (2)

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

Component: GPOSTITCHING

comment:2 Changed 6 years ago by xyang@maxgigapop.net

Resolution: fixed
Status: newclosed

This was an issue in OSCARS. Andy Lake from ESnet made a patch to the code. After we applied the patch to ION, we on longer see the problem.

Note: See TracTickets for help on using tickets.