You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using nodejs version 18.20.2 to deploy parallecluster 3.9.1 and 3.11.1 but have been failing to get 3.10.1 deployed due to error messages in my CreateParallelClusterConfig cloudwatch log about not finding rpds.rpds:
timestamp
message
1730586652150
INIT_START Runtime Version: python:3.12.v36 Runtime Version ARN: arn:aws:lambda:us-west-2::runtime:188d9ca2e2714ff5637bd2bbe06ceb81ec3bc408a0f277dab104c14cd814b081
1730586653191
[ERROR] Runtime.ImportModuleError: Unable to import module 'CreateParallelClusterConfig': No module named 'rpds.rpds' Traceback (most recent call last):
END RequestId: a3c4f82f-22c2-4a64-b5d8-b8e1139b5f3d
1730586846532
REPORT RequestId: a3c4f82f-22c2-4a64-b5d8-b8e1139b5f3d Duration: 996.60 ms Billed Duration: 997 ms Memory Size: 2048 MB Max Memory Used: 80 MB Status: error Error Type: Runtime.ImportModuleError
Thinking this might be an issue with me moving forward with different versions of nodejs (18.20.2) and CDK (2.130.0 or 2.165.0) I've reverted back to original setup.sh. I get big warning messages during deployment:--------------------------------------------
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! Node 16 has reached end-of-life on 2023-09-11 and is not supported. !!
!! Please upgrade to a supported node version as soon as possible. !!
!! !!
!! This software is currently running on node v16.20.2. !!
!! As of the current release of this software, supported node releases are: !!
!! - ^20.0.0 (Planned end-of-life: 2026-04-30) !!
!! - ^18.0.0 (Planned end-of-life: 2025-04-30) !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This is very disconcerting. Should/Can this not be moved forward?
I'm still debugging why I can't a 3.10.1 cluster deployed. I've done a clean pull, deploying a 3.10.1 custom AMI. Will then try 3.11.1 again to prove it still works with 3.11.1.
The text was updated successfully, but these errors were encountered:
Understood it isn't related to my issue, but having big red warnings pop up while doing the build would be disconcerting to noobies - it was for me originally, hence that is why I moved forward.
I'm just suggesting you make the move forward. I have successfully used nodejs 18.20.2 and CDK 2.130.0. But I just don't know enough if that is "safe" and the right thing to do.
I have been using nodejs version 18.20.2 to deploy parallecluster 3.9.1 and 3.11.1 but have been failing to get 3.10.1 deployed due to error messages in my CreateParallelClusterConfig cloudwatch log about not finding rpds.rpds:
Thinking this might be an issue with me moving forward with different versions of nodejs (18.20.2) and CDK (2.130.0 or 2.165.0) I've reverted back to original setup.sh. I get big warning messages during deployment:--------------------------------------------
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! Node 16 has reached end-of-life on 2023-09-11 and is not supported. !!
!! Please upgrade to a supported node version as soon as possible. !!
!! !!
!! This software is currently running on node v16.20.2. !!
!! As of the current release of this software, supported node releases are: !!
!! - ^20.0.0 (Planned end-of-life: 2026-04-30) !!
!! - ^18.0.0 (Planned end-of-life: 2025-04-30) !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This is very disconcerting. Should/Can this not be moved forward?
I'm still debugging why I can't a 3.10.1 cluster deployed. I've done a clean pull, deploying a 3.10.1 custom AMI. Will then try 3.11.1 again to prove it still works with 3.11.1.
The text was updated successfully, but these errors were encountered: