Closed zeekus closed 4 months ago
Hi zeekus,
Thank you for Identifying the Bug.
We are working on the Bug Fix. Are you currently blocked by this? If yes, we can try to find a workaround for you.
Hi zeekus,
Thank you for Identifying the Bug.
We are working on the Bug Fix. Are you currently blocked by this? If yes, we can try to find a workaround for you.
Thanks. The work around is just not to run updates. It is not the most secure approach, but it works.
Is there an ETA on a fix?
Hi rmarable-flaretx and zeekus,
We dont have an ETA on the next release.
For a current workaround
cookbooks/aws-parallelcluster-environment/resources/lustre/lustre_redhat8.rb
and cookbooks/aws-parallelcluster-environment/resources/lustre/lustre_rocky8.rb
as per the 2 PR's below
For Cookbook Repo
DevSettings:
Cookbook:
ChefCookbook: https://github.com/<UserName>/aws-parallelcluster-cookbook/tarball/<BranchName>
For S3:
DevSettings:
Cookbook:
ChefCookbook: s3://
This issue has been fixed by 3.10.0, which was released last Thursday. Thank you for reporting the issue to us!
Required Info:
pcluster describe-cluster
command: N/ABug description and how to reproduce:
Update a standard Rocky 8.9 AMI by doing a 'yum update;yum upgrade'
run pcluster build image with updated OS.
The update transforms Rocky 8.9 into Rocky 8.10 and chefs says:
Similar to this: https://github.com/aws/aws-parallelcluster/issues/6239
Please update to the Chef code to handle Rocky Linux version updates more gracefully.