Before doing the node-agent element migration, check if the nodes element already exists - #26170
Open
JackienStephan wants to merge 1 commit into
Open
Conversation
…ment already exists.
dmatej
reviewed
Aug 7, 2026
| } | ||
| }, domain); | ||
| } catch (Exception e) { | ||
| Logger.getAnonymousLogger().log(Level.SEVERE, |
Contributor
There was a problem hiding this comment.
Wouldn't be better to move the log to the message of the runtime exception?
Contributor
Author
There was a problem hiding this comment.
I just want to follow the same style of the other try-catch of ConfigSupport.apply(..) in this soruce code.
OndroMih
approved these changes
Aug 27, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After doing
start-domain --upgrade, all the nodes are removed.I think
createDefaultNodeList()should not be done whennodesexists andnode-agentsnot exist.