jenkins_kvm-philroche-trusty-supported-esm : Code : VMBuilder

Get this branch:: bzr branch lp://staging/~ubuntu-on-ec2/vmbuilder/jenkins_kvm-philroche-trusty-supported-esm

Members of Ubuntu on EC2 can upload to this branch. Log in for directions.

Branch merges

No branches dependent on this one.

Merged into lp://staging/~ubuntu-on-ec2/vmbuilder/jenkins_kvm at revision 827

David Krauser (community): Approve on 2019-05-02

Cody Shepherd (community): Approve on 2019-05-02

Related bugs

Link a bug report

Related blueprints

Branch information

Owner:: Ubuntu on EC2

Project:: VMBuilder

Status:: Development

Recent revisions

827. By Philip Roche on 2019-05-02

Bug fix for sorting non existent file

826. By Philip Roche on 2019-05-02

Merge lp:~ubuntu-on-ec2/vmbuilder/jenkins_kvm-philroche-trusty-supported into lp:~ubuntu-on-ec2/vmbuilder/jenkins_kvm [a=philroche] [r=codyshepherd,rcj]

Add Trusty to list of supported releases in ubuntu lists

MP: https://code.launchpad.net/~ubuntu-on-ec2/vmbuilder/jenkins_kvm-philroche-trusty-supported/+merge/366776

825. By Robert C Jennings on 2019-04-25

Merge lp:~rcj/vmbuilder/jenkins_kvm into lp:~ubuntu-on-ec2/vmbuilder/jenkins_kvm [a=rcj] [r=fginther,codyshepherd]

builder: Force boot with initramfs on disco

The initramfs-less boot causes a panic on initial boot for disco.
This should send it back to grub to reboot with an initramfs,
but the builder image is invoked with -no-reboot on the kvm command
line so the initramfs-less boot mechanism results in a panic and
no recovery. Rather than change how we launch to remove -no-reboot
this patch alters the grub environment to boot the first time with
an initrd.

Setting the initrdfail=1 grub variable for the builder means
that we boot correctly on the first boot and find the rootfs.

MP: https://code.launchpad.net/~rcj/vmbuilder/jenkins_kvm/+merge/366522

824. By Francis Ginther on 2019-04-24

Add cloud-init multi-nic workaround for SF Case #222480 (add for 16.04, 18.10, 19.04) [a=fginther][r=tobijk,davidkrauser]

When adding network devices after first boot, network configuration
data is not created and the devices are unusable.

This workaround creates a systemd drop-in file to clear out the
cloud-init persistent object forcing cloud-init to perform network
discovery on each boot.

MP: https://code.launchpad.net/~fginther/vmbuilder/jenkins_kvm-ci-wa-all/+merge/366457

823. By Robert C Jennings on 2019-04-23

Merge lp:~rcj/vmbuilder/jenkins_kvm into lp:~ubuntu-on-ec2/vmbuilder/jenkins_kvm [a=rcj] [r=codyshepherd,davidkrauser,fginther]

builder: Fixes to build disco images

Installation of qemu-user[-static] for disco image gets the chroot in
a state where the root filesystem can not be unmounted. This relates
to the binfmt-support package which is installed in the chroot as a
dependency of qemu-user. The simplest solution is to remove those
packages as the build system no longer requires them. This patch
retains the package installation in the prior supported releases.

MP: https://code.launchpad.net/~rcj/vmbuilder/jenkins_kvm/+merge/366297

822. By Francis Ginther on 2019-04-17

Add cloud-init multi-nic workaround for SF Case #222480

When adding network devices after first boot, network configuration data is not created and the devices are unusable.

This workaround creates a systemd drop-in file to clear out the cloud-init persistent object forcing cloud-init to perform network discovery on each boot.

821. By Tobias Koch on 2019-04-08

Merge lp:~ubuntu-on-ec2/vmbuilder/jenkins_kvm-disable-datasource-fix-bionic into lp:~ubuntu-on-ec2/vmbuilder/jenkins_kvm [a=tobijk] [r=davidkrauser,rcj]

Disable Azure data-source hotfix on Bionic

MP: https://code.launchpad.net/~ubuntu-on-ec2/vmbuilder/jenkins_kvm-disable-datasource-fix-bionic/+merge/365662