Comment 11 for bug 1649652

I've run curtin's vmtest testsuite on a test added to show this bug
 tests/vmtests/test_network_static_routes.py
Additionally, there were unit tests added that run during package
build.

Ran curtin vmtest like:

# get curtin for it tests at revision 460
$ bzr branch lp:curtin curtin.dist
$ bzr branch -r 460 curtin.dist curtin-r460
$ cd curtin-r460
## need to get 'curtainer' and 'curtin-in-container' from trunk
$ cp ../trunk.dist/tools/{curtainer,curtin-from-container} tools/
$ ./tools/vmtest-system-setup
$ ./tools/curtainer --proposed ubuntu-daily:yakkety sm-curtin-y1
Setting up curtin-common (0.1.0~bzr460-0ubuntu1~16.10.1) ...
Setting up python3-curtin (0.1.0~bzr460-0ubuntu1~16.10.1) ...
Setting up curtin (0.1.0~bzr460-0ubuntu1~16.10.1) ...

# bug 1649652 tests/vmtests/test_network_static_routes.py
$ name=sm-curtin-y1
$ CURTIN_VMTEST_TOPDIR=$PWD/$name CURTIN_VMTEST_CURTIN_EXE="./tools/curtin-from-container $name curtin" \
   ./tools/jenkins-runner tests/vmtests/test_network_static_routes.py

Note, due to packaging bug 1666986, we see in the installation logs:
   curtin: Installation started. (0.1.0)
when that is fixed, we'll start seeing 0.1.0~bzr460-0ubuntu1~16.10.1.