April 2019 - 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 1115000] New: cloud-init in TW snapshots 1105 and 1106 do not populate /etc/resolv.conf
by bugzilla_noreply＠novell.com 26 Sep '19

26 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1115000 Bug ID: 1115000 Summary: cloud-init in TW snapshots 1105 and 1106 do not populate /etc/resolv.conf Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Tools Assignee: public-cloud-maintainers(a)suse.de Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- cloud-init do not seem to correctly populate /etc/resolv.conf After a boot of Kubic with the kubeadm system role, the resulting /etc/resolv.conf has "; Created by cloud-init on instance boot automatically, do not edit" followed by the usual "### /etc/resolv.conf file autogenerated by netconfig" preamble, but has no name resolver configured This results in a system that has no working name resolution https://openqa.opensuse.org/tests/788925#step/first_boot/23 All other networking seems to behave fine EXPECTED BEHAVIOUR cloud-init should correctly populate /etc/resolv.conf when configuring the network of a system WORKAROUND docker automatically disables cloud-inits network configuration by editing /etc/cloud/cloud.cfg.d/01-network.cfg - for non-docker runtimes Kubic intends to do something similar until this bug is fixed at least. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[kubic-bugs] [Bug 1114818] New: New kubeadm NTP screen does not prefill ntp.org pool servers
by bugzilla_noreply＠novell.com 30 Jul '19

30 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1114818 Bug ID: 1114818 Summary: New kubeadm NTP screen does not prefill ntp.org pool servers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: rbrown(a)suse.com QA Contact: jsrain(a)suse.com CC: kubic-bugs(a)opensuse.org, lslezak(a)suse.com Found By: --- Blocker: --- The new kubeadm NTP screen in Kubic does not correctly prefil the NTP server field as described in https://en.opensuse.org/Kubic:CaaSPInstallationComparision EXPECTED BEHAVIOUR: "NTP server (chrony) (prefill field with dhcp answer, if there is no dhcp, prefill with ntp pool server if allowed, else leave empty and warn if it stays empty, no hard error)" ACTUAL BEHAVIOUR: NTP Server field does prefil with DHCP answer when it's available, but when it's not available it does not prefill with ntp.org pool servers (eg. 0.opensuse.pool.ntp.org, 1.opensuse.pool.ntp.org, 2.opensuse.pool.ntp.org, etc) Also, there is a cosmetic error - the screen says "Admin node configuration" when it should say "kubeadm node configuration" (the kubeadm nodes are not always admin nodes) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[kubic-bugs] [Bug 1132436] New: /srv should be an own subvolume
by bugzilla_noreply＠novell.com 12 Jun '19

12 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1132436 Bug ID: 1132436 Summary: /srv should be an own subvolume 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: --- /srv should contain user data to serve somehow. Like /srv/salt or /srv/www. To make this possible, /srv should be an own subvolume and writeable. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1131700] New: Make separate MicroOS media
by bugzilla_noreply＠novell.com 07 May '19

07 May '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1131700 Bug ID: 1131700 Summary: Make separate MicroOS media 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: --- MicroOS deserves it's own media -- You are receiving this mail because: You are the assignee for the bug.

1 2

[kubic-bugs] [Bug 1107283] New: Don't create /cloud-init-config subvolume by default
by bugzilla_noreply＠novell.com 06 May '19

06 May '19

http://bugzilla.suse.com/show_bug.cgi?id=1107283 Bug ID: 1107283 Summary: Don't create /cloud-init-config subvolume by default 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 CC: fvogt(a)suse.com Found By: --- Blocker: --- /cloud-init-config makes only sense if customers create their own, golden images which contain a cloud-init configuration from the beginning. On YaST, autoyast installed or with our kiwi by us created images, this subvolume does not make much sense, as the user has to boot and login at first to create the config files in this directory. So it makes no sense to provide that directory by default. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kubic-bugs] [Bug 1133820] New: health-checker[1697]: crio.sh: line 6: test: 1: unary operator expected
by bugzilla_noreply＠novell.com 30 Apr '19

30 Apr '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1133820 Bug ID: 1133820 Summary: health-checker[1697]: crio.sh: line 6: test: 1: unary operator expected 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: mkravec(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tested with openSUSE-Kubic-DVD-x86_64-Snapshot20190428-Media.iso > # health-checker > health-checker[1854]: Clearing GRUB flag > health-checker[1854]: grub2-editenv: error: cannot open `/boot/grub2/grubenv': Read-only file system. > health-checker[1854]: Starting health check > health-checker[1854]: /usr/lib/health-checker/crio.sh: line 6: test: 1: unary operator expected > health-checker[1854]: active > health-checker[1854]: Health check passed This is SR tracker bug, problem is already fixed in code by commit: https://github.com/kubic-project/health-checker/commit/b7f4808675004d59d612… -- 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＠novell.com 28 Apr '19

28 Apr '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! Upstream kubeadm page does not list openSUSE Kubic as supported platform -> http://bugzilla.novell.com/show_bug.cgi?id=1119508 tmpfiles.d/kubernetes.conf uses legacy path, systemd complaining -> http://bugzilla.novell.com/show_bug.cgi?id=1124129 Make separate MicroOS media -> http://bugzilla.novell.com/show_bug.cgi?id=1131700 /srv should be an own subvolume -> http://bugzilla.novell.com/show_bug.cgi?id=1132436 -- 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 1133514] New: Kubic image for Openstack sometimes couldn't boot
by bugzilla_noreply＠novell.com 26 Apr '19

26 Apr '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1133514 Bug ID: 1133514 Summary: Kubic image for Openstack sometimes couldn't boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: denis.kondratenko(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 803670 --> http://bugzilla.opensuse.org/attachment.cgi?id=803670&action=edit console log I use Openstack stack templates to spawn instances. Most of the time 1 instance couldn't start with this error message in the log: > overlayfs: failed to resolve '/sysroot/var/lib/overlay/1/etc': -2 Image that is used: openSUSE-Tumbleweed-Kubic.x86_64-15.0-kubeadm-cri-o-OpenStack-Cloud-Build7.35.qcow2 from https://build.opensuse.org/package/binaries/openSUSE:Factory/openSUSE-Tumbl… I can't reproduce it by spawning only 1 instance (maybe I haven't tried too many times). How to reproduce: * clone https://github.com/denisok/ceph-kubic-stack * replace images names in ceph-kubic-environment.yaml * openstack stack create -t ./ceph-kubic-stack.yaml -e ./ceph-kubic-environment.yaml --parameter keypair=YYY --wait ceph-kubic-stack * check console log of each instance * try couple of times if not reproduced (but usually reproduced from first shot) -- 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 21 Apr '19

21 Apr '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! Upstream kubeadm page does not list openSUSE Kubic as supported platform -> http://bugzilla.novell.com/show_bug.cgi?id=1119508 tmpfiles.d/kubernetes.conf uses legacy path, systemd complaining -> http://bugzilla.novell.com/show_bug.cgi?id=1124129 /srv should be an own subvolume -> http://bugzilla.novell.com/show_bug.cgi?id=1132436 -- To unsubscribe, e-mail: kubic-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kubic-bugs+owner(a)opensuse.org

1 0