Opened 9 years ago

Last modified 9 years ago

#1281 new

Some excludehop combinations can crash SCS

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

Description

This problem was found by Tim.

The following command crashed the SCS: 

tupty@weentop-work:~/rspecs/request/tuptystitch$ stitcher createsliver tuptystitch2 rutgers-ig-bbn-ig.rspec --useSliceMembers --excludehop urn:publicid:IDN+ion.internet2.edu+interface+rtr.wash:xe-0/2/2:*=3730-37327,3734-3739
14:21:29 INFO    : Configured logging from file /home/tupty/gcf/gcf-2.6/src/gcf/stitcher_logging.conf
14:21:30 INFO    : Reading slice tuptystitch2 credential...
14:21:30 INFO    : Slice urn:publicid:IDN+ch.geni.net:gpo-infra+slice+tuptystitch2 expires on 2014-08-15 00:00:00 UTC
14:21:30 INFO    : Calling SCS...
14:21:30 ERROR   : Exception from slice computation service: [Errno 111] Connection refused
SCS gave error: [Errno 111] Connection refused

Change History (1)

comment:1 Changed 9 years ago by tupty@bbn.com

A couple of peculiar things about this case:

  • The VLAN range is bad (due to a typo)
  • The link portion of the interface URN in the excludehop is incorrect:
    • The URN I used by accident is urn:publicid:IDN+ion.internet2.edu+interface+rtr.wash:xe-0/2/2:*
      • This does not exist in the ION AM advertisement
      • This does exist in OSCARS
    • The URN I should have used is urn:publicid:IDN+ion.internet2.edu+interface+rtr.wash:xe-0/2/2:rutgers-ig

I am not sure where the actual error comes from. It could be just one of those things, or some combination of them. I am also not sure if the fix belongs in just the SCS, or both the SCS and stitcher.

Note: See TracTickets for help on using tickets.