-
Notifications
You must be signed in to change notification settings - Fork 112
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
Few containers fail to start: iptables v1.4.21: can't initialize iptables table `filter' #82
Comments
@yprokule Are they being launched by the BMO as privileged containers with host networking? |
@juliakreger not sure how to check it, but here is containers' description from pod:
|
@imain @dhellmann All containers except the baremetal-operator have privileged set to True. https://github.com/openshift-metal3/dev-scripts/blob/master/operator_ironic.yaml |
@yprokule Are your steps to reproduce purely fire-up an install with openshift-metal3/dev-scripts? Or are you taking other steps? |
I suspect the only option here is to try ingress policy filters for the pod.... In other words, remove the ip tables statements and we update the yaml loading the pod. Thoughts? @dtantsur @derekhiggins see: https://kubernetes.io/docs/concepts/services-networking/network-policies/ |
As long as it works - I'm good with it :) I |
I thought this error could be ignored but maybe i'm wrong, hmm, in the pod description(above) i don't see mention of privileged (as in https://github.com/metal3-io/baremetal-operator/blob/8169897aeb6580c27671f1b78d6217a541c8e079/deploy/operator_ironic.yaml#L60) not sure if its relevant tbh.. |
I think #83 fixes this. |
What environment are you running this on? Is it a baremetal deployment? I'm wondering if 'provisioning interface' is set correctly? |
Virtual, deployed with make script from dev-scripts |
Few ironic* containers fail to start as part of bmo pod:
$ oc get po -n openshift-machine-api | grep baremet metal3-baremetal-operator-74fdb86688-pw6c4 4/8 CrashLoopBackOff 152 3h5m
The text was updated successfully, but these errors were encountered: