kapua
kapua copied to clipboard
Configuration PUT unable to parse example configuration
Describe the bug In version 1.5.2, the steps of type Configuration Put are unable to parse the example configuration neither other configurations based on it that were working on version 1.4.x.
To Reproduce Steps to reproduce the behavior:
-
Create a batch job
-
Create a step of type configuration put
-
Fill with template data
-
Launch the job against a device
-
See the error:
Version of Kapua 1.5.2
Type of deployment
- [ ] Local Vagrant deployment
- [x] Docker
- [ ] Openshift (in its variants)
- [ ] Others
Main component affected
- [ ] Console (in case of console please report info on which browser you encountered the problem)
- [ ] REST API
- [ ] Message Broker
- [x] Job-engine
- [ ] Others
Additional context Add any other context about the problem here.
I think I've found something that could point to the bug.
When you save/configure the step, it seems to check the config with DeviceConfiguration class. Whose child (DeviceConfigurationComponent requires a field id
:
However, when the job is launched, the same configuration is marshalled through KuraDeviceConfiguration class. Whose child KuraDeviceComponentConfiguration uses pid
field instead:
I don't know if there is some conversion in between.. However, is it possible this discrepancy between both formats may be behind this mashalling issue?
This issue remains on Kapua 1.6.2
The issue persists on Kapua 1.6.4