#244 Job Configuration problem

[Gabor Hermann]

Executable selected for upload disappears in case of virgin jobs (configured the first time) if

• “type” is “Cloudbroker”
• resource selected as “Name” permits the upload of user defined executable
• this option is selected.
  The phenomenon occurs in the moment when value for the next configuration component(“Resource”) will be selected.

Temporary workaround:

Check content of the field “Recently stored” in the line starting as “Executable code of binary”:
If it is empty against the expectation of the user then repeat the upload of the executable.
It will succeed if the input fields “Resource”,”Region” and “Instance type” are defined and saved as a result of a former job configuration step.

The phenomenon has been observed in a portal version 3.6.6 and can be reproduced in 3.6.8