Hello,
to bump the topic, I just checked and 792107900819
does not have new images listed for Rocky-9-EC2-Base-9.4*
Note: I do see 792107900819/Rocky-9-EC2-Base-9.4-20240523.0.x86_64 was created first on 2024/05/09 for AWS Public AMI then most probably have the fix on x86_64 with new create date 2024/06/03, However arm64 Image is still having problems per this issue rocky-9-4-aws-ami-not-booting-after-kernel-update
Any ETA on this fix and receive new public base image AMI in AWS 792107900819/Rocky-9-EC2-Base-9.4-20240509.0.aarch64 create date after 2024/05/09?
Hi,
Any update on this? Thanks
Good Morning! is there any update on image AMI in AWS 792107900819/Rocky-9-EC2-Base-9.4-20240509.0.aarch64 create date after 2024/05/09?
Iām using my own AMI Rocky 9.4 AMI and seeing same dnf update issues.
This did not work for meā¦
dnf -y update
grub2-mkconfig -o /boot/grub2/grub.cfg
shutdown --no-wall --reboot 1
Rocky 9.4 dnf update results in non-functional EC2. This is the worst sort of bug and will likely result in return to using RHEL instance (which I am loath to do).
Original āuname -aā
5.14.0-427.26.1.el9_4.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Jul 23 16:00:21 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
dnf update to kernel x86_64 5.14.0-427.31.1.el9_4
Hello, adding to the list of people seeing this issue with AWS ARM image Rocky-9-EC2-Base-9.4-20240509.0.aarch64.
Doesnāt appear to be a newer one.
When trying to do a deploy of an EC2 instance, I see the latest version.
What is the process you are using to deploy the instance?
Can you please describe what the console shows after performing an update? We have not received any reports of aarch64 systems having kernel update issues at our bug tracker.
I was matching on the name
12:02 $ aws ec2 describe-images --filter 'Name=name,Values=Rocky-9-EC2-Base-9.4-*.aarch64' --query 'Images[].Description'
[
"Rocky-9-EC2-Base-9.4-20240509.0.aarch64"
]
but didnāt realise there can be a uuid on the end
12:04 $ aws ec2 describe-images --filter 'Name=description,Values=Rocky-9-EC2-Base-9.4-*.aarch64' --query 'Images[].Name'
[
"Rocky-9-EC2-Base-9.4-20240509.0.aarch64",
"Rocky-9-EC2-Base-9.4-20240523.0.aarch64-0d51926d-1cd1-4223-bda9-346993accc16"
]
Iāll update the pattern in the selection process.
No thatās not why it didnāt get picked up. Itās because itās on a different owner ID
12:15 $ aws ec2 describe-images --filter 'Name=name,Values=Rocky-9-EC2-Base-9.4-*.aarch64*' --query 'sort_by(Images, &CreationDate)[*].[ImageId,OwnerId,CreationDate,Name]'
[
[
"ami-08dc5c2a8ee46cbcb",
"792107900819",
"2024-05-09T21:47:02.000Z",
"Rocky-9-EC2-Base-9.4-20240509.0.aarch64"
],
[
"ami-09e7c72f178c8efc1",
"679593333241",
"2024-06-03T21:35:14.000Z",
"Rocky-9-EC2-Base-9.4-20240523.0.aarch64-0d51926d-1cd1-4223-bda9-346993accc16"
]
]
We search for the owner ID of 792107900819
Hi team,
I couldnāt find an AWS AMI with the fix under the owner ID 792107900819 (Rocky Linux Project). Is this expected? We tested the AMI from AWS Marketplace, and it works fine. However, to use it, we need an additional Marketplace subscription for each account, Iād like to confirm before changing our internal AMI usage process.
For which architecture? I can see x86_64 ami in eu-west-2
Rocky-9-EC2-Base-9.4-20240523.0.x86_64
ami-0a7b5dd86d37ab5a4
aarch64 only seems to be available from the marketplace
@jaredc for aarch64, there is no build 20240523
available in any region.
For now, weāve decided to switch to AWS-owned AMIs and handle the subscription through the AWS License Manager service.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.