submit job fail with “porttype”

[boozyguo]

hello, there is a problem about submit job with "porttype".

I test submit a job with 'porttype', but the webportal reports "bad request":

If I submit the same job without "porttype", it is ok:

[Gerhut]

I reproduced this issue, frameworklauncher logs

com.microsoft.frameworklauncher.webserver.LauncherExceptionHandler: Http request failed due to: Bad Request 
com.microsoft.frameworklauncher.common.exceptions.BadRequestException: javax.validation.ConstraintViolationException: taskRoles[master].taskService.resource: Illegal PortDefinitions: All start fields should be nonzero or zero: PortDefinitions: [{<serverport = 7000,1>, <http = 0,1>, <ssh = 0,1>}]

Ping @yqwang-ms for help

[fanyangCS]

@Gerhut , could you please post the REST API log?

[yqwang-ms]

@qinchen123 to take a look.
It is by design, and below message is returned from Launcher RestAPI's body, RestServer should show them to user:
com.microsoft.frameworklauncher.common.exceptions.BadRequestException: javax.validation.ConstraintViolationException: taskRoles[master].taskService.resource: Illegal PortDefinitions: All start fields should be nonzero or zero: PortDefinitions: [{<serverport = 7000,1>, <http = 0,1>, <ssh = 0,1>}]

[qinchen123]

Hi Gerhut，
our design of ports support in backend is: if have multi-port labels, the ports for all labels either random or specified; it don't support some labels are random, some label are specified.

for your cases, you have specified the serverport 7000, but the webserver add too random port(http, ssh). the specified and random co-existed casued this BadRequest.

I suggest you to use a random port for your serverport, and after job is running, you can get the port number form the job detail view in PAI web site.

[fanyangCS]

this is a bug.

[fanyangCS]

solved by #1402