November 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

[Bug 1175379] microos-tools as of request 826035 renders MicroOs instances with /tmp not tmpfs unusable
by bugzilla_noreply＠suse.com 30 Nov '20

30 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1175379 https://bugzilla.suse.com/show_bug.cgi?id=1175379#c10 --- Comment #10 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1175379) was mentioned in https://build.opensuse.org/request/show/851893 15.2:MicroOS / microos-tools -- 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 29 Nov '20

29 Nov '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.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

1 0

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 22 Nov '20

22 Nov '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.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

1 0

[Bug 1175523] Installing kubeadm<next> shouldn't require installing kubelet<next>
by bugzilla_noreply＠suse.com 20 Nov '20

20 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175523 http://bugzilla.opensuse.org/show_bug.cgi?id=1175523#c2 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown(a)suse.com Assignee|kubic-bugs(a)opensuse.org |rbrown(a)suse.com --- Comment #2 from Richard Brown <rbrown(a)suse.com> --- Done, thanks for the bug report :) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1175524] Installing kubeadm<next> shouldn't care about cri-tools
by bugzilla_noreply＠suse.com 20 Nov '20

20 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175524 http://bugzilla.opensuse.org/show_bug.cgi?id=1175524#c1 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED Assignee|kubic-bugs(a)opensuse.org |rbrown(a)suse.com --- Comment #1 from Richard Brown <rbrown(a)suse.com> --- Done, thanks for the bug report :) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1177289] k8s missing apimachinery version data
by bugzilla_noreply＠suse.com 20 Nov '20

20 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177289 http://bugzilla.opensuse.org/show_bug.cgi?id=1177289#c5 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED --- Comment #5 from Richard Brown <rbrown(a)suse.com> --- resolved with https://build.opensuse.org/package/rdiff/devel:kubic/kubernetes1.19?linkrev… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1178868] New: cilium-k8s-yaml Helm Chart does not deploys a working cilium installation
by bugzilla_noreply＠suse.com 20 Nov '20

20 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1178868 Bug ID: 1178868 Summary: cilium-k8s-yaml Helm Chart does not deploys a working cilium installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: contact(a)ffreitas.io QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi all, I was using kubic with cilium just fine using kubic-control builded from source (master branch). With the latest helm chart of cilium packaged in cilium-k8s-yaml it does not work anymore. By searching a bit I think there might be issues with the cilium images from registry.opensuse.org. # The problem The latest commit of kubic-control deploys cilium using the helm chert installed with the package cilium-k8s-yaml. For a while this chart was not working (some default values were missing) so a quickfix was made with custom helm values pointing to upstream images. Recently the chart updated to the version 1.8.5 of cilium and the fix is now useless. The template is now working without having to add values. To deploy the following chart without any value we need to build kubic-control from source and to deploy it on our master node. We then do the following : ``` bash echo "#We do not want values here" > /etc/kubic/helm/cilium.yaml kubicctl init --pod-network=cilium ``` But doing so, the deployed cilium is not working : ```bash node-master:~ # kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system cilium-7sbtc 0/1 CrashLoopBackOff 10 30m kube-system cilium-operator-cfc74c99b-9wwhs 0/1 Pending 0 30m kube-system cilium-operator-cfc74c99b-qcqb2 0/1 ImagePullBackOff 0 30m kube-system coredns-76679c6978-dx2xc 0/1 ContainerCreating 0 30m kube-system coredns-76679c6978-pfp7c 0/1 ContainerCreating 0 30m kube-system etcd-node-master 1/1 Running 0 30m kube-system kube-apiserver-node-master 1/1 Running 0 30m kube-system kube-controller-manager-node-master 1/1 Running 0 30m kube-system kube-proxy-bzhrf 1/1 Running 0 30m kube-system kube-scheduler-node-master 1/1 Running 0 30m kube-system kured-j5dh8 0/1 ContainerCreating 0 30m ``` # cilium operator The first problem comes from the cilium-operator. The image used in the chart is registry.opensuse.org/kubic/cilium-operator-generic:1.8.5 put this image does not exist. It is due to the chart template : ```bash node-master:~ # grep gen /usr/share/k8s-helm/cilium/charts/operator/templates/deployment.yaml - cilium-operator-generic image: "{{ .Values.global.registry }}/{{ .Values.image }}-generic:{{ .Values.global.tag }}" ``` It can only be fixed by changing the chart or updating the image name in the registry. # cilium We still have the cilium pod in a CrashLoopBackOff. Looking at the logs it seems to come from the image stored in registry.opensuse.org : ```bash node-master:~ # kubectl logs -n kube-system cilium-7sbtc | tail level=info msg=" --tunnel='vxlan'" subsys=daemon level=info msg=" --version='false'" subsys=daemon level=info msg=" --write-cni-conf-when-ready=''" subsys=daemon level=info msg=" _ _ _" subsys=daemon level=info msg=" ___|_| |_|_ _ _____" subsys=daemon level=info msg="| _| | | | | | |" subsys=daemon level=info msg="|___|_|_|_|___|_|_|_|" subsys=daemon level=info msg="Cilium 1.8.5 go version go1.13.15 linux/amd64" subsys=daemon level=info msg="cilium-envoy version: 6d0a55191baac475046d13e52ffe330f3a56a4ce/1.14.4/Modified/DEBUG/BoringSSL" subsys=daemon level=fatal msg="clang: NOT OK" error="Invalid character(s) found in patch number \"0\\nTarget:\"" subsys=linux-datapath ``` Is someone already looking at this ? Is there any way for me to help with this issues ? Regards, Francisco -- You are receiving this mail because: You are the assignee for the bug.

1 1