Commit 367724c5 authored by moscatelli's avatar moscatelli
Browse files

SOL003_70: responses description fixed

parent 8911ef51
Loading
Loading
Loading
Loading
Loading
+20 −4
Original line number Diff line number Diff line
@@ -1782,7 +1782,7 @@ paths:
          description: >
            202 ACCEPTED

            The request was accepted for processing, but processing has not been completed.
            Shall be returned when the request has been accepted for processing.
            The response shall have an empty payload body.
          headers:
            WWW-Authenticate:
@@ -1805,17 +1805,33 @@ paths:
        403:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403"
        404:
          description: >
            Shall be returned upon the following error: The API producer did not find a current representation
            for the target resource or is not willing to disclose that one exists.
            The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013,
            including rules for the presence of the response body.
            Specifically in case of this task resource, the response code 404 shall also be returned if the task
            is not supported for the VNF LCM operation occurrence represented by the parent resource,
            which means that the task resource consequently does not exist.
          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404"
        405:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404"
          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405"
        406:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406"
        409:
          $ref: "responses/VNFLifecycleManagement_resp.yaml#/responses/409-state-conflict-not-FAILED_TEMP"
          description: >
            Shall be returned upon the following error: The operation cannot be executed currently,
            due to a conflict with the state of the VNF LCM operation occurrence.
            Typically, this is due to the fact that the VNF LCM operation occurrence is not in FAILED_TEMP state,
            or another error handling action is starting, such as rollback or fail.
          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/409"
        500:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500"
        503:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503"
        504:
          $ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504"

  ###############################################################################
  # Rollback operation task                                                     #
  ###############################################################################