-
Notifications
You must be signed in to change notification settings - Fork 85
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
1.27 csi-oci-controller pod CrashLoopBackOff #447
Comments
Can you please try to apply the manifest without the following lines in it |
Yes, removing the image-pull-secret does cleanup that FailedToRetrieveImagePullSecret warning. If the snapshot-controller came from the following, is it duplicate of the following (csi-snapshotter)? |
@YashasG98 PTAL |
@shihchang the snapshot-controller and external-snapshotter help take backups of volumes and restore from the backups when needed They can be removed if you do not intend to use the snapshot/restore ability. Could you please share the output for kubectl logs for the failing container to help understand why it is crashing |
Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT
Versions
CCM Version: 1.27
Environment:
kubectl version
):Client Version: v1.24.0
Kustomize Version: v4.5.4
Server Version: v1.28.3+1.el8
uname -a
): uname -aLinux k8sol8-api-server-001 5.15.0-105.125.6.2.1.el8uek.x86_64 Add support for disabling security rules to allow handling them differently #2 SMP Thu Sep 14 21:58:59 PDT 2023 x86_64 x86_64 x86_64 GNU/Linux
What happened?
csi-oci-controller pod CrashLoopBackOff, found two issues:
What you expected to happen?
csi-oci-controller status should be running
How to reproduce it (as minimally and precisely as possible)?
kubectl apply with https://github.com/oracle/oci-cloud-controller-manager/blob/master/manifests/container-storage-interface/oci-csi-controller-driver.yaml
Anything else we need to know?
The text was updated successfully, but these errors were encountered: