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
cert-provisioner-job failed due to missing pl-cloud-config ConfigMap #311
Comments
Thanks @lizrice ! We recently just switched to an operator-based deploy of Pixie, and are still working to make the operator more robust after a failed installation. Would it be possible to provide logs from the Could you try manually deleting the operator's namespace ( |
I'm getting the same "too many open files" in my failing deployment -
Just looking at the first post for more details you want before I blow all this away ...
|
I seem to be able to reproduce this at will on one of my clusters, so if there is any more useful information I can provide, please let me know. I'll be completely offline for a couple weeks starting in a few days though. Edit: Alright, I tracked my issue down thanks to a stack exchange (or something) comment that said something about needed persistent storage. I did have it and has the same SC that was working perfectly fine for my other cluster, but for whatever reason it wasn't working for this cluster (even though PVs were being created). When I ditched that CSI, created a new one and made a new default SC on top of it, it installed without a hitch, quickly, on the first try. Hopefully this tidbit of info helps someone in the future! |
For anyone bumping into this. For me it was enough to delete the pvc related and redeploy. |
Describe the bug
Running
px deploy
got errorFATA[0368] Timed out waiting for cluster ID assignment
Inspecting pods showed that the cert-provisioner-job was in CreateContainerConfigError state.
Output from
kubectl describe pod cert-provisioner-job-lwm57 -n pl
:To Reproduce
It may, or may not, be relevant that my first run of
px deploy
failed as follows:Trying a second time (in case fewer files were open):
The text was updated successfully, but these errors were encountered: