search

peeringdb / admincom

Track issues specific to AC work
3 stars 1 forks source link

Multiple DeskPRO tickets for one API ticket #194

Closed arnoldnipper closed 6 years ago

arnoldnipper commented 6 years ago

API creation: https://peeringdb.com/cp/peeringdb_server/deskproticket/2890/change/

DeskPRO: https://peeringdb.deskpro.com/agent/#app.tickets,inbox:agent,t:18960,t:18961,t:18962,t:18963,t:18964,t.o:18966,vis:6

20180619 peeringdb 00

arnoldnipper commented 6 years ago

Update: some of these tickets are lacking information, i.e. the body is empty

arnoldnipper commented 6 years ago

@vegu writes: Nothing in our code would explain this sort of behavior, furthermore the script should not even be capable of creating multiple tickets with identical titles. It will fail with a dupe ticket error.

This looks and smells like a race condition in the DeskPRO API to me, and i think best course of action on our end is that we observe and see if it happens again.

At least one of those tickets it created was good enough to be processed by admincom, correct? Or do you need me to re-queue?

arnoldnipper commented 6 years ago

there were 6 tickets opened at DeskPRO, 1/2 were good, 1/2 were bad.