coreos/fedora-coreos-tracker

kola-upgrade test fails on secureboot

jbtrystram opened this issue · 8 comments

jbtrystram commented

All the recent kola-upgrades fails on secure boot.
It starts on 34.20210427.2.0, then zincatti stage the update :

zincati[2532]: [INFO ] target release '34.20210611.2.0' selected, proceeding to stage it

But then it never reboot to the next version.

See https://jenkins-fedora-coreos-pipeline.apps.ocp.fedoraproject.org/job/kola-upgrade/4349/display/redirect for an instance of the issue

jlebon commented

It seems quite consistent. I would try to reproduce this locally, first by running the test (and e.g. tailing the console), or simply by booting the bootimage from that starting version and letting Zincati do its thing (you'd need to apply the same workarounds that the upgrade test does, notably for 34+, the GPG key workaround).

marmijo commented

We hit this issue today with the testing and stable releases:

  • 👍1
marmijo commented

It's interesting that we only see this failure on the upgrade from F34 -> F40 and only on testing and stable.
The test actually excludes running secure boot for this same upgrade versions on the next stream: https://github.com/coreos/fedora-coreos-pipeline/blob/main/jobs/kola-upgrade.Jenkinsfile#L203-L205

Is this something we should implement for the other two streams, or was it specific to an issue in next in the past?