import of i386 images on MAAS 2.1 fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maas-cert-server |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
running maniacs-setup to build a new install MAAS 2.1 server on 16.04.1 host.
During the "import point releases" phase, the i386 images seem to be rejected with the following messages appearing on console:
* Loading Ubuntu 16.04.1 GA (i386)
--2016-11-15 09:56:11-- http://
Resolving certification-
Connecting to certification-
HTTP request sent, awaiting response... 200 OK
Length: 382065351 (364M) [application/
Saving to: ‘/tmp/ubuntu-
ubuntu-
2016-11-15 09:59:18 (1.94 MB/s) - ‘/tmp/ubuntu-
{"architecture": ["'i386/generic' is not a valid architecture. It should be one of: 'amd64/generic'."]}
all i386 images for 16.04 resulted in that error. I didn't bother with Trusty or Precise images at this time.
I have a feeling MAAS has dropped support for 32bit altogether so perhaps we should as well.
EDIT: Turns out user error/misunders
Changed in maas-cert-server: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
description: | updated |
So after some chatting with the maas team and me pulling out tufts of hair in frustration, I finally figured it out.
Once the initial import is done, you need to do the following steps (manually, the automated part can come from this):
1: fine the boot source ID (likely 1, since that's the first one you get automatically) critical- maas:~$ maas admin boot-sources read
"keyring_ filename" : "/usr/share/ keyrings/ ubuntu- cloudimage- keyring. gpg", 14T18:32: 00.358" , images. maas.io/ ephemeral- v3/daily/",
"keyring_ data": "", 14T18:32: 00.358" ,
"resource_ uri": "/MAAS/ api/2.0/ boot-sources/ 1/"
bladernr@
Success.
Machine-readable output follows:
[
{
"created": "2016-11-
"url": "http://
"id": 1,
"updated": "2016-11-
}
]
which yields an ID of 1.
then you need to find the boot-resource- selection ID (also default of 1): critical- maas:~$ maas admin boot-source- selections read 1
"subarches" : [
"resource_ uri": "/MAAS/ api/2.0/ boot-sources/ 1/selections/ 1/"
bladernr@
Success.
Machine-readable output follows:
[
{
"*"
],
"arches": [
"amd64"
],
"id": 1,
"os": "ubuntu",
"labels": [
"*"
],
"release": "xenial",
}
]
Note that also has an ID of 1.
Then you need to modify that selection like so:
bladernr@ critical- maas:~$ maas admin boot-source- selection update 1 1 arches="amd64" arches="i386" api/2.0/ boot-sources/ 1/selections/ 1/"
Success.
Machine-readable output follows:
{
"subarches": [
"*"
],
"arches": [
"amd64",
"i386"
],
"id": 1,
"os": "ubuntu",
"labels": [
"*"
],
"release": "xenial",
"resource_uri": "/MAAS/
}
THEN you need to redo the import: critical- maas:~$ maas admin boot-resources import
bladernr@
Success.
Machine-readable output follows:
Import of boot resources started
and that should pull in i386.
Now, I have a suspicion that perhaps we can do the modification BEFORE we run the first import.
So the steps would be:
Find the source ID
find the selections ID
modify (or possibly create) the selection
THEN run the import
which should pull in both i386 and amd64 (or whatever we list/modify).
More can be found here: maas.io/ docs/en/ manage- cli-images
http://
additionally, maybe it's worth finding a way to list available arches and ask which ones to import, as some users may only need to pull in power, or arm, or amd64. or combinations of the available ones like "amd64, ppc64el"