Skip to content
This repository has been archived by the owner on Nov 19, 2023. It is now read-only.

Unable to delete outgoing poisons via HTTP API #56

Open
cdauphinee opened this issue Feb 2, 2018 · 1 comment · May be fixed by #64
Open

Unable to delete outgoing poisons via HTTP API #56

cdauphinee opened this issue Feb 2, 2018 · 1 comment · May be fixed by #64

Comments

@cdauphinee
Copy link

cdauphinee commented Feb 2, 2018

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.

@cdauphinee cdauphinee changed the title Unable to delete poisons via HTTP API Unable to delete outgoing poisons via HTTP API Feb 2, 2018
@amit1990sumit
Copy link

Hi @cdauphinee

Could you please guide me how you called HTTP API?
I need to set rules and poisons from my mobile app. please send some sample if possible.

@burcz burcz linked a pull request May 22, 2019 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants