May 2021 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1186125] MicroOS snapshot 20210515 CoreDNS fails to resolve external addresses
by bugzilla_noreply＠suse.com 19 May '21

19 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1186125 https://bugzilla.suse.com/show_bug.cgi?id=1186125#c15 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka(a)suse.com Flags|needinfo?(mfilka(a)suse.com) |needinfo?(locilka(a)suse.com) --- Comment #15 from Stefan Schubert <schubi(a)suse.com> --- Created attachment 849477 --> https://bugzilla.suse.com/attachment.cgi?id=849477&action=edit y2log Thanks Knut. I have made a new run with Y2DEBUG=1 and it seems that the default value is taken, what is OK. But we need to enable the forwarding on MicroOS. Would it be OK to add an new entry in the skelcd-control for ipv4_ip_forward and ipv6_ip_forward in the network section ? It is quite urgent, so I could provide the regarding PRs. Lukas, what do you think about it ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186213] New: Replace mkinitrd with dracut
by bugzilla_noreply＠suse.com 18 May '21

18 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1186213 Bug ID: 1186213 Summary: Replace mkinitrd with dracut Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- transactional-update is calling mkinitrd, but that's deprecated and will be removed in the near future (see factory@ mailing list). We should replace mkinitd with dracut. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1186125] MicroOS snapshot 20210515 CoreDNS fails to resolve external addresses
by bugzilla_noreply＠suse.com 18 May '21

18 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1186125 Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kanderssen(a)suse.c | |om) | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186125] MicroOS snapshot 20210515 CoreDNS fails to resolve external addresses
by bugzilla_noreply＠suse.com 18 May '21

18 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1186125 https://bugzilla.suse.com/show_bug.cgi?id=1186125#c12 --- Comment #12 from Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> --- (In reply to Stefan Schubert from comment #10) > (In reply to Thorsten Kukuk from comment #6) > > (In reply to Anthony Rabbito from comment #5) > > > Would be interested in knowing the root cause of this as this hack breaks > > > Cilium pod networking if kubeadm service is restarted.. > > > > That's the root cause: > > > > * Applying /etc/sysctl.d/70-yast.conf ... > > net.ipv4.ip_forward = 0 > > net.ipv6.conf.all.forwarding = 0 > > * Applying /usr/lib/sysctl.d/90-kubeadm.conf ... > > net.ipv4.ip_forward = 1 > > > > > > YaST disables forwarding during installation... > > It seems that this is the default value and is intent: > > "is_secure" => !Security.Settings["net.ipv4.ip_forward"] > > > > > Question is, can we forbid YaST to disable forwarding? > > I cannot see a way here. Knut, Michal do you see an option here to set it to > true via some configuration file ? yast2-network also permits to enable or disable ipv4 and ipv6 forwarding. So, it was the security module or network who wrote the file? I guess it was network (it reminds me this other bug https://bugzilla.suse.com/show_bug.cgi?id=1151649). BTW, I would need logs to be sure. yast2-network should read sysctl settings taking intoto account the precedence, so if there is some sysctl.d file which enables it then it should be enabled but I guess it is not when it reads the config. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186125] MicroOS snapshot 20210515 CoreDNS fails to resolve external addresses
by bugzilla_noreply＠suse.com 18 May '21

18 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1186125 https://bugzilla.suse.com/show_bug.cgi?id=1186125#c10 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kanderssen(a)suse.com, | |mfilka(a)suse.com, | |schubi(a)suse.com Flags| |needinfo?(mfilka(a)suse.com), | |needinfo?(kanderssen(a)suse.c | |om) --- Comment #10 from Stefan Schubert <schubi(a)suse.com> --- (In reply to Thorsten Kukuk from comment #6) > (In reply to Anthony Rabbito from comment #5) > > Would be interested in knowing the root cause of this as this hack breaks > > Cilium pod networking if kubeadm service is restarted.. > > That's the root cause: > > * Applying /etc/sysctl.d/70-yast.conf ... > net.ipv4.ip_forward = 0 > net.ipv6.conf.all.forwarding = 0 > * Applying /usr/lib/sysctl.d/90-kubeadm.conf ... > net.ipv4.ip_forward = 1 > > > YaST disables forwarding during installation... It seems that this is the default value and is intent: "is_secure" => !Security.Settings["net.ipv4.ip_forward"] > > Question is, can we forbid YaST to disable forwarding? I cannot see a way here. Knut, Michal do you see an option here to set it to true via some configuration file ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186125] MicroOS snapshot 20210515 CoreDNS fails to resolve external addresses
by bugzilla_noreply＠suse.com 18 May '21

18 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1186125 https://bugzilla.suse.com/show_bug.cgi?id=1186125#c9 --- Comment #9 from Thorsten Kukuk <kukuk(a)suse.com> --- There is a difference in the behavior of systemd-sysctl and sysctl -a --system: sysctl -a --system does not only change net.ipv4.ip_forward and default, but also all net.ipv4.conf.<device>.forwarding = 1, so for all existing devices. systemd-sysctl does not touch existing devices. So systemd-sysctl will not adjust existing devices, that's why the "workaround" solves the problem: it also changes existing devices. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186125] MicroOS snapshot 20210515 CoreDNS fails to resolve external addresses
by bugzilla_noreply＠suse.com 18 May '21

18 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1186125 https://bugzilla.suse.com/show_bug.cgi?id=1186125#c8 --- Comment #8 from Thorsten Kukuk <kukuk(a)suse.com> --- If you run "sysctl -a --system", following values will be changed: -net.ipv4.conf.enp1s0.forwarding = 0 +net.ipv4.conf.enp1s0.forwarding = 1 -net.ipv4.conf.lo.forwarding = 0 +net.ipv4.conf.lo.forwarding = 1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186125] MicroOS snapshot 20210515 CoreDNS fails to resolve external addresses
by bugzilla_noreply＠suse.com 18 May '21

18 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1186125 https://bugzilla.suse.com/show_bug.cgi?id=1186125#c7 --- Comment #7 from Thorsten Kukuk <kukuk(a)suse.com> --- Big question is: what executes only 70-yast.conf without 90-kubeadm.conf? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186125] MicroOS snapshot 20210515 CoreDNS fails to resolve external addresses
by bugzilla_noreply＠suse.com 18 May '21

18 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1186125 https://bugzilla.suse.com/show_bug.cgi?id=1186125#c6 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #6 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Anthony Rabbito from comment #5) > Would be interested in knowing the root cause of this as this hack breaks > Cilium pod networking if kubeadm service is restarted.. That's the root cause: * Applying /etc/sysctl.d/70-yast.conf ... net.ipv4.ip_forward = 0 net.ipv6.conf.all.forwarding = 0 * Applying /usr/lib/sysctl.d/90-kubeadm.conf ... net.ipv4.ip_forward = 1 YaST disables forwarding during installation... Question is, can we forbid YaST to disable forwarding? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186127] New: selinux-ready error
by bugzilla_noreply＠suse.com 17 May '21

17 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186127 Bug ID: 1186127 Summary: selinux-ready error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- SELinux works fine but # selinux-ready Start checking your system if it is selinux-ready or not: check_dir: OK. /sys/fs/selinux exists. check_filesystem: OK. Filesystem 'securityfs' exists. check_filesystem: OK. Filesystem 'selinuxfs' exists. check_boot: Assuming GRUB2 as bootloader. check_boot: OK. Current kernel 'vmlinuz-5.12.3-1-default' has boot-parameters 'security=selinux selinux=1' check_boot: OK. Other kernels with correct parameters: /usr/sbin/selinux-ready: Zeile 140: [: Zu viele Argumente. check_mkinitrd: ERR. Your initrd seems not to mount /proc of the root filesystem during boot and/or load_policy is missing, this may be a reason for SELinux not working. check_packages: ERR. Package 'restorecond' not installed, please run 'zypper in restorecond' as root check_config: OK. Config file seems to be there. check_config: OK. SELINUX is set to 'enforcing'. check_pam: OK. Your PAM configuration seems to be correct. check_runlevel: ERR. please enable restorecond with systemctl enable restorecond.service. -- You are receiving this mail because: You are the assignee for the bug.

1 0