-
Notifications
You must be signed in to change notification settings - Fork 542
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
olm spin loop when trying to install operator #1757
Comments
My problem appears to be independent of which operator I try to deploy. I just tried to deploy the Jaeger operator and got the same spin loop. |
Hi Bryan, Can you share the contents of the InstallPlan that is stuck? At this point, there should be a job in the "olm" namespace that is fetching and unpacking the contents of the requested bundle. It sounds like something has gone wrong there. |
Yep, makes sense now:
Is there documentation on installing olm when using PSP's? I'm not sure what PSP the olm namespace is using since I allowed the script to create the namespace and it did so outside of any Rancher project that would normally have a specific PSP. |
I think I'm getting closer. I deleted the olm and operator namespaces. I then created namespaces under a Rancher project that had a PSP defined. I created a
I applied the yaml files and everything looked ok, so I tried the following subscription:
Now, I get the following:
And, I'm getting errors in the catalog-operator:
|
I deleted the subscription and tried again. Now, I see the operator trying to start up, but has the error:
The error message is correct. The service account exists, but there is no API token. |
This issue is getting off track. For anyone that ends up here, the original problem was caused by deploying olm to the default namespaces which did not have a proper pod security policy. The fix was to deploy to custom namespaces that had a proper PSP. |
Bug Report
What did you do?
What did you expect to see?
Operator installed
What did you see instead? Under which circumstances?
Operator not installed
Environment
Rancher on-prem
Additional context
Catalog operator logs:
The text was updated successfully, but these errors were encountered: