FCOS-on-OKD e2e testing

coreos / fedora-coreos-tracker

Issue tracker for Fedora CoreOS

262 stars 59 forks source link

FCOS-on-OKD e2e testing #836

Open LorbusChris opened 4 years ago

LorbusChris commented 4 years ago

It has been agreed in the FCOS community meeting today to enable non-release-blocking end to end testing for FCOS on OKD clusters.

Opening this issue to discuss the details of where these tests should happen, i.e. per PR on this repo, per prod run in Jenkins, \<insert more options here>

bgilbert commented 3 years ago

For anyone else who just got a notification for this issue and was confused, this is an old bug that was just transferred to the FCOS tracker. The referenced meeting was in July 2020.

sandrobonazzola commented 2 years ago

Given recent discussion about OKD not being able to switch to FCOS 35 due to a regression in selinux shipped within FCOS 35 I believe this needs to be prioritized. I can offer help getting this done from OKD Virtualization SIG team. Please let's start discussing how to proceed here. @vrutkovs @dustymabe any suggestion?

vrutkovs commented 2 years ago

Please let's start discussing how to proceed here

https://github.com/openshift/okd/issues/501

dustymabe commented 2 years ago

Thanks @sandrobonazzola - I agree that us doing e2e testing in our CI would help find issues like this. We are currently doing node e2e testing with kubernetes upstream. See https://github.com/coreos/fedora-coreos-tracker/issues/990