Fuzzing core-metadata: 500 errors when invalid character in name for http://localhost:59881/api/v3/deviceservice

[vli11]

🐞 Bug Report

Affected Services [REQUIRED]

core-metadata

Is this a regression?

no

Description and Minimal Reproduction [REQUIRED]

use compose-builder command make run no-secty ds-virtual to bring up EdgeX system

On postman:
POST http://localhost:59881/api/v3/deviceservice
JSON body: (note invalid character in name)
{
"service": {
"name": "D0at>\u000bVA1CM",
"description": "fuzzstring",
"adminState": "LOCKED",
"labels": [
"fuzzstring"
],
"baseAddress": "fuzzstring"
},
"requestId": "d65fffc0-c8c3-4980-a208-9f798bd076a6",
"apiVersion": "v3"
}

This postman call will produce http status code 500, and message of "json: cannot unmarshal object into Go value of type []requests.AddDeviceServiceRequest", with this error message, it shouldn't be status code 500, but status code 400.

🔥 Exception or Error

{
"apiVersion": "v3",
"message": "json: cannot unmarshal object into Go value of type []requests.AddDeviceServiceRequest",
"statusCode": 500
}

🌍 Your Environment

use compose-builder command make run no-secty ds-virtual to bring up EdgeX system

EdgeX Version [REQUIRED]:
3.1

Anything else relevant?

[guyver30]

sorry for question, but how to launch "make run no-secty ds-virtual" in a docker container already deployed?
As I was going through the walkthrough https://docs.edgexfoundry.org/3.0/walk-through/Ch-WalkthroughDeviceService/ and had the same error as in this thread.

[vli11]

sorry for question, but how to launch "make run no-secty ds-virtual" in a docker container already deployed? As I was going through the walkthrough https://docs.edgexfoundry.org/3.0/walk-through/Ch-WalkthroughDeviceService/ and had the same error as in this thread.

here is the list of steps on your host machine to run that command:

1. open edgex-compose project
2. cd compose-builder
3. make pull
4. make run no-secty ds-virtual