bootupd-validate: remove condition as we have newer bootupd

[HuijingHei]

Fixes openshift/os#1687

[HuijingHei]

Hold on, as not yet tested it on ppc64le, will do testing if I could setup the env.

[HuijingHei]

Test on ppc64le using rhcos-419.96.202412161243-0, result is PASS.

[coreos-assembler]$ kola run -E ./test --qemu-image rhcos-419.96.202412161243-0-qemu.ppc64le.qcow2 ext.test.boot.bootupd-validate
=== RUN   ext.test.boot.bootupd-validate
--- PASS: ext.test.boot.bootupd-validate (57.24s)
PASS, output in tmp/kola/qemu-2024-12-17-1255-489

Test on ppc64le using rhcos-419.94.202412142136, result is PASS.

[coreos-assembler]$ kola run -E ./test --qemu-image rhcos-419.94.202412142136-0-qemu.ppc64le.qcow2 ext.test.boot.bootupd-validate
=== RUN   ext.test.boot.bootupd-validate
--- PASS: ext.test.boot.bootupd-validate (43.38s)
PASS, output in tmp/kola/qemu-2024-12-17-1300-559

cosa build c9s, and run test, result is PASS.

$ kola run -E ./test ext.test.boot.bootupd-validate
=== RUN   ext.test.boot.bootupd-validate                                                                                                                                     
--- PASS: ext.test.boot.bootupd-validate (60.72s) 

[dustymabe]

considering openshift/os#1687 (comment) do we still need this?

[HuijingHei]

considering openshift/os#1687 (comment) do we still need this?

Thanks for the pointer, refresh the code to remove the condition as we have the newer bootupd (https://issues.redhat.com/browse/RHEL-71040), could you help to review, thanks!

[dustymabe]

LGTM but suggested some better wording