rename BOOT_UPDATES_IMG_URL to TEST_UPDATES, add GRUBADD
ClosedPublic

Authored by adamwill on Apr 1 2016, 12:19 AM.

Details

Summary

BOOT_UPDATES_IMG_URL is a pretty misleading name - it used to
be the actual URL, but now it's simply a boolean that decides
whether we look for the effect of the openQA updates image or
not. TEST_UPDATES seems clearer.

GRUBADD does the same thing as GRUB, on top of it. The point of
this is so we can add an option to the scheduler CLI that lets
you say 'run the normal tests, but with this updates image' -
so we can easily (albeit manually triggered) check the impact
of some anaconda change that needs testing. It should never be
set in the templates or the tests, it's there strictly for the
scheduler (whether that's fedora_openqa_schedule or literally a
person calling client isos post) to use as a kind of override.
The tests that test updates image loading will probably fail
when doing this, but all other tests should work as intended,
including ones that specify GRUB, becase the extra params will
just get added on top. That's why I invented a new var instead
of just letting the scheduler override GRUB's value when POST
ing.

Test Plan

Check the rename didn't break anything (updates tests
still work). Run tests with GRUBADD param, make sure value is
correctly appended to cmdline both when GRUB is also specified
and when it is not.

Diff Detail

Repository
rOPENQATESTS os-autoinst-distri-fedora
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
adamwill retitled this revision from to rename BOOT_UPDATES_IMG_URL to TEST_UPDATES, add GRUBADD.Apr 1 2016, 12:19 AM
adamwill updated this object.
adamwill edited the test plan for this revision. (Show Details)
adamwill added reviewers: jskladan, garretraziel.
garretraziel accepted this revision.Apr 1 2016, 12:33 PM

Sure, looks good.

This revision is now accepted and ready to land.Apr 1 2016, 12:33 PM

This goes with D802, can you check that too? Thanks!

And now I read it, I see a bug...tum ti tum. Update coming.

adamwill updated this revision to Diff 2050.Apr 1 2016, 3:07 PM

do GRUBADD after REPOSITORY_VARIATION, check for both

REPOSITORY_VARIATION also gets glued into the kernel line, so do
GRUBADD after that and check for both before deciding whether to
do get_kernel_line. Perhaps we're at the point where this
would be cleaner with a little private subroutine that produces
a single chunk of text from all three vars and returns it, and
the main flow just adds that string if it's not empty? Meh.

This revision was automatically updated to reflect the committed changes.