January 2020 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[kubic-bugs] [Bug 1153687] New: Zypper repo name detection broken
by bugzilla_noreply＠novell.com 24 Nov '21

24 Nov '21

http://bugzilla.suse.com/show_bug.cgi?id=1153687 Bug ID: 1153687 Summary: Zypper repo name detection broken 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- zypper ar obs://some:where/ results in a URL such as https://download.opensuse.org/repositories/some:/where/openSUSE-MicroOS-201… -- You are receiving this mail because: You are the assignee for the bug.

2 16

[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 1140472] transactional-update causes undefined behaviour of overlayfs
by bugzilla_noreply＠novell.com 28 Jan '20

28 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1140472 http://bugzilla.opensuse.org/show_bug.cgi?id=1140472#c1 --- Comment #1 from Ignaz Forster <iforster(a)suse.com> --- This is referring to https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt, section "Changes to underlying filesystems": "Changes to the underlying filesystems while part of a mounted overlay filesystem are not allowed. If the underlying filesystem is changed, the behavior of the overlay is undefined, though it will not result in a crash or deadlock." Practice shows that changes done to the currently active system will usually not be visible to the update environment, but there's no guarantee. In the worst case it may happen that files from the live system that were changed after snapshot creation could be visible during an update already. It should be added that those files would be visible on next boot anyway, but it may influence e.g. scripts that don't expect the different contents. (Example: A package gets a major version update with a new configuration file; after package installation a script tries to customize some values; while the package was installing the same configuration file was changed in the live environment; if the file leaked into the update environment the customization script may operate on the wrong version of the configuration file.) Unfortunately there is currently no way to formalize the behavior. My original thought to use overlay snapshots (https://github.com/amir73il/overlayfs/wiki/Snapshots-HOWTO) also won't work, as those have the same limitation. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1162036] New: t-u bootloader pkg in still updates the bootloader even if zypper already fails
by bugzilla_noreply＠novell.com 28 Jan '20

28 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1162036 Bug ID: 1162036 Summary: t-u bootloader pkg in still updates the bootloader even if zypper already fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: iforster(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- Running transactional-update grub2.cfg pkg in asdf Tries to install asdf, which fails, then it runs grub2-mkconfig but immediately afterwards deletes the snapshot again as pkg in failed. Same applies to t-u bootloader: # transactional-update bootloader pkg in asdf Checking for newer version. transactional-update 2.20.1 started Options: bootloader pkg in asdf Separate /var detected. /etc on overlayfs detected. Calling zypper install Loading repository data... Reading installed packages... 'asdf' not found in package names. Trying capabilities. No provider of 'asdf' found. Resolving package dependencies... Nothing to do. ERROR: zypper install on /tmp/tmp.8LZ0NPgPHI failed with exit code 104! Creating a new grub2 config Generating grub configuration file ... Found theme: /boot/grub2/themes/openSUSE/theme.txt Found linux image: /boot/vmlinuz-5.4.14-6-kvmsmall Found initrd image: /boot/initrd-5.4.14-6-kvmsmall Found linux image: /boot/vmlinuz-5.4.13-1-default Found initrd image: /boot/initrd-5.4.13-1-default done Writing new bootloader Removing snapshot #8... Removing overlay directory /var/lib/overlay/8... transactional-update finished -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

26 Jan '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.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 Tumbleweed packages not visible in MicroOS installer -> http://bugzilla.novell.com/show_bug.cgi?id=1137460 kubelet.service tries to start even without config file -> http://bugzilla.novell.com/show_bug.cgi?id=1146372 Zypper repo name detection broken -> http://bugzilla.novell.com/show_bug.cgi?id=1153687 Terminal input over SSH breaks with non-en UTF-8 locale -> http://bugzilla.novell.com/show_bug.cgi?id=1156175 rebootmgrctl set-strategy off does not switch off rebooting -> http://bugzilla.novell.com/show_bug.cgi?id=1156509 MicroOS/Kubic images: btrfs-balance does not work, read-only root filesystem -> http://bugzilla.novell.com/show_bug.cgi?id=1159230 -- 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 1161289] New: Multi-Master setup: upgrade from 1.16.x to 1.17.0 breaks cluster (update order)
by bugzilla_noreply＠novell.com 20 Jan '20

20 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1161289 Bug ID: 1161289 Summary: Multi-Master setup: upgrade from 1.16.x to 1.17.0 breaks cluster (update order) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major 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: --- I have a multi-master setup: 1x loadbalancer (haproxy) 3x master 3x worker With the update to kubelet 1.17.0 and still on the control-plane 1.16.3, the cluster broke, all machines with kubelet 1.17.0 couldn't join the cluster anymore. On the other side, an upgrade was only possible with kubeadm 1.17.0 So I had to: rollback whole cluster to kubelet 1.16.3 update to kubeadm 1.17.0 on all machines update control-plane and all nodes to 1.17.0 update kubelet to 1.17.0 So as described in the kubernetes upgrade documentation. Looks like we need to install the old and new kubelet in parallel until we migrated the cluster. -- 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 19 Jan '20

19 Jan '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.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 Tumbleweed packages not visible in MicroOS installer -> http://bugzilla.novell.com/show_bug.cgi?id=1137460 kubelet.service tries to start even without config file -> http://bugzilla.novell.com/show_bug.cgi?id=1146372 Zypper repo name detection broken -> http://bugzilla.novell.com/show_bug.cgi?id=1153687 Terminal input over SSH breaks with non-en UTF-8 locale -> http://bugzilla.novell.com/show_bug.cgi?id=1156175 rebootmgrctl set-strategy off does not switch off rebooting -> http://bugzilla.novell.com/show_bug.cgi?id=1156509 MicroOS/Kubic images: btrfs-balance does not work, read-only root filesystem -> http://bugzilla.novell.com/show_bug.cgi?id=1159230 -- 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 1146802] kubic image does not call cloud-init
by bugzilla_noreply＠novell.com 19 Jan '20

19 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1146802 http://bugzilla.suse.com/show_bug.cgi?id=1146802#c4 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Thorsten Kukuk <kukuk(a)suse.com> --- No answer, assumes it works. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1143813] New: kubelet sometimes starting too fast
by bugzilla_noreply＠novell.com 13 Jan '20

13 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1143813 Bug ID: 1143813 Summary: kubelet sometimes starting too fast 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: --- kubelet is sometimes starting to fast, before wicked did setup the network fully, including the real hostname. In this cases, kubelet uses "localhost", which of course will fail. -- You are receiving this mail because: You are the assignee for the bug.

1 5

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

12 Jan '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.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 Tumbleweed packages not visible in MicroOS installer -> http://bugzilla.novell.com/show_bug.cgi?id=1137460 kubelet.service tries to start even without config file -> http://bugzilla.novell.com/show_bug.cgi?id=1146372 kubic image does not call cloud-init -> http://bugzilla.novell.com/show_bug.cgi?id=1146802 Zypper repo name detection broken -> http://bugzilla.novell.com/show_bug.cgi?id=1153687 Terminal input over SSH breaks with non-en UTF-8 locale -> http://bugzilla.novell.com/show_bug.cgi?id=1156175 rebootmgrctl set-strategy off does not switch off rebooting -> http://bugzilla.novell.com/show_bug.cgi?id=1156509 MicroOS/Kubic images: btrfs-balance does not work, read-only root filesystem -> http://bugzilla.novell.com/show_bug.cgi?id=1159230 -- To unsubscribe, e-mail: kubic-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kubic-bugs+owner(a)opensuse.org

1 0