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

add test queue for RedHat 8 #972

Closed
wfurt opened this issue Dec 17, 2019 · 24 comments · Fixed by #46205
Closed

add test queue for RedHat 8 #972

wfurt opened this issue Dec 17, 2019 · 24 comments · Fixed by #46205

Comments

@wfurt
Copy link
Member

wfurt commented Dec 17, 2019

While we sunsetting RH6, (#423) RH8 is out. Since we support last to major versions we should be testing them as well.

https://developers.redhat.com/blog/2019/05/07/red-hat-enterprise-linux-8-now-generally-available/

cc: @tmds

@wfurt wfurt added this to the 5.0 milestone Dec 17, 2019
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Dec 17, 2019
@ViktorHofer
Copy link
Member

cc @bartonjs @danmosemsft

@ViktorHofer
Copy link
Member

We need this for 5.0 as we state to support 7+. cc @safern

@ViktorHofer ViktorHofer added area-Infrastructure-installer and removed area-Infrastructure untriaged New issue has not been triaged by the area owner labels Jul 12, 2020
@NikolaMilosavljevic
Copy link
Member

This is not installer or setup related.

@NikolaMilosavljevic NikolaMilosavljevic added untriaged New issue has not been triaged by the area owner area-Infrastructure and removed area-Infrastructure-installer labels Jul 29, 2020
@ghost
Copy link

ghost commented Jul 29, 2020

Tagging subscribers to this area: @ViktorHofer
See info in area-owners.md if you want to be subscribed.

@dleeapho
Copy link

RHEL VMs are not suitable for public-facing infra since it requires subscription-manager registration to be functional. I would suggest using CentOS instead per Red Hat's guidance. An alternative is to switch to containerized solutions such as UBI

@safern
Copy link
Member

safern commented Jul 29, 2020

We do have a CentOS8 docker image already for building but not for testing. @MattGal @Chrisboh do you think someone from the dnceng team could help adding a helix image to test on CentOS 8?

https://github.com/dotnet/dotnet-buildtools-prereqs-docker/tree/master/src/centos/8

@MattGal
Copy link
Member

MattGal commented Jul 30, 2020

RHEL VMs are not suitable for public-facing infra since it requires subscription-manager registration to be functional. I would suggest using CentOS instead per Red Hat's guidance. An alternative is to switch to containerized solutions such as UBI

@dleeapho : Let's chat when you can, perhaps in a different venue. We have been providing public-facing Helix RHEL 6 and 7 VMs for some time, there's some magic in the Azure gallery images that doesn't require us to deal with subscription managers.

@ViktorHofer ViktorHofer removed the untriaged New issue has not been triaged by the area owner label Aug 4, 2020
@ericstj
Copy link
Member

ericstj commented Aug 31, 2020

@MattGal / @dleeapho any update on this?

@MattGal
Copy link
Member

MattGal commented Aug 31, 2020

@MattGal / @dleeapho any update on this?

I haven't had a conversation with Dan, but I think I know everything I need to know in this space.

  • We have some real challenges for test machines w.r.t. core availability in the post-COVID world, as such we're trying very hard to avoid growing new Linux queues where possible.
  • With RedHat, docker-ization from an Ubuntu machine (or any non-RHEL) is blocked, so we'd have to stand up such machines as a new queue (possibly installing docker on RHEL 7 / 8 and using this for future RHEL?)
  • RHEL 6 goes out of service in a few months (11/30/2020) so its queue capacity could contribute to RHEL 8's.

@Chrisboh will discuss this Thursday @ CI council.

@ViktorHofer
Copy link
Member

Note to myself, we should discuss this in next CI council's meeting. Also we should discuss if we need this for 5.0 and 3.x/2.x.

@ViktorHofer ViktorHofer self-assigned this Sep 1, 2020
@MattGal
Copy link
Member

MattGal commented Sep 1, 2020

From chatting with Eric it looks like RHEL 6 usage is already way down and could be swapped out for 8 soon.

@ViktorHofer
Copy link
Member

@MattGal do you think we should replace RHEL6 with RHEL8 in servicing branches as well?

@MattGal
Copy link
Member

MattGal commented Sep 1, 2020

Ideally, it should be removed from 2.x and 3.1 before we remove support for it from Helix, so it doesn't fail your test runs.

As for adding RHEL 8 support to the release branches, I think that's more of a @leecow question and I think would hinge based on whether we officially state support for RedHat 8 for that release.

@ViktorHofer ViktorHofer removed their assignment Sep 8, 2020
@dleeapho
Copy link

RHEL6 is also a @leecow question.

@danmoseley
Copy link
Member

@leecow ?

@leecow
Copy link
Member

leecow commented Oct 16, 2020

RHEL 6 will reach 'end of maintenance' 11/30 so we'll change our support statement for 2.1 and 3.1 with the December release (meaning November will be the last month RHEL 6 is supported).

@tmds
Copy link
Member

tmds commented Oct 20, 2020

@MattGal @leecow it would be very useful to have a RHEL8 CI machine because both Microsoft and Red Hat will be supporting .NET 5 on RHEL8.

Can you also look into adding a RHEL8 arm64 machine? We're seeing some issues: #43349.
We want to provide .NET on arm64 when we are able to source-build it.

cc @omajid

@MattGal
Copy link
Member

MattGal commented Oct 20, 2020

@MattGal @leecow it would be very useful to have a RHEL8 CI machine because both Microsoft and Red Hat will be supporting .NET 5 on RHEL8.

Can you also look into adding a RHEL8 arm64 machine? We're seeing some issues: #43349.
We want to provide .NET on arm64 when we are able to source-build it.

cc @omajid

AFAIK, RedHat still doesn't directly support running inside non-redhat docker hosts. Generally, Centos support has been deemed sufficient to cover this on ARM64.

@tmds
Copy link
Member

tmds commented Oct 27, 2020

AFAIK, RedHat still doesn't directly support running inside non-redhat docker hosts. Generally, Centos support has been deemed sufficient to cover this on ARM64.

CentOS8 and RHEL8 are built from the same source code. RHEL8 is supported by Red Hat, and CentOS8 is supported by the CentOS community. Using either in the CI setup is fine.

Does this issue also track adding an ARM64 RHEL8/CentOS8 machine? Any idea when these machines will be added?

@karelz
Copy link
Member

karelz commented Dec 2, 2020

@wfurt is this still needed or did we forget to close it?
Can you please update milestone to 5.0.x (5.0 servicing) or 6.0 as appropriate? Thanks!

@karelz
Copy link
Member

karelz commented Dec 17, 2020

@wfurt ping?

@wfurt
Copy link
Member Author

wfurt commented Dec 17, 2020

it seems like there is still no helix queue: https://helix.dot.net

I see that in some cases we use both Centosx7 and RedHat.7. It would make sense to me to flip one of them to 8 as testing both seems to provide little value. (@tmds to confirm)

While debate about ARM may linger, I still see value in x64 -> to cover issues with different library versions (like OpenSSL traditionally gives us ongoing pain)

@MattGal
Copy link
Member

MattGal commented Dec 17, 2020

That is correct. I had a chat with @wfurt and created https://github.com/dotnet/dotnet-buildtools-prereqs-docker/pull/389/files which we believe addresses test coverage for RHEL8.

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Dec 18, 2020
@wfurt
Copy link
Member Author

wfurt commented Dec 18, 2020

thanks to @MattGal, we have images and I have PR ready for runtime.
Since Hollidays are upon us, I start wondering if it is wise to merge even if it comes clean.
Unless somebody feels there is urgency, I'll hold off the merge until next year to decrease risk of disturbance.

@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jan 5, 2021
@karelz karelz modified the milestones: 5.0.0, 6.0.0 Jan 6, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Feb 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.