-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Executable breaks GitHub action - python version works #5262
Comments
I'm encountering the same issue using the Here are my relevant debug logs:
|
Can confirm, the docker image is also affected. I'm using |
Also confirm. version i'm using: I got this error:
Reinstalling awscli from python3 works as @simonwep say. |
I was also having this issue but discovered that the as a workaround I just removed the install from my script and it worked |
@lucianolxp thanks I will try it. It will save us precious seconds 👍 |
Looks like this might be related when running in Azure Kubernetes Service: #5234 I think the issue is that Azure has it's own instance metadata service using the same non-routable IP address: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service |
@simonwep I think this is due to a difference in behavior between the V1 and V2 clients. When you You can set a region to avoid this request from being made. There is also an undocumented environment variable that can be set to disable this:
I will open a separate documentation issue to make sure this is added to the list of AWS CLI environment variables. |
Opened the following documentation issue: #5623 |
|
Github upgrading
in order to get it working. If i use latest this goes to 20.04 and i would need to use new cli commands |
For me, the problem was that I had commented out my step to "Configure AWS credentials" on the GitHub action during testing 🤦♂️ - name: Configure AWS Credentials
uses: aws-actions/configure-aws-credentials@v1
with:
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
aws-region: us-west-2 That caused any Adding the credentials back worked even with |
For those who prefer to not use an action to upload a file to S3, I found that I had to do the following on
|
aws/aws-cli#5262 (comment) It failed to run `aws s3 cp` because the region isn't specified.
See aws/aws-cli#5262 (comment) If we don't provide a region then the aws CLI v1 fails.
Use the official way to configure AWS credentials instead of raw environment variables as recommended here: aws/aws-cli#5262 (comment). Because GitHub action cannot run `aws s3` successfully due to unknown `AWS_EC2_METADATA` or region issues.
* feat: rename intel mac pkg * chore: add env var to avoid unnecessary aws API calls more info here: aws/aws-cli#5262 (comment) * fix: don't use docker since gha runners already have aws cli * chore: change rename mac pkg job to a composite action * chore: for testing * fix: step ids * Revert "chore: for testing" This reverts commit cf409ca. * fix: remove rename mac job from reusable workflow
* feat: rename intel mac pkg * chore: add env var to avoid unnecessary aws API calls more info here: aws/aws-cli#5262 (comment) * fix: don't use docker since gha runners already have aws cli * chore: change rename mac pkg job to a composite action * chore: for testing * fix: step ids * Revert "chore: for testing" This reverts commit cf409ca. * fix: remove rename mac job from reusable workflow * fix: don't hardcode sfdx * fix: add .pkg file extension
Confirm by changing [ ] to [x] below to ensure that it's a bug:
Describe the bug
It's related to actions/runner#503 - the problem is that the most recent executable (Taken from here) always causes builds to fail with
Example builds (notice that the workflow config hasn't changed)
✅ Working: https://github.com/Simonwep/conway/runs/683296327?check_suite_focus=true
❎ Broken: https://github.com/Simonwep/conway/runs/703702976?check_suite_focus=true
✅ Fixed by using the python version: https://github.com/Simonwep/conway/runs/739054745?check_suite_focus=true
✅ Working: https://github.com/Simonwep/intl-demo/runs/531009403?check_suite_focus=true
❎ Broken: https://github.com/Simonwep/intl-demo/runs/703653450?check_suite_focus=true
It works if the python version is installed using
SDK version number
Platform/OS/Hardware/Device
To Reproduce (observed behavior)
See actions/runner#503
Expected behavior
The executable should work I guess.
Logs/output
Taken from this build:
Show Log
The text was updated successfully, but these errors were encountered: