Adding boot-source keyring_data is confusing

[Edward Hope-Morley]

The boot-sources keyring_data option for the maascli is confusing and not self-documenting. The operation is fully documented here: http://maas.ubuntu.com/docs/bootsources.html#downloading-the-images-from-a-different-source but by reading the output of help for that operation it does not explain what needs to be done.

[Edward Hope-Morley (hopem)]

This is MAAS 1.9.1+bzr4543-0ubuntu1~trusty1

[Andres Rodriguez (andreserl)]

maas admin boot-sources create url='http://maas.ubuntu.com/images/ephemeral-v2/releases/' keyring_data='mQINBFCMc9EBEADDKn9'
{"__all__": ["One of keyring_data or keyring_filename must be specified."]}

looked into it and it seems it is not allowing to add keyring_data if no keyring_filename is specified. IT should allow me to add one or the other.

[Andres Rodriguez (andreserl)]

Also, this needs to be a file, not a string:

maas admin boot-sources create url='http://maas.ubuntu.com/images/ephemeral-v2/releases/' keyring_data@=./keyring.data
Success.
Machine-readable output follows:
{
    "url": "http://maas.ubuntu.com/images/ephemeral-v2/releases/",
    "keyring_filename": "",
    "id": 2,
    "resource_uri": "/MAAS/api/2.0/boot-sources/2/",
    "keyring_data": "bVFJTkJGQ01jOUVCRUFEREtuOQo="
}

[Edward Hope-Morley (hopem)]

OK I've now tried every possible combination I can think of to get this to work using the cli. I have tried:

    1 setting keyring_data=<base64-encoded gpg key>

    2 setting keyring_data@=<file-containing-base64-encoded-gpg-key>

    3 setting keyring_data@=<file-containing-raw-gpg-key>

    4 writing my key to a file and setting keyring_filename to point to that file.

Only method 4 appears to work but according to the MAAS folks, method 3 should work as well but as we can see here it does not - http://paste.ubuntu.com/15481253/

At least, the create succeeds but a subsequent boot-sources read fails. I think we need to get this fixed.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team