November 2020 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 13 Nov '20

13 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c6 --- Comment #6 from Arek P. <ahhhrrreeecccek2710(a)gmail.com> --- I have the same issue... https://forums.opensuse.org/showthread.php/547237-MicroOS-Tumbleweed-Transa… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1175850] MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 13 Nov '20

13 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c5 Arek P. <ahhhrrreeecccek2710(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ahhhrrreeecccek2710(a)gmail.c | |om --- Comment #5 from Arek P. <ahhhrrreeecccek2710(a)gmail.com> --- Created attachment 843582 --> http://bugzilla.opensuse.org/attachment.cgi?id=843582&action=edit Logs -- 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＠suse.com 08 Nov '20

08 Nov '20

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.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.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.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! security enhancement: no setuid -> http://bugzilla.suse.com/show_bug.cgi?id=1171174 live-add-yast-repos: uses openSUSE-release -> http://bugzilla.suse.com/show_bug.cgi?id=1172100 transactional-update: warn about reboot etc. -> http://bugzilla.suse.com/show_bug.cgi?id=1173261 Installing kubeadm<next> shouldn't require installing kubelet<next> -> http://bugzilla.suse.com/show_bug.cgi?id=1175523 Installing kubeadm<next> shouldn't care about cri-tools -> http://bugzilla.suse.com/show_bug.cgi?id=1175524 MicroOS Desktop can't reboot? -> http://bugzilla.suse.com/show_bug.cgi?id=1175850 transactional-update: Notification on failing update -> http://bugzilla.suse.com/show_bug.cgi?id=1176882 k8s missing apimachinery version data -> http://bugzilla.suse.com/show_bug.cgi?id=1177289 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 -- 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] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 01 Nov '20

01 Nov '20

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.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.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.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! security enhancement: no setuid -> http://bugzilla.suse.com/show_bug.cgi?id=1171174 live-add-yast-repos: uses openSUSE-release -> http://bugzilla.suse.com/show_bug.cgi?id=1172100 transactional-update: warn about reboot etc. -> http://bugzilla.suse.com/show_bug.cgi?id=1173261 Installing kubeadm<next> shouldn't require installing kubelet<next> -> http://bugzilla.suse.com/show_bug.cgi?id=1175523 Installing kubeadm<next> shouldn't care about cri-tools -> http://bugzilla.suse.com/show_bug.cgi?id=1175524 MicroOS Desktop can't reboot? -> http://bugzilla.suse.com/show_bug.cgi?id=1175850 transactional-update: Notification on failing update -> http://bugzilla.suse.com/show_bug.cgi?id=1176882 k8s missing apimachinery version data -> http://bugzilla.suse.com/show_bug.cgi?id=1177289 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 -- To unsubscribe, e-mail: kubic-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kubic-bugs+owner(a)opensuse.org

1 0