December 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1233690] Docker containers are not reachable from network after OS update from 20241114 to 20241115
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233690 https://bugzilla.suse.com/show_bug.cgi?id=1233690#c11 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |awoo(a)posteo.de --- Comment #11 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- *** Bug 1233980 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233980] Recent update to uptables/nftables/xtables breaks docker inter-container networking
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233980 https://bugzilla.suse.com/show_bug.cgi?id=1233980#c8 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(awoo(a)posteo.de) | Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- I managed to reproduce the issue, and this is currently a duplicate issue. Feel free to review and comment on the original issue. *** This bug has been marked as a duplicate of bug 1233690 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233690] Docker containers are not reachable from network after OS update from 20241114 to 20241115
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233690 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Flags|needinfo?(seifert(a)alesak.ne | |t) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233690] Docker containers are not reachable from network after OS update from 20241114 to 20241115
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233690 https://bugzilla.suse.com/show_bug.cgi?id=1233690#c10 --- Comment #10 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- I managed to reproduce a scenario where the container does not have internet. It only happens when using iptables v1.8.11 (nf_tables) not iptables v1.8.11 (legacy). To reproduce this issue I had to do the following: > sudo iptables-legacy -F > sudo iptables-legacy -X > sudo iptables -F > sudo iptables -X > sudo systemctl restart docker > docker run --rm alpine ping -c 4 1.1.1.1 The result was: > PING 1.1.1.1 (1.1.1.1): 56 data bytes > --- 1.1.1.1 ping statistics --- > 4 packets transmitted, 0 packets received, 100% packet loss The current workaround is to remove iptables-backend-nft, reset iptables rules, and restart Docker. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233690] Docker containers are not reachable from network after OS update from 20241114 to 20241115
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233690 https://bugzilla.suse.com/show_bug.cgi?id=1233690#c9 --- Comment #9 from JDA <jda82(a)vicious-gaming.de> --- For me this changes nothing. I tried a "clean" start by removing all my compose stacks, stopping docker, flushing the FORWARD and the related DOCKER-* Chains , starting docker and re-upping the stacks - the rules are still incomplete and the DROP-Counter of FORWARD increases. Any suggestion on keywords to look for regarding docker not being able to update the rules? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231278] [doc] Domain name system
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231278 https://bugzilla.suse.com/show_bug.cgi?id=1231278#c1 Tomáš Bažant <tbazant(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Whiteboard| |https://jira.suse.com/brows | |e/DOCTEAM-1649 Assignee|fs(a)suse.com |jsindelarova(a)suse.com --- Comment #1 from Tomáš Bažant <tbazant(a)suse.com> --- Thank you for reporting this bug! It is being tracked and processed as part of our queue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234026] preempt=full causes frequent freezing
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234026 https://bugzilla.suse.com/show_bug.cgi?id=1234026#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lassi.vaatamoinen(a)gmail.com | |, tiwai(a)suse.com Flags| |needinfo?(lassi.vaatamoinen | |(a)gmail.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- As TW is already moving to 6.12.x, could you verify whether the issue is reproducible with the kernel in OBS Kernel:stable repo? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233690] Docker containers are not reachable from network after OS update from 20241114 to 20241115
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233690 https://bugzilla.suse.com/show_bug.cgi?id=1233690#c8 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(seifert(a)alesak.ne | |t) CC| |containers-bugowner(a)suse.de Assignee|containers-bugowner(a)suse.de |alexandre.vicenzi(a)suse.com --- Comment #8 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- Restarting Docker service usually recreates iptables rules: > sudo systemctl restart docker Can you test if a restart fixes anything? You can also reset all iptables rules to get rid of possible corrupted rules, but be aware that this resets everything, I recommend backing up any rules before you proceed. If you are in a ssh session you can get locked out if you reset iptables. A backup or snapshot is recommended to not lose any data before you proceed. To reset iptable rules: > sudo iptables -F > sudo iptables -X To recreate docker rules just restart the service as shown before. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234010] Unable to unlock multiple encrypted partitions with FIDO2 Key, Systemdboot+LUKS
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234010 https://bugzilla.suse.com/show_bug.cgi?id=1234010#c2 --- Comment #2 from Chris Miller <chris.beaudry.miller(a)gmail.com> --- Once the swap partition gets decrypted swap works fine, the issue is that initial decryption of the swap partition is not happening with FIDO2. Here is my system swap status after booting with plymouth disabled and not plugging in the FIDO2 key, which avoids the issue since the system falls back to password immediately. In this case I only have to enter my password once to unlock both the root and swap partitions. (base) cbmiller@localhost:/dev> sudo swapon --show NAME TYPE SIZE USED PRIO /dev/dm-1 partition 31.3G 0B -2 /dev/zram0 partition 31.3G 139.5M 100 (base) cbmiller@localhost:/dev> sudo dmsetup info cr_swap Name: cr_swap State: ACTIVE Read Ahead: 1024 Tables present: LIVE Open count: 1 Event number: 0 Major, minor: 254, 1 Number of targets: 1 UUID: CRYPT-LUKS2-1b692ff923f54d8486ee51b3c3cb72c4-cr_swap (base) cbmiller@localhost:/dev> lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 465.8G 0 disk └─sda1 8:1 0 465.8G 0 part /OFFLOAD sdb 8:16 0 10.9T 0 disk └─sdb1 8:17 0 10.9T 0 part /run/media/cbmiller/Chris_Backup zram0 253:0 0 31.3G 0 disk [SWAP] nvme0n1 259:0 0 931.5G 0 disk ├─nvme0n1p1 259:1 0 512M 0 part /boot/efi ├─nvme0n1p2 259:2 0 899.7G 0 part │ └─cr_root 254:0 0 899.7G 0 crypt /var │ /usr/local │ /srv │ /root │ /home │ /boot/grub2/x86_64-efi │ /opt │ /boot/grub2/i386-pc │ /.snapshots │ / └─nvme0n1p3 259:3 0 31.3G 0 part └─cr_swap 254:1 0 31.3G 0 crypt [SWAP] Here is the output from cryptenroll: (base) cbmiller@localhost:/dev> sudo systemd-cryptenroll /dev/nvme0n1p2 SLOT TYPE 0 password 1 fido2 (base) cbmiller@localhost:/dev> sudo systemd-cryptenroll /dev/nvme0n1p3 SLOT TYPE 0 password 1 fido2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232486] Improvements for man ifcfg(5)
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1232486 https://bugzilla.suse.com/show_bug.cgi?id=1232486#c1 Tomáš Bažant <tbazant(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Assignee|fs(a)suse.com |marco.strigl(a)suse.com --- Comment #1 from Tomáš Bažant <tbazant(a)suse.com> --- Thank you for reporting this bug! It is being tracked and processed as part of our queue. Assigning to Marco Strigl as he seems to be the maintainer of the wicked package @Marco, hope you're the right assignee. If not, reassign accordingly please. -- You are receiving this mail because: You are on the CC list for the bug.

1 0