Public bug reported: On execution of create object metadata use case using following curl command, on an environment where container server is down,
curl -i <public_url>/<container-name>/<object-name> -X POST -H "X-Auth- Token: <token>" -H "X-Object-Meta-<property name>: <value>" Http response code 404 is returned i.e., resource not found. While in logs container server refuses to connect with response code 503 i.e., service unavailable. The proxy should return HTTP response 503 , as container services are stopped, hence unavailable. Response code 404 mislead the user as it signifies that container server is working but the container, for which metadata is being created, is not found. Cause: After getting 503 from container server multiple times, proxy server send POST request to object server which responds with error code 404 i.e., requested object not found. This response is sent to the user which is not correct. Proxy server should return error code 503, as the actual error is coming due to unavailability of Container server. ** Affects: keystone Importance: Undecided Assignee: rohita joshi (rjoshi16) Status: New ** Changed in: keystone Assignee: (unassigned) => rohita joshi (rjoshi16) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1567246 Title: Proxy server returning response code 404 instead of 503 Status in OpenStack Identity (keystone): New Bug description: On execution of create object metadata use case using following curl command, on an environment where container server is down, curl -i <public_url>/<container-name>/<object-name> -X POST -H "X -Auth-Token: <token>" -H "X-Object-Meta-<property name>: <value>" Http response code 404 is returned i.e., resource not found. While in logs container server refuses to connect with response code 503 i.e., service unavailable. The proxy should return HTTP response 503 , as container services are stopped, hence unavailable. Response code 404 mislead the user as it signifies that container server is working but the container, for which metadata is being created, is not found. Cause: After getting 503 from container server multiple times, proxy server send POST request to object server which responds with error code 404 i.e., requested object not found. This response is sent to the user which is not correct. Proxy server should return error code 503, as the actual error is coming due to unavailability of Container server. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1567246/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp