[LP#2067404] Check and log all events on failed resources #7
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
addyess
commented
Jul 8, 2024
addyess
commented
Jul 8, 2024
addyess
commented
Jul 8, 2024
addyess
commented
Jul 8, 2024
|
@HomayoonAlimohammadi how does it look. Are we happy? |
|
@addyess Yea I was waiting for the CI to pass. Let's merge this! |
HomayoonAlimohammadi
deleted the
KU-1026/lp2067404-controllerplugin-unavailable
branch
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.
LP#2067404
Overview
It's been reported the charm is stuck in a Waiting state that doesn't resolve due to conditions on the
csi-cinder-controllerplugindeployment resource not going active. These changes will log to the charm debug log in the event of such circumstances.Details
Gather the deployment and pod events associated with the deployment (or daemonsets) deployed by this charm to determine if there is anything the juju administrator can do to improved the deployment state.
Events will be logged in the charm's debug log in timestamp order, least recent to most recent.