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

Build failures related to Node upgrade #11459

Closed
2 of 3 tasks
terrytangyuan opened this issue Jul 27, 2023 · 4 comments · Fixed by #11461
Closed
2 of 3 tasks

Build failures related to Node upgrade #11459

terrytangyuan opened this issue Jul 27, 2023 · 4 comments · Fixed by #11461
Labels
area/build Build or GithubAction/CI issues javascript Pull requests that update Javascript dependencies P3 Low priority type/bug type/dependencies PRs and issues specific to updating dependencies

Comments

@terrytangyuan
Copy link
Member

Pre-requisites

  • I have double-checked my configuration
  • I can confirm the issues exists when I tested with :latest
  • I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?

https://github.com/argoproj/argo-workflows/actions/runs/5676125574/job/15383405669

 /home/runner/runners/2.306.0/externals/node16/bin/node: --openssl-legacy-provider is not allowed in NODE_OPTIONS

https://github.com/argoproj/argo-workflows/actions/runs/5676115276/job/15382363976

error [email protected]: The engine "node" is incompatible with this module. Expected version ">=20". Got "18.17.0"

Version

latest

Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.

Not needed

Logs from the workflow controller

kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

Logs from in your workflow's wait container

kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded
@agilgur5
Copy link

The snyk workflow needs to use Node v20 similar to the ci-build workflow's setup-node step. I'll write up a PR for that in a jiffy

@terrytangyuan
Copy link
Member Author

The first issue is on publish-release workflow

@agilgur5
Copy link

Oh didn't realize the first one was a different workflow. That one's a weirder one since it's erroring on checkout before setup-node even runs 🤔

@agilgur5
Copy link

agilgur5 commented Jul 27, 2023

Oh... the version on the runner itself is failing to run checkout (which is in JS) due to the --openssl-legacy-provider. The reason it works during ci-build is because its NODE_OPTIONS is currently missing that flag.
EDIT: It doesn't need the flag anymore since the package.json#scripts now all have it in-line.
Also I see a decent amount of the UI deps are outdated now, Webpack (v4 -> v5) and React (v16 -> v18) being pretty core ones.

That's gonna take a few more changes to get working

@sarabala1979 sarabala1979 added P3 Low priority P1 High priority. All bugs with >=5 thumbs up that aren’t P0, plus: Any other bugs deemed high priority and removed P1 High priority. All bugs with >=5 thumbs up that aren’t P0, plus: Any other bugs deemed high priority labels Jul 27, 2023
@agilgur5 agilgur5 added area/build Build or GithubAction/CI issues type/dependencies PRs and issues specific to updating dependencies javascript Pull requests that update Javascript dependencies labels Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build Build or GithubAction/CI issues javascript Pull requests that update Javascript dependencies P3 Low priority type/bug type/dependencies PRs and issues specific to updating dependencies
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants