Comment 12 for bug 1890803

Revision history for this message
Sean Feole (sfeole) wrote :

Due to the major inconsistencies between all of the maas servers affected. I did this Started from scratch...

1.) Deployed Maas Snap from maas/stable 2.8
2.) Configured AMD64 groovy to download using the custom mirror (https://images.maas.io/ephemeral-v3/daily/)

3.) Because this was a test MAAS, i ensured DHCP was disabled and created a DHCP snippet on our production MAAS to direct all pxe requests to the test MAAS

4.) Test Deployed the machine( Success, the new test MAAS saw the enlisted machine)
5.) Successfully commissioned with 18.04
6.) Attempted to Deploy 20.10(Using the latest -daily)

 6a) This daily should include the latest fix for the following: https://bugs.launchpad.net/cloud-init/+bug/1886531 (per http://cloud-images.ubuntu.com/groovy/current/groovy-server-cloudimg-amd64.manifest this image has cloud-init 20.2-94-g3d06abc2-0ubuntu1 So 20200811 or later should work)

The deploy still fails.

I tried the oldest maas.io cloud image here: https://images.maas.io/ephemeral-v3/daily/groovy/amd64/ and still have the same outcome as the attached machine.txt