~smoser/curtin/trunk.yakkety : changes

~smoser/curtin/trunk.yakkety » Changes from revision 405

From Revision 405 to 386

Rev	Summary	Authors	Date
405	shrink dictionary vertically in doc string shrink dictionary vertically in doc string	Scott Moser	7 years ago
404	add example ifconfig output add example ifconfig output	Scott Moser	7 years ago
403	fix flake8 fix flake8	Scott Moser	7 years ago
402	move the ifconfig parser to vmtests/helpers move the ifconfig parser to vmtests/helpers	Scott Moser	7 years ago
401	support parsing ifconfig output on yakkety support parsing ifconfig output on yakkety http://paste.ubuntu.com/17373461/ has some example data that is being parsed.	smoser at diglett	7 years ago
400	merge from trunk merge from trunk	Scott Moser	7 years ago
399	yakkety install logs are not necessarily readable as text yakkety install logs are not necessarily readable as text Without this, we could see errors like: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 96684: ordinal not in range(128) This is just the same fix that was applied some time ago 3 lines up when reading the boot log.	Scott Moser	7 years ago
398	set fallback kernel to 'linux-generic' set fallback kernel to 'linux-generic' this is making yakkety work much nicer, and we should definitely have a fallback. I'm just not sure that this is the right way to do this. It seems like some more involved kernel package handling might be needed. For example * an image might have a kernel installed already. They'd reasonably want to just use that kernel as is. * installing 'package' could result in 2 kernels being installed and 'package' kernel not even being selected as it is older. some thought required.	Scott Moser	7 years ago
397	fix bug in fallback kernel installation fix bug in fallback kernel installation fallback kernel installation installed into the host environment.	Scott Moser	7 years ago
396	revert previous commit revert previous commit While the assumption of getting a bootloader by instaling linux-generic is definitely an assumption, its one that still works.	Scott Moser	7 years ago
395	if amd64 and not uefi, ensure that grub-pc is installed. if amd64 and not uefi, ensure that grub-pc is installed. We were getting this for free somehow in a dependency of linux-generic in xenial. That seems to have changed, and images do not have grub-pc installed, so we need to install it.	smoser at diglett	7 years ago
394	tests/vmtests: add yakkety, remove vivid tests/vmtests: add yakkety, remove vivid Wily is unsupported now, so remove those tests. Add Yakkety tests for any test that had a xenial.	smoser at diglett	7 years ago
393	spelling spelling	Scott Moser	7 years ago
392	log cleanup log cleanup	Scott Moser	7 years ago
391	improve net-meta network configuration improve net-meta network configuration when network configuration is not provided 'net-meta' would write a very simplistic /etc/network/interfaces file for each of the devices that were brought up in install environment. This had the following issues a.) it did not disable cloud-init networking b.) it did not account for naming of devices (causing issue if devices changed names between install and boot environment). c.) did not include interfaces.d as ideally it would.	Scott Moser	7 years ago
390	curtin/net: fix inet value for subnets, don't add interface ... curtin/net: fix inet value for subnets, don't add interface attributes to alias Apply two separate fixes for configuring bonding with ip aliases. Curtin re-used the interface's inet value for each subnet that might be configured. In the case where the configuration included an ipv4 address after an ipv6 one resulted in emitting 'inet6' for ipv4 address which is not correct. Resolve this issue by calculating the inet value independent of the current status of the iface, using the subnet config instead. When rendering a network_config which includes ip alias interfaces do not emit any attributes, like MTU, or bond/bridge options Including these values is almost always wrong or will result in confusing behavior on the target system.	Ryan Harper	7 years ago
389	Detect and remove legacy /etc/network/interfaces.d/eth0.cfg ... Detect and remove legacy /etc/network/interfaces.d/eth0.cfg from target Prior to Xenial release, Ubuntu Cloud images included a default network configuration in /etc/network/interfaces.d/eth0.conf. The presence of this legacy configuration file can cause a delay during boot when cloud- init is expecting a non-existent interface to become available. curtin installations handle configuring networking in the target installed system subsequently the embedded configuration is not needed. This patch reuses most of cloud-init's version of detecting and examining the legacy config, confirming if the contents are what is expected. Upon finding expected content the file will be removed, otherwise it will remain. Additional changes to vmtest and unittest were added to remove the reliance on fallback nic naming (eth0); we always use non-kernel names in our configuration now. An additional common test has been added to check that in all cases we ensure we remove the embedded config.	Ryan Harper	7 years ago
388	vmtests: Add Xenial to LVM test bucket. vmtests: Add Xenial to LVM test bucket.	Ryan Harper	7 years ago
387	fix timestamp in reporting events. fix timestamp in reporting events. If no timestamp was passed into a ReportingEvent, then the default was used. That default was 'time.time()' which was evaluated once only at import time.	Scott Moser	8 years ago
386	debian/control: add bcache-tools dependency debian/control: add bcache-tools dependency	Scott Moser	8 years ago

Older »