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.
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
Unexpected broker pod restarts caused by TRIGGERED_ROLL_COUNT #815
Labels
bug
Something isn't working
Comments
brusdev
added a commit
to brusdev/activemq-artemis-operator
that referenced
this issue
Mar 6, 2024
The requestedResources need to be sorted because they are extracted from a map and adler32 depends on the prder of the bytes.
brusdev
added a commit
to brusdev/activemq-artemis-operator
that referenced
this issue
Mar 6, 2024
The requestedResources need to be sorted because they are extracted from a map and adler32 depends on the prder of the bytes.
brusdev
added a commit
to brusdev/activemq-artemis-operator
that referenced
this issue
Mar 6, 2024
The requestedResources need to be sorted because they are extracted from a map and adler32 depends on the prder of the bytes.
brusdev
added a commit
to brusdev/activemq-artemis-operator
that referenced
this issue
Mar 6, 2024
…ERED_ROLL_COUNT The requestedResources need to be sorted because they are extracted from a map and adler32 depends on the prder of the bytes.
gaohoward
pushed a commit
that referenced
this issue
Mar 7, 2024
The requestedResources need to be sorted because they are extracted from a map and adler32 depends on the prder of the bytes.
This issue will be fixed in 1.1.0 |
brusdev
added a commit
that referenced
this issue
Mar 7, 2024
brusdev
added a commit
that referenced
this issue
Mar 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Sometimes the broker pods are restarted because the value of the environment variable
TRIGGERED_ROLL_COUNT
changes even if the tracked secretes don't change.Tip
Vote this issue reacting with 👍 or 👎
The text was updated successfully, but these errors were encountered: