March 2020 - 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

[kubic-bugs] [Bug 1162432] New: conmon binary lacks journald support (Devel:Kubic repo)
by bugzilla_noreply＠novell.com 27 Apr '20

27 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1162432 Bug ID: 1162432 Summary: conmon binary lacks journald support (Devel:Kubic repo) 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: jobbara.artalmatlan(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I have been using the Devel:Kubic repo in OpenSUSE Leap 15.1 for getting recent releases of podman. Today I tried to use journald logging driver but it failed. It reports missing journald support. See error message below. I found a similar issue regarding Ubuntu [2], which indicates it is a build time flag to have it enabled and downstream distros should build the binary that way. If I understood it correctly. Steps of reproduction: 1) install podman from Devel:Kubic repo # podman pod create --name test # podman run -d --name example --expose 80 --expose 443 --pod test --log-driver journald --log-opt tag="nginx|{{.ImageName}}|podman" nginx:1.16 [conmon:e] Include journald in compilation path to log to systemd journal Error: write child: broken pipe # echo $? 126 # rpm -qa | egrep "podman|conmon" conmon-2.0.10-lp151.21.1.x86_64 podman-cni-config-1.7.0-lp151.4.1.noarch podman-1.7.0-lp151.4.1.x86_64 [1] http://download.opensuse.org/repositories/devel:/kubic/openSUSE_Leap_15.1/ [2] https://github.com/containers/conmon/issues/67 Let me know how can I help further. Best regards, Balázs NÉMETH -- You are receiving this mail because: You are the assignee for the bug.

1 4

[kubic-bugs] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 29 Mar '20

29 Mar '20

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.novell.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.novell.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&… Or, you can use the general query page, at http://bugzilla.novell.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! Upstream kubeadm page does not list openSUSE Kubic as supported platform -> http://bugzilla.novell.com/show_bug.cgi?id=1119508 tmpfiles.d/kubernetes.conf uses legacy path, systemd complaining -> http://bugzilla.novell.com/show_bug.cgi?id=1124129 Tumbleweed packages not visible in MicroOS installer -> http://bugzilla.novell.com/show_bug.cgi?id=1137460 kubelet.service tries to start even without config file -> http://bugzilla.novell.com/show_bug.cgi?id=1146372 Terminal input over SSH breaks with non-en UTF-8 locale -> http://bugzilla.novell.com/show_bug.cgi?id=1156175 rebootmgrctl set-strategy off does not switch off rebooting -> http://bugzilla.novell.com/show_bug.cgi?id=1156509 MicroOS/Kubic images: btrfs-balance does not work, read-only root filesystem -> http://bugzilla.novell.com/show_bug.cgi?id=1159230 Introduce MicroOS Desktop -> http://bugzilla.novell.com/show_bug.cgi?id=1163453 [MicroOS] 9p modules are not in initrd, systems where cloud-init defines 9p mounts in fstab will stuck on reboot -> http://bugzilla.novell.com/show_bug.cgi?id=1165739 -- To unsubscribe, e-mail: kubic-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kubic-bugs+owner(a)opensuse.org

1 0

[kubic-bugs] [Bug 1167780] MicroOS images don't update grub if booted without EFI
by bugzilla_noreply＠novell.com 27 Mar '20

27 Mar '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1167780 http://bugzilla.opensuse.org/show_bug.cgi?id=1167780#c11 Neil Rickert <nwr10cst-oslnx(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx(a)yahoo.com --- Comment #11 from Neil Rickert <nwr10cst-oslnx(a)yahoo.com> --- Just a note on this. I have Tumbleweed installed on an external USB drive, for booting with either MBR/BIOS booting or UEFI booting. Installing that way works (the install succeeds) even if the installer is booted with UEFI. At install time, I configured for MBR/BIOS booting, so I have LOADER_TYPE="grub2" I manually install for EFI booting with: shim-install --no-nvram --removable And that works, even if the system is booted with MBR/BIOS booting (but it does require an EFI partition mounted at "/boot/efi"). With this setup, "grub.cfg" is suitably updated after kernel updates, no matter how it is booted. However, updates to grub2 do not automatically reinstall efi booting. So I occasionally reinstall that (such as after the update from grub-2.02 to grub-2.04), though this reinstall does not seem to be essential. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1167369] New: Snapshot 20200318-0 disables kubelet
by bugzilla_noreply＠novell.com 23 Mar '20

23 Mar '20

http://bugzilla.suse.com/show_bug.cgi?id=1167369 Bug ID: 1167369 Summary: Snapshot 20200318-0 disables kubelet Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- with snapshot 20200318: The following 3 NEW packages are going to be installed: kubernetes-kubelet-common kubernetes-kubelet1.17 libffi8 [...] (34/56) Installing: kubernetes-kubelet-common-1.17.4-1.1.x86_64 [....done] Additional rpm output: Updating /etc/sysconfig/kubelet ... Running in chroot, ignoring request: daemon-reload Removed /etc/systemd/system/multi-user.target.wants/kubelet.service. [...] With the next reboot, the whole cluster is not starting anymore. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 22 Mar '20

22 Mar '20

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.novell.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.novell.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&… Or, you can use the general query page, at http://bugzilla.novell.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! Upstream kubeadm page does not list openSUSE Kubic as supported platform -> http://bugzilla.novell.com/show_bug.cgi?id=1119508 tmpfiles.d/kubernetes.conf uses legacy path, systemd complaining -> http://bugzilla.novell.com/show_bug.cgi?id=1124129 Tumbleweed packages not visible in MicroOS installer -> http://bugzilla.novell.com/show_bug.cgi?id=1137460 kubelet.service tries to start even without config file -> http://bugzilla.novell.com/show_bug.cgi?id=1146372 Terminal input over SSH breaks with non-en UTF-8 locale -> http://bugzilla.novell.com/show_bug.cgi?id=1156175 rebootmgrctl set-strategy off does not switch off rebooting -> http://bugzilla.novell.com/show_bug.cgi?id=1156509 MicroOS/Kubic images: btrfs-balance does not work, read-only root filesystem -> http://bugzilla.novell.com/show_bug.cgi?id=1159230 Introduce MicroOS Desktop -> http://bugzilla.novell.com/show_bug.cgi?id=1163453 [MicroOS] 9p modules are not in initrd, systems where cloud-init defines 9p mounts in fstab will stuck on reboot -> http://bugzilla.novell.com/show_bug.cgi?id=1165739 -- To unsubscribe, e-mail: kubic-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kubic-bugs+owner(a)opensuse.org

1 0

[kubic-bugs] [Bug 1166999] New: 'kubicctl init' fails with Error invoking kubeadm: exit status 1
by bugzilla_noreply＠novell.com 19 Mar '20

19 Mar '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1166999 Bug ID: 1166999 Summary: 'kubicctl init' fails with Error invoking kubeadm: exit status 1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: ladislav.mate(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0 Build Identifier: >From logs what I think is important before 'kubeadm reset --force' is issued. Mar 18 15:13:19 kubeadm kubelet[16176]: E0318 15:13:19.466964 16176 manager.go:1086] Failed to create existing container: /kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod15de0f7e22fd1290312d477b9efcd91d.slice/crio-8297a0b68df97dc26d0f37d8bdcc50039ccb0e70bdbfc8004f729163969ada81.scope: Error finding container 8297a0b68df97dc26d0f37d8bdcc50039ccb0e70bdbfc8004f729163969ada81: Status 404 returned error &{%!s(*http.body=&{0xc0011f62a0 <nil> <nil> false false {0 0} false false false <nil>}) {%!s(int32=0) %!s(uint32=0)} %!s(bool=false) <nil> %!s(func(error) error=0x74f5f0) %!s(func() error=0x74f580)} Mar 18 15:13:19 kubeadm kubelet[16176]: E0318 15:13:19.467558 16176 manager.go:1086] Failed to create existing container: /kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod71b345beeb10c733ebd61851f0a38f4c.slice/crio-c0aed94b84d47d6a41783b3a4187e5db0ba6bef851f13a4100a4ad298b878157.scope: Error finding container c0aed94b84d47d6a41783b3a4187e5db0ba6bef851f13a4100a4ad298b878157: Status 404 returned error &{%!s(*http.body=&{0xc0008076e0 <nil> <nil> false false {0 0} false false false <nil>}) {%!s(int32=0) %!s(uint32=0)} %!s(bool=false) <nil> %!s(func(error) error=0x74f5f0) %!s(func() error=0x74f580)} Mar 18 15:13:19 kubeadm kubelet[16176]: E0318 15:13:19.468019 16176 manager.go:1086] Failed to create existing container: /kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod71b345beeb10c733ebd61851f0a38f4c.slice/crio-b46ce18b09597d91bf8cba339ea88c17700c23871864896eb50ee727192aa18a.scope: Error finding container b46ce18b09597d91bf8cba339ea88c17700c23871864896eb50ee727192aa18a: Status 404 returned error &{%!s(*http.body=&{0xc0011f6420 <nil> <nil> false false {0 0} false false false <nil>}) {%!s(int32=0) %!s(uint32=0)} %!s(bool=false) <nil> %!s(func(error) error=0x74f5f0) %!s(func() error=0x74f580)} Mar 18 15:13:24 kubeadm kubelet[16176]: W0318 15:13:24.254444 16176 prober.go:108] No ref for container "cri-o://37ff09f5038f1c428bccf2015629ac7def3ef9c6c4f6c908dbe0dbd9a926d896" (etcd-kubeadm_kube-system(add521f89bbc3fc01ff194af48568a77):etcd) Mar 18 15:13:24 kubeadm kubelet[16176]: I0318 15:13:24.254480 16176 prober.go:116] Liveness probe for "etcd-kubeadm_kube-system(add521f89bbc3fc01ff194af48568a77):etcd" failed (failure): HTTP probe failed with statuscode: 503 Mar 18 15:13:27 kubeadm kubelet[16176]: I0318 15:13:27.988365 16176 prober.go:116] Liveness probe for "kube-apiserver-kubeadm_kube-system(15de0f7e22fd1290312d477b9efcd91d):kube-apiserver" failed (failure): HTTP probe failed with statuscode: 500 Mar 18 15:13:36 kubeadm systemd[1]: crio-097e2c22c53ee0d065e67d5677ef71a6c6c1edfea90ad75f1fe48407be77cd5a.scope: Succeeded. Mar 18 15:13:36 kubeadm systemd[1]: crio-097e2c22c53ee0d065e67d5677ef71a6c6c1edfea90ad75f1fe48407be77cd5a.scope: Consumed 1.397s CPU time. Mar 18 15:13:37 kubeadm kubelet[16176]: I0318 15:13:37.638250 16176 prober.go:116] Liveness probe for "kube-apiserver-kubeadm_kube-system(15de0f7e22fd1290312d477b9efcd91d):kube-apiserver" failed (failure): HTTP probe failed with statuscode: 500 Mar 18 15:13:38 kubeadm systemd[1]: crio-conmon-097e2c22c53ee0d065e67d5677ef71a6c6c1edfea90ad75f1fe48407be77cd5a.scope: Succeeded. Mar 18 15:13:38 kubeadm kubelet[16176]: I0318 15:13:38.812370 16176 kubelet.go:1951] SyncLoop (PLEG): "kube-controller-manager-kubeadm_kube-system(ca2a9edec1631e0fee63d05d4afc1576)", event: &pleg.PodLifecycleEvent{ID:"ca2a9edec1631e0fee63d05d4afc1576", Type:"ContainerDied", Data:"097e2c22c53ee0d065e67d5677ef71a6c6c1edfea90ad75f1fe48407be77cd5a"} Mar 18 15:13:38 kubeadm kubelet[16176]: E0318 15:13:38.813675 16176 pod_workers.go:191] Error syncing pod ca2a9edec1631e0fee63d05d4afc1576 ("kube-controller-manager-kubeadm_kube-system(ca2a9edec1631e0fee63d05d4afc1576)"), skipping: failed to "StartContainer" for "kube-controller-manager" with CrashLoopBackOff: "back-off 10s restarting failed container=kube-controller-manager pod=kube-controller-manager-kubeadm_kube-system(ca2a9edec1631e0fee63d05d4afc1576)" Mar 18 15:13:44 kubeadm kubelet[16176]: W0318 15:13:44.140345 16176 conversion.go:110] Could not get instant cpu stats: cumulative stats decrease Mar 18 15:13:46 kubeadm kubelet[16176]: I0318 15:13:46.787636 16176 kubelet.go:1984] SyncLoop (container unhealthy): "kube-controller-manager-kubeadm_kube-system(ca2a9edec1631e0fee63d05d4afc1576)" Mar 18 15:13:46 kubeadm kubelet[16176]: E0318 15:13:46.788900 16176 pod_workers.go:191] Error syncing pod ca2a9edec1631e0fee63d05d4afc1576 ("kube-controller-manager-kubeadm_kube-system(ca2a9edec1631e0fee63d05d4afc1576)"), skipping: failed to "StartContainer" for "kube-controller-manager" with CrashLoopBackOff: "back-off 10s restarting failed container=kube-controller-manager pod=kube-controller-manager-kubeadm_kube-system(ca2a9edec1631e0fee63d05d4afc1576)" Mar 18 15:13:47 kubeadm kubelet[16176]: I0318 15:13:47.541420 16176 prober.go:116] Liveness probe for "kube-apiserver-kubeadm_kube-system(15de0f7e22fd1290312d477b9efcd91d):kube-apiserver" failed (failure): HTTP probe failed with statuscode: 500 Mar 18 15:13:51 kubeadm kubicd[1719]: time="2020-03-18T15:13:51Z" level=error msg="Error invoking kubeadm: exit status 1\nW0318 15:09:38.677827 15452 validation.go:28] Cannot validate kube-proxy config - no validator is available\nW0318 15:09:38.677907 15452 validation.go:28] Cannot validate kubelet config - no validator is available\nW0318 15:09:48.210563 15452 manifests.go:214] the default kube-apiserver authorization-mode is \"Node,RBAC\"; using \"Node,RBAC\"\nW0318 15:09:48.212596 15452 manifests.go:214] the default kube-apiserver authorization-mode is \"Node,RBAC\"; using \"Node,RBAC\"\nerror execution phase wait-control-plane: couldn't initialize a Kubernetes cluster\nTo see the stack trace of this error execute with --v=5 or higher\n" Mar 18 15:13:51 kubeadm kubicd[1719]: time="2020-03-18T15:13:51Z" level=info msg="Executing /usr/bin/kubeadm: [kubeadm reset --force]" During init phase I can see 4 containers are started , after some time they are restarted and at the end removed. CONTAINER IMAGE CREATED STATE NAME AT TEMPT POD ID a6b00704c77c6 c4dbbd93404efeff8a6e4786acbeacedb3d09b1bf853fad7c1ff9c3151059561 About a minute ago Running kube-controller-manager 0 290f739c0580e d496e5ff6a1e6 9886f51d5876dfa7a2a53ad25651d982b03f1573d64060facd41a743db95e40d About a minute ago Running kube-apiserver 0 59a02a8e7dd1b a6c16a4754e7a 7a43dd7408a648c68d90c9439ef6e81a46202ae83e8405adbbc7029f69f40d1d About a minute ago Running etcd 0 85371e0c09e4e e151c1729e999 b8aa11f465e53db4c21f519fed6d610d015aae2dae6266c4ed5f9cd427144255 About a minute ago Running kube-scheduler 0 a2e24ab789161 Reproducible: Always Steps to Reproduce: 1. Fresh install of Kubic(Master role) & transactional-update 2. kubeadm:~/.config/kubicctl # ls admin.crt admin.key Kubic-Control-CA.crt user.crt user.key 3. kubicctl init Actual Results: kubeadm:~/.config/kubicctl # kubicctl init Initializing kubernetes master can take several minutes, please be patient. Setting up single-master kubernetes node with weave Initialize Kubernetes control-plane Error invoking kubeadm: exit status 1 kubeadm:~/.config/kubicctl # Expected Results: kubicctl should finish properly -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1166857] New: Remove apparmor from MicroOS systemrole
by bugzilla_noreply＠novell.com 17 Mar '20

17 Mar '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1166857 Bug ID: 1166857 Summary: Remove apparmor from MicroOS systemrole 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: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- MicroOS doesn't require apparmor, but the containerhost still does -- You are receiving this mail because: You are the assignee for the bug.

1 1