Custom Query (1408 matches)
Results (28 - 30 of 1408)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1195 | fixed | Delete of sliver whose circuit on longer exists in MAX causes subsequent circuits to not complete | ||
| Description |
This ticket tracks the resolution of a problem identified in the an email exchange. Symptoms seen in stitcher: WARNING stitch.Aggregate: sliverstatus #### is (still) changing at <Aggregate urn:publicid:IDN+dragon.maxgigapop.net+authority+am>. Delete and retry. The above message is reported for all attempts to get a circuit at MAX aggregate. Some additional details: On 2/7/14 10:24 AM, Xi Yang wrote: The problem we had yesterday at DRAGON layer left inconsistent states in OSCARS, which caused problem when OSCARS tried to delete a sliver whose circuit on longer existed in DRAGON. I restarted OSCARS-pss-dragon module. Please try again. On 2/7/14 10:43 AM, Luisa Nevers wrote: Deleting a sliver whose circuit is no longer available should be handled because it is likely that an experimenter may just clean up some sliver that not longer working. A delete for a missing circuit should not impact all future attempts. BTW, retried and it worked. On 2/7/14 10:57 AM, Xi Yang wrote: Yes it normally worked. But somehow the OSCARS dragonPSS gets stuck in a strange state due to some bug. Part of the OSCARS dragonPSS is developed by me. I will try figuring it out but it is not my priority for now. |
|||
| #1199 | wontfix | ION aggregate project name of a certain lenght that include hypens will fail | ||
| Description |
While using the I2/ION aggregate a failure was reported for some longer project names that included hyphens: WARNING stitcher: Stitching failed but will retry: Project name or slice name too long? At <Aggregate max>: AMAPIError: Error from Aggregate: code 5. sfa AM code: 5: Internal API error: <Fault 102: 'person_id 2: AddSite: Invalid... Following are naming scenario that were tested to characterize the problem: urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Project-01+slice+ig-gpo-ig-max --> Fail urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Project-0+slice+ig-gpo-ig-max --> Works urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Project-AA+slice+ig-gpo-ig-max --> Fails urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Project_01+slice+ig-gpo-ig-max --> Works urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Projectx01+slice+ig-gpo-ig-max --> Works urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Project-01+slice+A --> Fails urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Project+slice+ig-gpo-ig-max --> Works urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Proj-01+slice+ig-gpo-ig-max --> Works urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Proj_01+slice+ig-gpo-ig-max --> Works Based on the results seen with project names above, it seems that if a project is of a certain length and it includes a "-" than the project will cause the failures |
|||
| #1262 | wontfix | ION aggregate should support sitching request for `any` VLAN | ||
| Description |
The ION Aggregate should support stitching requests for <suggestedVLANRange>any</suggestedVLANRange>. |
|||
