search

ocp-power-automation / ocp4-upi-powervm-hmc

OpenShift on IBM PowerVM servers managed using HMC
Apache License 2.0
6 stars 6 forks source link

master and worker nodes fail to run Ignition after installation of CoreOS #3

Closed TGerisch closed 3 years ago

TGerisch commented 3 years ago

Hi, i opened this bug erroneously in ocp4-upi-powervm: https://github.com/ocp-power-automation/ocp4-upi-powervm/issues/216#issue-934904866

TGerisch commented 3 years ago

found the root cause of this issue - it's because we're using an unusal network configuration. We have configured to ibmveth VLANs - one is attached to a a SEA and extends the lab network, the other one (configured with a private IP range) is isolated. We created a LPAR which has two ibmveth adapters for each VLAN configured and we use this machine as a router. Unfortunately, if TCP packages are routed through ibmveth adapters, the RX and TX checksums are broken. So TCP connections cannot be established between the two networks. This can be mitigated by running the "ethtool -K rx off tx off" command - it switches off checksum creation and TCP works fine. But we did not find a way to automate this when we install CoreOS - so we're able to set up the bootstrap machine, but than bootstrap fails to fetch all arbitrary data - like docker files etc. The other nodes (master and workers) will receive empty data instead from the bootstrap node: 1784.746250] ignition[1248]: GET error: Get "https://api-int.bignumbers-01.saphana.example.com:22623/config/master": EOF [ **] A start job is running for Ignition (fetch) (29min 46s / no limit)[ 1789.746774] ignition[1248]: GET https://api-int.bignumbers-01.saphana.example.com:22623/config/master: attempt #361

Closing this as a bug - maybe there is a chance to set up CoreOS with such special device settings, but i didn't found any description how to do this.