Open pmokrz opened 2 years ago
I don't know anything about trident. Here's the package list that changed during the update from 36.20220605.3.0
to 36.20220618.3.1
:
Upgraded:
NetworkManager 1:1.38.0-1.fc36 -> 1:1.38.0-2.fc36
NetworkManager-cloud-setup 1:1.38.0-1.fc36 -> 1:1.38.0-2.fc36
NetworkManager-libnm 1:1.38.0-1.fc36 -> 1:1.38.0-2.fc36
NetworkManager-team 1:1.38.0-1.fc36 -> 1:1.38.0-2.fc36
NetworkManager-tui 1:1.38.0-1.fc36 -> 1:1.38.0-2.fc36
afterburn 5.3.0-1.fc36 -> 5.3.0-2.fc36
afterburn-dracut 5.3.0-1.fc36 -> 5.3.0-2.fc36
containerd 1.6.4-1.fc36 -> 1.6.6-1.fc36
coreos-installer 0.14.0-1.fc36 -> 0.15.0-1.fc36
coreos-installer-bootinfra 0.14.0-1.fc36 -> 0.15.0-1.fc36
crypto-policies 20220203-2.git112f859.fc36 -> 20220428-1.gitdfb10ea.fc36
fuse-sshfs 3.7.2-3.fc36 -> 3.7.3-1.fc36
grub2-common 1:2.06-40.fc36 -> 1:2.06-42.fc36
grub2-efi-x64 1:2.06-40.fc36 -> 1:2.06-42.fc36
grub2-pc 1:2.06-40.fc36 -> 1:2.06-42.fc36
grub2-pc-modules 1:2.06-40.fc36 -> 1:2.06-42.fc36
grub2-tools 1:2.06-40.fc36 -> 1:2.06-42.fc36
grub2-tools-minimal 1:2.06-40.fc36 -> 1:2.06-42.fc36
kernel 5.17.12-300.fc36 -> 5.18.5-200.fc36
kernel-core 5.17.12-300.fc36 -> 5.18.5-200.fc36
kernel-modules 5.17.12-300.fc36 -> 5.18.5-200.fc36
libipa_hbac 2.7.0-1.fc36 -> 2.7.1-2.fc36
libnfsidmap 1:2.6.1-2.rc5.fc36 -> 1:2.6.1-2.rc6.fc36
libsss_certmap 2.7.0-1.fc36 -> 2.7.1-2.fc36
libsss_idmap 2.7.0-1.fc36 -> 2.7.1-2.fc36
libsss_nss_idmap 2.7.0-1.fc36 -> 2.7.1-2.fc36
libsss_sudo 2.7.0-1.fc36 -> 2.7.1-2.fc36
libtool-ltdl 2.4.6-50.fc36 -> 2.4.7-1.fc36
linux-firmware 20220509-132.fc36 -> 20220610-135.fc36
linux-firmware-whence 20220509-132.fc36 -> 20220610-135.fc36
moby-engine 20.10.16-1.fc36 -> 20.10.17-2.fc36
mozjs91 91.9.0-1.fc36 -> 91.10.0-1.fc36
nfs-utils-coreos 1:2.6.1-2.rc5.fc36 -> 1:2.6.1-2.rc6.fc36
ostree 2022.3-3.fc36 -> 2022.4-2.fc36
ostree-libs 2022.3-3.fc36 -> 2022.4-2.fc36
podman 3:4.1.0-1.fc36 -> 3:4.1.0-8.fc36
podman-plugins 3:4.1.0-1.fc36 -> 3:4.1.0-8.fc36
rpm-ostree 2022.9-1.fc36 -> 2022.10-2.fc36
rpm-ostree-libs 2022.9-1.fc36 -> 2022.10-2.fc36
shim-x64 15.4-5 -> 15.6-1
skopeo 1:1.7.0-1.fc36 -> 1:1.8.0-8.fc36
sssd-ad 2.7.0-1.fc36 -> 2.7.1-2.fc36
sssd-client 2.7.0-1.fc36 -> 2.7.1-2.fc36
sssd-common 2.7.0-1.fc36 -> 2.7.1-2.fc36
sssd-common-pac 2.7.0-1.fc36 -> 2.7.1-2.fc36
sssd-ipa 2.7.0-1.fc36 -> 2.7.1-2.fc36
sssd-krb5 2.7.0-1.fc36 -> 2.7.1-2.fc36
sssd-krb5-common 2.7.0-1.fc36 -> 2.7.1-2.fc36
sssd-ldap 2.7.0-1.fc36 -> 2.7.1-2.fc36
sssd-nfs-idmap 2.7.0-1.fc36 -> 2.7.1-2.fc36
systemd 250.6-1.fc36 -> 250.7-1.fc36
systemd-container 250.6-1.fc36 -> 250.7-1.fc36
systemd-libs 250.6-1.fc36 -> 250.7-1.fc36
systemd-pam 250.6-1.fc36 -> 250.7-1.fc36
systemd-resolved 250.6-1.fc36 -> 250.7-1.fc36
systemd-udev 250.6-1.fc36 -> 250.7-1.fc36
vim-data 2:8.2.5052-1.fc36 -> 2:8.2.5085-1.fc36
vim-minimal 2:8.2.5052-1.fc36 -> 2:8.2.5085-1.fc36
Removed:
sssd-idp-2.7.0-1.fc36.x86_64
The problem may be somewhere in that package set change.
Do you have any more information about what exactly is failing?
From what I found it somewhere after the update, some strange way is blocking communication between the pods in the k8s cluster. Maybe someone had a similar case?
My solution sudo ethtool --offload vxlan.calico rx off tx off was done on every node
Describe the bug After doing upgrade Fedora CoreOS to ver 36.20220716.3.1 the Node-CSI driver still connecting.
I have this problem only with new OS: Fedora CoreOS 36.20220618.3.1 Fedora CoreOS 36.20220703.3.1 Fedora CoreOS 36.20220716.3.1
Environment