August 2019 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[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 1143813] New: kubelet sometimes starting too fast
by bugzilla_noreply＠novell.com 13 Jan '20

13 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1143813 Bug ID: 1143813 Summary: kubelet sometimes starting too fast 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: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- kubelet is sometimes starting to fast, before wicked did setup the network fully, including the real hostname. In this cases, kubelet uses "localhost", which of course will fail. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kubic-bugs] [Bug 1115000] New: cloud-init in TW snapshots 1105 and 1106 do not populate /etc/resolv.conf
by bugzilla_noreply＠novell.com 26 Sep '19

26 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1115000 Bug ID: 1115000 Summary: cloud-init in TW snapshots 1105 and 1106 do not populate /etc/resolv.conf Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Tools Assignee: public-cloud-maintainers(a)suse.de Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- cloud-init do not seem to correctly populate /etc/resolv.conf After a boot of Kubic with the kubeadm system role, the resulting /etc/resolv.conf has "; Created by cloud-init on instance boot automatically, do not edit" followed by the usual "### /etc/resolv.conf file autogenerated by netconfig" preamble, but has no name resolver configured This results in a system that has no working name resolution https://openqa.opensuse.org/tests/788925#step/first_boot/23 All other networking seems to behave fine EXPECTED BEHAVIOUR cloud-init should correctly populate /etc/resolv.conf when configuring the network of a system WORKAROUND docker automatically disables cloud-inits network configuration by editing /etc/cloud/cloud.cfg.d/01-network.cfg - for non-docker runtimes Kubic intends to do something similar until this bug is fixed at least. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[kubic-bugs] [Bug 1145002] New: 'kubeadm init' fails to start inside openQA on aarch64
by bugzilla_noreply＠novell.com 04 Sep '19

04 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1145002 Bug ID: 1145002 Summary: 'kubeadm init' fails to start inside openQA on aarch64 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: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openQA link: https://openqa.opensuse.org/tests/1001293#step/kubeadm/10 'kubeadm init' fails because it cannot download some images from registry.opensuse.org: * kube-apiserver * kube-controller-manager * kube-scheduler * kube-proxy * etc * coredns -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kubic-bugs] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 25 Aug '19

25 Aug '19

[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 -- 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 1146802] kubic image does not call cloud-init
by bugzilla_noreply＠novell.com 22 Aug '19

22 Aug '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1146802 http://bugzilla.opensuse.org/show_bug.cgi?id=1146802#c3 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alinm.elena(a)gmail.com Flags| |needinfo?(alinm.elena@gmail | |.com) --- Comment #3 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Thorsten Kukuk from comment #2) > (In reply to Fabian Vogt from comment #1) > > Most likely caused by datasource_list in cloud-init-config-{caasp,MicroOS}, > > reassigning. > > > > Would it hurt to remove that line in the packages? > > If yes, I'd need to drop it in the images only. > > I added that line because it was necesssary at that point in time. > No idea how this is today. I don't care much, as we don't want to use > cloud-init anymore for bare metal and KVM/XEN. Ok, I made https://build.opensuse.org/request/show/725277. Once accepted, images in devel:kubic:images (devel_kubic repo) should build with the changes. Once they're built, please give them a try. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1146802] kubic image does not call cloud-init
by bugzilla_noreply＠novell.com 22 Aug '19

22 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=1146802 http://bugzilla.suse.com/show_bug.cgi?id=1146802#c2 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kukuk(a)suse.com) | --- Comment #2 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Fabian Vogt from comment #1) > Most likely caused by datasource_list in cloud-init-config-{caasp,MicroOS}, > reassigning. > > Would it hurt to remove that line in the packages? > If yes, I'd need to drop it in the images only. I added that line because it was necesssary at that point in time. No idea how this is today. I don't care much, as we don't want to use cloud-init anymore for bare metal and KVM/XEN. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1146802] kubic image does not call cloud-init
by bugzilla_noreply＠novell.com 22 Aug '19

22 Aug '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1146802 http://bugzilla.opensuse.org/show_bug.cgi?id=1146802#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com, | |kukuk(a)suse.com Component|Cloud:Tools |Kubic Assignee|public-cloud-maintainers@su |kubic-bugs(a)opensuse.org |se.de | Flags| |needinfo?(kukuk(a)suse.com) --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- Most likely caused by datasource_list in cloud-init-config-{caasp,MicroOS}, reassigning. Would it hurt to remove that line in the packages? If yes, I'd need to drop it in the images only. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1146372] New: kubelet.service tries to start even without config file
by bugzilla_noreply＠novell.com 20 Aug '19

20 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=1146372 Bug ID: 1146372 Summary: kubelet.service tries to start even without config file 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: --- Installing Kubic results in this multiple times: Aug 20 11:34:33 install systemd[1]: kubelet.service: Service RestartSec=10s expired, scheduling restart. Aug 20 11:34:33 install systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 5. Aug 20 11:34:33 install systemd[1]: Stopped kubelet: The Kubernetes Node Agent. Aug 20 11:34:33 install systemd[1]: Started kubelet: The Kubernetes Node Agent. Aug 20 11:34:33 install kubelet[1961]: Flag --runtime-request-timeout has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information. Aug 20 11:34:33 install kubelet[1961]: F0820 11:34:33.955572 1961 server.go:198] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory Aug 20 11:34:33 install systemd[1]: kubelet.service: Main process exited, code=exited, status=255/EXCEPTION Aug 20 11:34:33 install systemd[1]: kubelet.service: Failed with result 'exit-code'. Sounds like adding a ConditionPathExists=/var/lib/kubelet/config.yaml would be useful. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 18 Aug '19

18 Aug '19

[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 sometimes starting too fast -> http://bugzilla.novell.com/show_bug.cgi?id=1143813 -- To unsubscribe, e-mail: kubic-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kubic-bugs+owner(a)opensuse.org

1 0