August 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 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 1105992] Transactional-Update broken in snapshot 20180824
by bugzilla_noreply＠novell.com 30 Aug '18

30 Aug '18

http://bugzilla.suse.com/show_bug.cgi?id=1105992 http://bugzilla.suse.com/show_bug.cgi?id=1105992#c5 --- Comment #5 from Ignaz Forster <iforster(a)suse.com> --- As this bug was blocking the next Tumbleweed snapshot I confined myself to fixing the regular expression and kept the current behaviour. *Using* the new attribute to detect the number of to be installed packages will be available in the next version, as only this attribute can guarantee we actually detect every change (e.g. updates of metapackages where the size of the installed packages won't change). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1105992] Transactional-Update broken in snapshot 20180824
by bugzilla_noreply＠novell.com 30 Aug '18

30 Aug '18

http://bugzilla.suse.com/show_bug.cgi?id=1105992 http://bugzilla.suse.com/show_bug.cgi?id=1105992#c4 --- Comment #4 from Thorsten Kukuk <kukuk(a)suse.com> --- The fix is not really correct (see https://trello.com/c/WPmWWpIx/60-transactional-update-parse-new-zypper-valu…) If the attribute "packages-to-change" exist, we should use that to find out, if there are pending updates. If this attribute does not exist, we should fall back to the current attributes (which means best guess, which could go wrong). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1105992] Transactional-Update broken in snapshot 20180824
by bugzilla_noreply＠novell.com 27 Aug '18

27 Aug '18

http://bugzilla.suse.com/show_bug.cgi?id=1105992 http://bugzilla.suse.com/show_bug.cgi?id=1105992#c3 --- Comment #3 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1105992) was mentioned in https://build.opensuse.org/request/show/631811 15.0 / transactional-update -- 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 26 Aug '18

26 Aug '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 -- 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 1087891] no python3 mysql module available which works with salt.
by bugzilla_noreply＠novell.com 24 Aug '18

24 Aug '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 http://bugzilla.suse.com/show_bug.cgi?id=1087891#c56 --- Comment #56 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2018:2504-1: An update that has 23 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1057635,1072599,1087055,1087581,1087891,1089526,1092161,1094055,1095507,1096514,1097174,1097413,1098394,1099323,1099460,1099945,1100142,1100225,1100697,1101812,1101880,1102218,1102265 CVE References: Sources used: openSUSE Leap 15.0 (src): salt-2018.3.0-lp150.3.6.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1105484] New: Error during installation: Snapshot20180815
by bugzilla_noreply＠novell.com 21 Aug '18

21 Aug '18

http://bugzilla.suse.com/show_bug.cgi?id=1105484 Bug ID: 1105484 Summary: Error during installation: Snapshot20180815 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: --- Created attachment 780299 --> http://bugzilla.suse.com/attachment.cgi?id=780299&action=edit First error Received two different error during installation. See the two screenshots attached. I am also attaching the y2logs VM is KVM/OpenSUSE 42.3 with 8G RAM -- You are receiving this mail because: You are the assignee for the bug.

1 4

[kubic-bugs] [Bug 1087891] no python3 mysql module available which works with salt.
by bugzilla_noreply＠novell.com 20 Aug '18

20 Aug '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 http://bugzilla.suse.com/show_bug.cgi?id=1087891#c55 --- Comment #55 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2018:2462-1: An update that has 23 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1057635,1072599,1087055,1087581,1087891,1089526,1092161,1094055,1095507,1096514,1097174,1097413,1098394,1099323,1099460,1099945,1100142,1100225,1100697,1101812,1101880,1102218,1102265 CVE References: Sources used: SUSE Linux Enterprise Module for Server Applications 15 (src): salt-2018.3.0-5.9.1 SUSE Linux Enterprise Module for Basesystem 15 (src): salt-2018.3.0-5.9.1 -- 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 19 Aug '18

19 Aug '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 -- 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 1099700] Kubic snapshot 20180618: Bootstrap Kubernetes cluster failed
by bugzilla_noreply＠novell.com 14 Aug '18

14 Aug '18

http://bugzilla.suse.com/show_bug.cgi?id=1099700 http://bugzilla.suse.com/show_bug.cgi?id=1099700#c2 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Thorsten Kukuk <kukuk(a)suse.com> --- As announced in the kubic blog, we will switch to kubeadm. *** This bug has been marked as a duplicate of bug 1103906 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

14 Aug '18

http://bugzilla.suse.com/show_bug.cgi?id=1103906 http://bugzilla.suse.com/show_bug.cgi?id=1103906#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias.eliasson(a)gmail.com --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- *** Bug 1099700 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1089871] New: Cluster node vanishes in velum after accepting it
by bugzilla_noreply＠novell.com 14 Aug '18

14 Aug '18

http://bugzilla.suse.com/show_bug.cgi?id=1089871 Bug ID: 1089871 Summary: Cluster node vanishes in velum after accepting it Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kubic Assignee: containers-bugowner(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- Kubic with all salt and container fixes (image from https://build.opensuse.org/project/monitor/devel:CaaSP:1.0) You can: connect to velum create account login Start cluster nodes which connect to this server Accept Cluster nodes in velum -> cluster nodes are no longer visible in velum But: login to salt-master container, salt-key will list the cluster nodes as accepted. That's currently blocking all further deployment testing and work. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[kubic-bugs] [Bug 1084149] Introduce read-only-root-fs system_role in Leap 15 and Tumbleweed
by bugzilla_noreply＠novell.com 14 Aug '18

14 Aug '18

http://bugzilla.suse.com/show_bug.cgi?id=1084149 http://bugzilla.suse.com/show_bug.cgi?id=1084149#c2 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Thorsten Kukuk <kukuk(a)suse.com> --- I think this is done. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1104598] New: /etc/crictl.yaml owned by wrong package (cri-o not cri-tools)
by bugzilla_noreply＠novell.com 13 Aug '18

13 Aug '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1104598 Bug ID: 1104598 Summary: /etc/crictl.yaml owned by wrong package (cri-o not cri-tools) 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: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org, vrothberg(a)suse.com Found By: --- Blocker: --- CC: vrothberg(a)suse.com Flags: needinfo?(vrothberg(a)suse.com) /etc/crictl.yaml is consumed by the crictl binary provided by cri-tools But /etc/crictl.yml is currently packaged as part of cri-o This seems very wrong to me And also has very real world issues - as crictl on Kubic is constantly complaining about the deprecated syntax for it's container runtime endpoint, which should be unix:///var/run/crio/crio.sock not the current /var/run/crio/crio.sock 2 Solutions are possible Option a) get crictl.yaml packaged in cri-tools instead or b) get cri-o packaged in devel:kubic and caught up with the respective cri-tools version to solve this discrepency Valentin, which do you prefer? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

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

12 Aug '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 Introduce read-only-root-fs system_role in Leap 15 and Tumbleweed -> http://bugzilla.novell.com/show_bug.cgi?id=1084149 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 Kubic snapshot 20180618: Bootstrap Kubernetes cluster failed -> http://bugzilla.novell.com/show_bug.cgi?id=1099700 -- 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 1102825] New: [Build 20180726]
by bugzilla_noreply＠novell.com 07 Aug '18

07 Aug '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1102825 Bug ID: 1102825 Summary: [Build 20180726] 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: --- Found by openQA: https://openqa.opensuse.org/tests/714799#step/first_boot/3 The test scenario MicroOS-autoyast-generated@64bit-4G-HD40G fails to perform the login after installation. Is it not clear when this issue started (or if it ever worked): that test was wrongly chained after MicroOS-plain, which failed and as a result this very test had been skipped in the past, leaving us without test results. Please investigate if this is a Product issue (autoyast installation broken) or if the test code needs be updated -- 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 05 Aug '18

05 Aug '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 Introduce read-only-root-fs system_role in Leap 15 and Tumbleweed -> http://bugzilla.novell.com/show_bug.cgi?id=1084149 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 Kubic snapshot 20180618: Bootstrap Kubernetes cluster failed -> http://bugzilla.novell.com/show_bug.cgi?id=1099700 [Build 20180726] -> http://bugzilla.novell.com/show_bug.cgi?id=1102825 -- 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 1087891] no python3 mysql module available which works with salt.
by bugzilla_noreply＠novell.com 02 Aug '18

02 Aug '18

http://bugzilla.suse.com/show_bug.cgi?id=1087891 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:7664:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0