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

[CI] [C#] Verifiy release on c-sharp has been failing since upgrading ubuntu to 22.04 #31674

Closed
asfimport opened this issue Apr 22, 2022 · 6 comments

Comments

@asfimport
Copy link

asfimport commented Apr 22, 2022

We upgraded the verify-release job for c-sharp from Ubuntu 20.04 to Ubuntu 22.04 and we can see how the nightly release job has been failing since then.

Working for ubuntu 20.04 on 2022-04-08:

https://github.com/ursacomputing/crossbow/tree/nightly-release-2022-04-08-0-github-verify-rc-source-csharp-linux-ubuntu-20.04-amd64

Failing for ubuntu 22.04 on 2022-04-09:

https://github.com/ursacomputing/crossbow/tree/nightly-release-2022-04-09-0-github-verify-rc-source-csharp-linux-ubuntu-22.04-amd64

The error seems to be related with missing libssl:

 ===========================
Build and test C# libraries
===========================
└ Ensuring that C# is installed...
└ Installed C# at  (.NET 3.1.405)Welcome to .NET Core 3.1!
---------------------
SDK Version: 3.1.405Telemetry
---------
The .NET Core tools collect usage data in order to help us improve your experience. It is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.Read more about .NET Core CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry----------------
Explore documentation: https://aka.ms/dotnet-docs
Report issues and find source on GitHub: https://github.com/dotnet/core
Find out what's new: https://aka.ms/dotnet-whats-new
Learn about the installed HTTPS developer cert: https://aka.ms/aspnet-core-https
Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli-docs
Write your first app: https://aka.ms/first-net-core-app
--------------------------------------------------------------------------------------
No usable version of libssl was found
/arrow/dev/release/verify-release-candidate.sh: line 325:    49 Aborted                 (core dumped) dotnet tool install --tool-path ${csharp_bin} sourcelink
Failed to verify release candidate. See /tmp/arrow-HEAD.CiwJM for details.
134
Error: `docker-compose --file /home/runner/work/crossbow/crossbow/arrow/docker-compose.yml run --rm -e VERIFY_VERSION= -e VERIFY_RC= -e TEST_DEFAULT=0 -e TEST_CSHARP=1 ubuntu-verify-rc` exited with a non-zero exit code 134, see the process log above.

Reporter: Raúl Cumplido / @raulcd
Assignee: Jacob Wujciak / @assignUser

Related issues:

PRs and other links:

Note: This issue was originally created as ARROW-16282. Please see the migration documentation for further details.

@asfimport
Copy link
Author

Raúl Cumplido / @raulcd:
I can reproduce locally by using:

$ UBUNTU=22.04 docker-compose run --rm ubuntu-verify-rc 

@asfimport
Copy link
Author

Krisztian Szucs / @kszucs:
cc @eerhardt

@asfimport
Copy link
Author

Jacob Wujciak / @assignUser:
This is most likely due to ubuntu 22 using openssl 3 https://discourse.ubuntu.com/t/openssl-3-0-transition-plans/24453

@asfimport
Copy link
Author

Kouhei Sutou / @kou:
We have an issue for this: ARROW-16176

I don't think that this is a blocker of 8.0.0 because we didn't have support for Ubuntu 22.04 (OpenSSL 3) in the previous release. This is not break a backward compatibility. This is just a new feature.

@asfimport
Copy link
Author

Raúl Cumplido / @raulcd:
Thanks @kou , I missed the other ticket and thought we wanted to have all verify-rc passing for the release. I am happy to close this as duplicate and remove the blocker if you think is not a blocker.

@asfimport
Copy link
Author

Kouhei Sutou / @kou:
OK. I close this as a duplicated.

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