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

Passwordless sudo not working on ubuntu-latest #9303

Closed
3 of 13 tasks
siddvenk opened this issue Feb 5, 2024 · 4 comments
Closed
3 of 13 tasks

Passwordless sudo not working on ubuntu-latest #9303

siddvenk opened this issue Feb 5, 2024 · 4 comments

Comments

@siddvenk
Copy link

siddvenk commented Feb 5, 2024

Description

We have recently encountered issues with passwordless sudo on the ubuntu-latest runner image.

We leverage sudo on ubuntu-latest in quite a few of our workflows, but we are only experiencing this issue in a single workflow.

Our workflow did not change between the previous successful runs, and the recent failed runs. The only changes I see are to the image and version used by the runner.

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • macOS 11
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

Latest Successful Run:

Sample Failed Run:

Is it regression?

yes

Expected behavior

Passwordless sudo should work.

Actual behavior

Passwordless sudo does not work (though we have other workflows where it does work using the same ubuntu-latest runner image)

Repro steps

This is the workflow that we are seeing the issue in https://github.com/deepjavalibrary/djl/blob/master/.github/workflows/native_jni_s3_pytorch_android.yml#L29.

To reproduce, I think one could create a new workflow that runs the steps through the "Install NDK" step (nothing prior to that relies on the repo or custom resources/permissions)

@mikhailkoliada
Copy link
Member

@siddvenk hey, does the path you try to call with sudo really exist?

@siddvenk
Copy link
Author

siddvenk commented Feb 5, 2024

That may be the issue, did the location of the Android SDK manager change between the runner versions I linked above?

It seems like it may have based on what I can parse from #8952.

I will test that and report back.

@mikhailkoliada
Copy link
Member

It might be a combination of non-existing path + sudo bug described here

@siddvenk
Copy link
Author

siddvenk commented Feb 5, 2024

Yes, that was exactly the issue. Thanks for the quick response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants