View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0016614||CentOS-8||Cloud-Images||public||2019-10-16 21:14||2020-01-27 20:51|
|Target Version||Fixed in Version|
|Summary||0016614: No Centos 8 AMIs|
|Description||I'd like to request Centos 8 AMI images. You currently provide them for Centos 6 and 7, but not 8:|
The ZFS on Linux project uses Centos AMIs for our automated testing. We currently can't release Centos 8 ZFS RPMs, since we have no way to test them without the AMIs:
|We really need to get this resolved asap....is there a way that I can assist building the image?|
Red Hat Enterprise Linux 8 AMI was built by Amazon Web Services. They have been available since July 2019.
CentOS.org has built the previous official AMI.
I am assuming it is not a technical issue to build a certified AMI, but one of priority.
|So where should the request be made for a Centos ami? I am not interested in the RH ami's|
This is in the Cloud Instance SIG purview - https://wiki.centos.org/SpecialInterestGroup/CloudInstance
There's a kickstart file for a generic CentOS 8 cloud image in this pull request:
There's also an outstanding pull request for an Azure image kickstart file for CentOS 8
I'm sure they would be happy to accept changes to build an AMI, should someone create one.
I tried to https://github.com/CentOS/sig-cloud-instance-build/pull/159/commits/2c542bb2b1bc54c007fbf57a5da0a3213ce73fbb (and turned off BLS) and when attempting to import to AWS (amazon-import), it fails with
Unsupported kernel version 4.18.0-80.el8.x86_64
Any way to fix this?
I got the same error....it's a bit funny since I installed a RH 8.0 in AWS which is running the same kernel version the only difference is that the RH kernel is tagged with RH in the end.
I ended up following this article https://weldr.io/Pushing-Images-to-AWS/ which works really well.
|If you made a CentOS 8 image and uploaded it to AWS via https://weldr.io/Pushing-Images-to-AWS/, I will try it out. Thanks|
|It works just make sure that you get both cloud-init.noarch and cloud-utils-growpart.noarch installed without cloud-utils-growpart.noarch changing the EBS disk size wont be discovered by Centos.|
Looking at AWS us-east-1: what are the images published by owner 679593333241? That's the same owner ID as the official CentOS 7 images (e.g. ami-02eac2c0129f6376b which is the latest published). If you just go to us-east-1 > EC2 > AMIs > select Public images > search for "centos8", you'll find the images I'm talking about. For example:
- ami-034a46a96c820cc75 (CentOS 8 Minimal Latest with Updates-f399b70b-09d8-4df4-ba78-bc1813b4b257-ami-063710974a98495cb.4)
- ami-0c69cc337830690b6 (CentOS8-ENA-AWS-cea6f7dd-49db-40fd-a49e-16617be018a3-ami-025c3654e9b105dbb.4)
And others (there's a dozen). I haven't tested any of them, but are they official?
@shubbeh No; the official builds are linked in the Issue Description;
The only official-ish comment I could find was the Forum Moderator who seemed to not care;
were pretty close to getting 8.1 out of the door, as soon as that hits, i will aim to get the AMI's up within a week from 8.1 drop for x86 and aarch64.
going forward, I've got 90% of the automation in place to keep the cadence rolling ( expect 4 to 5 updates a year for the base image per distro 6/7/8 in the AMP stack, and a weekly build for BYOI flow )
this is for x86_64, the aarch64 images will lag a bit, but will catchup farily quickly ( by Mar '20 is a good goal to set )
Thanks for the quick and detailed answer kbsingh.
The Current 8.1 Timeline Link;
is 2 months in and does look close (AFAIR it ranges from 1 to 7 months).
based on the current status, we shouldnt be more than a week or two to release, the challenge with that board is that it does not quantify the amount of work, so even small checks and changes trigger a package build etc.
A good metric to track is the CR/ drop - once that is in, its safe to assume the content base is done, or extremely close.
> were pretty close to getting 8.1 out of the door, as soon as that hits, i will aim to
> get the AMI's up within a week from 8.1 drop for x86 and aarch64.
Thank you kbsingh!
Am very very eager for the Centos8 AMi to be available because there's a bunch of servers I want to deploy and get rid of python2!
I'm also anxious for the Centos8 AMI to become officially available.
I noticed that there is a CentOS-8-ec2-8.1.1911-20200113.3.x86_64.qcow2 file available at https://cloud.centos.org/centos/8/x86_64/images/. Is the official AMI going to be created from this file?
|Any updates on this?|
I am also waiting for CentOS 8.
I need to upload servers on aws and I wanted it to be CentOS but version 7.7 with the 4.4.210 kernel has some
vulnerabilities Specter and Meltdown vulnerabilities.
|2019-10-16 21:email@example.com||New Issue|
|2019-10-16 21:firstname.lastname@example.org||Tag Attached: centos 8|
|2019-10-30 12:01||qvindesland||Note Added: 0035605|
|2019-10-30 13:email@example.com||Note Added: 0035607|
|2019-11-04 11:09||qvindesland||Note Added: 0035636|
|2019-11-05 23:26||jhhaller||Note Added: 0035643|
|2019-11-15 02:39||raiden||Note Added: 0035695|
|2019-11-15 08:54||qvindesland||Note Added: 0035697|
|2019-11-15 15:12||raiden||Note Added: 0035700|
|2019-11-15 15:17||qvindesland||Note Added: 0035701|
|2020-01-06 15:58||shubbeh||Note Added: 0035943|
|2020-01-09 13:54||TimL||Note Added: 0035981|
|2020-01-09 14:firstname.lastname@example.org||Note Added: 0035982|
|2020-01-09 14:56||TimL||Note Added: 0035983|
|2020-01-09 15:email@example.com||Note Added: 0035984|
|2020-01-09 19:firstname.lastname@example.org||Note Added: 0035988|
|2020-01-23 18:13||speculatrix||Note Added: 0036106|
|2020-01-24 02:35||rm||Note Added: 0036109|
|2020-01-27 10:33||jormatuomainen||Note Added: 0036129|
|2020-01-27 12:59||thiago.antonio||Note Added: 0036134|