Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed aws-cli installation : Illegal instruction (core dumped) from aws-crt-python #485

Closed
Dennis-Johnson opened this issue Jul 4, 2023 · 5 comments
Assignees
Labels
bug This issue is a bug. closed-for-staleness p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to 'closing-soon' in 7 days.

Comments

@Dennis-Johnson
Copy link

Dennis-Johnson commented Jul 4, 2023

Describe the bug

Hi, trying to install the AWS CLI on Linux ARM64 resulted in a failure. This is related to aws-cli #8008, which suggested to file an issue here as well.

After following the instructions for installation on Linux ARM, I get the following error on trying to invoke the CLI tool.

$ aws --version
Illegal instruction (core dumped)

Expected Behavior

Expected to get the installed CLI version.

Current Behavior

Broken installation of aws-cli from source bundle, possibly due to an issue in underlying aws-crt-python

Reproduction Steps

$ aws --version
Illegal instruction (core dumped)

Possible Solution

No response

Additional Information/Context

System Info

$ uname -r
Linux agx 4.9.253-tegra #1 SMP PREEMPT Mon Jul 26 12:19:28 PDT 2021 aarch64 aarch64 aarch64 GNU/Linux

GDB Output

$  gdb /usr/local/aws-cli/v2/current/dist/aws

GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1

Reading symbols from /usr/local/aws-cli/v2/current/dist/aws...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/local/aws-cli/v2/dist/aws
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
process 11080 is executing new program: /usr/local/aws-cli/v2/dist/aws
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
OPENSSL_cpuid_setup () at /aws-crt-python/crt/aws-lc/crypto/fipsmodule/cpucap/cpu_aarch64_linux.c:132
132	/aws-crt-python/crt/aws-lc/crypto/fipsmodule/cpucap/cpu_aarch64_linux.c: No such file or directory.

aws-crt-python version used

Latest as of 28 June '23

Python version used

3.10

Operating System and version

Linux-4-Tegra (Ubuntu 18.04)

@Dennis-Johnson Dennis-Johnson added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jul 4, 2023
@yasminetalby yasminetalby self-assigned this Jul 6, 2023
@yasminetalby
Copy link
Contributor

Hello @Dennis-Johnson ,

Thank you very much for your submission. I have reached out to the aws-lc team internally to investigate the issue. I will post any updates or questions they might have here.

Thank you very much for your time and collaboration.

Sincerely,

Yasmine

@yasminetalby yasminetalby added p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. labels Jul 6, 2023
@andrewhop
Copy link

What CPU are you attempting to install the CLI on, can you run lscpu and attach the output?

@andrewhop
Copy link

Based on the line number cpu_aarch64_linux.c:132 I believe you are hitting the same MIDR_EL1 issue that Valgrind was hitting. This was fixed in aws/aws-lc#1006 which was released in v1.10.0 of AWS-LC. The most recent version of the Python CRT includes aws-lc @ 80c3943 which is v1.11.0 which includes the fix. Can you try updating to a newer version of the AWS CLI?

@jmklix
Copy link
Member

jmklix commented Nov 15, 2023

@Dennis-Johnson has updating to the latest version fixed this for you?

@jmklix jmklix added the response-requested Waiting on additional info and feedback. Will move to 'closing-soon' in 7 days. label Nov 15, 2023
Copy link

Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Nov 30, 2023
@github-actions github-actions bot closed this as completed Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. closed-for-staleness p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to 'closing-soon' in 7 days.
Projects
None yet
Development

No branches or pull requests

4 participants