Skip to content
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

Open
2 of 9 tasks
pintify opened this issue Dec 30, 2021 · 6 comments
Open
2 of 9 tasks

Configuration PUT unable to parse example configuration #3481

pintify opened this issue Dec 30, 2021 · 6 comments

Comments

@pintify
Copy link

pintify commented Dec 30, 2021

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:

  1. Create a batch job

  2. Create a step of type configuration put

  3. Fill with template data

  4. Launch the job against a device

  5. See the error:

    imagen
    imagen

Version of Kapua
1.5.2

Type of deployment

  • Local Vagrant deployment
  • 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
  • Job-engine
  • Others

Additional context
Add any other context about the problem here.

@pintify
Copy link
Author

pintify commented Feb 16, 2022

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:

imagen

However, when the job is launched, the same configuration is marshalled through KuraDeviceConfiguration class. Whose child KuraDeviceComponentConfiguration uses pid field instead:

imagen

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?

@pintify
Copy link
Author

pintify commented Nov 23, 2022

This issue remains on Kapua 1.6.2

@pintify
Copy link
Author

pintify commented Nov 30, 2022

The issue persists on Kapua 1.6.4

@Agnul97
Copy link
Contributor

Agnul97 commented Apr 28, 2023

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

@pintify
Copy link
Author

pintify commented Jul 18, 2024

The issue seems to persist in 1.6.10

@pintify
Copy link
Author

pintify commented Oct 31, 2024

Just to verify, version 1.6.12 still has this bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants