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.
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-i...)
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)
Opinions, thoughts ?
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-i...) 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@centos.org https://lists.centos.org/mailman/listinfo/ci-users
On 02/04/2024 10:16, František Šumšal wrote:
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-i...) 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.
Yep, I added a comment to see if/when they'll provide a ubi9 image, which seems on the planning but without any ETA .. let's keep our fingers crossed :)
https://github.com/openshift/jenkins/issues/1766#issuecomment-2031960137
On 08/04/2024 09:17, Fabian Arrotin wrote:
On 02/04/2024 10:16, František Šumšal wrote:
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-i...) 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.
Yep, I added a comment to see if/when they'll provide a ubi9 image, which seems on the planning but without any ETA .. let's keep our fingers crossed :)
https://github.com/openshift/jenkins/issues/1766#issuecomment-2031960137
Doesn't seem to get any traction/momentum .. :/ So what about we just either let it in that state, or at least convert it to point to vault.centos.org ? Pointing to vault wouldn't produce *any* security update for that jenkins cico-workspace container but at least would be reproducible for now, while waiting for the newer UBI9 based image to finally land ...
I'd like to get your feedback/opinions/thoughts on that plan . TIA
On Tue, 2024-05-28 at 14:31 +0200, Fabian Arrotin wrote:
On 08/04/2024 09:17, Fabian Arrotin wrote:
On 02/04/2024 10:16, František Šumšal wrote:
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/Do ckerfile#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.
Yep, I added a comment to see if/when they'll provide a ubi9 image, which seems on the planning but without any ETA .. let's keep our fingers crossed :)
https://github.com/openshift/jenkins/issues/1766#issuecomment-2031960137
Doesn't seem to get any traction/momentum .. :/ So what about we just either let it in that state, or at least convert it to point to vault.centos.org ? Pointing to vault wouldn't produce *any* security update for that jenkins cico-workspace container but at least would be reproducible for now, while waiting for the newer UBI9 based image to finally land ...
I'd like to get your feedback/opinions/thoughts on that plan . TIA
Pointing it to vault.centos.org for the time being is acceptable for me. The cico-workspace image has a very limited task and it should not be used by others outside of the CentOS CI anyway, I think?
Depending on the current state of the UBI9 base image, it may be useful to contribute with suggestions and/or testing results in the GitHub Issue/PR. That might help in getting more traction and progress there, and you would not need to create your own UBI9 based version. Getting to an 'official' UBI9 based image should still be a relatively high priority, with a goal set to maybe 2 or 3 months from now?
Cheers, Niels
On 5/28/24 17:40, Niels de Vos wrote:
On Tue, 2024-05-28 at 14:31 +0200, Fabian Arrotin wrote:
On 08/04/2024 09:17, Fabian Arrotin wrote:
On 02/04/2024 10:16, František Šumšal wrote:
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/Do ckerfile#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.
Yep, I added a comment to see if/when they'll provide a ubi9 image, which seems on the planning but without any ETA .. let's keep our fingers crossed :)
https://github.com/openshift/jenkins/issues/1766#issuecomment-2031960137
Doesn't seem to get any traction/momentum .. :/ So what about we just either let it in that state, or at least convert it to point to vault.centos.org ? Pointing to vault wouldn't produce *any* security update for that jenkins cico-workspace container but at least would be reproducible for now, while waiting for the newer UBI9 based image to finally land ...
I'd like to get your feedback/opinions/thoughts on that plan . TIA
Pointing it to vault.centos.org for the time being is acceptable for me. The cico-workspace image has a very limited task and it should not be used by others outside of the CentOS CI anyway, I think?
I second this. The cico-workspace image changes very rarely, so pointing it to the Vault should be a good (enough) intermediate solution.
Depending on the current state of the UBI9 base image, it may be useful to contribute with suggestions and/or testing results in the GitHub Issue/PR. That might help in getting more traction and progress there, and you would not need to create your own UBI9 based version. Getting to an 'official' UBI9 based image should still be a relatively high priority, with a goal set to maybe 2 or 3 months from now?
Cheers, Niels
CI-users mailing list -- ci-users@lists.centos.org To unsubscribe send an email to ci-users-leave@lists.centos.org
On 29/03/2024 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.
Reminder : CentOS 7 is going EOL and so will be removed from Duffy pools next Monday
-
Fabian Arrotin -
František Šumšal -
Niels de Vos