I'm experiencing that I'm unable to delete outgoing poisons after adding them via the HTTP API.

I added an outgoing latency poison to a route via the HTTP API, resulting in the call to GET /servers/882/routes/20e/poisons looking like this:

[
   {
      "name":"latency",
      "enabled":true,
      "phase":"outgoing",
      "rules":[

      ],
      "links":{
         "self":{
            "href":"/servers/882/routes/20e/poisons/latency:outgoing"
         },
         "parent":{
            "href":"/servers/882/routes/20e/poisons"
         }
      }
   }
]

I then attempt to delete the poison via DELETE /servers/882/routes/20e/poisons and get back a 204 No Content, but the poison is still present.

I also experience the same problem when I try to delete the specific poison, both via DELETE /servers/882/routes/20e/poisons/latency and DELETE /servers/882/routes/20e/poisons/latency:outgoing; I get a 204 No Content, but the poison is still there.

Note that I can delete any incoming poisons; the problem is exclusive to outgoing ones.