Merge lp://staging/~josvaz/vmbuilder/jenkins_kvm+fix-eth1boot into lp://staging/~ubuntu-on-ec2/vmbuilder/jenkins_kvm

Commit 774 re-applies the broken eth1+ autoconfig patch.
Commit 775 is the actual fix.
Commit 776 is a enhancement.

Although it looks good so far, this is still under testing.
Feel free to review and even Approve, but code won't be merged until all testing is completed succesfully.

Syntax looks good to me.

Will need more work, testing reveals that trusty fails to boot now.
This is a surprise, as the eth1+ patch tries to apply most changes to xenial, onward, leaving previous releases like trusty almost untouched, apart from using /run... for the ephemeral net devices config instead of /etc/network/interfaces/dynamic.d

upstart code path fixed with commit 777, please review

This MP has passed manual multi-nic tests for the combinations:
{Standard_DS2_v2,A8} x {precise, trusty, xenial, yakkety, zesty}

No issues or regressions found.

This looks good. Glad to hear that testing covered the two instance types across the full set of supported suites.

I will be merging this once I pass all AzureTests against all suites using test images

xenial tests:

https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/787/

Ubuntu_DAILY_BUILD-xenial-16_04-LTS-amd64-server-20161104-ethx-1478604131-en-us-30GB

The xenial test image passed AzureTests:
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/787

Trusty tests:
Ubuntu_DAILY_BUILD-trusty-14_04_5-LTS-amd64-server-20161104-ethx-1478613062-en-us-30GB
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/788/

Trusted passed

(Passed = unstable ONLY in lxd tests, success everywhere else)

Just discovered the precise test image is NOT properly built:
- It has the udev changes IN, instead of the upstart ones.

I checked trusty (that just passed the tests) and is ALSO using the udev change sinstead of the upstart.

I think something did not work as expected when bulding the Azure tests images. I am guessing I might have missed a build parameter setting. Precise & trusty were built as if SUITE was set to xenial or yakkety.

I can let yakkety pass the tests (as the image will be buolt correctly for it) and then repeat trusty test and add precise tests ONCE I get test images properly built for them.

Just a clarification, so far NOTHING is found wrong with the MP, the test images might have been misbuilt due to improper inputs. When I did test the MP manually trusty & precise where setup with upstart and no udev, as expected.

Yakkety tests:
Ubuntu_DAILY_BUILD-yakkety-16_10-amd64-server-20161105-ethx-1478613973-en-us-30GB
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/789/

Need to setup
https://cloud-images-jenkins.canonical.com/view/Azure/job/CloudImages_Azure-Custom_or_Test_Images/configure
So that the KVM scipt ALSO gets passed the proper SUITE variable.

Right now some scripts infer SUITE from VERSION. But the value is NOT job wide scope, so if it is not detected in the script, it is NOT set.

Yakkety tests failed in a couple of LXD test cases:
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/789/

Rerunning those as I think they are transients.

Yakkety tests passed, the issues were transient as suspected:
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/789/
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/790/

Pending are the precise, trusty & zesty tests, but for that I need first to fix this job:
https://cloud-images-jenkins.canonical.com/view/Azure/job/CloudImages_Azure-Custom_or_Test_Images/configure
To make sure the test images are generated with a proper SUITE setting.

Job fixed to compute SUITE from VERSION and export the value to a properties file that is later injected to all subsequent jobs:
https://cloud-images-jenkins.canonical.com/view/Azure/job/CloudImages_Azure-Custom_or_Test_Images/configure

Re-running trusty & precise test image generation:

trusty
https://cloud-images-jenkins.canonical.com/view/Azure/job/CloudImages_Azure-Custom_or_Test_Images/304

precise
https://cloud-images-jenkins.canonical.com/view/Azure/job/CloudImages_Azure-Custom_or_Test_Images/305

For some reason, the KVM builds of precise & trusty is STILL not getting my SUITE setting right.

Turns out that inside KVM the SUITE var used is in lowercase "suite"!

So instead of fixing the lack of consistency I should probably just fix this MP instead and use ${suite} instead of ${SUITE}

Suite variable used now by this MP is lowercase, so lets try it...

precise test image created correctly now:

Ubuntu_DAILY_BUILD-precise-12_04_5-LTS-amd64-server-20161109-ethx-1479204698-en-us-30GB

https://cloud-images-jenkins.canonical.com/view/Azure/job/CloudImages_Azure-Custom_or_Test_Images/307/console

proper precise test image in test here:
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/791/

trusty test image createc correctly:
Ubuntu_DAILY_BUILD-trusty-14_04_5-LTS-amd64-server-20161111-ethx-1479205498-en-us-30GB

https://cloud-images-jenkins.canonical.com/view/Azure/job/CloudImages_Azure-Custom_or_Test_Images/308/console

proper trusty test image in test here:
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/792/

trusty test image passed AzureTests as expected (only unstable at lxd tests):
https://cloud-images-jenkins.canonical.com/job/Azure-Tests/792/

precise test experienced a single failure, a transient:
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/791/

Rerun of the failed precise test passed at:
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/793/

This MP right now passes all AzureTests for all supported suites.

Zesty is missing but I fear I will continue to have issues creating a test image for it.

Please review and approve, also let me know if we should or not wait for zesty tests to marge this MP.

Might have fixed the zesty test image building for Azure, testing it here:
https://cloud-images-jenkins.canonical.com/view/Azure/job/CloudImages_Azure-Custom_or_Test_Images/311/console

zesty test image produced:
https://cloud-images-jenkins.canonical.com/view/Azure/job/CloudImages_Azure-Custom_or_Test_Images/311/console

Ubuntu_DAILY_BUILD-zesty-17_04-amd64-server-20161111-ethx-1479217570-en-us-30GB

Now I need to validate is probably built with this MP changes applied to the image.

Zesty image is good, it has the MP changes as expected.

Testing now at:
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/794/

Zesty passed:
https://cloud-images-jenkins.canonical.com/view/Azure/job/Azure-Tests/794/

As zesty can pass right now in Azure, which is azure-general fails due to a known issue, which bug I can't find at the moment.

Please, review, all test passed this is ready to go!

BTW, the zesty azure-general issue is:
https://bugs.launchpad.net/cloud-images/+bug/1638964

LGTM

+1 on the SuItE change.

This has been "git pull --rebase"d so that now they can be mergen cleanly

merged cleanly I meant