June 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 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 1135342] New: MicroOS patterns have no daemon for time syncing
by bugzilla_noreply＠novell.com 16 Aug '19

16 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=1135342 Bug ID: 1135342 Summary: MicroOS patterns have no daemon for time syncing 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The openSUSE-MicroOS images contain (same as the skelcd): <namedCollection name="basesystem"/> <package name="patterns-microos-basesystem"/> <namedCollection name="microos_defaults"/> <package name="patterns-microos-defaults"/> <namedCollection name="microos_apparmor"/> <package name="patterns-microos-apparmor"/>  <namedCollection name="microos_cloud"/> <package name="patterns-microos-cloud"/> Neither ntpd, chrony nor systemd-timesyncd end up installed. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kubic-bugs] [Bug 1114818] New: New kubeadm NTP screen does not prefill ntp.org pool servers
by bugzilla_noreply＠novell.com 30 Jul '19

30 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1114818 Bug ID: 1114818 Summary: New kubeadm NTP screen does not prefill ntp.org pool servers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: rbrown(a)suse.com QA Contact: jsrain(a)suse.com CC: kubic-bugs(a)opensuse.org, lslezak(a)suse.com Found By: --- Blocker: --- The new kubeadm NTP screen in Kubic does not correctly prefil the NTP server field as described in https://en.opensuse.org/Kubic:CaaSPInstallationComparision EXPECTED BEHAVIOUR: "NTP server (chrony) (prefill field with dhcp answer, if there is no dhcp, prefill with ntp pool server if allowed, else leave empty and warn if it stays empty, no hard error)" ACTUAL BEHAVIOUR: NTP Server field does prefil with DHCP answer when it's available, but when it's not available it does not prefill with ntp.org pool servers (eg. 0.opensuse.pool.ntp.org, 1.opensuse.pool.ntp.org, 2.opensuse.pool.ntp.org, etc) Also, there is a cosmetic error - the screen says "Admin node configuration" when it should say "kubeadm node configuration" (the kubeadm nodes are not always admin nodes) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[kubic-bugs] [Bug 1139800] New: Cillium not working in Kubic
by bugzilla_noreply＠novell.com 22 Jul '19

22 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1139800 Bug ID: 1139800 Summary: Cillium not working in Kubic 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: jason.evans(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am testing this on the latest Snapshot20190627. Init worked well: > master:~ # kubicctl init --pod-network cilium Initializing kubernetes master can take several minutes, please be patient. Initialize Kubernetes control-plane Deploy cilium Deploy Kubernetes Reboot Daemon (kured) Kubernetes master was succesfully setup. > cilium-etcd-operator pod is still not coming up: > master:~ # kubectl get pods -n kube-system NAME READY STATUS RESTARTS AGE cilium-5fdrl 0/1 PodInitializing 0 73s cilium-etcd-operator-5f9468cf8c-6b5bn 0/1 ImagePullBackOff 0 73s cilium-operator-cb87f5c57-d8qwz 0/1 Pending 0 73s coredns-fb8b8dccf-c7f8n 0/1 Pending 0 73s coredns-fb8b8dccf-wl5rg 0/1 Pending 0 73s etcd-master 1/1 Running 0 30s kube-apiserver-master 1/1 Running 0 40s kube-controller-manager-master 1/1 Running 0 37s kube-proxy-jgttd 1/1 Running 0 73s kube-scheduler-master 1/1 Running 0 37s > Can not pull the image from registry.opensuse.org/kubic/cilium-etcd-operator:2.0 > Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 4m28s default-scheduler Successfully assigned kube-system/cilium-etcd-operator-5f9468cf8c-6b5bn to master Normal Pulling 103s (x4 over 4m25s) kubelet, master Pulling image "registry.opensuse.org/kubic/cilium-etcd-operator:2.0" Warning Failed 103s (x4 over 4m11s) kubelet, master Failed to pull image "registry.opensuse.org/kubic/cilium-etcd-operator:2.0": rpc error: code = Unknown desc = Error reading manifest 2.0 in registry.opensuse.org/kubic/cilium-etcd-operator: name unknown Warning Failed 103s (x4 over 4m11s) kubelet, master Error: ErrImagePull Normal BackOff 89s (x6 over 4m10s) kubelet, master Back-off pulling image "registry.opensuse.org/kubic/cilium-etcd-operator:2.0" Warning Failed 78s (x7 over 4m10s) kubelet, master Error: ImagePullBackOff > -- You are receiving this mail because: You are the assignee for the bug.

1 2

[kubic-bugs] [Bug 1139801] New: Salt Warnings in Kubic
by bugzilla_noreply＠novell.com 22 Jul '19

22 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1139801 Bug ID: 1139801 Summary: Salt Warnings in Kubic 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: jason.evans(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I receive the following warnings when trying to run any salt commands in Kubic. The commands still run but encoding is deprecated. master:~ # salt '*' test.ping [WARNING ] /usr/lib/python3.7/site-packages/salt/transport/ipc.py:292: DeprecationWarning: encoding is deprecated, Use raw=False instead. self.unpacker = msgpack.Unpacker(encoding=encoding) [WARNING ] /usr/lib/python3.7/site-packages/salt/payload.py:150: DeprecationWarning: encoding is deprecated, Use raw=False instead. ret = msgpack.loads(msg, use_list=True, ext_hook=ext_type_decoder, encoding=encoding) worker2: True worker1: True -- You are receiving this mail because: You are the assignee for the bug.

1 2

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

30 Jun '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 MicroOS does not enable any daemon for time syncing -> http://bugzilla.novell.com/show_bug.cgi?id=1135342 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] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 23 Jun '19

23 Jun '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 MicroOS does not enable any daemon for time syncing -> http://bugzilla.novell.com/show_bug.cgi?id=1135342 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 1138725] New: Add Ignition to Tumbleweed
by bugzilla_noreply＠novell.com 19 Jun '19

19 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1138725 Bug ID: 1138725 Summary: Add Ignition to Tumbleweed 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: iforster(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Ignition (https://github.com/coreos/ignition) is supposed to replace cloud-init as a minimal alternative for several system images (https://en.opensuse.org/Kubic:MicroOS#Configuration) This bug tracks the necessary changes done to include the project into the distribution. -- 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 16 Jun '19

16 Jun '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 MicroOS does not enable any daemon for time syncing -> http://bugzilla.novell.com/show_bug.cgi?id=1135342 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