Steven Presti

@travier Yeah it does not mention it either, and needs to be updated. https://github.com/openshift/openshift-docs/pull/74419

1 through 4 are reserved for specific purposes, and so var would be 5. Ugh Just noticed butane is wrong too. Filesystems and partitions https://coreos.github.io/butane/examples/ https://github.com/coreos/butane/pull/524

> Isn't the partition number automatically picked-up by Ignition? > > From https://coreos.github.io/ignition/configuration-v3_4/: > > > number (integer): the partition number, which dictates its position in the partition table (one-indexed)....

Ok, I went and added an example with a number and notes. I hope this is fine lmk.

@jlebon, it was something I stumbled across with an old co-worker, and we made a ticket for it. Im not sure I captured enough details at the time. I am...

We re-evaluated this and found it still relevant.

hmm, I might have missed it but I did not see what triggers the CI to run `kola -p qemu --build latest run --rerun --allow-rerun-success=tags=needs-internet --on-warn-failure-exit-77 --arch=x86_64 --basic-qemu-scenarios` If someone...

> > hmm, I might have missed it but I did not see what triggers the CI to run `kola -p qemu --build latest run --rerun --allow-rerun-success=tags=needs-internet --on-warn-failure-exit-77 --arch=x86_64 --basic-qemu-scenarios`...

> So we just need to make sure that the nvme and uefi/uefi-secure tests dont run on other arches. If thats the case It sounds like I need to update...

> So overall I think there are at least two main ways I see we can approach this: > > 1. Have knobs as part of `register.Test` to say e.g....