January 2021 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[kubic-bugs] [Bug 1167780] New: MicroOS images don't update grub if booted without EFI
by bugzilla_noreply＠novell.com 09 Jan '23

09 Jan '23

http://bugzilla.suse.com/show_bug.cgi?id=1167780 Bug ID: 1167780 Summary: MicroOS images don't update grub if booted without EFI Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: fvogt(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- The .qcow2 images are meant to work fine on systems with EFI (optionally secure boot) and without, so they have both i386-pc and x86_64-efi targets of grub2 installed by kiwi during image building. Kiwi sets LOADER_TYPE="grub2-efi" for this. When booting the image without EFI though, this is not changed by anything and so update-bootloader only manages the x86_64-efi target of grub2. As the grub.cfg file is in the same location, there aren't any immediate issues, but it means that grub is never updated in those deployments. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[kubic-bugs] [Bug 1153687] New: Zypper repo name detection broken
by bugzilla_noreply＠novell.com 24 Nov '21

24 Nov '21

http://bugzilla.suse.com/show_bug.cgi?id=1153687 Bug ID: 1153687 Summary: Zypper repo name detection broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- zypper ar obs://some:where/ results in a URL such as https://download.opensuse.org/repositories/some:/where/openSUSE-MicroOS-201… -- You are receiving this mail because: You are the assignee for the bug.

2 16

[kubic-bugs] [Bug 1085619] New: Softlockup with btrfs and kubic (CaaSP on openSUSE)
by bugzilla_noreply＠novell.com 16 Sep '21

16 Sep '21

http://bugzilla.suse.com/show_bug.cgi?id=1085619 Bug ID: 1085619 Summary: Softlockup with btrfs and kubic (CaaSP on openSUSE) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kubic Assignee: jeffm(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org, lpechacek(a)suse.com Found By: --- Blocker: --- With current openSUSE Kubic builds (CaaSP based on openSUSE Tumbleweed), we seem to run into the same issue as with CaaSP v1: bsc#1041296 - admin node freezes - no shell after putting password into login prompt Could it be that the fixes are missing in the upstream kernel? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1179453] New: [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1179453 Bug ID: 1179453 Summary: [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 URL: https://openqa.suse.de/tests/5078838/modules/journal_c heck/steps/20 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: ioannis.bonatakis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation /usr/lib/udev/rules.d/50-udev-default.rules contains ``` SUBSYSTME=="kfd", GROUP="render",MODE="0666" ``` but this group does not exists ``` root:x:0:[m shadow:x:15:[m trusted:x:42:[m users:x:100:[m messagebus:x:499:[m nogroup:x:65533:nobody[m nobody:x:65534:[m wheel:x:498:[m kmem:x:497:[m lock:x:496:[m tty:x:5:[m utmp:x:495:[m audio:x:494:[m cdrom:x:493:[m dialout:x:492:[m disk:x:491:[m input:x:490:[m kvm:x:489:[m lp:x:488:[m tape:x:487:[m video:x:486:[m systemd-journal:x:485:[m systemd-network:x:484:[m systemd-resolve:x:483:[m systemd-timesync:x:482:[m systemd-coredump:x:481:[m sshd:x:480:[m chrony:x:479:[m ``` The output from the journal reports `localhost systemd-udevd[221]: /usr/lib/udev/rules.d/50-udev-default.rules:40 Unknown group 'render', ignoring` openQA test in scenario microos-5.0-DVD-x86_64-suse_microos_autoyast@64bit fails in [journal_check](https://openqa.suse.de/tests/5078838/modules/journal_check/steps/20) ## Test suite description ## Reproducible Fails since (at least) Build [49.1_13.7](https://openqa.suse.de/tests/5032758) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=microos&flavor=DVD&machine=64bit&test=suse_microos_autoyast&version=5.0) -- You are receiving this mail because: You are the assignee for the bug.

1 1

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 31 Jan '21

31 Jan '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 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules -> http://bugzilla.suse.com/show_bug.cgi?id=1179453

1 0

[Bug 1181547] New: [Build 20210128] openQA test fails in journal_check
by bugzilla_noreply＠suse.com 29 Jan '21

29 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181547 Bug ID: 1181547 Summary: [Build 20210128] openQA test fails in journal_check Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/1609113/modules/jour nal_check/steps/21 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-aarch64-microos2microosnext@aarch64_lse_smp4 fails in [journal_check](https://openqa.opensuse.org/tests/1609113/modules/journal_ch… In openQA, journal_check test fails randomly because it sometimes finds the following lines in the journal: Jan 29 05:48:25.562772 localhost wickedd-nanny[682]: device eth0: call to org.opensuse.Network.Addrconf.ipv4.dhcp.requestLease() failed: Service not known Jan 29 05:48:25.562802 localhost wickedd-nanny[682]: eth0: failed to bring up device, still continuing Having a look at the lines right after those lines in the journal, it seems that eth0 finally come up: Jan 29 05:48:25.596799 localhost health-checker[705]: active Jan 29 05:48:25.634662 localhost health-checker[662]: Health check passed Jan 29 05:48:25.642461 localhost systemd[1]: health-checker.service: Succeeded. Jan 29 05:48:25.642677 localhost systemd[1]: Finished MicroOS Health Checker. Jan 29 05:48:30.838814 localhost wicked[683]: lo up Jan 29 05:48:30.838814 localhost wicked[683]: eth0 up Jan 29 05:48:30.839526 localhost systemd[1]: Finished wicked managed network interfaces. Jan 29 05:48:30.839981 localhost systemd[1]: Reached target Network. ## Test suite description Boot from the latest published MicroOS image and transactional-update dup to snapshot under test. Make sure to use %BUILD% in the URL and file name to force a redownload for new builds. ## Reproducible Fails since (at least) Build [20210128](https://openqa.opensuse.org/tests/1609113) (current job) ## Expected result Last good: [20210127](https://openqa.opensuse.org/tests/1608050) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=microo… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181482] New: microos.o.o does not contain a link to the container wiki
by bugzilla_noreply＠suse.com 27 Jan '21

27 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181482 Bug ID: 1181482 Summary: microos.o.o does not contain a link to the container wiki 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: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- MicroOS is a container Host OS, but does not contain a link to our Container Portal (https://en.opensuse.org/Portal:Container). But this contains the most important informations for a containerized workload. -- You are receiving this mail because: You are the assignee for the bug.

1 1

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 24 Jan '21

24 Jan '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 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules -> http://bugzilla.suse.com/show_bug.cgi?id=1179453

1 0

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 17 Jan '21

17 Jan '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 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules -> http://bugzilla.suse.com/show_bug.cgi?id=1179453

1 0

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1175850 https://bugzilla.suse.com/show_bug.cgi?id=1175850#c20 --- Comment #20 from Franck Bui <fbui(a)suse.com> --- (In reply to Fabian Vogt from comment #19) > So is that a systemd bug? I now remember a shortcoming in libmount which is probably related, see: https://github.com/systemd/systemd/issues/15266 So basically 'x-initrd.mount' is lost after switching to the rootfs and that's the reason why PID1 attempts to unmount it during shutdown. > I got rid of haveged, but it still fails. It seems to finalize cr_var > properly though, so it's working as expected? If '/' is hosted on a DM device I would say so. -- You are receiving this mail because: You are on the CC list for the bug.

1 0