From frantisek at sumsal.cz Tue Apr 2 08:16:14 2024 From: frantisek at sumsal.cz (=?UTF-8?B?RnJhbnRpxaFlayDFoHVtxaFhbA==?=) Date: Tue, 2 Apr 2024 10:16:14 +0200 Subject: [Ci-users] Reminder : CentOS 7 and 8s EOL soon (impact on CI workflow) In-Reply-To: <3992faaf-83f2-47e0-825c-cd5fc30af06b@centos.org> References: <3992faaf-83f2-47e0-825c-cd5fc30af06b@centos.org> Message-ID: <5af42241-b3ba-43a4-8806-0c48e4d66cd5@sumsal.cz> Hey, On 3/29/24 16:14, Fabian Arrotin wrote: > Hi CI tenants ! > > Just a reminder that (as you know it) CentOS Stream 8 will go EOL in May and then CentOS Linux 7 itself going EOL in June (so very soon) > > That would mean that we'll just remove the various pools that provide CentOS 8s and 7 for your tests. > > Reason is that mirror network itself will be unavailable and so all tests would fail anyway. > > Happy to discuss here but we'll send reminders about when we'll just remove the various pools in Duffy. Already started migration of the remaining C7/C8S jobs to C9S (and already hitting multiple not-CentOS-CI-infra-related issues, as usual). > > I also need to find an option for something else that you *still* all use when using Jenkins on openshift cluster : our cico-workspace image (https://quay.io/repository/centosci/cico-workspace) > That one is "problematic" as it's based on upstream openshift jenkins agent (https://github.com/openshift/jenkins/tree/master?tab=readme-ov-file#hosted-images) > These ones are based on UBI8 and it seems that there is (still) no momentum to move to UBI9 (don't have direct contact with them though) > While our current images were based from the upstream ones, we could just "convert" these to 8s (https://github.com/centosci/images/blob/master/cico-workspace/Dockerfile#L1 and https://github.com/centosci/images/blob/master/cico-workspace/Dockerfile#L8) > > We need to find a solution but was wondering if just using vault (archived mirror content) would be a good solution or not : tempted myself to answer "no" as that would mean running container that will *never* be updated for security reasons (CentOS Stream 8 going EOL in May) There seems to be _some_ kind of movement to migrate it to C9S in [0]. So, we could either just wait (potentially risky if the new version is not out before C8S EOL and we'd need to tweak the container image [unlikely, but still]), temporarily pin it to Vault repos (the lazy way), or just make our own C9S version until the official one is out. [0] https://github.com/openshift/jenkins/issues/1766 > > Opinions, thoughts ? > > > _______________________________________________ > CI-users mailing list > CI-users at centos.org > https://lists.centos.org/mailman/listinfo/ci-users From arrfab at centos.org Tue Apr 2 14:25:20 2024 From: arrfab at centos.org (Fabian Arrotin) Date: Tue, 2 Apr 2024 16:25:20 +0200 Subject: [Ci-users] [Infra] - Planned outage : lists.centos.org (migration to mailman3) : please read Message-ID: Due to a needed upgrade , we'll have to move the existing CentOS mailman instance (aka https://lists.centos.org) to a new server/host. Migration is scheduled for """"Tuesday April 8th, 7:00 am UTC time"""". You can convert to local time with $(date -d '2024-04-08 07:00 UTC') The expected "downtime" is estimated to ~60 minutes , time needed to : - take last mailman2 backup - reimport / convert mailman2 archives to mailman3 DB - DNS propagation for A/AAAA/MX records Here are also some important information about the mailman2 => mailman3 migration : # Renamed lists Worth knowing that, based on open discussion on the centos-devel list (see whole thread at https://lists.centos.org/pipermail/centos-devel/2024-March/165576.html), existing lists will be *renamed* , so while we'll put aliases for incoming mails, each list member will start receiving list mails from new list name. So start updating your filters if you filter on email address instead of "subject:" Here is the overview of the new lists names : arm-dev at centos.org => arm-dev at lists.centos.org centos at centos.org => discuss at lists.centos.org centos-devel at centos.org => devel at lists.centos.org centos-announce at centos.org => announce at lists.centos.org centos-automotive-sig at centos.org => automotive-sig at lists.centos.org centos-{cz,de,es,fr,nl,pt-br,zh}@centos.org => discuss-{cz,de,es,fr,nl,pt-br,zh}@lists.centos.org ci-users at centos.org => ci-users at lists.centos.org centos-gsoc: => gsoc at lists.centos.org centos-mirror at centos.org => mirror at lists.centos.org centos-mirror-announce at centos.org => mirror-announce at lists.centos.org centos-newsletter at centos.org => newsletter at lists.centos.org centos-promo at centos.org => promo at lists.centos.org centos-virt at centos.org => virt at lists.centos.org # Authentication Mailman2 had no real concept of authentication so you could just subscribe to one or more lists, and have a password associated with your email address for that/these subscription(s). Mailman3 itself is split into "core" and "webui" components, so when we'll import mailman2 lists/config into mailman3, your existing subscriptions will continue to work *but* not your password. Mailman3 will be configured to support SSO, and so if you already have a FAS/ACO account (https://accounts.centos.org) you'll be able to login directly into new webui and manage your settings/subscriptions *if* your ACO email address of course matches the one you initially subscribed with for lists.centos.org. If that's not the case, either create an ACO/FAS account that will match and you'll be then able to "link" your mailman3 account with FAS and so manage your settings/subscriptions. If you don't want to, there is always the documented process : https://docs.mailman3.org/en/latest/userguide.html#making-a-mailman-account Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org] -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: