We want to run the desktop upgrade tests on aarch64; to do that,
we need the required base images to be built. We also need to
do the `console=tty0 quiet` boot args for the desktopencrypt
image so the decrypt prompt is visible on boot; to handle this,
we extend the existing hack for using a release-specific ks
to be more generic and allow for a more specific kickstart by
arch, release or both.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
"current" is just a synonym for "-1" but made the code more
complex. Let's ditch it and just note in a comment that -1 is
CURRREL and -2 is PREVREL. We need minimal-uefi for aarch64 as
install_blivet_btrfs_preserve_home_uefi uses it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is for
https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/201 -
we're working around that by using the F32 image for now, but it
doesn't exist on aarch64 ATM. We'll have to remember to take
this out when that's fixed.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We bumped it for the live image build update test, but I tweaked
that to use a separate scratch disk now, so the base image no
longer needs to be so big.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We need this for upgrade tests now I fixed the upgrade test
scheduling so Rawhide upgrade tests run from Rawhide-1 and
Rawhide-2, not currrel and prevrel...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It's only used for upgrade tests, and we don't test upgrading
from Branched, only from current stables.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is related to enabling update tests for KDE. While testing
that it transpired that the KDE disk image is missing various
stuff that is on the live image and systems installed from the
live image; this is because the kde-desktop-environment env
group doesn't by default include several groups and individual
packages that the live kickstart *does* include. So our current
disk image closely matches what you get if you do a network
install and pick the KDE env group and don't pick any option
groups, but that's not a very common thing to do, and it causes
problems for the tests (e.g. okular and firefox not being
there). I think it's reasonable to make the image resemble a
live install more closely; this is more convenient but I think
it's *also* more useful, as there are probably far more KDE
installs out there *with* these things than without them. More
KDE installs are probably done with the live than via network
install, and even KDE installs done via netinst may well have
these bits added subsequently.
Obviously, we bump the image version with this change, so we'll
need to update the scheduler and templates also.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit adds support for boot options, that can be passed
from `hdds.json` to control the creation of the virtual
machines, such as enabling of EFI based machines, boot order
control, etc. It also adds EFI based machine to `hdds.json`
and adds a kickstart file for such machine.
We need minimal to be 18GB now, because we're booting from it for
the Workstation live image build test. Not doing a version bump
as they turn out to be a bit of a pain to deal with, I should
enhance that somehow.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We need it bigger for the new 'update installer image' test,
and when changing it we must bump its version.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Rawhide tests are failing as there isn't enough disk space in
this image to copy the whole Server DVD...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This ensures that gnome-initial-setup will run in user mode on
first login as 'test' user for F26+, as it did for <=F25 and as
the tests expected (we can now remove the workaround I added
because this stopped happening with F26). Bump the image version
so the images get rebuilt.
Assumption createhdds executed on a PowerPC ppc64le host
to create the PowerPC specific images.
Detect current CPU arch of host machine to create virt-install images
only for supported architectures. (hardcoded lists)
hdds.json specific changes for PowerPC
* no desktop or kde images
Signed-off-by: Michel Normand <normand@linux.vnet.ibm.com>
'stable' means 'all current stable releases', and is used for
desktop and server as we need to ensure we have those images
available for all stable releases (including the '-3' release
while it's not EOL) for update testing. (Currently, F24 update
tests are all failing as the images are missing).
'current' means 'the current stable release' - it's the same as
'-1', but just easier to understand. It's used for support.
