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.

Sign up for GitHub

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

Jump to bottom

[cloud2edge] No connection from Hono device registry to MongoDB #482

Closed
calohmn opened this issue Aug 9, 2023 · 1 comment · Fixed by #483
Closed

[cloud2edge] No connection from Hono device registry to MongoDB #482

calohmn opened this issue Aug 9, 2023 · 1 comment · Fixed by #483
Assignees
@calohmn
Labels
bug Something isn't working Cloud2Edge Improvements to the Cloud2Edge package

Comments

@calohmn
Copy link
Contributor

calohmn commented Aug 9, 2023 •
edited
Loading

Installing the cloud2edge chart with the default configuration from the values.yaml leads to the Hono service registry not being able to connect to the MongoDB. The device registry is using the wrong hostname (ditto-mongodb) for connecting to the MongoDB (available under <release-name>-mongodb, e.g. c2e-mongodb).

Apart from that, the MongoDB pod is also not getting ready (container getting OOM killed and using a lot of CPU).
@calohmn calohmn added bug Something isn't working Cloud2Edge Improvements to the Cloud2Edge package labels Aug 9, 2023
@calohmn calohmn self-assigned this Aug 9, 2023
@calohmn
Copy link
Contributor Author

calohmn commented Aug 9, 2023 •
edited
Loading

The first issue seems to be due to this change in the ditto chart, letting a non-fixed mongodb hostname to be used - which the Hono device registry isn't using.

The MongoDB pod CPU/memory issues seem to be due to a MongoDB chart update, letting #403 come up again.

Workaround for both is using the ditto 3.1.0 chart version instead of a newer one. That means changing version: ~3.1.0 to version: 3.1.0 in packages/cloud2edge/requirements.yaml.

calohmn added a commit to bosch-io/packages that referenced this issue Aug 10, 2023
@calohmn
[eclipse#482] Fix wrong MongoDB hostname; fix MongoDB health checks.
b4c6d87 
Fixes Hono devices registry not being able to connect to the
MongoDB instance because it used the wrong hostname.
Also fixes MongoDB not getting ready because the health checks
took too long and caused OOM errors.
Also restrict Hono chart dependency version range (needed for
upcoming changes addressing eclipse#430).

Signed-off-by: Carsten Lohmann <[email protected]>
This was referenced Aug 10, 2023
Merged
Closed
Closed
@calohmn calohmn linked a pull request Aug 17, 2023 that will close this issue
[#482] Fix wrong MongoDB hostname; fix MongoDB health checks. #483
Merged
calohmn added a commit that referenced this issue Aug 18, 2023
@calohmn
[#482] Fix wrong MongoDB hostname; fix MongoDB health checks.
04aebcd 
Fixes Hono devices registry not being able to connect to the
MongoDB instance because it used the wrong hostname.
Also fixes MongoDB not getting ready because the health checks
took too long and caused OOM errors.
Also restrict Hono chart dependency version range (needed for
upcoming changes addressing #430).

Signed-off-by: Carsten Lohmann <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@calohmn calohmn

Labels
bug Something isn't working Cloud2Edge Improvements to the Cloud2Edge package
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[#482] Fix wrong MongoDB hostname; fix MongoDB health checks. bosch-io/packages
1 participant
@calohmn