lp:~powersj/curtin/add-bionic
- Get this branch:
- bzr branch lp:~powersj/curtin/add-bionic
Branch merges
- Server Team CI bot: Approve (continuous-integration)
- Scott Moser (community): Approve
-
Diff: 532 lines (+183/-4)29 files modifiedtests/vmtests/releases.py (+5/-0)
tests/vmtests/test_apt_config_cmd.py (+4/-0)
tests/vmtests/test_basic.py (+8/-0)
tests/vmtests/test_bcache_basic.py (+4/-0)
tests/vmtests/test_bcache_bug1718699.py (+4/-0)
tests/vmtests/test_iscsi.py (+4/-0)
tests/vmtests/test_journald_reporter.py (+4/-0)
tests/vmtests/test_lvm.py (+4/-0)
tests/vmtests/test_lvm_iscsi.py (+4/-0)
tests/vmtests/test_mdadm_bcache.py (+34/-0)
tests/vmtests/test_mdadm_iscsi.py (+4/-0)
tests/vmtests/test_multipath.py (+4/-0)
tests/vmtests/test_network.py (+4/-0)
tests/vmtests/test_network_alias.py (+4/-0)
tests/vmtests/test_network_bonding.py (+14/-0)
tests/vmtests/test_network_bridging.py (+13/-0)
tests/vmtests/test_network_enisource.py (+5/-1)
tests/vmtests/test_network_ipv6.py (+4/-0)
tests/vmtests/test_network_ipv6_enisource.py (+1/-3)
tests/vmtests/test_network_ipv6_static.py (+4/-0)
tests/vmtests/test_network_ipv6_vlan.py (+4/-0)
tests/vmtests/test_network_mtu.py (+10/-0)
tests/vmtests/test_network_static.py (+4/-0)
tests/vmtests/test_network_static_routes.py (+5/-0)
tests/vmtests/test_network_vlan.py (+4/-0)
tests/vmtests/test_nvme.py (+8/-0)
tests/vmtests/test_raid5_bcache.py (+4/-0)
tests/vmtests/test_simple.py (+4/-0)
tests/vmtests/test_uefi_basic.py (+8/-0)
Branch information
Recent revisions
- 542. By Scott Moser
-
vmtest: Remove ArtfulTestBridging skip_by_date check, bug fixed
Bug 1721157 is now fixed, so do not need to skip by date anymore.
- 540. By Ryan Harper
-
clear_holders: bcache log IO/OS exceptions but do not raise
While stopping bcache devices, curtin races with the kernel w.r.t how
quickly it removes the bcache device (and the sysfs tree related).
The result is that as curtin attempts to write "1" into the sysfs tree
of bcache device to stop it, the range of errors changes depending on
when we race with the kernel asynchronously removing the sysfs path.
Therefore we log the exception errno we got but do not re-raise. The
the calling process is watching whether the same sysfs path is being
removed; if the bcache device fails to go away then curtin will have a
log of the exceptions to debug. - 539. By Scott Moser
-
vmtest: Support newer qemu and multipath.
If you pass the same backing device for a disk to qemu, newer
versions (2.10+) will fail. In order to allow this, it requires
you to pass 'file.locking=off'.This change makes the multipath tests add a 'file.locking=off' argument
to the disks that are actually intended to be added more than once.
xkvm is modified to remove that flag if the qemu being used does not
support it.In order to accomplish this:
a.) make launch use xkvm '--disk' for all its disks rather than
passing -drive and -device. This is good in that we know have
a single way of passing disks around.
b.) fix a logic bug in xkvm when --disk= specified format= on it.vmtest and launch now only use '--disk=' args, which are interpreted
by xkvm rather than using a mix of '--disk=' and '-drive'. - 538. By Ryan Harper
-
block: enable control over exclusive_open use when wiping volumes
The exclusive_open check on a device is very useful to determine if
curtin is removing all metadata from a device w.r.t storage
configuraiton. However, in some cases during creation of new storage
configations when curtin attempts to add additional partitions to a
device that has partitions already added to an raid device, the
exclusive open is blocked while we attempt to zero some data on the
underlying device. The Mirrorboot-UEFI vmtest exemplifies this
situation.This patch exposes a flag to the zero_file_at_offset method to allow
callers (block_meta in this case) to disable the exclusive_open. This
lets curtin wipe data at specific offsets on a volume without
requiring exclusive ownership of the device. - 537. By Ryan Harper
-
block: handle wiping bcache parts
In some cases block devices may have bcache parts which are owned by the
block layer but are not assembled into a bcache device. The result is that
curtin fails to get exclusive opens when attempting to wipe the device.
Resolve this by testing if a volume has a 'bcache' directory under sysfs
and issuing the appropriate stop commands before wiping.It's also possible for old "buried" metadata for bcache or lvm or raid
at particular partition offsets. Once curtin starts partitioning the
device the bcache kernel layer "finds" the parts and claims device
ownership and prevents wiping of the partition. We resolve this issue
by having curtin wipe 1M at the location of the partition before we
actually create it.Fix 'curtin clear-holders' subcommand.
LP: #1718699
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:~curtin-dev/curtin/trunk