September 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 1151072] New: health-checker causes grub to print "Invalid file name ``"
by bugzilla_noreply＠novell.com 12 Dec '19

12 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1151072 Bug ID: 1151072 Summary: health-checker causes grub to print "Invalid file name ``" 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 CC: iforster(a)suse.com Found By: --- Blocker: --- If no grubenv is available, it prints a non-fatal error message when booting a menu option. Cause seems to be bug 1126900. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1152185] New: kube-flannel-ds-arm64
by bugzilla_noreply＠novell.com 06 Nov '19

06 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1152185 Bug ID: 1152185 Summary: kube-flannel-ds-arm64 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: --- kubeadm test fails on openQA because kube-flannel-ds-arm64 is in Init:CrashLoopBackOff state. See: https://openqa.opensuse.org/tests/1042006#step/kubeadm/21 -- You are receiving this mail because: You are the assignee for the bug.

1 3

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

29 Sep '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.service tries to start even without config file -> http://bugzilla.novell.com/show_bug.cgi?id=1146372 kubic image does not call cloud-init -> http://bugzilla.novell.com/show_bug.cgi?id=1146802 health-checker causes grub to print "Invalid file name ``" -> http://bugzilla.novell.com/show_bug.cgi?id=1151072 -- 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 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 1151081] New: transactional-update shell does not provide resolv.conf
by bugzilla_noreply＠novell.com 25 Sep '19

25 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1151081 Bug ID: 1151081 Summary: transactional-update shell does not provide resolv.conf Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: iforster(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- Inside the t-u shell, /etc/resolv.conf is dangling, which means that no DNS lookups are possible. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[kubic-bugs] [Bug 1151081] transactional-update shell does not provide resolv.conf
by bugzilla_noreply＠novell.com 25 Sep '19

25 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1151081 http://bugzilla.opensuse.org/show_bug.cgi?id=1151081#c1 Ignaz Forster <iforster(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Ignaz Forster <iforster(a)suse.com> --- Recent installations of Tumbleweed create the /etc/resolv.conf symlink directly to /run/netconfig instead of /var/run/netconfig as before. When copying the netconfig files transactional-update will now support both locations by copying the netconfig files to /run/netconfig and enforcing a symlink from /var/run to /run on the root file system (but only if /var is a separate subvolume of course). Fixed in transactional-update 2.17. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1149701] Ignition needs to autodetect the platform
by bugzilla_noreply＠novell.com 23 Sep '19

23 Sep '19

http://bugzilla.novell.com/show_bug.cgi?id=1149701 http://bugzilla.novell.com/show_bug.cgi?id=1149701#c2 --- Comment #2 from Ignaz Forster <iforster(a)suse.com> --- I've been discussing this with a CoreOS developer at All Systems Go!. The general feedback was that there isn't any interest in it, as it doesn't match the intended design (with them having to provide a separate image with provider specific stuff for each platform anyway) and because of the fear of potential security implications (e.g. by querying random IP addresses). I guess it's still worth to open a ticket upstream to have these things documented and / or gather additional feedback. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

22 Sep '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.service tries to start even without config file -> http://bugzilla.novell.com/show_bug.cgi?id=1146372 kubic image does not call cloud-init -> http://bugzilla.novell.com/show_bug.cgi?id=1146802 -- To unsubscribe, e-mail: kubic-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kubic-bugs+owner(a)opensuse.org

1 0