October 2018 - 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 1107283] New: Don't create /cloud-init-config subvolume by default
by bugzilla_noreply＠novell.com 06 May '19

06 May '19

http://bugzilla.suse.com/show_bug.cgi?id=1107283 Bug ID: 1107283 Summary: Don't create /cloud-init-config subvolume by default 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 CC: fvogt(a)suse.com Found By: --- Blocker: --- /cloud-init-config makes only sense if customers create their own, golden images which contain a cloud-init configuration from the beginning. On YaST, autoyast installed or with our kiwi by us created images, this subvolume does not make much sense, as the user has to boot and login at first to create the config files in this directory. So it makes no sense to provide that directory by default. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kubic-bugs] [Bug 1076265] New: openSUSE-Tumbleweed-Kubic-release will never be updated
by bugzilla_noreply＠novell.com 04 Feb '19

04 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1076265 Bug ID: 1076265 Summary: openSUSE-Tumbleweed-Kubic-release will never be updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dleuenberger(a)suse.com Found By: --- Blocker: --- openSUSE-Tumbleweed-Kubic-release is only on the Kubic media, which means, it will never be updated. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kubic-bugs] [Bug 1105992] New: Transactional-Update broken in snapshot 20180824
by bugzilla_noreply＠novell.com 22 Nov '18

22 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1105992 Bug ID: 1105992 Summary: Transactional-Update broken in snapshot 20180824 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kubic Assignee: iforster(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- 0824 introduced transactional-update 2.6 https://build.opensuse.org/package/rdiff/openSUSE:Factory/transactional-upd… It's failing all tests and appears to be displaying incorrect behaviour https://openqa.opensuse.org/tests/742638#step/transactional_update/57 Compared to 0822 I'm noticing the following differences: https://openqa.opensuse.org/tests/741289#step/transactional_update/57 (note: the code for the test does not appear to have changed: https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/test… ) Update test #2 is meant to be a no-op, because it should be updating when there is nothing to do In 0822 the pointless `cleanup up` test produced the following logs: > # Result: > Checking for newer version. > transactional-update 2.6 started > Options: cleanup up > Separate /var detected. > Adding cleanup algorithm to snapshot #6 > Adding "important=yes" to snapshot #6 > zypper: nothing to update > transactional-update finished > trup-0- In 0824 the exact same test produces the following logs: > # Result: > Checking for newer version. > transactional-update 2.6 started > Options: cleanup up > Separate /var detected. > Adding cleanup algorithm to snapshot #6 > Adding "important=yes" to snapshot #6 > /usr/sbin/transactional-update: line 760: [: too many arguments > Creating read-only snapshot of current system state (#8) > Copying /etc state into snapshot /.snapshots/9/snapshot > Copying /etc state into snapshot /.snapshots/10/snapshot > Calling zypper up > Loading repository data... > Reading installed packages... > > Nothing to do. > Trying to rebuild kdump initrd > Please reboot your machine to activate the changes and avoid data loss. > transactional-update finished > trup-0- I find the following lines in 0824 suspicious, leading me to the questions below: > /usr/sbin/transactional-update: line 760: [: too many arguments Why does txl-upd now complain about too many arguments? > Creating read-only snapshot of current system state (#8) > Copying /etc state into snapshot /.snapshots/9/snapshot > Copying /etc state into snapshot /.snapshots/10/snapshot Why does txl-upd make 3 snapshots (8, 9, 10) even when there is nothing to do? Why does txl-upd make 2 snapshots for /etc? (This is less suspicious, I'm just curious) Bug marked as Major because it makes all of Kubics tests red ;) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[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 1111012] New: cri-o writes log files to /tmp
by bugzilla_noreply＠novell.com 05 Nov '18

05 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1111012 Bug ID: 1111012 Summary: cri-o writes log files to /tmp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: vrothberg(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- cri-o seems to write log files to /tmp. This should never be done, as the name seems to be guessable, it could be a security problem, too. As cri-o is creating several files, I think best would be an own directory /var/log/cri-o -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[kubic-bugs] [Bug 1113779] New: rebootmgrctl: org.opensuse.RebootMgr not provided
by bugzilla_noreply＠novell.com 29 Oct '18

29 Oct '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1113779 Bug ID: 1113779 Summary: rebootmgrctl: org.opensuse.RebootMgr not provided 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://openqa.opensuse.org/tests/783551#step/rebootmgr/19 This is newly failing in openQA (since 1025) A very likely candidate is a mis-generation of the DVD (ghc-bootstrap 'masked' libffi, which seems to have killed cloud-init); snapshot 1029 should address this -- 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 28 Oct '18

28 Oct '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