I am currently using Kolla-ansible for deploying my OpenStack environment and I am running the Openstack Victoria version on CentOS Linux 8. Due to EOL of CentOS Linux 8 is no longer supported. I wanted to migrate now on CentOS stream8.
On the official website they have mentioned the following Note:
CentOS Linux 8 (as opposed to CentOS Stream 8) is no longer supported as a host OS. The Victoria release will in the future support both CentOS Linux 8 and CentOS Stream 8, and provide a route for migration.
My question is:
Has anyone done this migration (any worrisome issues)?
Any idea, are they going to provide a migration route soon because the above-mentioned note is there for around 3-4 months and they stopped supporting CentOS Linux 8?
Related
We are using 'CentOS Linux release 7.9.2009 (Core)' for production servers. But it seems that Redhat stopped Centos 7 full updates from November 2020 onwards. We are in confusion do we need to upgrade to CentOS 8 or Centos Stream?, As per Centos / wiki official docs. They were providing full/maintenance support for Centos 8 Stream still 2024. Is this Centos 8 Steam version is stable or can we continue with Centos 7 maintenance version?
Reference URLS :
https://wiki.centos.org/About/Product,
https://en.wikipedia.org/wiki/CentOS#CentOS_version_7
In my career i have seen prod servers even running on Solaris 11 which was released 10 years ago and has no support now.
This usually depends, whether the underlying dependencies required by your application change/requires to be updated frequently or not,
If yes - Go with supported version.( which will also run out of support :D )
If No - Stay where you are. ( Best choice Mostly )
I have a google VM instance which was running flawlessly. It has Centos-7 and Plesk installed in it.
I just stopped it, upgraded machine type (to better CPU and RAM) and started it again. My server stopped responding at all. No websites are running, I can't connect to SSH & Google Cloud SDK Shell is unable to reach server. It says NETWORK ERROR, CONNECTION TIMED OUT. My all other instances works well.
I tried rebooting & resetting multiple times. Reading out stuff from internet since last 6 hours but for no luck. I also tried to clone disk of the instance and creating new instance with the cloned disk but for no luck. Same network connection issue. May be something in OS got corrupted? Please suggest. I have a number of websites hosted on the server which are down due to this. Thanks a lot in advance.
I took screenshot of my VM using Google Cloud Shell. It is as follows:
I connected with serial console which is as follows:
While creating a ticket with google, I found that they've posted some information under "Known Issues". I am pasting the whole stuff as there is no direct link to reach there. The symptoms they told were exactly what was happening to me:
Below is Known Issue Posted by Google:
Description:
We are experiencing an issue with Google Compute Engine instances running RHEL and CentOS 7 and 8. More details on this issue are available in the following article and bugs: https://access.redhat.com/solutions/5272311 https://bugzilla.redhat.com/show_bug.cgi?id=1861977 (RHEL 8) https://bugzilla.redhat.com/show_bug.cgi?id=1862045 (RHEL 7) Symptoms: Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart with errors messages referring to a combination of: "X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID", "FXSAVE_STATE" or "Find image based on IP". This issue affects instances with specific versions of the shim package installed. To find the currently installed shim version, use the following command: rpm -q shim-x64 Affected shim versions: CentOS 7: shim-x64-15-7.el7_9.x86_64 CentOS 8: shim-x64-15-13.el8.x86_64 RHEL 7: shim-x64-15-7.el7_8.x86_64 RHEL 8: shim-x64-15-14.el8_2.x86_64 Workaround: Do not update or reboot instances running RHEL or CentOS 7 and 8. If you are on an affected shim version, run yum downgrade shim\* grub2\* mokutil to downgrade to the correct version. This command may not work on CentOS 8. If you have already rebooted, you will need to attach the disk to another instance, chroot into the disk, then run the yum downgrade command. We will provide an update by Thursday, 2020-07-30 14:00 US/Pacific with current details.
Start time:
July 30, 2020 at 9:08:34 PM GMT+5
How to diagnose:
Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart with errors messages referring to a combination of: "X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID", "FXSAVE_STATE" or "Find image based on IP". This issue affects instances with specific versions of the shim package installed. To find the currently installed shim version, use the following command: rpm -q shim-x64 Affected shim versions: CentOS 7: shim-x64-15-7.el7_9.x86_64 CentOS 8: shim-x64-15-13.el8.x86_64 RHEL 7: shim-x64-15-7.el7_8.x86_64 RHEL 8: shim-x64-15-14.el8_2.x86_64
Workaround:
Do not update or reboot instances running RHEL or CentOS 7 and 8. If you are on an affected shim version, run yum downgrade shim\* grub2\* mokutil to downgrade to the correct version. This command may not work on CentOS 8. If you have already rebooted, you will need to attach the disk to another instance, chroot into the disk, then run the yum downgrade command.
I have a quick question related to "Kubespray".
Does "Kubespray" support CentOS 8?
I wanted to deploy "Kubespray" on "CentOS" and I came to know that the CentOS 8 has Kernel version 4.18 and If I can use "CentOS 8" for "Kubernetes" deployment, maybe I can get rid of the "c-group" issue which we are currently facing for all the CentOS distribution which has Kernal Version less than 4.18.
Thanks in Advance.
According to the official documentation Kubesprawy provides support for CentOS/RHEL 7 only. The problem is that:
Installing Kubespray on a RHEL8 systems does not work since the
default Python version is 3.6 and thus python3-libselinux should be
installed instead of libselinux-python. Even that python2 is still
available, the libselinux-python package is not.
I hope it helps.
I learn that RHEL and Centos has the exact same source code. So my question here is if one application built for RHEL 6.4, could we just install and make it running on Centos 6.4 without any update?
And another question is RHEL and Centos will always use the same version number for the same source code, right?
Yes, software built on RHEL 6.4 should work as-is on CentOS 6.4 (assuming you don't depend on one of the relatively few RHEL-specific details, mostly to do with branding).
CentOS, except where necessary, uses upstream RHEL sources unmodified. When they need to modify a package they indicate that in the release notes and in the release field of the RPM in question.
I want to install VestaCP on my digitalocean droplet. I can't see supported os list on vestacp's web site. Is VestaCP compatible with centos 7 ?
http://vestacp.com/
Yes, its CentOS 7 compatible, you only have to use their installer running this:
curl -O http://vestacp.com/pub/vst-install.sh
It doesn't look like it. I just tried installing it on a minimal-install image of CentOS 7, and it failed. Tried to find /sbin/ifconfig (7 minimal-install uses nmcli and nmtui) and failed.
The rhel-specific install script that got downloaded only has provisions for CentOS 5 and 6 in it, no mention of 7, and so the install failed further on when adding some rpm repos.
tldr: doesn't look like it has support for it yet.