November 2018 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[kubic-bugs] [Bug 1107283] Don't create /cloud-init-config subvolume by default
by bugzilla_noreply＠novell.com 14 Nov '18

14 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1107283 http://bugzilla.opensuse.org/show_bug.cgi?id=1107283#c3 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED --- Comment #3 from Richard Brown <rbrown(a)suse.com> --- Resolved with https://github.com/yast/skelcd-control-Kubic/pull/23 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1103906] New: Refocus Kubic on new architecture design
by bugzilla_noreply＠novell.com 14 Nov '18

14 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1103906 Bug ID: 1103906 Summary: Refocus Kubic on new architecture design 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: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kubic will be divesting itself from it's previous goal of synchronising with the SUSE CaaS Stack, and instead focusing on the investigation and integration of a new Kubic CaaS Stack (which may also become the future SUSE CaaS Stack) This means the following for Kubic immediately - the removal of current admin/worker/plain system roles - focus on kubeadm as the default k8s bootstrapping tool (including a new system role) - adaption & introduction of new openQA tests to fit this new architecture - removal of Container RPMs from Factory & Kubic media Future steps include - replace kubeadm containers with opensuse based ones - establishment of new Container release process to a registry For more, see https://trello.com/b/wjHyQDK6/kubic-project This new direction will be described to the community more verbosely in a pending blog post to kubic.opensuse.org, meanwhile this bug is to track any efforts and fallout of this major change. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1105421] New: CoreDNS doesn't start
by bugzilla_noreply＠novell.com 14 Nov '18

14 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1105421 Bug ID: 1105421 Summary: CoreDNS doesn't start 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: pgeorgiadis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I followed the guide at https://kubic.opensuse.org/blog/2018-08-20-kubeadm-intro/ As I have previously said [1], the CNI plugin binaries are misplaced, thus the pods cannot talk to each other. The kubeadm cluster is able to join nodes (you can happily see them: kubectl get nodes) but it's kinda useless the cluster cannot deploy any containers or kube-apps on it. [1] https://bugzilla.novell.com/show_bug.cgi?id=1093132#c29 Feel free to re-open: https://github.com/kubernetes/kubernetes/issues/67390 Reproducer: - Follow https://kubic.opensuse.org/blog/2018-08-20-kubeadm-intro/ - At the end, do: kubectl get pods --namespace=kube-system you will notice two pods of core-dns 0/1 with status "ContainerCreating". This stays forever, thus there's no DNS in the cluster. This happens because kubelet looks at Ubuntu's location by default for CNI plugins: > # cat /var/lib/kubelet/kubeadm-flags.env > KUBELET_KUBEADM_ARGS=--cgroup-driver=cgroupfs --cni-bin-dir=/opt/cni/bin --cni-conf-dir=/etc/cni/net.d --network-plugin=cni Workaround: ~~~~~~~~~~~ Move the cni-plugins into /opt/cni/bin (not recommended) find a way to tell kubelet to look into the correct path (recommended) or even better, use CRI-O instead of Docker and you won't have that problem. See the steps: https://pastebin.com/raw/bJB0zJLD -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kubic-bugs] [Bug 1087685] New: Kubic's New-installation-flow; yast2-caasp specific functionality missing
by bugzilla_noreply＠novell.com 14 Nov '18

14 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1087685 Bug ID: 1087685 Summary: Kubic's New-installation-flow; yast2-caasp specific functionality missing 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: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The worker role services-enabled and one-line-checks tests are failing https://openqa.opensuse.org/tests/646725#step/services_enabled/22 This is because of yast2-caasp specific functionality not being called during the new workflow https://github.com/yast/yast-caasp/tree/master/src/lib/y2caasp/cfa These (and any other missing configuration steps) need to be added to the planned additional screens for the Worker & Admin system roles -- You are receiving this mail because: You are the assignee for the bug.

1 2

[kubic-bugs] [Bug 1085632] salt-api container with python3 backtrace
by bugzilla_noreply＠novell.com 14 Nov '18

14 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1085632 http://bugzilla.opensuse.org/show_bug.cgi?id=1085632#c8 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED --- Comment #8 from Richard Brown <rbrown(a)suse.com> --- Kubic no longer has a salt-api container -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1085619] Softlockup with btrfs and kubic (CaaSP on openSUSE)
by bugzilla_noreply＠novell.com 14 Nov '18

14 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1085619 http://bugzilla.opensuse.org/show_bug.cgi?id=1085619#c2 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm(a)suse.com, | |rbrown(a)suse.com Flags| |needinfo?(jeffm(a)suse.com) --- Comment #2 from Richard Brown <rbrown(a)suse.com> --- (In reply to Jeff Mahoney from comment #1) > Without details, I can't really say. The fix that we carry in the SLE > kernels is to just revert the offending commit. That's not upstreamable. I > have patches in testing that will resolve this properly. Hi Jeff, How are those patches, are they in Kubic? Can I close this bug? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1114818] New kubeadm NTP screen does not prefill ntp.org pool servers
by bugzilla_noreply＠novell.com 14 Nov '18

14 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1114818 http://bugzilla.suse.com/show_bug.cgi?id=1114818#c2 Ladislav Slezák <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #2 from Ladislav Slezák <lslezak(a)suse.com> --- Fixed in yast2-caasp-4.1.2 (https://github.com/yast/yast-caasp/pull/37) and skelcd-control-Kubic-20181114 (https://github.com/yast/skelcd-control-Kubic/pull/22) -- 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 11 Nov '18

11 Nov '18

[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! openSUSE-Tumbleweed-Kubic-release will never be updated -> http://bugzilla.novell.com/show_bug.cgi?id=1076265 salt-api container with python3 backtrace -> http://bugzilla.novell.com/show_bug.cgi?id=1085632 Kubic's New-installation-flow; yast2-caasp specific functionality missing -> http://bugzilla.novell.com/show_bug.cgi?id=1087685 Refocus Kubic on new architecture design -> http://bugzilla.novell.com/show_bug.cgi?id=1103906 Don't create /cloud-init-config subvolume by default -> http://bugzilla.novell.com/show_bug.cgi?id=1107283 -- 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] cloud-init in TW snapshots 1105 and 1106 do not populate /etc/resolv.conf
by bugzilla_noreply＠novell.com 10 Nov '18

10 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1115000 http://bugzilla.suse.com/show_bug.cgi?id=1115000#c5 Robert Schweikert <rjschwei(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rbrown(a)suse.com) --- Comment #5 from Robert Schweikert <rjschwei(a)suse.com> --- Everything as far as cloud-init is concerned appears to be behaving as expected. The config at https://build.opensuse.org/package/view_file/openSUSE:Factory/cloud-init-co… contains: datasource_list: [ LocalDisk, NoCloud, OpenStack, None ] where local disk is our own DataSource implementation and carried as a patch as have had no time yet to investigate differences to NoCloud. ANyway, the code looks for the data sources and cannot find them, from the log: 2018-11-07 10:50:20,208 - handlers.py[DEBUG]: finish: init-local/search-LocalDisk: SUCCESS: no local data found from DataSourceLocalDisk 2018-11-07 10:50:20,911 - handlers.py[DEBUG]: finish: init-local/search-NoCloud: SUCCESS: no local data found from DataSourceNoCloud 2018-11-07 10:50:20,936 - handlers.py[DEBUG]: finish: init-local/search-OpenStackLocal: SUCCESS: no local data found from DataSourceOpenStackLocal 2018-11-07 10:50:38,142 - cc_resolv_conf.py[DEBUG]: Skipping module named resolv_conf, no 'manage_resolv_conf' key in configuration And /cloud-init-config on the system in question is empty: # ls /cloud-init-config/ # The cloud.cfg contains: - resolv_conf as a configuration module and the module is executed as expected; from the log: 2018-11-07 10:50:38,142 - cc_resolv_conf.py[DEBUG]: Skipping module named resolv_conf, no 'manage_resolv_conf' key in configuration The cloud.cfg does not contain any information about how to setup resolve.conf and since no data sources are found there is no information about resolve.conf available form the data sources. Therefore, the template file is put in place with no name resolution information. Setting up name resolution is configured with the following syntax: manage_resolv_conf: <true/false> resolv_conf: nameservers: ['8.8.4.4', '8.8.8.8'] searchdomains: - foo.example.com - bar.example.com domain: example.com options: rotate: <true/false> timeout: 1 >From my point of view this is a configuration issue, or a missing data source attachment in the test scenarion, but cloud-init behaves as designed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1114818] New kubeadm NTP screen does not prefill ntp.org pool servers
by bugzilla_noreply＠novell.com 08 Nov '18

08 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1114818 Ladislav Slezák <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS Assignee|yast-internal(a)suse.de |lslezak(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0