-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuration PUT unable to parse example configuration #3481
Comments
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 However, when the job is launched, the same configuration is marshalled through KuraDeviceConfiguration class. Whose child KuraDeviceComponentConfiguration uses 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 |
Hi, Right now on the develop branch the issue should be solved. I'll check soon if it's the case also for the last 1.6.x build |
The issue seems to persist in 1.6.10 |
Just to verify, version 1.6.12 still has this bug |
It seems to be solved on 2.0.0-BETA-M11. Really looking forward final release 👏👏 |
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
Main component affected
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: