MAAS

[2.2, r5770, UI] No block devices listed in UI after commissioning

Bug #1669221 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
LaMont Jones
MAAS 2.2.0

Bug Description

After commissioning, I noticed that the machine didn't have any block devices, which is obviously a regression. That said, the commissioning script for block devices was successful:

00-maas-07-block-devices Wed, 01 Mar. 2017 21:24:22 Passed

[
{
"SERIAL": "S24BNXAH218013Z",
"RO": "0",
"ROTA": "0",
"BLOCK_SIZE": "4096",
"NAME": "sda",
"RM": "0",
"SIZE": "250059350016",
"PATH": "/dev/sda",
"MODEL": "Samsung SSD 850",
"ID_PATH": "/dev/disk/by-id/wwn-0x5002538d40b3d537",
"SATA": "1",
"RPM": "0"
},
{
"SIZE": "188272640",
"PATH": "/dev/sdb",
"SERIAL": "60000000000000000e00000000030001",
"MODEL": "VIRTUAL-DISK",
"ROTA": "1",
"ID_PATH": "/dev/disk/by-id/wwn-0x60000000000000000e00000000030001",
"RO": "1",
"BLOCK_SIZE": "1024",
"NAME": "sdb",
"RM": "0"
}
]

00-maas-07-block-devices.err Wed, 01 Mar. 2017 21:24:22 Passed

sudo: unable to resolve host node01
sudo: unable to resolve host node01
sudo: unable to resolve host node01
sudo: unable to resolve host node01

Also, note that machines show correctly the amount of storage, just doesn't list the block devices.

node01.maas Ready 4 16.0 1 250.1
node02.maas Ready 4 8.0 1 250.1
node03.maas Ready admin 4 8.0 1 120.0
node04.maas Ready 4 8.0 1 120.0
node05.maas Ready 4 8.0 1 120.0

See original description

Related branches

lp://qastaging/~lamont/maas/bug-1669221
Blake Rouse (community): Approve
Diff: 15 lines (+2/-2)
1 file modified
src/maasserver/static/partials/node-details.html (+2/-2)
Andres Rodriguez (andreserl)
Changed in maas:
importance: Undecided → Critical
status: New → Triaged
milestone: none → 2.2.0
Revision history for this message
Andres Rodriguez (andreserl) wrote : Re: [2.2, r5770, UI] No block devices after commissioning

machines read shows:

        "physicalblockdevice_set": [
            {
                "used_for": "GPT partitioned with 2 partitions",
                "tags": [
                    "ssd",
                    "sata"
                ],
                "available_size": 0,
                "id": 3,
                "block_size": 4096,
                "size": 120034123776,
                "filesystem": null,
                "path": "/dev/disk/by-dname/sda",
                "used_size": 120033640448,
                "id_path": "/dev/disk/by-id/wwn-0x5002538d4094d99a",
                "type": "physical",
                "serial": "S24ANXAH102398W",
                "resource_uri": "/MAAS/api/2.0/nodes/b7r7et/blockdevices/3/",
                "system_id": "b7r7et",
                "partitions": [
                    {
                        "used_for": "fat32 formatted filesystem mounted at /boot/efi",
                        "filesystem": {
                            "mount_options": null,
                            "mount_point": "/boot/efi",
                            "fstype": "fat32",
                            "label": "efi",
                            "uuid": "79836e19-d50a-4384-b22c-f601b1f612bb"
                        },
                        "id": 4,
                        "device_id": 3,
                        "size": 536870912,
                        "system_id": "b7r7et",
                        "resource_uri": "/MAAS/api/2.0/nodes/b7r7et/blockdevices/3/partition/4",
                        "bootable": true,
                        "uuid": "a6c68074-b81d-411b-863a-2b3669b766b0",
                        "path": "/dev/disk/by-dname/sda-part1",
                        "type": "partition"
                    },

summary: - [2.2, 5770] No block devices after commissioning
+ [2.2, r5770] No block devices after commissioning
description: updated
summary: - [2.2, r5770] No block devices after commissioning
+ [2.2, r5770, UI] No block devices after commissioning
Revision history for this message
Andres Rodriguez (andreserl) wrote :

fwiw, the node deployed fine, so itis a UI issue.

summary: - [2.2, r5770, UI] No block devices after commissioning
+ [2.2, r5770, UI] No block devices listed in UI after commissioning
Revision history for this message
Blake Rouse (blake-rouse) wrote :

When you reloaded the page did they appear? Or are they always missing?

Revision history for this message
Andres Rodriguez (andreserl) wrote :

They are always missing.

Revision history for this message
Blake Rouse (blake-rouse) wrote :

If they are always missing but the exist over the API then I would say the change lamont made to the websocket handler for devices has broken machines.

LaMont Jones (lamont)
Changed in maas:
assignee: nobody → LaMont Jones (lamont)
MAAS Lander (maas-lander)
Changed in maas:
status: Triaged → Fix Committed
Andres Rodriguez (andreserl)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.