This completely breaks bos02, since the network interface and disk block device name have changed. Still, we decided to drop bos02, so this won't matter much, and even if we did want to go back to bos02, it's just a revert away :-)
Diff comments: > diff --git > a/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/tools/armhf-lxd.userdata > > b/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/tools/armhf-lxd.userdata > index bb50ada..291715b 100644 > --- > a/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/tools/armhf-lxd.userdata > +++ > b/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/tools/armhf-lxd.userdata > @@ -61,7 +61,6 @@ write_files: > ipv4.address: 10.0.4.1/24 > ipv4.nat: "true" > ipv6.address: none > - raw.dnsmasq: dhcp-option=6,91.189.91.130 Because this hardcoding is unnecessary, and is even not valid anymore in bos03 (nor in bos02 fwiw). This made LXD images building to fail, unable to resolve names. > description: "" > name: lxdbr0 > type: bridge -- https://code.launchpad.net/~hyask/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/463351 Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~hyask/autopkgtest-cloud:skia/lxd-remote-bos03 into autopkgtest-cloud:master. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
