Uploaded image for project: 'Evergreen'
  1. Evergreen
  2. EVG-7939

Failing patch creation does not provide diagnostic output

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: app
    • Labels:

      Description

      I attempted to create a patch using the API endpoint. The request & response are here: https://gist.github.com/p-mongo/e718f20715c8c8ff2479beb76656dd6f

      I received the following response:

      (byebug) response.status
      500
      (byebug) response.body
      "400 (Bad Request): can't get patched config: Could not patch remote configuration file: could not run patch command: error waiting on process '49b71340-dd2c-4ccb-a6a1-f22a6a365385': exit status 1"
      

      What this appears to say is that patch command execution failed on the server side.

      This error message is missing the reason why patch command failed. I imagine this information is provided in standard error stream of the patch command. As a user of Evergreen API I would like Evergreen to capture the error information and return it in the API response, so that I can efficiently diagnose why requests are failing.

      This error response is also mixing the status codes - the HTTP status is 500 as shown above but the message claims to have status 400.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-evg Backlog - Evergreen Team
            Reporter:
            oleg.pudeyev Oleg Pudeyev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: