lp:~raharper/curtin/trunk.vmtest_add_huge_disk_tests

Created by Ryan Harper on 2017-05-02 and last modified on 2017-05-02
Get this branch:
bzr branch lp:~raharper/curtin/trunk.vmtest_add_huge_disk_tests
Only Ryan Harper can upload to this branch. If you are Ryan Harper please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Ryan Harper
Project:
curtin
Status:
Development

Recent revisions

495. By Ryan Harper on 2017-05-02

vmtests: add test for huge disks 8TB in lvm and raid

494. By Ryan Harper on 2017-04-26

uc16 curthooks: add 'network' key to config file

When deploying UC16 with a network config, ensure that we include the
top-level 'network' key for cloud-init to detect network configuration.

Update vmtest and unittest to exercise network path.

493. By Chad Smith on 2017-04-25

Doc and makefile updates for build and test on new systems.

Add a couple of doc/makfile fixes for fresh installs. Add doc dependency
python3-sphinx-rtd-theme to the makefile and separate check-doc-deps make
target. Callout make sync-images in integration test docs as sync'd images
are required for vmtests to run. Fix sphinx doc warnings and content
alignment.

492. By Ryan Harper on 2017-04-24

clear-holders: make bcache handler wait for device shutdown

Clear-holder's bcache shutdown handler does not wait for devices owned by
bcache driver to be released before returning. On sufficiently fast
systems (and with multiple cpus) the time for bcache to release the
backing devices may occur slower than the time it takes for curtin to
start attempting to wipe partition data on a backing device. This results
in an IO error due to curtin asserting exclusive access to a device for
wiping.

This series introduces some additional logic in the bcache shutdown
handler by testing that the bcache devices are removed before returning
from the handler.

If the underlying devices are not released, the handler raises an
exception.

Fixes: LP:#1680409

491. By Joshua Powers on 2017-04-24

vmtest: Use utf-8 and fix pseudo test collect_output

Updates curtin-log-print to use utf-8 over ascii. Also updates the vmtest
PseudoTests to allow for creating pseudo output files.

490. By Scott Moser on 2017-04-21

vmtest: fix path to install log, and utilize the globally copied paths.

2 changes here:
 a.) the base class is already collecting /root, so we dont need
     to copy those files specifically.
 b.) fix spelling 'curtin-install.log' (it was curtin-install-log).

489. By Scott Moser on 2017-04-20

Copy curtin install log into target.

The install log was not correctly being copied into the target as a
regression merged in at revno 465.
Now, by default the target should get:
  install log: /root/curtin-install.log
  merged config: /root/curtin-install-cfg.yaml

488. By Joshua Powers on 2017-04-19

vmtest: add in post-test log post-processing

Adds additional post-processing of logs using curtin-print-log to the
collected vmtest logs. Makes curting-print-log thread-safe and allows
it to accept an output directory.

487. By Joshua Powers on 2017-04-13

vmtest: update source.list test

The change that was made to the builtin /etc/apt/sources.list in the
cloud images for xenial was done so recently under bug LP: #1513529.
That was by design and required for consistency and this change updates
the curtin vmtest accordingly.

LP: #1682516

486. By Scott Moser on 2017-04-12

add recursive flag to do_umount, add --umount to block-meta

This adds a 'recursive' argument to util.do_umount, and utilizes
it from install.py. The basic idea of do_umount with recursive
is to walk through /proc/mounts in reverse and unmount anything
mounted under the provided mountpoint (or the mountpoint itself).

Also added here is use of that function from block-meta command.
We add a flag --umount to unmount filesystems at its end.

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
This branch contains Public information 
Everyone can see this information.

Subscribers