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
readinessProbe.sh-script fails silently #79
Labels
bug
Something isn't working
Comments
aboucham
added a commit
to aboucham/activemq-artemis-broker-kubernetes-image
that referenced
this issue
Oct 9, 2023
Fix the readinessProbe.sh-script issue.
aboucham
added a commit
to aboucham/activemq-artemis-broker-kubernetes-image
that referenced
this issue
Oct 9, 2023
Fix the readinessProbe.sh-script issue.
gaohoward
pushed a commit
that referenced
this issue
Oct 9, 2023
Fix the readinessProbe.sh-script issue.
gaohoward
pushed a commit
that referenced
this issue
Oct 9, 2023
Fix the readinessProbe.sh-script issue.
aboucham
changed the title
readinessProbe.sh-script fails
readinessProbe.sh-script fails silently
Oct 9, 2023
rh-messaging-ci
pushed a commit
to rh-messaging/activemq-artemis-broker-kubernetes-image
that referenced
this issue
Nov 28, 2023
Fix the readinessProbe.sh-script issue. (cherry picked from commit aee9eab) downstream: ENTMQBR-8476
rh-messaging-ci
pushed a commit
to rh-messaging/activemq-artemis-broker-kubernetes-image
that referenced
this issue
Nov 28, 2023
Fix the readinessProbe.sh-script issue. (cherry picked from commit d5bb905) downstream: ENTMQBR-8476
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The problem is that when the scripts fetch an empty list from
/proc/net/tcp
and since it doesn't get an exception it won't fetch/proc/net/tcp6
where the ports are really are. It then doesn't find any open ports.The problem here is that the value-variable is not stripped before it is split. This results in all ports equals
None
and then it will always continue - no matter whether the ports are listening or not.The text was updated successfully, but these errors were encountered: