Fix CrashLoopBackOff, ramdisk-logs no inotifywait#564
Merged
openshift-merge-bot[bot] merged 1 commit intoopenstack-k8s-operators:mainfrom Jun 16, 2025
Merged
Fix CrashLoopBackOff, ramdisk-logs no inotifywait#564openshift-merge-bot[bot] merged 1 commit intoopenstack-k8s-operators:mainfrom
openshift-merge-bot[bot] merged 1 commit intoopenstack-k8s-operators:mainfrom
Conversation
When updating the operators we end up recreating the conductor and
inspector deployments. But the old service images does not yet have
the required command: inotifywait - because of the missing command
the pod enter CrashLoopBackOff state.
To resolve the issue, the OpenstackVersion must be patch to update
the container images.
To workaround this issue, add a check for the inotifywait command,
and in case it does not exist:
a) Print a Warning
b) Starta a tail for follow /dev/null to have the container do
nothing forever. (e.g. until it is restarted with new service
container images after patching the OpenstackVersion.)
Jira: OSPRH-17520
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hjensas The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
steveb
reviewed
Jun 16, 2025
Collaborator
steveb
left a comment
steveb
left a comment
There was a problem hiding this comment.
/lgtm
tail exits on SIGTERM, which is good
openshift-merge-bot
bot
merged commit e634c08
into
openstack-k8s-operators:main
7 checks passed
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
2 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.
When updating the operators we end up recreating the conductor and inspector deployments. But the old service images does not yet have the required command:
inotifywait- because of the missing command the pod enterCrashLoopBackOffstate.To resolve the issue, the
OpenstackVersionmust be patched to update the container images.To workaround this issue, add a check for the
inotifywaitcommand, and in case it does not exist:tail -f /dev/null) to have the container do nothing forever.(e.g. until it is restarted with new service container images after patching the
OpenstackVersion.)Jira: OSPRH-17520