Closed Yarboa closed 1 week ago
I also see this from ip netns
[root@node1 ~]# ip netns exec netns-f7133da7-ba6f-4ba2-f366-ad80f5835436 netstat -st
IcmpMsg:
InType0: 2594
OutType3: 1
OutType8: 9218
Tcp:
1756 active connection openings
0 passive connection openings
0 failed connection attempts
1717 connection resets received
1 connections established
136362 segments received
141673 segments sent out
14798 segments retransmitted
0 bad segments received
16 resets sent
UdpLite:
TcpExt:
3 TCP sockets finished time wait in fast timer
9 packets rejected in established connections because of timestamp
1747 delayed acks sent
Quick ack mode was activated 763 times
1759 packet headers predicted
61560 acknowledgments not containing data payload received
32411 predicted acknowledgments
TCPLostRetransmit: 11314
TCPTimeouts: 13056
TCPLossProbes: 1742
TCPBacklogCoalesce: 5
TCPDSACKOldSent: 763
TCPRcvCoalesce: 70
TCPOrigDataSent: 39469
TCPKeepAlive: 62338
TCPDelivered: 37735
TcpTimeoutRehash: 13056
@dougsland Maybe need to sync all containers with ntp
I also see this
[root@default-0 ~]# date
Sun Jun 16 04:37:05 AM EDT 2024
[root@default-0 ~]# podman exec -it node1 bash
[root@node1 ~]# date
Sun Jun 16 08:37:17 UTC 2024
[root@node1 ~]#
[root@node1 ~]# exit
exit
[root@default-0 ~]# podman exec -it control bash
[root@control ~]# date
Sun Jun 16 08:37:33 UTC 2024
Need to check adding --tz=local
to control and node1
Followed this blog https://www.redhat.com/sysadmin/tick-tock-container-time
I also see this
[root@default-0 ~]# date Sun Jun 16 04:37:05 AM EDT 2024 [root@default-0 ~]# podman exec -it node1 bash [root@node1 ~]# date Sun Jun 16 08:37:17 UTC 2024 [root@node1 ~]# [root@node1 ~]# exit exit [root@default-0 ~]# podman exec -it control bash [root@control ~]# date Sun Jun 16 08:37:33 UTC 2024
Need to check adding
--tz=local
to control and node1
I remember this one: https://github.com/containers/qm/issues/394
Followed this blog https://www.redhat.com/sysadmin/tick-tock-container-time
Tiers e2e tests started to fail on qm-node
Jun 14 15:48:57 control bluechi-controller[158]: Node 'qm-node1' disconnected Jun 14 15:49:53 control bluechi-controller[158]: Registered managed node from fd 11 as 'qm-node1'
While bluechi-agent inside qm indicates log connectivity
While the following
More tests here, it seems that network is down every 60-90 seconds Install in node1
dnf -y install --releasever 9 --installroot /usr/lib/qm/rootfs python iputils
ControllerHost=10.90.0.2
[root@node1 ~]# podman exec qm bash -c "ping 10.90.0.2"
It also happens from the namespace itself
While ping from node1 to controller adress is not uninterruptible