The failure in the crashdump looks unrelated - it hadn't made it far enough to start calico-node yet.
The accidental /2 is likely to cause major problems. That's claiming the entire address range from 192.0.0.0 to 255.255.255.255. Let us know if you see a problem with the /22 and we'll look into it deeper.
The failure in the crashdump looks unrelated - it hadn't made it far enough to start calico-node yet.
The accidental /2 is likely to cause major problems. That's claiming the entire address range from 192.0.0.0 to 255.255.255.255. Let us know if you see a problem with the /22 and we'll look into it deeper.