filesystem 2.0 schema check failed: mount_point: expected string, got nothing

Bug #1575808 reported by Martin Packman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Michael Foord

Bug Description

Bootstrapping MAAS 2.0 (beta4+bzr4958) on finfolk vmaas fails with the following error:

2016-04-27 17:19:09 ERROR cmd supercommand.go:448 failed to bootstrap model: cannot start bootstrap instance: cannot run instances: cannot run instance: blockdevice 0: partition 0: filesystem 2.0 schema check failed: mount_point: expected string, got nothing

This is apparently because some of the filesystems of an allocated machine are 'null' rather than containing the configuration juju expects:

<http://paste.ubuntu.com/16085749/>

$ maas env20 block-devices read node-ce3fd804-71e4-11e5-80fe-525400c43ce5
[
    {
        ...
        "filesystem": null,
        "used_for": "MBR partitioned with 1 partition",
        ...
    },
    {
        ...
        "filesystem": null,
        "used_for": "Unused",
        ...
    },
    {
        ...
        "filesystem": {
            "uuid": "ac5c61b8-84bb-4b10-b399-466570bae392",
            "mount_point": "/",
            "label": "root",
            "mount_options": null,
            "fstype": "ext4"
        },
        "used_for": "ext4 formatted filesystem mounted at /",
        ...
    }
]

Michael Foord (mfoord)
Changed in juju-core:
status: Triaged → In Progress
assignee: nobody → Michael Foord (mfoord)
Michael Foord (mfoord)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta7 → none
milestone: none → 2.0-beta7
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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