You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
openshift-machine-api/metal3-6f5bf78c49-8vtzw/metal3-ramdisk-logs is in a CrashLoopBackOff
/usr/bin/python3: No module named pyinotify
Stream closed EOF for openshift-machine-api/metal3-6f5bf78c49-8vtzw (metal3-ramdisk-logs)
Also, I've had this other problem ever since I enabled IPv6 RA on my network (even if not actively using IPv6 in the install-config.yaml or on the network), where the ovs-configuration.service fails whenever the nodes are rebooted (which happens atleast once during an installation or upgrade). My workaround is to ssh into the node, deleting /etc/NetworkManager/system-connections/ovs-if-br-ex.nmconnection, and restarting NetworkManager.service. By using this "work-around" I currently run a dual-stack cluster.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
openshift-machine-api/metal3-6f5bf78c49-8vtzw/metal3-ramdisk-logsis in aCrashLoopBackOffAlso, I've had this other problem ever since I enabled IPv6 RA on my network (even if not actively using IPv6 in the
install-config.yamlor on the network), where theovs-configuration.servicefails whenever the nodes are rebooted (which happens atleast once during an installation or upgrade). My workaround is to ssh into the node, deleting/etc/NetworkManager/system-connections/ovs-if-br-ex.nmconnection, and restartingNetworkManager.service. By using this "work-around" I currently run a dual-stack cluster.Beta Was this translation helpful? Give feedback.
All reactions