...The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
...Typically, this is due to the fact that another LCM operation is ongoing. The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.
[Setup]Launch another LCM operation
logTrying to modify an individual VNF instance
Set Headers{"Accept":"${ACCEPT}"}
Set Headers{"Content-Type": "${CONTENT_TYPE_PATCH}"}
[Teardown]#We cannot know if the "scale" operation is finished easily because the 202 indicates only whether the operation has been accepted, not whether the operation has been finished
# TODO: Need to set the pre-condition of the test. VNF instance shall be in INSTANTIATED state
[Documentation]Conflict.
...The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
...Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, or that another lifecycle management operation is ongoing.
...The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.
[Setup]Check resource not instantiated
LogTrying to Scale a vnf Instance
Set Headers{"Accept":"${ACCEPT}"}
Set Headers{"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If${AUTH_USAGE}== 1Set Headers{"Authorization":"${AUTHORIZATION}"}
Scale a vnfInstance Conflict (parallel LCM operation)
# TODO: Need to set the pre-condition of the test
[Documentation]Conflict
...The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
...Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, or that another lifecycle management operation is ongoing.
...The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.
[Setup]Launch another LCM operation
logTrying to Scale a vnf Instance
Set Headers{"Accept":"${ACCEPT}"}
Set Headers{"Content-Type": "${CONTENT_TYPE_PATCH}"}
Run Keyword If${AUTH_USAGE}== 1Set Headers{"Authorization":"${AUTHORIZATION}"}
[Teardown]#We cannot know if the "scale" operation is finished easily because the 202 indicates only whether the operation has been accepted, not whether the operation has been finished
Scale a vnfInstance Not Found
# TODO: Need to create a vnfInstance which's instantiatedVnfInfo.scaleStatus is absent
[Documentation]Not Found
...Error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists.
...Specifically in case of this task resource, the response code 404 shall also returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist.
...In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error.
[Setup]Check scale not supported
LogTrying to scale a vnf Instance, not exist
Set Headers{"Accept":"${ACCEPT}"}
Set Headers{"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If${AUTH_USAGE}== 1Set Headers{"Authorization":"${AUTHORIZATION}"}
Scale a vnfInstance to level Conflict (Not-Instantiated)
# TODO: Need to set the pre-condition of the test. VNF instance shall be in INSTANTIATED state
[Documentation]Conflict.
...The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
...Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, or that another lifecycle management operation is ongoing.
...The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.
[Setup]Check resource not instantiated
LogTrying to Scale a vnf Instance
Set Headers{"Accept":"${ACCEPT}"}
Set Headers{"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If${AUTH_USAGE}== 1Set Headers{"Authorization":"${AUTHORIZATION}"}
Scale a vnfInstance to level Conflict (parallel LCM operation)
# TODO: Need to set the pre-condition of the test
[Documentation]Conflict
...The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
...Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, or that another lifecycle management operation is ongoing.
...The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.
[Setup]Launch another LCM operation
logTrying to Scale a vnf Instance
Set Headers{"Accept":"${ACCEPT}"}
Set Headers{"Content-Type": "${CONTENT_TYPE_PATCH}"}
Run Keyword If${AUTH_USAGE}== 1Set Headers{"Authorization":"${AUTHORIZATION}"}
[Teardown]#We cannot know if the "scale" operation is finished easily because the 202 indicates only whether the operation has been accepted, not whether the operation has been finished
Scale a vnfInstance Not Found
# TODO: Need to create a vnfInstance which's instantiatedVnfInfo.scaleStatus is absent
[Documentation]Not Found
...Error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists.
...Specifically in case of this task resource, the response code 404 shall also returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist.
...In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error.
[Setup]Check scale to level not supported
LogTrying to scale a vnf Instance, not exist
Set Headers{"Accept":"${ACCEPT}"}
Set Headers{"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If${AUTH_USAGE}== 1Set Headers{"Authorization":"${AUTHORIZATION}"}