eclipse-kura / kura

Eclipse Kura™ is a versatile framework to supercharge your edge devices, streamlining the process of configuring your gateway, connecting sensors, and IoT devices to seamlessly collect, process, and send data to the cloud.
https://eclipse.dev/kura/
Eclipse Public License 2.0
499 stars 306 forks source link

In kura 5.3.1 I have duplicate keystores #4863

Open MurtadhaS opened 1 year ago

MurtadhaS commented 1 year ago

Describe the bug in kura security tab there are multiple duplicates of the same keystore name. this causes rest service to not work properly and to return 503 error.

To Reproduce Steps to reproduce the behavior:

  1. stop OSGI kura core bundle and start it again.
  2. go to security tab -> keystore configuration in kura GUI

or

deploying my own configuration via kapua (that basically just injects wire graph).

Expected behavior Only one instance of each keystore.

Screenshots image

Target Environment (please complete the following information): Linux

salvatore-coppola commented 1 year ago

Hi @MurtadhaS, how do you stop the Kura core bundles ? Via Web Console or osgi shell ?

MurtadhaS commented 1 year ago

osgi shell.

salvatore-coppola commented 1 year ago

osgi shell.

Do you mean the gogo shell available on the 5002 port ? Are you running a docker instace or a installation on some devices ?

Thanks

MurtadhaS commented 1 year ago

yes the equinox shell by telnetting it. I tried it on both actual device and docker.

salvatore-coppola commented 1 year ago

Ok @MurtadhaS i was able to reproduce the bug, I'll give updates asap.

salvatore-coppola commented 1 year ago

@MurtadhaS as far as i understood the problem is only an entry duplication on webui, it doesn't affect the components. Restarting Kura solve the problem as a temporary solution.

MurtadhaS commented 12 months ago

the api doesn't work when this bug happens. I mean /services/assets for example will return 503 as I recall.

marcellorinaldo commented 11 months ago

Hi @MurtadhaS, the problem seems related to the fact that there is a misalignment between what is present in the ConfigurationAdmin and what is tracked by the ConfigurationService after a component removal. Please refer to PR https://github.com/eclipse/kura/pull/4937 for details.

We won't merge the PR during this Kura 5.4 release since we do not have time to investigate the implications of this change and we think it is not common for users to stop and restart the kura.core bundle.

Feel free to properly test the PR and report any findings.

Best, Marcello

MurtadhaS commented 11 months ago

ok, thanks.

github-actions[bot] commented 9 months ago

This issue is stale because it has been open for 60 days with no activity.