July 2021 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1188075] New: motd displayed twice on screen
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188075 Bug ID: 1188075 Summary: motd displayed twice on screen 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: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 850815 --> http://bugzilla.opensuse.org/attachment.cgi?id=850815&action=edit Screenshot of the login screen, displaying the motd twice Hi, I've notices that on a fresh MicroOS installation, the motd is displayed twice. See the attached screenshot. # Reproducer 1. Edit /etc/motd (add anything) 2. Login via the normal login terminal After the password, the motd is displayed twice -- You are receiving this mail because: You are the assignee for the bug.

1 0

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 04 Jul '21

04 Jul '21

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! security enhancement: no setuid -> http://bugzilla.suse.com/show_bug.cgi?id=1171174 live-add-yast-repos: uses openSUSE-release -> http://bugzilla.suse.com/show_bug.cgi?id=1172100 transactional-update: warn about reboot etc. -> http://bugzilla.suse.com/show_bug.cgi?id=1173261 transactional-update: Notification on failing update -> http://bugzilla.suse.com/show_bug.cgi?id=1176882 [Build 20210128] openQA test fails in journal_check -> http://bugzilla.suse.com/show_bug.cgi?id=1181547 transactional server role has very inconsistent package selection (TW, SLE, Leap) -> http://bugzilla.suse.com/show_bug.cgi?id=1183582 Opening polari flatpak crashes packagekitd and makes gnome go back to login screen -> http://bugzilla.suse.com/show_bug.cgi?id=1184411 ignition doesn't reset firstboot -> http://bugzilla.suse.com/show_bug.cgi?id=1185461 kdump fails on microos -> http://bugzilla.suse.com/show_bug.cgi?id=1185463 Impossible to trigger PackageKit offline update on MicroOS -> http://bugzilla.suse.com/show_bug.cgi?id=1185647 Kubelet/CRI-O/CA-Advisor is not reporting memory -> http://bugzilla.suse.com/show_bug.cgi?id=1185801 selinux-ready error -> http://bugzilla.suse.com/show_bug.cgi?id=1186127 SElinux is blocking podman socket access to /var/run/podman/podman.sock -> http://bugzilla.suse.com/show_bug.cgi?id=1186158 snapper cleanup: Deleting snapshot failed. -> http://bugzilla.suse.com/show_bug.cgi?id=1186943 virtlogd cannot read token due to SElinux -> http://bugzilla.suse.com/show_bug.cgi?id=1187219 Snapshoot unusable (and "reverted") after updates, when SELinux enabled -> http://bugzilla.suse.com/show_bug.cgi?id=1187462

1 0

[Bug 1187897] New: Running kubelet1.21 on MicroOS Kubic crashes with Bus error
by bugzilla_noreply＠suse.com 01 Jul '21

01 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187897 Bug ID: 1187897 Summary: Running kubelet1.21 on MicroOS Kubic crashes with Bus error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: dom(a)capture.blue QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0 Build Identifier: When I try to run `kubelet --version` (or with any flags) I get: ``` Bus error (core dumped) ``` This is happening on a Raspberry Pi 4 using the aarch64 Kubic image. Strangely `kubelet1.20` works fine, but `kubelet1.21` crashes every time. I have SELinux installed, but I see the same behavior with it enabled/enforcing and when it's totally disabled. Reproducible: Always Steps to Reproduce: 1. Install Kubic 2. Run kubelet --version Actual Results: It crashes Expected Results: It shouldn't crash Here is the `strace` output from when the command crashes: ``` execve("/usr/bin/kubelet1.21", ["kubelet1.21", "--version"], 0xffffeed92038 /* 58 vars */) = 0 brk(NULL) = 0xaaaac2275000 faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=14120, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 14120, PROT_READ, MAP_PRIVATE, 3, 0) = 0xffffae88e000 close(3) = 0 openat(AT_FDCWD, "/lib64/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0\220l\0\0\0\0\0\0"..., 832) = 832 newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=177672, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffffae88c000 mmap(NULL, 213312, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xffffae822000 mprotect(0xffffae83d000, 81920, PROT_NONE) = 0 mmap(0xffffae851000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1f000) = 0xffffae851000 mmap(0xffffae853000, 12608, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xffffae853000 close(3) = 0 openat(AT_FDCWD, "/lib64/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0\240\21\0\0\0\0\0\0"..., 832) = 832 newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=72896, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 131168, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xffffae801000 mprotect(0xffffae804000, 114688, PROT_NONE) = 0 mmap(0xffffae820000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0xffffae820000 close(3) = 0 openat(AT_FDCWD, "/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0@K\2\0\0\0\0\0"..., 832) = 832 pread64(3, "\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\327\225\343\235t\\\213+\201\232\3:\220n\346\215"..., 68, 768) = 68 newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=1847400, ...}, AT_EMPTY_PATH) = 0 mmap(NULL, 1616440, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xffffae676000 mprotect(0xffffae7de000, 86016, PROT_NONE) = 0 mmap(0xffffae7f3000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x16d000) = 0xffffae7f3000 mmap(0xffffae7f9000, 31288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xffffae7f9000 close(3) = 0 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffffae88a000 mprotect(0xffffae7f3000, 12288, PROT_READ) = 0 mprotect(0xffffae820000, 4096, PROT_READ) = 0 mprotect(0xffffae851000, 4096, PROT_READ) = 0 --- SIGBUS {si_signo=SIGBUS, si_code=BUS_ADRERR, si_addr=0xaaaabdedf000} --- +++ killed by SIGBUS (core dumped) +++ ``` -- You are receiving this mail because: You are the assignee for the bug.

1 0