February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1207917] installation fails with static hostname (was: ip address)
by bugzilla_noreply＠suse.com 06 Feb '23

06 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207917 https://bugzilla.suse.com/show_bug.cgi?id=1207917#c8 Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kanderssen(a)suse.com --- Comment #8 from Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> --- (In reply to Giacomo Comes from comment #7) > Stefan, > I'm perfectly aware how to use static hostnames, DHCP, LDAP NIS, DNS, etc. > For the bug report I modified, during the installation, the single setting > that would cause the crash, even if it does not make sense to use it alone. > The initial bug report was about the ip address because I was using a full > static ip configuration with static hostnames etc. But later I realized that > the ip itself was not the issue and I went with the single change that would > trigger the bug (to make your life easier essentially). As commented by HuHa, the problem is faced when sysctl yast config file is written during the installation and copied to the target system and should be fixed with yast2-network-4.5.13 (in the logs I can see that the Leap 15.5 release is still using yast2-network-4.5.12). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207836] container-selinux conflicting with rke2-selinux and k3s-selinux (MicroOS)
by bugzilla_noreply＠suse.com 06 Feb '23

06 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207836 https://bugzilla.suse.com/show_bug.cgi?id=1207836#c2 Johannes Segitz <jsegitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsegitz(a)suse.com --- Comment #2 from Johannes Segitz <jsegitz(a)suse.com> --- This needs to be fixed in the downstream modules that build on top of container-selinux -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207917] New: installation fails with static ip address
by bugzilla_noreply＠suse.com 06 Feb '23

06 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207917 Bug ID: 1207917 Summary: installation fails with static ip address Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: comes(a)naic.edu QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Testing 15.5 in a VM. If I set the network to use DHCP, the installation is successful, if I set static ip address the installation fails. Tested with KDE and Server system role. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1207940] [Build 20230205] openssl-3: tpm unable to enable public key encoding
by bugzilla_noreply＠suse.com 06 Feb '23

06 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207940 https://bugzilla.suse.com/show_bug.cgi?id=1207940#c1 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |otto.hollmann(a)suse.com, | |pmonrealgonzalez(a)suse.com --- Comment #1 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- I have submitted the recently released update to version 1.2.0, just in case this is solved upstream, here: * https://build.opensuse.org/request/show/1063432 I'm adding Otto in CC also. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207945] New: [doc] 6.9 Importing TLS server certificates and keys - invalid command example listed
by bugzilla_noreply＠suse.com 06 Feb '23

06 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207945 Bug ID: 1207945 Summary: [doc] 6.9 Importing TLS server certificates and keys - invalid command example listed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation Assignee: fs(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: fs(a)suse.com Found By: --- Blocker: --- In the chapter mentioned (https://doc.opensuse.org/documentation/leap/security/html/book-security/cha…) the following command is listed for importing certificates and keys: sudo dsctl INSTANCE_NAME tls remove-cert Self-Signed-CA pk12util -i SERVER.p12 \ -d /etc/dirsrv/slapd-INSTANCE-NAME/cert9.db This suggests that pk12util is a parameter of dsctl, in fact it is a separate command and should be like this: sudo dsctl INSTANCE_NAME tls remove-cert Self-Signed-CA pk12util -i SERVER.p12 -d /etc/dirsrv/slapd-INSTANCE-NAME/cert9.db or be displayed like this sudo dsctl INSTANCE_NAME tls remove-cert Self-Signed-CA; \ pk12util -i SERVER.p12 -d /etc/dirsrv/slapd-INSTANCE-NAME/cert9.db -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207917] installation fails with static hostname (was: ip address)
by bugzilla_noreply＠suse.com 06 Feb '23

06 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207917 https://bugzilla.suse.com/show_bug.cgi?id=1207917#c6 --- Comment #6 from Stefan Hundhammer <shundhammer(a)suse.com> --- As for that static hostname: This is a bit misleading, mostly for historical reasons. Back in the olden days (in the last millenium), you had to configure your hostname manually in /etc/hostname, and you had to carefully maintain your /etc/hosts file. Then the "hostname" command came along, and NIS and LDAP, and DHCP. Since almost all home networks and most small business networks use DHCP these days, maintaining the hostnames on the DHCP server (typically the Internet router) has become the norm; hence the default is to change the hostname via DHCP once the network services are started. So the most useful settings are to either leave it to the DHCP server (and configure the hostnames there) and leave the static hostname alone, or to use a manually set static IP address AND a static hostname. Mixing both may end up in surprising results. Also notice that it's not very useful to configure the hostname statically only on one machine; if you want to make any use of it, you also need to make it known to the other machines in the network, otherwise you have to "ssh" to an IP address which negates the whole purpose of a hostname. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207943] New: btrfs i/o error on Alderlake
by bugzilla_noreply＠suse.com 06 Feb '23

06 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207943 Bug ID: 1207943 Summary: btrfs i/o error on Alderlake Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kokeko(a)mac.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- HI I update my leap 15.4 transactional-server from Skylake(6th core)to Alderlake(12th core) nuc. nuc12wshi5 Intel Core i5-1240P 32GB DDR4 memory After update many btrfs i/o error happen on console I cannot operate anything. I try to following method. Reset PC grub menu->advanced->set kernel recovery mode after it success boot. but Regenerate initrd and grub.cfg, same situation. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207917] installation fails with static hostname (was: ip address)
by bugzilla_noreply＠suse.com 06 Feb '23

06 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207917 https://bugzilla.suse.com/show_bug.cgi?id=1207917#c5 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Stefan Hundhammer <shundhammer(a)suse.com> --- But this other problem is a hard failure: 2023-02-06 01:37:48 <3> 192-231-93-158(4093) [Ruby] yast/wfm.rb(handle_exception):271 Client /mounts/mp_0001/usr/share/YaST2/clients/save_network.rb failed with 'undefined method `dirname' for "/mnt/etc/sysctl.d/70-yast.conf":String' (NoMethodError). But the good news is that it's already fixed. https://github.com/yast/yast-network/pull/1320 (Duplicate of bug #1207382) Pity, no trip to Arecibo. ;-) *** This bug has been marked as a duplicate of bug 1207382 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207382] [Build 20230121] yast2-network: undefined method dirname
by bugzilla_noreply＠suse.com 06 Feb '23

06 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207382 https://bugzilla.suse.com/show_bug.cgi?id=1207382#c9 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |comes(a)naic.edu --- Comment #9 from Stefan Hundhammer <shundhammer(a)suse.com> --- *** Bug 1207917 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 1207917] installation fails with static hostname (was: ip address)
by bugzilla_noreply＠suse.com 06 Feb '23

06 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207917 https://bugzilla.suse.com/show_bug.cgi?id=1207917#c4 --- Comment #4 from Stefan Hundhammer <shundhammer(a)suse.com> --- AFAICS you set a static hostname, but you also left the default for "Set hostname via DHCP" to the default "any". That would explain why you did get your manually set hostname for a short while, but as soon as there was any operation on that interface, it was reset. -- You are receiving this mail because: You are on the CC list for the bug.

1 0