July 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 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 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 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 29 Jul '18

29 Jul '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] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 22 Jul '18

22 Jul '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] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 15 Jul '18

15 Jul '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 1100868] Can't start server with Kubic OpenStack images
by bugzilla_noreply＠novell.com 11 Jul '18

11 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=1100868 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kubic-bugs(a)opensuse.org |fvogt(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1100868] New: Can't start server with Kubic OpenStack images
by bugzilla_noreply＠novell.com 11 Jul '18

11 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1100868 Bug ID: 1100868 Summary: Can't start server with Kubic OpenStack images 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: pgonin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- using images from: https://download.opensuse.org/repositories/devel:/CaaSP:/images/images/ with both openSUSE-Tumbleweed-Kubic.x86_64-15.0-CaaSP-Stack-OpenStack-Cloud-Build8.79.qcow2 and openSUSE-Tumbleweed-Kubic.x86_64-15.0-MicroOS-OpenStack-Cloud-Build8.13.qcow2 I am unable to start a server. It fails at first boot with final error message: Cannot open access to console, the root account is locked. See sulogin(8) man page for more details. Press Enter to continue. -- You are receiving this mail because: You are the assignee for the bug.

1 2