Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CentOS Stream 8 reaches EOL #102

Open
anoopcs9 opened this issue Jun 3, 2024 · 5 comments
Open

CentOS Stream 8 reaches EOL #102

anoopcs9 opened this issue Jun 3, 2024 · 5 comments

Comments

@anoopcs9
Copy link
Collaborator

anoopcs9 commented Jun 3, 2024

A placeholder issue to think about the current usage of CentOS Stream 8 in our environment as it is discontinued with no further updates. As of now GPFS and GlusterFS backends uses CentOS 8 based nodes.

@anoopcs9
Copy link
Collaborator Author

anoopcs9 commented Jun 6, 2024

@xhernandez Do you remember the specific dependency requirement from GPFS side for now EOL CentOS(Stream) 8?

Was it some ansible collections?

@xhernandez
Copy link
Collaborator

@xhernandez Do you remember the specific dependency requirement from GPFS side for now EOL CentOS(Stream) 8?

Was it some ansible collections?

If I remember correctly, the only issue was that Storage Scale's ansible playbooks were using a deprecated feature (or something that was working differently in the version available in CentOS 9 Stream), causing the scripts to fail installation.

We can try to switch to CentOS 9 Stream to check if the newer installer has fixed the issue. I'll send a patch.

xhernandez added a commit to xhernandez/sit-environment that referenced this issue Jun 6, 2024
@xhernandez
Copy link
Collaborator

We can try to switch to CentOS 9 Stream to check if the newer installer has fixed the issue. I'll send a patch.

It seems there's an issue with the compilation of the GPFS' kernel module.

anoopcs9 added a commit to anoopcs9/sit-environment that referenced this issue Jun 11, 2024
CentOS Stream 8 reached EOL but our GPFS and GlusterFS environment
setup still has some dependecnies which are not yet fulfilled by
CentOS Stream 9. In case of GlusterFS it lacks few gluster-ansible
related rpms whereas GPFS is not yet ready to be compiled agianst
newer kernel versions from CentOS Stream 9.

Therefore we stick to CentOS Stream 8 till requirements are met.
See samba-in-kubernetes#102
for further developments.

Signed-off-by: Anoop C S <[email protected]>
anoopcs9 added a commit to anoopcs9/sit-environment that referenced this issue Jun 11, 2024
CentOS Stream 8 reached EOL but our GPFS and GlusterFS environment
setup still has some dependencies which are not yet fulfilled by
CentOS Stream 9. In case of GlusterFS it lacks few gluster-ansible
related rpms whereas GPFS is not yet ready to be compiled against
newer kernel versions from CentOS Stream 9.

Therefore we stick to CentOS Stream 8 till requirements are met.
See samba-in-kubernetes#102
for further developments.

Signed-off-by: Anoop C S <[email protected]>
anoopcs9 added a commit to anoopcs9/sit-environment that referenced this issue Jun 11, 2024
CentOS Stream 8 reached EOL but our GPFS and GlusterFS environment
setup still has some dependencies which are not yet fulfilled by
CentOS Stream 9. In case of GlusterFS it lacks few gluster-ansible
related rpms whereas GPFS is not yet ready to be compiled against
newer kernel versions from CentOS Stream 9.

Therefore we stick to CentOS Stream 8 till requirements are met.
See samba-in-kubernetes#102
for further developments.

Signed-off-by: Anoop C S <[email protected]>
anoopcs9 added a commit to anoopcs9/sit-environment that referenced this issue Jun 11, 2024
CentOS Stream 8 reached EOL but our GPFS and GlusterFS environment
setup still has some dependencies which are not yet fulfilled by
CentOS Stream 9. In case of GlusterFS it lacks few gluster-ansible
related rpms whereas GPFS is not yet ready to be compiled against
newer kernel versions from CentOS Stream 9.

Therefore we stick to CentOS Stream 8 till requirements are met.
See samba-in-kubernetes#102
for further developments.

Signed-off-by: Anoop C S <[email protected]>
anoopcs9 added a commit to anoopcs9/sit-environment that referenced this issue Jun 11, 2024
CentOS Stream 8 reached EOL but our GPFS and GlusterFS environment
setup still has some dependencies which are not yet fulfilled by
CentOS Stream 9. In case of GlusterFS it lacks few gluster-ansible
related rpms whereas GPFS is not yet ready to be compiled against
newer kernel versions from CentOS Stream 9.

Therefore we stick to CentOS Stream 8 till requirements are met.
See samba-in-kubernetes#102
for further developments.

Signed-off-by: Anoop C S <[email protected]>
anoopcs9 added a commit that referenced this issue Jun 12, 2024
CentOS Stream 8 reached EOL but our GPFS and GlusterFS environment
setup still has some dependencies which are not yet fulfilled by
CentOS Stream 9. In case of GlusterFS it lacks few gluster-ansible
related rpms whereas GPFS is not yet ready to be compiled against
newer kernel versions from CentOS Stream 9.

Therefore we stick to CentOS Stream 8 till requirements are met.
See #102
for further developments.

Signed-off-by: Anoop C S <[email protected]>
@anoopcs9
Copy link
Collaborator Author

As indicated above GPFS doesn't compile with recent kernel versions from CentOS Stream 9. #104 can be periodically refreshed to check for any developments with upcoming versions.

GlusterFS lacks few gluster-ansible packages on CentOS Stream 9. There is uncertainty in building those missing packages.

For the time being we are sticking to CentOS Stream 8 with repositories pointing to vault. This modification is already in place(#106).

@anoopcs9
Copy link
Collaborator Author

anoopcs9 commented Jul 9, 2024

GlusterFS lacks few gluster-ansible packages on CentOS Stream 9. There is uncertainty in building those missing packages.

These are now available via the usual copr repositories. #112 has been created to switch the platform for all GlusterFS related nodes to use CentOS Stream 9.

xhernandez added a commit to xhernandez/sit-environment that referenced this issue Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants