-
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
Communication from Kapua to Kura broken #3581
Comments
Hi, |
Greetings to both of you. Sorry for the late reply, I tested this issue using the latest kura version hosted on docker hub https://hub.docker.com/r/eclipse/kura/ both with a build of kapua on the develop branch and a build of kapua based on the last commit for the 1.6.x release (the 1.6.3 version) and the problem is no more present. I suspect this was an issue on kura side with the version you were using and now the thing should be solved. Thanks, have a good day |
What versions of kapua/kura you were using? |
Describe the bug
When running a Kura device (version 5.1.1) it shows up as online within Kapua. But when trying to open one of the tabs for configuration the following error message appears:
Error
There was an error while sending the request. Error: An error occurred when sending the message: org.eclipse.kapua.service.device.management.asset.message.internal.AssetRequestMessage@667ebd87
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Normally the configuration components should get loaded.
I have also running an old instance of Kapua (0.3.0) where the same Device is working properly... the configuration and the other tabs are loading like expected.
Screenshots
If applicable, add screenshots to help explain your problem.
Version of Kapua
1.6.1
Version of Kura
5.1.1
Type of deployment
[x] Docker -> with Portainer and .yml file
[ ] 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
[ ] - Others
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: