November 2018 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[kubic-bugs] [Bug 1114447] New: [20181101] transactional-updates: line 707: [: single: integer expression expected
by bugzilla_noreply＠novell.com 07 Nov '18

07 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1114447 Bug ID: 1114447 Summary: [20181101] transactional-updates: line 707: [: single: integer expression 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://openqa.opensuse.org/tests/785870#step/transactional_update/120 Since snapshot 1101, t-u fails to operate: transactional-update 2.10 started Options: rollback single Separate /var detected. Separate /etc detected. /usr/sbin/transactional-update: line 707: [: single: integer expression expected Rollback to snapshot single... transactional-update finished trup-1- A very possible cause for this error is snapper 0.8 update that landed in snapshot 1101 -- You are receiving this mail because: You are the assignee for the bug.

1 3

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

06 Nov '18

1 0

[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 1114455] New: [20181101] kubeadm_base installation failed
by bugzilla_noreply＠novell.com 05 Nov '18

05 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1114455 Bug ID: 1114455 Summary: [20181101] kubeadm_base installation failed 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openQA test user_settings_root is failing with a yast error https://openqa.opensuse.org/tests/785871#step/user_settings_root/2 10:29 < jreidinger> DimStar: looks like some rpm is missing? 2018-11-02 09:06:53 <3> install(3329) [Interpreter] installation/select_system_role.rb:174 Can't find YCP client component inst_kubic_kubeadm_role: No such file or directory -- You are receiving this mail because: You are the assignee for the bug.

1 3

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

04 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 1104598] /etc/crictl.yaml owned by wrong package (cri-o not cri-tools)
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.novell.com/show_bug.cgi?id=1104598 SMASH SMASH <smash_bz(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| | maint:planned:update -- You are receiving this mail because: You are on the CC list for the bug.

1 0