January 2019 - openSUSE Kubic Bugs - openSUSE Mailing Lists

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

27 Jan '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! kubic.opensuse.org needs prominent link to Portal:Kubic wiki -> http://bugzilla.novell.com/show_bug.cgi?id=1119359 Define labels for openSUSE containers -> http://bugzilla.novell.com/show_bug.cgi?id=1119378 Upstream kubeadm page does not list openSUSE Kubic as supported platform -> http://bugzilla.novell.com/show_bug.cgi?id=1119508 Not possible to login to Kubic/MicroOS anymore via ssh -> http://bugzilla.novell.com/show_bug.cgi?id=1119511 -- 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 1122799] New: Tumbleweed base container on hub.docker.com broken, contains 2 layers, 1 expected
by bugzilla_noreply＠novell.com 22 Jan '19

22 Jan '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1122799 Bug ID: 1122799 Summary: Tumbleweed base container on hub.docker.com broken, contains 2 layers, 1 expected 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: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dimstar(a)opensuse.org, fvogt(a)suse.com Found By: --- Blocker: --- https://openqa.opensuse.org/tests/835073#step/podman/43 This error happens also on previous Tumbleweed snapshots that were green, confirming that the issue is with the delivered base container opensuse/tumbleweed:latest from hub.docker.com I've even confirmed it manually to make sure that absolutely without a shadow of a doubt previously green podman versions are now broken with the current tumbleweed container. Therefore, this issue was almost certainly introduced in snapshot 0115's base container image This issue cannot be reproduced with the current leap containers, even with the 0121 snapshot, so I am 100% certain than the problem is not anything on the media. Dominique, that means I'm comfortable with TTM ignoring this for the purposes of releasing the snapshot - the broken image is already out there. Fabian - HELP! :) Bug marked as critical because it does mask some of the testing done by openQA, but for now I can supplement that with manual testing -- 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 20 Jan '19

20 Jan '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! kubic.opensuse.org needs prominent link to Portal:Kubic wiki -> http://bugzilla.novell.com/show_bug.cgi?id=1119359 Upstream kubeadm page does not list openSUSE Kubic as supported platform -> http://bugzilla.novell.com/show_bug.cgi?id=1119508 Not possible to login to Kubic/MicroOS anymore via ssh -> http://bugzilla.novell.com/show_bug.cgi?id=1119511 -- 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 1122296] openSUSE:Factory/kubic-kured-image is unresolvable for i586
by bugzilla_noreply＠novell.com 18 Jan '19

18 Jan '19

http://bugzilla.suse.com/show_bug.cgi?id=1122296 http://bugzilla.suse.com/show_bug.cgi?id=1122296#c3 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Thorsten Kukuk <kukuk(a)suse.com> --- I added the line and made more adjustements. I hope it works now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1122296] openSUSE:Factory/kubic-kured-image is unresolvable for i586
by bugzilla_noreply＠novell.com 18 Jan '19

18 Jan '19

http://bugzilla.suse.com/show_bug.cgi?id=1122296 http://bugzilla.suse.com/show_bug.cgi?id=1122296#c2 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fvogt(a)suse.com) | --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Thorsten Kukuk from comment #1) > Fabian, any idea how we can say that the container cannot build on i586, > since kubernetes does not exist there? OBS supports a comment in form of:  kubernetes uses ExcludeArch: %ix86 s390 while go has ExclusiveArch. I'm not sure which one fits best here, be conservative and only build the archs kubic is built on:  Or try to build everything except known broken:  -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1122296] openSUSE:Factory/kubic-kured-image is unresolvable for i586
by bugzilla_noreply＠novell.com 18 Jan '19

18 Jan '19

http://bugzilla.suse.com/show_bug.cgi?id=1122296 http://bugzilla.suse.com/show_bug.cgi?id=1122296#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com Flags| |needinfo?(fvogt(a)suse.com) --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- Fabian, any idea how we can say that the container cannot build on i586, since kubernetes does not exist there? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1122296] New: openSUSE:Factory/kubic-kured-image is unresolvable for i586
by bugzilla_noreply＠novell.com 17 Jan '19

17 Jan '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1122296 Bug ID: 1122296 Summary: openSUSE:Factory/kubic-kured-image is unresolvable for i586 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://build.opensuse.org/package/show/openSUSE:Factory/kubic-kured-image -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1122154] New: openssh-askpass always pulled in with an update
by bugzilla_noreply＠novell.com 16 Jan '19

16 Jan '19

http://bugzilla.suse.com/show_bug.cgi?id=1122154 Bug ID: 1122154 Summary: openssh-askpass always pulled in with an update 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: --- openssh-askpass has a wrong split provides, that file was not removed from openssh. So it always matches and as result, openssh-askpass will always be pulled in again. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1122024] New: [Build20190112] Podman containers have no network after CNI configured for kubeadm cluster
by bugzilla_noreply＠novell.com 16 Jan '19

16 Jan '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1122024 Bug ID: 1122024 Summary: [Build20190112] Podman containers have no network after CNI configured for kubeadm cluster 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: --- https://openqa.opensuse.org/tests/831669#step/podman/24 After installing kubeadm and setting up flannel CNI using the https://en.opensuse.org/Kubic:kubeadm approach, podman containers should inherit that CNI config and use it with a CNI network Instead, there seems to be some form of incompatibility between the kubeadm flannel CNI and Podmans expectations Error message from a "podman container run hello-world" error parsing CNI plugin result "IP4:{IP:{IP:10.244.0.3 Mask:ffffff00} Gateway:10.244.0.1 Routes:[{Dst:{IP:10.244.0.0 Mask:ffff0000} GW:10.244.0.1} {Dst:{IP:0.0.0.0 Mask:00000000} GW:10.244.0.1}]}, DNS:{Nameservers:[] Domain: Search:[] Options:[]}": cannot convert version ["" "0.1.0" "0.2.0"] to 0.4.0: cannot convert version ["" "0.1.0" "0.2.0"] to 0.4.0 Suspicion is that podman requires a CNI config of version 0.4.0 but flannel is providing a version 0.1.0/0.2.0 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1121910] New: [Build 20190111] podman test failed: Error configuring network
by bugzilla_noreply＠novell.com 14 Jan '19

14 Jan '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1121910 Bug ID: 1121910 Summary: [Build 20190111] podman test failed: Error configuring network 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: --- openQA reported an error in the podman test: https://openqa.opensuse.org/tests/830808#step/podman/24 It reports: error configuring network namespace for container <ID> : Missing CNI default network -- You are receiving this mail because: You are the assignee for the bug.

1 1