May 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1185625] transactional-update: /etc has wrong selinux label
by bugzilla_noreply＠suse.com 10 May '21

10 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185625 http://bugzilla.opensuse.org/show_bug.cgi?id=1185625#c6 --- Comment #6 from G.M. Venekamp <gm.venekamp(a)quicknet.nl> --- I seem unable to resolve the dependencies when I try to install transactional-update from https://download.opensuse.org/repositories/home:/lnussel:/tu/openSUSE_Facto… # zypper lr -P # | Alias | Name | Enabled | GPG Check | Refresh | Priority --+-----------------------------+--------------------------------------------------------------------+---------+-----------+---------+--------- 1 | home_lnussel_tu | Branch project for package transactional-update (openSUSE_Factory) | Yes | (r ) Yes | Yes | 80 2 | openSUSE-MicroOS-20210507-0 | openSUSE-MicroOS-20210507-0 | No | ---- | ---- | 99 3 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | 99 4 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes | 99 5 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes | 99 6 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | 99 7 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | 99 # zypper refresh --repo 1 Repository 'Branch project for package transactional-update (openSUSE_Factory)' is up to date. Specified repositories have been refreshed. # transactional-update pkg install --repo 1 --force transactional-update Checking for newer version. transactional-update 3.3.0 started Options: pkg install --repo 1 --force transactional-update Separate /var detected. WARNING: You are creating a snapshot from a different base (1) than the current default snapshot (4). If you want to continue a previous snapshot use the --continue option, otherwise the previous changes will be discarded. 2021-05-10 16:41:26 tukit 3.3.0 started 2021-05-10 16:41:26 Options: -c1 open 2021-05-10 16:41:26 Using snapshot 1 as base for new snapshot 5. 2021-05-10 16:41:26 No previous snapshot to sync with - skipping ID: 5 2021-05-10 16:41:26 Transaction completed. Calling zypper install 2021-05-10 16:41:27 tukit 3.3.0 started 2021-05-10 16:41:27 Options: callext 5 zypper -R {} install --repo 1 --force transactional-update 2021-05-10 16:41:27 Executing `zypper -R /tmp/transactional-update-4e0Buo install --repo 1 --force transactional-update`: Loading repository data... Reading installed packages... Forcing installation of 'transactional-update-v3.3.0+git20210507.413301b-6.1.x86_64' from repository 'Branch project for package transactional-update (openSUSE_Factory)'. Resolving package dependencies... Problem: dracut-transactional-update-3.3.0-1.2.noarch conflicts with transactional-update < 3.0.0 provided by transactional-update-v3.3.0+git20210507.413301b-6.1.x86_64 Solution 1: do not install transactional-update-v3.3.0+git20210507.413301b-6.1.x86_64 Choose the above solution using '1' or cancel using 'c' [1/c/d/?] (c): c 2021-05-10 16:41:29 Application returned with exit status 4. ERROR: zypper install on /.snapshots/5/snapshot failed with exit code 4! Removing snapshot #5... 2021-05-10 16:41:29 tukit 3.3.0 started 2021-05-10 16:41:29 Options: abort 5 2021-05-10 16:41:29 Discarding snapshot 5. 2021-05-10 16:41:29 Transaction completed. transactional-update finished -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185801] New: Kubelet/CRI-O/CA-Advisor is not reporting memory
by bugzilla_noreply＠suse.com 10 May '21

10 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185801 Bug ID: 1185801 Summary: Kubelet/CRI-O/CA-Advisor is not reporting memory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE MicroOS Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: hello(a)anthonyrabbito.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Posting a bug here as I opened tickets in several places and it doesn't seem like anyone is reproducing this except for Kubic users. https://github.com/kubernetes-sigs/metrics-server/issues/738 https://github.com/cri-o/cri-o/issues/4867 https://github.com/kubernetes/kubeadm/issues/2470 https://github.com/kubernetes/kubernetes/issues/101786 It seems as though some default CRI-O values may need to be bumped. `kubectl get --raw /api/v1/nodes/nyc1-master-1/proxy/stats/summary` ``` { "node": { "nodeName": "nyc1-master-1", "systemContainers": [ { "name": "kubelet", "startTime": "2021-05-06T01:33:03Z", "cpu": { "time": "2021-05-06T21:53:29Z", "usageNanoCores": 0, "usageCoreNanoSeconds": 0 }, "memory": { "time": "2021-05-06T21:53:29Z", "availableBytes": 4108148736, "usageBytes": 0, "workingSetBytes": 0, "rssBytes": 0, "pageFaults": 0, "majorPageFaults": 0 } }, { "name": "pods", "startTime": "2021-05-06T01:33:03Z", "cpu": { "time": "2021-05-06T21:53:31Z", "usageNanoCores": 194810666, "usageCoreNanoSeconds": 15374004459000 }, "memory": { "time": "2021-05-06T21:53:31Z", "availableBytes": 1932058624, "usageBytes": 2959253504, "workingSetBytes": 2176090112, "rssBytes": 1329647616, "pageFaults": 1091871, "majorPageFaults": 33 } } ], ``` Nodes do not report memory -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1172259] Feature Request - monitoring-plugins-zypper to support transactional server
by bugzilla_noreply＠suse.com 10 May '21

10 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1172259 https://bugzilla.suse.com/show_bug.cgi?id=1172259#c3 Lars Vogdt <lars.vogdt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Lars Vogdt <lars.vogdt(a)suse.com> --- Coming back to this after some discussions. The recommendation is (and stays) to install all official updates to get a supported system state. Especially security updates should be installed as soon as possible. If an update breaks the system, it should be clarified and fixed. Either on the packaging or on the machine side. check_zypper only displays what zypper reports. If there were broken updates, that resulted in an automatic roll-back, zypper should be able to report this. In this case, we can adjust check_zypper to display this information as well. As far as I know at the moment, there is only support for a manual rollback implemented in zypper. If a roll-back (manually or automated) happened, a user should still see if there are pending updates. Silently hiding (important) updates automatically just because their installation somehow failed is not seen as a good practice. So check_zypper reporting pending updates, even if an update failed, is not only accepted but recommended. Users can always decide on their own to ignore specific updates by manually (or via configuration management) adding packages or patches to a file. (Same applies to zypper with adding 'untouchable' packages or patches to the zypper lock file.) Anyway: I hope I explained my reason to finally deny this feature request. If ever, zypper itself should include some information about broken package (updates) in it's output. This could be used in check_zypper to provide this information also to the user. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177548] With monitoring-plugins-jitsi-icinga2-templates installed icinga2 does not start
by bugzilla_noreply＠suse.com 10 May '21

10 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1177548 https://bugzilla.suse.com/show_bug.cgi?id=1177548#c1 Lars Vogdt <lars.vogdt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |lars.vogdt(a)suse.com Resolution|--- |FIXED --- Comment #1 from Lars Vogdt <lars.vogdt(a)suse.com> --- This was clearly a packaging bug. Thanks to Dirk Stoecker for identifying and fixing this. Fixed package is already available in server:monitoring since Oct 21. Only cleaning up/closing old bugs here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185845] Add dtb-apple for kernel 5.13
by bugzilla_noreply＠suse.com 10 May '21

10 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185845 Dirk Mueller <dmueller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185845] Add dtb-apple for kernel 5.13
by bugzilla_noreply＠suse.com 10 May '21

10 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185845 https://bugzilla.suse.com/show_bug.cgi?id=1185845#c1 --- Comment #1 from Dirk Mueller <dmueller(a)suse.com> --- pushed to users/dmueller/master/for-next - however we do not have 5.13-rc1 yet in master. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185794] New: named fails to start
by bugzilla_noreply＠suse.com 10 May '21

10 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185794 Bug ID: 1185794 Summary: named fails to start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: robert.koktan(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Updated Tumbleweed this morning to 20210505, bind-9.16.12-2.1.x86_64, now it fails to start, and what's really weird is it's trying to start from /etc/systemd/system/ instead of /usr/lib/systemd/system/... # systemctl status named.service �� named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/etc/systemd/system/named.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2021-05-07 13:56:31 EDT; 5min ago CPU: 783us May 07 13:56:31 rkoktan-w541 systemd[1]: Starting Berkeley Internet Name Domain (DNS)... May 07 13:56:31 rkoktan-w541 systemd[1210]: named.service: Failed to execute command: No such file or directory May 07 13:56:31 rkoktan-w541 systemd[1210]: named.service: Failed at step EXEC spawning /usr/sbin/named.init: No such file or directory May 07 13:56:31 rkoktan-w541 systemd[1]: named.service: Control process exited, code=exited, status=203/EXEC May 07 13:56:31 rkoktan-w541 systemd[1]: named.service: Failed with result 'exit-code'. May 07 13:56:31 rkoktan-w541 systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1185855] New: dkim filter extension in Kmail fails to work correctly with spamassasin (spamd daemon)
by bugzilla_noreply＠suse.com 10 May '21

10 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185855 Bug ID: 1185855 Summary: dkim filter extension in Kmail fails to work correctly with spamassasin (spamd daemon) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Go to the 5.17.0 version of kmail. The following applies when activating dkim extension in kmail, provided you are using spamd daemon with spamassasin (I did not verify the scripted version). The new mails will be correctly identified as dkim compliant, or not. Fair enough, this is the purpose. BUT, the usability is greatly reduced in case you have old mail inside a local folder or even a imap account with old mail. The old mail (as at the time there was no dkim will ALL be signed as spam and put into the trash. Once aware of it you may the instinct to select all messages and sign them as "Ham". Then to replace them into the inbox. Unfortunately, after few minutes you find them again signed as spam in the trash. So: DKIM check estension works for new DKIM compliant mail. When no DKIM is present mail i set as spam. But when mail has been wrongly classified as spam, then even if manually restored and then signed explicitly as HAM (I refer particularly to older so to say "historical mail") this is not honored by spamd daemon and the mail is trashed again. The described behavior stops immediately when the DKIM verification plugin is deactivated in the extension. What the software should do: verify new mail on DKIM compliance. What the software should also do: honor the manual settings as "no spam / ham, once the user provides this information. Any further check of DKIM of such a message should NOT trigger trashing as spam. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185799] New: /etc/os-release shows wrong version
by bugzilla_noreply＠suse.com 10 May '21

10 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185799 Bug ID: 1185799 Summary: /etc/os-release shows wrong version Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE MicroOS Status: NEW Severity: Minor Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: gm.venekamp(a)quicknet.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It seems that the /etc/os-release does not show the correct version. I have downloaded the latest version of MicroOS today (2021-05-09), which should have been 20210507. This is what /etc/os-release shows me: # cat /usr/lib/os-release NAME="openSUSE MicroOS" # VERSION="20210430" ID="opensuse-microos" ID_LIKE="suse opensuse opensuse-tumbleweed" VERSION_ID="20210430" PRETTY_NAME="openSUSE MicroOS" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:microos:20210430" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:MicroOS" LOGO="distributor-logo" The mounted iso image shows the following: > cat /mnt/media.1/products / openSUSE-MicroOS 20210507-0 Regards, Gerben -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1185851] New: rsync.opensuse.org missing Leap 15.3
by bugzilla_noreply＠suse.com 10 May '21

10 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185851 Bug ID: 1185851 Summary: rsync.opensuse.org missing Leap 15.3 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: ralf.koelmel(a)kit.edu QA Contact: adrian.schroeter(a)suse.com Found By: --- Blocker: --- Created attachment 849202 --> http://bugzilla.opensuse.org/attachment.cgi?id=849202&action=edit list leap versions on rsync.opensuse.org Leap 15.3 directories are not available on the rsync-server rsync.opensuse.org, although mirror servers (e.g. ftp.halifax.rwth-aachen.de) are providing these over rsync. -- You are receiving this mail because: You are on the CC list for the bug.

1 1