July 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1184399] New: purge-kernels.service might conflict with other background services using zypper as well
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184399 Bug ID: 1184399 Summary: purge-kernels.service might conflict with other background services using zypper as well Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: marius.kittler(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I observed the following problem on a Leap 15.2 system (used as openQA worker): ``` martchus@openqaworker3:/srv/salt> sudo systemctl status purge-kernels.service purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2021-03-15 06:51:54 CET; 1 day 4h ago Main PID: 1166 (code=exited, status=7) Mar 15 06:51:36 openqaworker3 systemd[1]: Starting Purge old kernels... Mar 15 06:51:54 openqaworker3 zypper[1166]: System management is locked by the application with pid 1286 (zypper). Mar 15 06:51:54 openqaworker3 zypper[1166]: Close this application before trying again. Mar 15 06:51:54 openqaworker3 systemd[1]: purge-kernels.service: Main process exited, code=exited, status=7/NOTRUNNING Mar 15 06:51:54 openqaworker3 systemd[1]: Failed to start Purge old kernels. Mar 15 06:51:54 openqaworker3 systemd[1]: purge-kernels.service: Unit entered failed state. Mar 15 06:51:54 openqaworker3 systemd[1]: purge-kernels.service: Failed with result 'exit-code'. ``` Maybe this can be improved, e.g. by adding a retry? Unfortunately I don't know what the conflicting process was because I only found out about the problem when it had already terminated. Related openQA project ticket: https://progress.opensuse.org/issues/90170 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1187952] New: sle-module-certifications-release not found
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187952 Bug ID: 1187952 Summary: sle-module-certifications-release not found Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: kim.frederiksen(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Field Engineer Blocker: --- The repodata contains information about the "sle-module-certifications-release" rpms but these are not available in the repository. Looks like the package directories were touched on Jun 8th but the metadata is still from May 24th. Issue was found when trying to use a SLES15 SP2 RMT to mirror openSUSE Leap 15.3, the following rpms shows "HTTP request failed with code 404": sle-module-certifications-release-15.3-47.1.x86_64.rpm sle-module-certifications-release-15.3-47.1.aarch64.rpm sle-module-certifications-release-15.3-47.1.ppc64le.rpm sle-module-certifications-release-15.3-47.1.s390x.rpm -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1187329] Kernel Panic loading initial ramdisk with kernel version 5.3.18-57.3 and pm80xx module
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187329 https://bugzilla.suse.com/show_bug.cgi?id=1187329#c6 Lee Duncan <lduncan(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dave(a)redmoor.org. | |uk) --- Comment #6 from Lee Duncan <lduncan(a)suse.com> --- Even with the panic output, I have no idea what the issue is. I looked over the pm80* patches I added for SLE-15-SP3, and none of the 32 commits looks suspect, on the surface. Can you try passing in the "logging_level" parameter to pm80xx? I believe it's something like "pm80xx.logging_level=4095" on the boot command line. I _think_ this will work, because it seems like you are already accessing the disc by the time this panic occurs, and the panic is in the pm80xx module. Lastly, I'm not clear on which version of Leap worked and which one didn't. I am checking on SLES 15.3 (same kernel), and it has 5.3.18-57-default. You said that "5.3.18-lp152.75" worked? Where did that version come from? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187018] [systemd248] various yast modules failing test suite
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187018 https://bugzilla.suse.com/show_bug.cgi?id=1187018#c13 --- Comment #13 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2021:2235-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1187018 CVE References: JIRA References: Sources used: SUSE MicroOS 5.0 (src): yast2-4.2.94-3.30.1 SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): yast2-4.2.94-3.30.1 SUSE Linux Enterprise Installer 15-SP2 (src): yast2-4.2.94-3.30.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186786] lxd exec don't work
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1186786 https://bugzilla.suse.com/show_bug.cgi?id=1186786#c8 --- Comment #8 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2021:0957-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1186786,1186906 CVE References: JIRA References: Sources used: openSUSE Leap 15.2 (src): lxd-4.15-lp152.2.38.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084742] Multiple CIFS mounts produce significant I/O anomalies under kernel versions 4.13, 4.14 and 4.15
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1084742 https://bugzilla.suse.com/show_bug.cgi?id=1084742#c2 Aurelien Aptel <aaptel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Aurelien Aptel <aaptel(a)suse.com> --- closing -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187981] New: VUL-1: CVE-2020-36401: mruby: double free in mrb_default_allocf()
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187981 Bug ID: 1187981 Summary: VUL-1: CVE-2020-36401: mruby: double free in mrb_default_allocf() Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/303345/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: rpm(a)fthiessen.de Reporter: rfrohl(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2020-36401 mruby 2.1.2 has a double free in mrb_default_allocf (called from mrb_free and obj_free). References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36401 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=23801 https://github.com/mruby/mruby/commit/97319697c8f9f6ff27b32589947e1918e3015… https://github.com/google/oss-fuzz-vulns/blob/main/vulns/mruby/OSV-2020-744… http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36401 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1185261] UEFI Boot fail after standard update - could not create MoklistXRT, import_mok_state() failed: Out of Resources
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1185261 Mischa Salle <mischa.salle(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mischa.salle(a)gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180388] New: Removing samba-client results in "Failed to disable unit: Unit file cifs.service does not exist."
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1180388 Bug ID: 1180388 Summary: Removing samba-client results in "Failed to disable unit: Unit file cifs.service does not exist." Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: gp(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- I just removed the samba-client package on a current Tumbleweed system, and noted... # zypper rm --clean-deps samba{,-client,-python*} The following 5 packages are going to be REMOVED: liburing1 nautilus-share samba samba-client samba-python3 5 packages to remove. After the operation, 24.9 MiB will be freed. (1/5) Removing nautilus-share-0.7.3-16.3.x86_64 ...[done] (2/5) Removing samba-python3-4.13.2+git.176.0a5e55b510c-1.1.x86_64 ...[done] (3/5) Removing samba-4.13.2+git.176.0a5e55b510c-1.1.x86_64 ...[done] (4/5) Removing samba-client-4.13.2+git.176.0a5e55b510c-1.1.x86_64 ...[done] ...the following error/warning: Additional rpm output: Failed to disable unit: Unit file cifs.service does not exist. Failed to stop cifs.service: Unit cifs.service not loaded. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1177182] Don't use DES as default password encryption
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1177182 http://bugzilla.opensuse.org/show_bug.cgi?id=1177182#c3 Jan Engelhardt <jengelh(a)inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh(a)inai.de --- Comment #3 from Jan Engelhardt <jengelh(a)inai.de> --- Can't you just patch /shadow/lib/getdef.c:88 and replace {"ENCRYPT_METHOD", NULL} by {"ENCRYPT_METHOD", "SHA512"}? -- You are receiving this mail because: You are on the CC list for the bug.

1 0