Specifying architecture in AWS Greengrass seems not to work

Question

I have a component with one lifecycle for aarch64 devices, and another for x86 devices. See recipe.yaml snippet below:

```
Manifests:
  - Platform:
      architecure: x86
    Lifecycle:
      Run: "echo 'Not valid for x86 devices. Exiting with no action'"
  - Platform:
      architecture: aarch64
    Artifacts:
      - URI: "s3://BUCKET_NAME/COMPONENT_NAME/COMPONENT_VERSION/ComponentName.zip"
        Unarchive: ZIP
    Lifecycle:
      Run:   
        Script: ""
```

When I deploy this to the edge device (which is x86, I get):
```
com.aws.greengrass.componentmanager.exceptions.NoAvailableComponentVersionException: No local or cloud component version satisfies the requirements Check whether the version constraints conflict and that the component exists in your AWS account with a version that matches the version constraints. If the version constraints conflict, revise deployments to resolve the conflict.
```

And on the AWS console, I see the tabs at the bottom of the component page for "All" and "aarch64", rather than for x86 as I would expect.

scriobhneoir · Answer

A follow-up:
Thanks for the typo suggestion, that has been resolved and the AWS console now has the two tabs for x86,aarch64.

The component resolution error still occurs. Debug steps I have done:
 - Deployed the component in question to another device in the same stack (aarch64 device). Finds and deploys the component correctly. 
 - On the x86 device, deployed another new device, which it finds in the cloud without issue. Stored in the same bucket, in the same way. (both the find-able component and the non-findable component have the same "publish" key in their gdk-config.json's)

More follow up:

The component will now deploy, if I add an 'all' key to the architecture. It seems to ignore the x86 architrecture key altogether.

uname -a output:
```
Linux  5.15.0-56-generic #62~20.04.1-Ubuntu SMP Tue Nov 22 21:24:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
```

Questions:
 - Why does the component seem unable to detect the arch ?
 - When the arch is not detected, is this normal behaviour ?

ochoanel · Answer

Hey scriobhneoir,

The error you are seeing doesn't seem to be relate to the architecture variable. That error you posted occurs  when Greengrass fails to resolve (find) your component locally or on the cloud. There could be several reasons this happens, to solve it ensure

1) Ensure that the role your device assumes has the s3:GetObject permission to that bucket where you are uploading your component. Without this your device won't be able to download the component and it will fail to install it

2) Ensure your recipe file is correct, I can not tell just from that part  of your recipe file if you have specified the correct version (make sure it has a version number and that the version number is matching the one you want to install)

3) You have a typo on the recipe `architecure != architecture`

If non of that works, could you post here your full recipe and gdk-config.json files so we can further assist you?

Specifying architecture in AWS Greengrass seems not to work

Add your answer

Relevant content