February 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 1162432] New: conmon binary lacks journald support (Devel:Kubic repo)
by bugzilla_noreply＠novell.com 27 Apr '20

27 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1162432 Bug ID: 1162432 Summary: conmon binary lacks journald support (Devel:Kubic repo) 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: jobbara.artalmatlan(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I have been using the Devel:Kubic repo in OpenSUSE Leap 15.1 for getting recent releases of podman. Today I tried to use journald logging driver but it failed. It reports missing journald support. See error message below. I found a similar issue regarding Ubuntu [2], which indicates it is a build time flag to have it enabled and downstream distros should build the binary that way. If I understood it correctly. Steps of reproduction: 1) install podman from Devel:Kubic repo # podman pod create --name test # podman run -d --name example --expose 80 --expose 443 --pod test --log-driver journald --log-opt tag="nginx|{{.ImageName}}|podman" nginx:1.16 [conmon:e] Include journald in compilation path to log to systemd journal Error: write child: broken pipe # echo $? 126 # rpm -qa | egrep "podman|conmon" conmon-2.0.10-lp151.21.1.x86_64 podman-cni-config-1.7.0-lp151.4.1.noarch podman-1.7.0-lp151.4.1.x86_64 [1] http://download.opensuse.org/repositories/devel:/kubic/openSUSE_Leap_15.1/ [2] https://github.com/containers/conmon/issues/67 Let me know how can I help further. Best regards, Balázs NÉMETH -- You are receiving this mail because: You are the assignee for the bug.

1 4

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

23 Feb '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 Multi-Master setup: upgrade from 1.16.x to 1.17.0 breaks cluster (update order) -> http://bugzilla.novell.com/show_bug.cgi?id=1161289 conmon binary lacks journald support (Devel:Kubic repo) -> http://bugzilla.novell.com/show_bug.cgi?id=1162432 Introduce MicroOS Desktop -> http://bugzilla.novell.com/show_bug.cgi?id=1163453 -- 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 1163328] New: Kubic Installer System Role should not disable ip_forward by default
by bugzilla_noreply＠novell.com 19 Feb '20

19 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1163328 Bug ID: 1163328 Summary: Kubic Installer System Role should not disable ip_forward 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: zzhou(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My first time to play with Kubic. At the first impression, looks like, by default, Installer System Role (eg. kubeadm) disable ip_forward in Network Configuration. After installation, grep -r ip_forward /etc/sysctl.d /etc/sysctl.d/70-yast.conf:net.ipv4.ip_forward = 0 which overrides /usr/lib/sysctl.d/50-kubeadm.conf basically, cat /usr/lib/sysctl.d/50-kubeadm.conf net.ipv4.ip_forward = 1 As workaround, I have to manually delete 70-yast.conf, or enable ip_forward in Installer. [1] Otherwise, kubeadm init will suffer [ERROR FileContent--proc-sys-net-ipv4-ip_forward] [1] https://github.com/kubernetes/kubeadm/issues/1062 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1163967] New: Ignition: Set rd.neednet=1 only on demand
by bugzilla_noreply＠novell.com 17 Feb '20

17 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1163967 Bug ID: 1163967 Summary: Ignition: Set rd.neednet=1 only on demand Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: iforster(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently Ignition statically sets rd.neednet=1 on first run. However for most platforms this is not needed, including the most commonly used "metal" platform, and setting up a network during initrd is quite error prone, leading to an emergency shell in case something goes wrong. To optimize this add a dracut module running during the cmdline stage and check whether the selected ignition platform or configuration requires network, and only add 'rd.neednet=1 ip=dhcp' when this is the case. -- 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 16 Feb '20

16 Feb '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 Multi-Master setup: upgrade from 1.16.x to 1.17.0 breaks cluster (update order) -> http://bugzilla.novell.com/show_bug.cgi?id=1161289 conmon binary lacks journald support (Devel:Kubic repo) -> http://bugzilla.novell.com/show_bug.cgi?id=1162432 -- 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 1163453] Introduce MicroOS Desktop
by bugzilla_noreply＠novell.com 12 Feb '20

12 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1163453 http://bugzilla.suse.com/show_bug.cgi?id=1163453#c3 --- Comment #3 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1163453) was mentioned in https://build.opensuse.org/request/show/773808 Factory / patterns-microos -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1163453] New: Introduce MicroOS Desktop
by bugzilla_noreply＠novell.com 12 Feb '20

12 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1163453 Bug ID: 1163453 Summary: Introduce MicroOS Desktop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is the tracker bug for introducing the MicroOS Desktop into Factory/Tumbleweed https://hackweek.suse.com/projects/microos-desktop Current Steps In Progress at Time of Writing: * Submit new skelcd-control-MicroOS to YaST>Factory * Submit new microos-patterns to Factory * Ensure product builds media with new patterns-microos-[gnome|kde]-desktop patterns At this point MicroOS ISO's should have both a KDE and GNOME system role in 'Alpha' status Steps that must be accomplished to reach 'Beta' * Some openQA testing * Basic working functionality like logging in, application installation, etc Steps to remove the ugly 'Alpha' or 'Beta' flag from the installation * openQA testing for boot, login, application installation and some apps running * No unexpected reboots/sensible rebootmgr configuration * Notification to the user when a reboot is required The above steps can be added to in comments here and/or will be tracked on the linked Hackweek Page -- You are receiving this mail because: You are the assignee for the bug.

1 2

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

09 Feb '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 Multi-Master setup: upgrade from 1.16.x to 1.17.0 breaks cluster (update order) -> http://bugzilla.novell.com/show_bug.cgi?id=1161289 -- To unsubscribe, e-mail: kubic-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kubic-bugs+owner(a)opensuse.org

1 0