- openSUSE Kubic Bugs

[Bug 1215709] segfault in libglib/libgio/libgobject 2.0.so.0.7800.0 since MicroOS-20230921
by bugzilla_noreply＠suse.com 10 Oct '23

10 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215709 https://bugzilla.suse.com/show_bug.cgi?id=1215709#c4 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |rbrown(a)suse.com Status|NEW |RESOLVED --- Comment #4 from Richard Brown <rbrown(a)suse.com> --- Reported fixed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215709] New: segfault in libglib/libgio/libgobject 2.0.so.0.7800.0 since MicroOS-20230921
by bugzilla_noreply＠suse.com 10 Oct '23

10 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215709 Bug ID: 1215709 Summary: segfault in libglib/libgio/libgobject 2.0.so.0.7800.0 since MicroOS-20230921 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: VMWare OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: dirk.datzert(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869748 --> https://bugzilla.suse.com/attachment.cgi?id=869748&action=edit Hardcopy of the segfault messages After Upgrading to MicroOS-20230921 I see such segfaults pasted in the hardcopy on serveral VM Machines. I can revert to a snapshot from 20230918 and disable transactional-update.timer. Has this segfault seen somewhere else ? I'm running different k3s-version-branches on top of MicroOS and reverted also this to an older release. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1215903] MicroOS: current openstack image not allowing ssh keys to be added on digitalocean
by bugzilla_noreply＠suse.com 06 Oct '23

06 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215903 https://bugzilla.suse.com/show_bug.cgi?id=1215903#c4 --- Comment #4 from Johannes Hölzel <freelancing(a)hoelzel.it> --- so root is locked and the update seems to uninstall container-selinux and consecutively rke2-selinux. I added both manually into my toolchain and now im up and running again. So to sum up the workaround is: - deploy deploy user with cloud-init - install selinux packages separatetly I guess pulling container selinux is fair when using the "Base System" image. Also i have seen that there has been a new iso provided on the 4th so i will check that now too. If anything this shows that we need a dedicated changelog for MicroOS and need to stop treating it as a component of tumbleweed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215903] MicroOS: current openstack image not allowing ssh keys to be added on digitalocean
by bugzilla_noreply＠suse.com 06 Oct '23

06 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215903 https://bugzilla.suse.com/show_bug.cgi?id=1215903#c3 --- Comment #3 from Johannes Hölzel <freelancing(a)hoelzel.it> --- I think there is even more to it. I have currently adapted all my systems to use cloud-init but i can not even get rke2 to work at all. I checked the audit logs for selinux denies but there were none. Something has seriously crippled root and currently there is no way to run rke2 rootless... my current workaround is to deploy a deploy user with cloud-init and the old version then updated right with dup after. ``` users: - name: ${var.deploy_user} sudo: ALL=(ALL) NOPASSWD:ALL ssh_authorized_keys: - ${var.SSH_pub_key} ``` -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215903] MicroOS: current openstack image not allowing ssh keys to be added on digitalocean
by bugzilla_noreply＠suse.com 06 Oct '23

06 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215903 https://bugzilla.suse.com/show_bug.cgi?id=1215903#c2 Klaas Kienemann <k.kienemann(a)theco.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |k.kienemann(a)theco.de --- Comment #2 from Klaas Kienemann <k.kienemann(a)theco.de> --- Same here - I've rolled back to MicroOS 20230927 and deactivated automatic transactional updates: systemctl --now disable transactional-update.timer sshd log output: "User root not allowed because account is locked" I suspect it is related to the libssh-config update in MicroOS 20230929. AFAIK cloud-init writes custom ssh configuration to /etc/ssh/sshd_config and libssh (libssh_server.config) does not parse this file any more. https://build.opensuse.org/request/show/1113627 I would like to enable automatic transactional updates back again. Are there any workarounds for this? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215903] MicroOS: current openstack image not allowing ssh keys to be added on digitalocean
by bugzilla_noreply＠suse.com 04 Oct '23

04 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215903 Johannes Hölzel <freelancing(a)hoelzel.it> changed: What |Removed |Added ---------------------------------------------------------------------------- OS|Other |Mac Alias| |MicroOS:, cloud, init, | |broken, on, digitalocean -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215903] MicroOS: current openstack image not allowing ssh keys to be added on digitalocean
by bugzilla_noreply＠suse.com 04 Oct '23

04 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215903 Johannes Hölzel <freelancing(a)hoelzel.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215903] MicroOS: current openstack image not allowing ssh keys to be added on digitalocean
by bugzilla_noreply＠suse.com 04 Oct '23

04 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215903 https://bugzilla.suse.com/show_bug.cgi?id=1215903#c1 --- Comment #1 from Johannes Hölzel <freelancing(a)hoelzel.it> --- I also took the liberty to check the so called "digialocean image" which was working even worse than the regular opentsack one. ( https://download.opensuse.org/tumbleweed/appliances/openSUSE-MicroOS.x86_64… ) Simply using the image without cloud-init returned this ``` ssh root@... (root(a)164.90.130.104) "System is booting up. Unprivileged users are not permitted to log in yet. Please come back later. For technical details, see pam_nologin(8)." Password: ``` Whilst just providing another ssh key with this: ``` ssh_authorized_keys: - ssh-ed25519 x/P5 x@x ``` left me with ``` ssh: connect to host x.x.x.x port 22: Connection refused ``` Help please, i dont know what else to do at this point -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215903] MicroOS: current openstack image not allowing ssh keys to be added on digitalocean
by bugzilla_noreply＠suse.com 03 Oct '23

03 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215903 Johannes Hölzel <freelancing(a)hoelzel.it> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://download.opensuse.o | |rg/tumbleweed/appliances/op | |enSUSE-MicroOS.x86_64-OpenS | |tack-Cloud.qcow2 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215903] MicroOS: current openstack image not allowing ssh keys to be added on digitalocean
by bugzilla_noreply＠suse.com 03 Oct '23

03 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215903 Johannes Hölzel <freelancing(a)hoelzel.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are the assignee for the bug.

1 0