2026-05-09T05:01:43  <matrix-o-o> <e73va> Mailing list does show correct number of replys.
2026-05-09T05:03:10  <matrix-o-o> <e73va> Thread "Tumbleweed - Review of the weeks 2026/18 & 19" has 3 replies. Showed as 0 in the list.
2026-05-09T15:48:28  <acidsys> falkor leap 16 upgrade is in a bit of a liimbo. amazing how I can find zero information in Leap or SLE release notes or HA documentation about how to safely migrate corosync 2 to corosync 3
2026-05-09T15:54:52  <acidsys> https://lists.clusterlabs.org/pipermail/users/2020-June/027245.html suggests I should migrate everything to a second cluster :D
2026-05-09T16:54:21  <acidsys> and the next problem, libvirtd appears to no longer be built with_apparmor "libvirtd[63589]: internal error: Security driver apparmor not found" ...
2026-05-09T16:56:19  <acidsys> do we need to branch SUSE:SLFO:1.2/libvirt into o:i and set it in our prjconf ? :-(
2026-05-09T17:12:41  <cboltz> great :-/
2026-05-09T17:13:12  <cboltz> I'd try a bugreport first, but in worst case we'll indeed need to branch
2026-05-09T17:15:09  <acidsys> it's not the only package no longer built with AA support. I suppose bug report does not help much, because since AA libraries are not in SLFO, you cannot build against them there
2026-05-09T17:17:24  <cboltz> I'm surprised by that, https://src.opensuse.org/pool/apparmor/src/branch/slfo-1.2/ exists
2026-05-09T17:19:26  <acidsys> I assumed slfo-1.2 == SLE 16, but apparently not, https://scc.suse.com/packages?name=SUSE%20Linux%20Enterprise%20Server&version=16.0&arch=x86_64&query=apparmor&module says it's only in Package Hub (i.e. Leap)
2026-05-09T17:20:45  <cboltz> ok, that makes things interesting[tm]
2026-05-09T17:21:45  <cboltz> this might (unchecked/untested) mean that systemd AppArmorProfile= is also gone, and we might need to rebuild systemd for it
2026-05-09T17:22:01  <acidsys> that is already confirmed
2026-05-09T17:22:20  <acidsys> marcus mentioned there is a "trick" but I have not yet asked what that is
2026-05-09T17:26:17  <cboltz> I could imagine to change ExecStart to use   aa-exec -p $profile   but I'd prefer something better
2026-05-09T17:28:30  <acidsys> well, I summarized the falkor problems so far in https://progress.opensuse.org/issues/189810?issue_count=462&issue_position=111&next_issue_id=189771&prev_issue_id=190062#note-10. honestly thinking I must be missing something, as this setup is a standard SUSE HA stack .. and it won't fit into my believes that there is no documented and supported migration path
2026-05-09T17:29:33  <acidsys> wonder if downgrade to 15.7 would work
2026-05-09T17:34:50  <cboltz> I wonder if you should request an official SLE 16 licence, and then open a support ticket...
2026-05-09T17:35:27  <acidsys> for employee licenses, the support ticket platform is called bugzilla :)
2026-05-09T17:35:59  <cboltz> is openSUSE an employee? I'd say no ;-)
2026-05-09T17:36:34  <acidsys> well, if you get the board to get us an official support agreement ^^
2026-05-09T17:37:36  <cboltz> I'd hope SUSE will pay for it ;-)  *g,d&r*
2026-05-09T17:38:20  <acidsys> :) anyways I asked for help in $channel
2026-05-09T17:38:49  <cboltz> maybe a public-enough mail saying "Leap 16 and SLE 16 don't fit our needs, we might need to switch to Proxmox" could also help ;-)
2026-05-09T17:39:18  <acidsys> believe it or not, the proxmox documentation does have a section about migrating from corosync 2 to 3
2026-05-09T17:39:43  <cboltz> I'm not even surprised
2026-05-09T17:39:45  <acidsys> using proxmox tooling, of course
2026-05-09T17:40:16  <cboltz> I was afraid of that - would be too easy if we could just follow it on Leap
2026-05-09T17:41:39  <matrix-o-o> <malcolmlewis> acidsys: Ask the right folks you can get one.... maybe Robert Sirchia can help...
2026-05-09T17:42:14  <acidsys> robert will tell me to use rancher
2026-05-09T17:45:23  <acidsys> I'll figure something out, just quiet now as it's the weekend
2026-05-09T18:05:00  <acidsys> on a different note, I shut down GitLab now, will remove configuration in a bit