Andres,
Yes, if I submit a POST with the valid headers to /MAAS/api/2.0/license-keys/ with osystem=windows, distro_series=win2016-std, license_key=validkey to the license-keys endpoint I get:
{
"distro_series": [ "'windows/win2016-std' is not a valid distro_series. It should be one of: 'windows/win2016'."
]
}
If I try the same thing with distro_series=win2016 I get:
Andres, 2.0/license- keys/ with osystem=windows, distro_ series= win2016- std, license_ key=validkey to the license-keys endpoint I get:
Yes, if I submit a POST with the valid headers to /MAAS/api/
{ series" : [
"'windows/ win2016- std' is not a valid distro_series. It should be one of: 'windows/win2016'."
"distro_
]
}
If I try the same thing with distro_ series= win2016 I get:
'LicenseKey' object is not iterable
which may be a separate bug. When I use the CLI:
$ maas admin license-keys create osystem=windows distro_ series= win2016- std license_ key=XXXXX- XXXXX-XXXXX- XXXXX-XXXXX
I get:
{"distro_series": ["'windows/ win2016- std' is not a valid distro_series. It should be one of: 'windows/ win2016' ."]}
$ maas admin license-keys create osystem=windows distro_ series= win2016 license_ key=XXXXX- XXXXX-XXXXX- XXXXX-XXXXX
On the cli with distro_ series= win2016:
Success. series" : "win2016", XXXXX-XXXXX- XXXXX-XXXXX" , api/2.0/ license- key/windows/ win2016"
Machine-readable output follows:
{
"osystem": "windows",
"distro_
"license_key": "XXXXX-
"resource_uri": "/MAAS/
}