RPL-67: Fix - Added max aliases field to set a valid value #404
Conversation
This file contains 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
alexander-variacode
force-pushed
the
issue_rpl-67_ansible-max-aliases
branch
from
eeb4791 to
1b7915f
Compare
alexander-variacode
force-pushed
the
issue_rpl-67_ansible-max-aliases
branch
from
d6c96c0 to
9e0847e
Compare
ltamaster
approved these changes
Dec 2, 2024
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.
⛔️ Ticket
https://pagerduty.atlassian.net/browse/RPL-67
❌ Issue
Since upgrade to Rundeck 5.5.0, the ansible nodes are not refreshed
This message is displayed in Rundeck node settings:
Number of aliases for non-scalar nodes exceeds the specified max=50
✅ Solution
Added max aliases field to set a valid value according to the inventory.