polite-translator-35958
05/25/2023, 3:09 PMsystemctl start rke2-server
eventually times out and fails. It seems like it’s waiting for etcd startup which never happens. I’m guessing something changed in the rhel release, but I’m failing to grok what the issue is. Anyone seen this?hundreds-evening-84071
05/25/2023, 4:26 PMpolite-translator-35958
05/25/2023, 4:54 PMgray-lawyer-73831
05/25/2023, 6:32 PMrpm -qi container-selinux
polite-translator-35958
05/25/2023, 7:08 PMcontainer-selinux
went from v2.189.0-1
on a working RHEL8.7 system to v2.205.0-2
on non-working RHEL8.8 system./etc/NetworkManager/conf.d/rke2-canal.conf
file as described on that known issues page.gray-lawyer-73831
05/25/2023, 7:11 PMyum install container-selinux-2:2.189.0-1.module+el8.7.0+17824+66a0202b
polite-translator-35958
05/25/2023, 7:11 PMbillowy-afternoon-45803
05/25/2023, 9:20 PMhundreds-evening-84071
05/25/2023, 9:26 PMjournalctl -u rke2-server
to see it contains any pointers?billowy-afternoon-45803
05/25/2023, 9:44 PMT15:30:14-06:00" level=info msg="Waiting for API server to become available"
T15:30:14-06:00" level=info msg="Tunnel server egress proxy waiting for runtime core to become available"
T15:30:16-06:00" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: <https://192.168.56.3:9345/v1-rke2/readyz>: 500 Internal Server Error"
T15:30:19-06:00" level=info msg="Tunnel server egress proxy waiting for runtime core to become available"
T15:30:21-06:00" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: <https://192.168.56.3:9345/v1-rke2/readyz>: 500 Internal Server Error"
T15:30:24-06:00" level=info msg="Container for etcd not found (no matching container found), retrying"
T15:30:24-06:00" level=info msg="Tunnel server egress proxy waiting for runtime core to become available"
T15:30:26-06:00" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: <https://192.168.56.3:9345/v1-rke2/readyz>: 500 Internal Server Error"
"ts":"2023-05-25T15:30:29.464-0600","logger":"etcd-client","caller":"v3@v3.5.4-k3s1/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"<etcd-endpoints://0xc00079dc00/127.0.0.1:2379>","attempt":0,"error":"rpc error: code = Deadline>
"ts":"2023-05-25T15:30:29.465-0600","logger":"etcd-client","caller":"v3@v3.5.4-k3s1/client.go:210","msg":"Auto sync endpoints failed.","error":"context deadline exceeded"}
T15:30:29-06:00" level=info msg="Tunnel server egress proxy waiting for runtime core to become available"
T15:30:31-06:00" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: <https://192.168.56.3:9345/v1-rke2/readyz>: 500 Internal Server Error"
T15:30:34-06:00" level=info msg="Tunnel server egress proxy waiting for runtime core to become available"
Nothing very specific, as far as I can telll RKE2 isnt even starting any containers checking the /var/log/containers log directory yields an empty folder.polite-translator-35958
05/26/2023, 4:28 AMhundreds-evening-84071
05/26/2023, 1:16 PM