Custom Query (1408 matches)
Results (130 - 132 of 1408)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1349 | fixed | SCS ignores excludeHops on one path when there are multiple paths | ||
Description |
If a request has multiple paths, a hop_exclusion_list on only one of the paths gets ignored. Request RSpec is attached. Failure case: 12:39:01 DEBUG : Calling SCS with options {'geni_workflow_paths_merged': True, 'geni_routing_profile': {'link-gpo-stan': {'hop_inclusion_list': ['urn:publicid:IDN+instageni.stanford.edu+interface+procurve2:1.24.ion.salt.xe-0_1_1']}, u'link-stan-miss': {'hop_exclusion_list': [u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:*=1164', u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.sunn.net.internet2.edu:e5/1:*=1644']}}} 12:39:18 DEBUG : SCS gave hop urn:publicid:IDN+instageni.rnet.missouri.edu+interface+procurve2:1.19.al2s.kans.eth5_1 suggested VLAN 1164, avail: '1161-1165' 12:39:18 DEBUG : SCS gave hop urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:* suggested VLAN 1164, avail: '1161-1165' 12:39:18 DEBUG : SCS gave hop urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.sunn.net.internet2.edu:e5/1:* suggested VLAN 1643, avail: '1640-1644,1650-1669' 12:39:18 DEBUG : SCS gave hop urn:publicid:IDN+instageni.stanford.edu+interface+procurve2:1.24.al2s.sunn.e5_1 suggested VLAN 1643, avail: '1640-1644' As you can see, the SCS picked a tag I specifically asked it not to. Works: 12:30:08 DEBUG : Calling SCS with options {'geni_workflow_paths_merged': True, 'geni_routing_profile': {u'link-gpo-stan': {'hop_exclusion_list': [u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:*=1164', u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.sunn.net.internet2.edu:e5/1:*=1644'], 'hop_inclusion_list': ['urn:publicid:IDN+instageni.stanford.edu+interface+procurve2:1.24.ion.salt.xe-0_1_1']}, u'link-stan-miss': {'hop_exclusion_list': [u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:*=1164', u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.sunn.net.internet2.edu:e5/1:*=1644']}}} ... 12:30:24 DEBUG : SCS gave hop urn:publicid:IDN+instageni.rnet.missouri.edu+interface+procurve2:1.19.al2s.kans.eth5_1 suggested VLAN 1165, avail: '1161-1163,1165' 12:30:24 DEBUG : SCS gave hop urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:* suggested VLAN 1165, avail: '1161-1163,1165' 12:30:24 DEBUG : SCS gave hop urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.sunn.net.internet2.edu:e5/1:* suggested VLAN 1642, avail: '1640-1643,1650-1669' 12:30:24 DEBUG : SCS gave hop urn:publicid:IDN+instageni.stanford.edu+interface+procurve2:1.24.al2s.sunn.e5_1 suggested VLAN 1642, avail: '1640-1643' This is the desired behavior. The SCS excluded the tag that I said was unavailable from the vlanRangeRequest - both at the hop where I said it was unavailable, AND at the hop where that hop actually imports tags. |
|||
#1347 | fixed | ION allocates VLAN not in requested range | ||
Description |
In a scenario that includes Rutgers and UKYPKS2 connected by two links errors are reported for the ION createsliver that show that VLANs not in the requested ranges are used. The command output: $ stitcher.py createsliver loop-rut-pks23 /home/lnevers/gcf-test/stitch-test/stitch-loop-ig-rut-ig-pks2.rspec --ionRetryIntervalSecs 120 --ionStatusIntervalSecs 60 -o ... 14:19:48 INFO : Calling SCS... 14:19:50 INFO : Multi-AM reservation will include resources from these aggregates: 14:19:50 INFO : <Aggregate ukypks2-ig> 14:19:50 INFO : <Aggregate rutgers-ig> 14:19:50 INFO : <Aggregate ion> 14:19:50 INFO : Stitcher doing createsliver at <Aggregate ukypks2-ig>... 14:20:48 INFO : ... Allocation at <Aggregate ukypks2-ig> complete. 14:20:49 INFO : Stitcher doing createsliver at <Aggregate rutgers-ig>... 14:21:41 INFO : ... Allocation at <Aggregate rutgers-ig> complete. 14:21:41 INFO : Stitcher doing createsliver at <Aggregate ion>... 14:22:27 INFO : DCN AM <Aggregate ion>: must wait for status ready.... 14:22:27 INFO : Pausing 60 seconds to let circuit become ready... 14:23:43 ERROR : <Aggregate ion> gave VLAN 3733 for hop <Hop u'urn:publicid:IDN+ion.internet2.edu+interface+rtr.wash:xe-0/2/2:rutgers-ig' on path u'link2'> which is not in our request 3739 14:23:43 ERROR : <Aggregate ion> gave VLAN 3730 for hop <Hop u'urn:publicid:IDN+ion.internet2.edu+interface+rtr.wash:xe-0/2/2:rutgers-ig' on path u'link'> which is not in our request 3735 14:23:43 ERROR : <Aggregate ion> gave VLAN 1836 for hop <Hop u'urn:publicid:IDN+ion.internet2.edu+interface+rtr.atla:xe-0/1/3:ukypks2-ig' on path u'link2'> which is not in our request 1843 14:23:43 ERROR : <Aggregate ion> gave VLAN 1834 for hop <Hop u'urn:publicid:IDN+ion.internet2.edu+interface+rtr.atla:xe-0/1/3:ukypks2-ig' on path u'link'> which is not in our request 1849 14:23:43 INFO : ... Allocation at <Aggregate ion> complete. 14:23:43 WARNING : Stitching failed but will retry: VLAN was unavailable at <Aggregate ion> and not enough available VLAN tags at <Hop u'urn:publicid:IDN+ion.internet2.edu+interface+rtr.wash:xe-0/2/2:rutgers-ig' on path u'link2'> to try again locally. Try again from the SCS 14:23:43 INFO : Deleting existing reservations... ... }}}} The command completed on the next attempt without any problem. Attaching request and manifest RSpecs along with stitcher logs and full command output. |
|||
#1345 | wontfix | ION looses circuit status information over time | ||
Description |
A stitching topology (lncube) was set up with 4 stitched links between two IG sites. A sliver status ran with 20 seconds sleep between calls from 11:06:37 to 12:02:52: Circuits allocated: "urn:publicid:IDN+ch.geni.net:ln-test+sliver+lncube_vlan_ion.internet2.edu-123861", "urn:publicid:IDN+ch.geni.net:ln-test+sliver+lncube_vlan_ion.internet2.edu-123871", "urn:publicid:IDN+ch.geni.net:ln-test+sliver+lncube_vlan_ion.internet2.edu-123881", "urn:publicid:IDN+ch.geni.net:ln-test+sliver+lncube_vlan_ion.internet2.edu-123891", Sliver status output shows: Circuit 123861: Shows in all sliverstatus up to 12:01:00 but is missing from the sliverstatus at: - 12:01:28 - 12:01:56 - 12:02:24 - 12:02:52 Circuit 123871: Shows up in all sliverstatus except on at 11:59:34. Circuit 123881: Missing from 11:15:51 to 11:27:22 and again missing for one call at 11:27:22 Circuit 123891: Missing for one sliverstatus at 12:00:03. Attaching two files:
|