August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1228772] Expert partitioner: enable BTRFS snapshots as default action
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228772 https://bugzilla.suse.com/show_bug.cgi?id=1228772#c11 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers(a)suse.de |forgotten_kWxJsf0s20(a)user.n | |et --- Comment #11 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- Assigning this usability improvement to yast-community (our list of tasks for people looking how to start contributing). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228772] Expert partitioner: enable BTRFS snapshots as default action
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228772 https://bugzilla.suse.com/show_bug.cgi?id=1228772#c10 --- Comment #10 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #4) > > When I have time, I will check in the code the conditions to show that > checkbox enabled/disabled by default in that particular situation. I see no code specific to this particular case. Since the partition is not being created from scratch or configured using "import mount points", this fallbacks to the default for editing any existing partition. And that default handling does not include any logic to try to ensure snapshots are used. As commented on the other bug#1228365, this would have been solved if we would had ever have time to implement something similar to https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui/idea… but I don't see that happening in the near future (due to other priorities). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228742] [SELinux] denied avc when xen VM is started via virtmgr-2
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228742 https://bugzilla.suse.com/show_bug.cgi?id=1228742#c1 --- Comment #1 from Cathy Hu <cathy.hu(a)suse.com> --- just a quick update, i am still working on reproducing the issue, could take a while since we have a couple other high prio bugs, sorry for the delay -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228772] Expert partitioner: enable BTRFS snapshots as default action
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228772 https://bugzilla.suse.com/show_bug.cgi?id=1228772#c9 --- Comment #9 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Lassi Väätämöinen from comment #8) > > if there's a case where no checkbox at all shows, that sounds even worse to > me. Not really. The situation I described in which there is no snapshots checkbox is that in which the user is installing on top of an existing Btrfs file-system WITHOUT reformatting it. In that situation, snapshots cannot be configured because the file-system is not being created from scratch. In any case, that's an unsupported scenario and the user will see a pop-up stating the following: "You chose to install onto an existing partition that will not be formatted. YaST cannot guarantee your installation will succeed, particularly if this is an existing Btrfs partition". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228808] grub error: ../../grub-core/script/function.c:119:can't find command `None'. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found.
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228808 https://bugzilla.suse.com/show_bug.cgi?id=1228808#c8 Marcus Schäfer <marcus.schaefer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Assignee|bootloader-maintainers@suse |marcus.schaefer(a)suse.com |.de | --- Comment #8 from Marcus Schäfer <marcus.schaefer(a)suse.com> --- Hi, thanks much for the info, 9.24.43 stone age :) and yes this is clearly a kiwi bug in that version. I'll take it -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228808] grub error: ../../grub-core/script/function.c:119:can't find command `None'. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found.
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228808 https://bugzilla.suse.com/show_bug.cgi?id=1228808#c7 Gary Ching-Pang Lin <glin(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(vinaygahlout@goog | |le.com) | --- Comment #7 from Gary Ching-Pang Lin <glin(a)suse.com> --- (In reply to Marcus Schäfer from comment #6) > Hmm, the current code in kiwi does this > > ``` > if self.serial_line_setup and \ > ('serial' in self.terminal_input or 'serial' in self.terminal_output): > grub_default_entries['GRUB_SERIAL_COMMAND'] = '"{0}"'.format( > self.serial_line_setup > ) > ``` > > So if self.serial_line_setup is a None type or empty string it will not be > handled. I also checked the integration test that we have for this case and > it > does not include any GRUB_SERIAL_COMMAND in /etc/default/grub > > - which version of kiwi are we talking about exactly ? Both openSUSE Leap 15.5 and 15.6 are using the kiwi inherited from SLE-15-SP1:Update, and the version is 9.24.43. > - can I see the kiwi build log file for this build, it should show entries > like > > [ 80s] [ INFO ]: 02:16:05 | --> GRUB_TERMINAL_INPUT:"serial" > ... > and I would expect GRUB_SERIAL_COMMAND:"None" if kiwi did something wrong > Per the result of the command: $ osc rbl Cloud:Images:Leap_15.6 openSUSE-Leap-15.6-Guests -M GCE images x86_64 ... [ 132s] [ INFO ]: 09:10:51 | --> GRUB_SERIAL_COMMAND:"None" [ 132s] [ INFO ]: 09:10:51 | --> GRUB_TERMINAL_INPUT:"serial" [ 132s] [ INFO ]: 09:10:51 | --> GRUB_TERMINAL_OUTPUT:"serial" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228808] grub error: ../../grub-core/script/function.c:119:can't find command `None'. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found.
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228808 https://bugzilla.suse.com/show_bug.cgi?id=1228808#c6 Marcus Schäfer <marcus.schaefer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(vinaygahlout@goog | |le.com) CC| |vinaygahlout(a)google.com --- Comment #6 from Marcus Schäfer <marcus.schaefer(a)suse.com> --- Hmm, the current code in kiwi does this ``` if self.serial_line_setup and \ ('serial' in self.terminal_input or 'serial' in self.terminal_output): grub_default_entries['GRUB_SERIAL_COMMAND'] = '"{0}"'.format( self.serial_line_setup ) ``` So if self.serial_line_setup is a None type or empty string it will not be handled. I also checked the integration test that we have for this case and it does not include any GRUB_SERIAL_COMMAND in /etc/default/grub - which version of kiwi are we talking about exactly ? - can I see the kiwi build log file for this build, it should show entries like [ 80s] [ INFO ]: 02:16:05 | --> GRUB_TERMINAL_INPUT:"serial" ... and I would expect GRUB_SERIAL_COMMAND:"None" if kiwi did something wrong Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228831] SELinux sshd policy missing VSOCK support
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228831 https://bugzilla.suse.com/show_bug.cgi?id=1228831#c14 --- Comment #14 from Johannes Segitz <jsegitz(a)suse.com> --- I know that they are for some other program, but if they occur then the vsock support doesn't work. I think there's some ebpf logic that's needed and currently blocked. No, I use a default Tumbleweed installation. I'll set this up and test it again. ATM there's no better interface, that's why I used it for now -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228957] New: Support cockpit-file-sharing
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228957 Bug ID: 1228957 Summary: Support cockpit-file-sharing Classification: openSUSE Product: openSUSE Distribution Version: Leap 16.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cockpit Assignee: Cockpit-bugs(a)suse.de Reporter: egotthold(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The Fedora documentation mentions the file sharing plugin for Cockpit. It would be nice if we could ship that too as it automates the common task of setting up NFS and Samba Shares for administrators. GitHub: https://github.com/45Drives/cockpit-file-sharing Fedora Docs: https://docs.stg.fedoraproject.org/en-US/fedora-server/services/filesharing… P.S.: I just selected Leap 16.0 but it of course applies to any version of our OS. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1228383] 'No free space in /boot/efi for new kernel' error during dist-upgrade
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228383 https://bugzilla.suse.com/show_bug.cgi?id=1228383#c4 Alberto Planas Dominguez <aplanas(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(aplanas(a)suse.com) | --- Comment #4 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Michael Chang from comment #3) > (In reply to Alberto Planas Dominguez from comment #2) > > The main bug I think is why sdbootutil is installed. It should not. > > The reporter seems to have trouble in removing sdbootutil [1]. It was > re-installed again in later updates. > > [1] > https://forums.opensuse.org/t/no-free-space-in-boot-efi-for-new-kernel-erro… > during-update/177234/23 Thanks! IIUC is because systemd-boot was installed. > > pbl is not used in suse-module-tools, so the criteria of how to behave is if > > sdbootutil is present or not: > > As long as grub2 is still using pbl, which doesn't seem to follow the same > critia in suse-module-tools, they would keep stepping on each other's toe. They should not interfere ... I think. sdbootutil is a 'temporary' (yeah, I know) replacement for bootctl. Calling it is an opt-in, and its presence is an indicative of the features of your system (that part is the one that needs to be re-evaluated). If grub is using pbl it should be fine, this means that the system is not BLS. > Let's check with Steffen how sdbootutil is determined in pbl in case this > would be an issue. pbl is gaining features in this direction now. For example, it completed the support for systemd-boot and recognize now grub2-bls. There are some issues, like it still depends on the /boot links to detect the default kernel, instead of checking with bootctl / sdbootutil to find the active and default entry, to get the kernel and initrd paths from it (this will cause bugs in kdump). Still WIP. -- You are receiving this mail because: You are on the CC list for the bug.

1 0