#trident-controller main won't start with chmod /plugin/: operation not permitted

1 messages · Page 1 of 1 (latest)

compact falcon
#

I have upgraded trident from 22.07.0 to 23.07.0 in OCP 4.10 environment with trident operator. The trident-controller pod keeps "CrashLoopBackOff" due to trident-main container won't start with error "chmod /plugin/: operation not permitted". All trident daemonset pods are not running too.
It is almost the same case as issue #843 (https://github.com/NetApp/trident/issues/843). The only difference is that I've upgraded trident with trident operator instead of helm.
In issue #843, the possible reason is missing SCCs. During upgrade, I have wrongly chosen bundle_post_1_25.yaml instead of bundle_pre_1_25.yaml but I fell back. I am not sure if SCCs were removed when I fell back by using "oc delete -f bundle_post_1_25.yaml" command.
May I know how I can check and exact how to add back the missing SCCs with "oc adm" command to fix it?
Thanks.

GitHub

Storage orchestrator for containers. Contribute to NetApp/trident development by creating an account on GitHub.

raw ermine
#

Run through the upgrade process again for 23.07.0, but choose the bundle_pre_1_25.yaml this time.

prisma blade