[2.2] Adding custom image with ddxz filetype seems to think it is root-tgz

[Andres Rodriguez]

I added a custom image like this:

maas admin boot-resources create name=customcore16 title="Custom Ubuntu Core test" architecture='amd64/generic' filetype=ddxz content@=curtin-ubuntu-core-16-pc-amd64.img.xz

And during the deployment process, this happened:

curtin: Installation started. (0.1.0~bzr480-0ubuntu1~ubuntu16.04.1)
--2017-04-12 21:31:20-- http://192.168.122.2:5248/images/custom/amd64/generic/customcore16/uploaded/root-tgz
Connecting to 192.168.122.2:5248... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-04-12 21:31:20 ERROR 404: Not Found.

tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
Unexpected error while running command.
Command: ['sh', '-cf', 'wget "$1" --progress=dot:mega -O - |smtar -C "$2" --xattrs --xattrs-include=* -Sxpf - --numeric-owner', '--', 'http://192.168.122.2:5248/images/custom/amd64/generic/customcore16/uploaded/root-tgz', '/tmp/tmpxmixd1rx/target']
Exit code: 2
Reason: -
Stdout: ''
Stderr: ''
curtin: Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'extract']
Exit code: 3
Reason: -
Stdout: --2017-04-12 21:31:20-- http://192.168.122.2:5248/images/custom/amd64/generic/customcore16/uploaded/root-tgz
        Connecting to 192.168.122.2:5248... connected.
        HTTP request sent, awaiting response... 404 Not Found
        2017-04-12 21:31:20 ERROR 404: Not Found.

        tar: This does not look like a tar archive
        tar: Exiting with failure status due to previous errors
        Unexpected error while running command.
        Command: ['sh', '-cf', 'wget "$1" --progress=dot:mega -O - |smtar -C "$2" --xattrs --xattrs-include=* -Sxpf - --numeric-owner', '--', 'http://192.168.122.2:5248/images/custom/amd64/generic/customcore16/uploaded/root-tgz', '/tmp/tmpxmixd1rx/target']
        Exit code: 2
        Reason: -
        Stdout: ''
        Stderr: ''

Stderr: ''

[Paul Larson (pwlars)]

I think for this to work, the custom osystem driver would have to be taught about ddxz. Right now it checks for a file that exists called "root-dd" and if it doesn't find it, it assumes it is root-tgz