The Architecture 'x86_64' Of The Specified Instance Type Does Not ...

Home » Architecture Type X86_64 » The Architecture 'x86_64' Of The Specified Instance Type Does Not ...

Maybe your like

Skip to content Dismiss alert {{ message }} / aws-parallelcluster Public
  • Notifications You must be signed in to change notification settings
  • Fork 319
  • Star 886
  • Code
  • Issues 139
  • Pull requests 47
  • Actions
  • Wiki
  • Security 2
  • Insights
Additional navigation options The architecture 'x86_64' of the specified instance type does not match the architecture 'arm64' of the specified AMI #3795New issueNew issueClosedClosedThe architecture 'x86_64' of the specified instance type does not match the architecture 'arm64' of the specified AMI#3795@metma99

Description

@metma99metma99opened on Feb 18, 2022

Required Info:

  • AWS ParallelCluster version [e.g. 2.9.0]: 2.9.1

  • Full cluster configuration without any credentials or personal data: [aws] aws_region_name = ....

    [aliases] ssh = ssh {CFN_USER}@{MASTER_IP} {ARGS}

    [global] cluster_template = default update_check = true sanity_check = true

    [cluster default] key_name = ... base_os = alinux2 scheduler = slurm master_instance_type = t3a.large vpc_settings = default queue_settings = compute efs_settings = default scaling_settings = default post_install = ... ec2_iam_role = ... tags = ...

    [vpc default] vpc_id = ... master_subnet_id = ... use_public_ips = false

    [queue compute] enable_efa = false compute_resource_settings = default compute_type = spot

    [compute_resource default] instance_type = c5a.4xlarge max_count = 25

    [efs default] shared_dir = efs encrypted = false performance_mode = generalPurpose

    [scaling default] scaledown_idletime = 15

  • Cluster name: if really required I can provide it

Bug description and how to reproduce: Note this cluster setup has worked before. I used it 6 months ago w/o any issues. Yesterday I was not able to run any jobs on the cluster and finally tracked the issue down to: I deleted the cluster successfully and issued: pcluster create omeros-nextflow-pcluster

This is the error message: pcluster create omeros-nextflow-pcluster Beginning cluster creation for cluster: omeros-nextflow-pcluster ERROR: Unable to validate configuration parameters. Please double check your cluster configuration. The architecture 'x86_64' of the specified instance type does not match the architecture 'arm64' of the specified AMI. Specify an instance type and an AMI that have matching architectures, and try again. You can use 'describe-instance-types' or 'describe-images' to discover the architecture of the instance type or AMI. I checked describe-instance-types, describe-images all fine. The above specified instance types are available for architecture x86_64. The image is also x86_64.

  1. aws ec2 describe-instance-types --filters Name=processor-info.supported-architecture,Values=x86_64 --query "InstanceTypes[*].InstanceType" --output text

The instance types specified in config are indeed of architecture x86_64 (not showing the rather lengthy output): master_instance_type = t3a.large instance_type = c5a.4xlarge

  1. aws ec2 describe-images --region us-west-2 --image-ids ami-09975e5a942d87be0 output: { "Images": [ { "Architecture": "x86_64", "CreationDate": "2020-09-14T23:26:13.000Z", "ImageId": "ami-09975e5a942d87be0", "ImageLocation": "amazon/aws-parallelcluster-2.9.1-amzn2-hvm-x86_64-202009142226", "ImageType": "machine", "Public": true, "OwnerId": "247102896272", "PlatformDetails": "Linux/UNIX", "UsageOperation": "RunInstances", "State": "available", "BlockDeviceMappings": [ { "DeviceName": "/dev/xvda", "Ebs": { "DeleteOnTermination": true, "SnapshotId": "snap-08f7546394e9eeffb", "VolumeSize": 25, "VolumeType": "gp2", "Encrypted": false } } ], "EnaSupport": true, "Hypervisor": "xen", "ImageOwnerAlias": "amazon", "Name": "aws-parallelcluster-2.9.1-amzn2-hvm-x86_64-202009142226", "RootDeviceName": "/dev/xvda", "RootDeviceType": "ebs", "SriovNetSupport": "simple", "VirtualizationType": "hvm"

If you are reporting issues about scaling or job failure:

We cannot work on issues without proper logs. We STRONGLY recommend following this guide and attach the complete cluster log archive with the ticket.

This script failed issuing an error that files are missing: ERROR:retrieve-cluster-logs.py:Unable to find log group in region us-west-2 for cluster

For issues with AWS ParallelCluster >= v2.9.0 and scheduler == slurm, please attach the following logs:

  • From Head node: /var/log/parallelcluster/clustermgtd, /var/log/parallelcluster/clusterstatusmgtd (if version >= 3.2.0), /var/log/parallelcluster/slurm_resume.log, /var/log/parallelcluster/slurm_suspend.log, /var/log/parallelcluster/slurm_fleet_status_manager.log (if version >= 3.2.0) and/var/log/slurmctld.log

  • From Compute node: /var/log/parallelcluster/computemgtd.log, and /var/log/slurmd.log Otherwise, please attach the following logs:

  • From Head node: /var/log/jobwatcher, /var/log/sqswatcher, and /var/log/slurmctld.log if scheduler == slurm.

  • From Compute node:/var/log/nodewatcher, and /var/log/slurmd.log if scheduler == slurm

    I have no access to any of those files above. Instead I am posting: pcluster-cli_02182022.log

If you are reporting issues about cluster creation failure or node failure: If the cluster fails creation, please re-execute create action using --norollback option. If I understood you correctly then I did the following resulting in the same error. pcluster create omeros-nexflow-pcluster --norollback

We cannot work on issues without proper logs. We STRONGLY recommend following this guide and attach the complete cluster log archive with the ticket.

  • From Head node: /var/log/cloud-init.log, /var/log/cfn-init.log, and /var/log/chef-client.log

  • From Compute node: /var/log/cloud-init-output.log

    Only the cloud-init.log file was available which is attached: cloud-init.log

I tried to include as much info as possible. Kindly let me know if you require any more details. Thank you very much in advance for any input you might have.

Markus

Metadata

Metadata

Assignees

No one assigned

Labels

No labelsNo labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

You can’t perform that action at this time.

Tag » Architecture Type X86_64