Fix DCD crash in openapi validation if meta_data is null - #921
Closed
sehaeg wants to merge 1 commit into
Closed
Conversation
Contributor
|
Thanks for the PR. We have merged it |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
General information
DCD is crashing in Checkmk 2.5 if there are Hosts with following meta_data:
"meta_data": { "created_at": null, "updated_at": "2026-06-08T08:39:43.296016+00:00", "created_by": null } },This case is happening with hosts created directly with hosts.mk or hosts older than Checkmk 1.6 (werk #7235)
Bug reports
I tried this with Checkmk 2.5.0p3 pro.
All DCD connections are affected (Piggyback and FileConnector tested)
For more logs and informations see SUP-29418
Proposed changes
Target of the fix is to prevent making a timestamp from a not existing value.
There should be no other impact.