Fix SDNC enhanced healthcheck failure

- add expected_status=any to DELETE On Session call in
  RUN SDNC Delete Request

Issue-ID: INT-2356
Change-Id: I498079d980dd99033f62ef57447c166f76b6d00e
Signed-off-by: Fiete Ostkamp <fiete.ostkamp@telekom.de>

diff --git a/robot/resources/sdnc_interface.robot b/robot/resources/sdnc_interface.robot
index 7d2fb4b..7bb5075 100644 (file)
--- a/robot/resources/sdnc_interface.robot
+++ b/robot/resources/sdnc_interface.robot
@@ -64,12 +64,15 @@ Run SDNC Health Check Generic Resource API
     Should Be Equal As Strings  ${delete_response.status_code}     204
 
 Run SDNC Delete Request
-    [Documentation]    Runs an SDNC Delete Request
+    [Documentation]    Runs an SDNC Delete Request and returns the response.
+    ...    expected_status=any is used because the /rests/ (RFC 8040) endpoint
+    ...    returns 409 instead of 404 for non-existing resources. Callers are
+    ...    responsible for validating the status code.
     [Arguments]    ${URL}
     Disable Warnings
     ${session}=    Create Session       SDNC     ${SDNC_REST_ENDPOINT}    auth=${GLOBAL_SDNC_AUTHENTICATION}
     ${headers}=  Create Dictionary     Accept=*/*    Accept-Encoding=gzip, deflate, br    Connection=keep-alive
-    ${resp}=    Delete On Session  SDNC     ${URL}     data=${None}    headers=${headers}
+    ${resp}=    Delete On Session  SDNC     ${URL}     data=${None}    headers=${headers}    expected_status=any
     [Return]    ${resp}
 
 Preload Vcpe Networks