tools: jenkins-runner show curtin version in output.
I was looking at output of a jenkins run, and it was very non-clear
what actual version of curtin was running. The change here will
get 'curtin version' output into the CURTIN_VMTEST_VERSION variable
which then gets printed out with all the other CURTIN_VMTEST_* variables.
So, we see something like:
CURTIN_VMTEST_CURTIN_EXE=./tools/curtin-from-container xc1 curtin
CURTIN_VMTEST_CURTIN_EXE_VERSION=18.1-619-g4bf7750-0ubuntu1
CURTIN_VMTEST_CURTIN_VERSION=18.1-17-g0fc297bd
The zfs kernel module is not available for i386 so curtin cannot
expect that missing that module is fatal. Concentrate the various
checks for when we load the zfs kernel module into the zfs python
module. Add vmtest to exercise the i386 path.
Support mount entries not tied to a device, including bind and tmpfs.
Previously an entry in the storage configuration of type 'mount'
was required to have a 'device' entry that was a reference to
an id of type 'format'. That meant that there was no way to add
a mount for anything that wasn't a traditional filesystem.
The change here allows a type 'mount' entry to not have a 'device'
as long as it has a 'spec' and a 'fstype' entry. The word 'spec'
comes from fstab(5).
It also adds support for the mount type to have a 'passno' and 'freq'
which are entries in a fstab file.
block/clear_holders/mdadm: refactor handling of layered device wiping
The block layer handling of checking efi/dos signatures did not ensure
that it always used a devpath (/dev/<kname>) which resulted in
failures when attempting to identify dos partitions, including
extended partitions due to attempting to open /sys/class/block/<kname>
to look for metadata. In addition there is a window where
wiping/removing lvm devices in dos logical partitions renders the
/dev/<kname> path to the extended partition missing, no /dev/<kname>
We now re-read a block device's partition table after completing a
shutdown of each device. Doing this re-read triggered mdadm devices
which had been stopped to resume preventing wiping of the underlying
devices. A refactor of how raid devices are shutdown now includes
collecting the list of raid members and spares, failing each element
out of the array, stopping the rescan/rebuild of the array and finally
removing the mdadm metadata on the underlying devices.
With this in place, we can now successful run the LVM test-cases with
dirty_disk mode enabled and simultaneously continue to pass the
complex bcache/raid examples.
clear_holders: only export zpools that have been imported
Curtin may encounter disks from a previous install which are
zfs_members but are part of a pool which isn't currently
imported. Attempting to export a pool that is not imported
results in a failure. Instead, only export a pool if it's
found in the list of currently imported pools.
Also enable Bionic ZfsRoot vmtest (BionicTestZfsRootFsType)
LP: #1770280
vmtests: allow env control of apt, system_upgrade, package upgrade
Add environment variables to support adding repositories, toggling
system_upgrade boolean, and installing packages.
This supports several use-cases where we want to test if a package
fixes an issue found in vmtest.
CURTIN_VMTEST_ADD_REPOS:
Comma separated list of repos to add via apt: config
Typically in the form: ppa:lpuser/pocket but also supports
'proposed' to generate a sources entry for adding that pocket.
extend the apt syntax to allow for the string 'proposed' to turn
CURTIN_VMTEST_SYSTEM_UPGRADE:
Enable curtin's system_upgrade feature, default value is 0
If there are values in CURTIN_VMTEST_ADD_REPOS, this will default to 1.
Users may use ADD_REPOS and disable system_upgrade by setting value
to 0.
CURTIN_VMTEST_UPGRADE_PACKAGES:
Comma separated list of packages that will be installed/upgraded
in a late command.
Lastly, allow ./tools/jenkins-runner to take CURTIN_* declarations
on the command line. This makes it easier to feed these to a manually
run jenkins run.
