CI Storage tests failed because tmpfs now has life data

[Curtis Hovey]

As seen at
    http://reports.vapour.ws/releases/issue/58b988f5749a562867f5003e

The storage test fails because there is a new life key deep in the data that does not meet expectations. The expected data is there, but the extra key cause a failure of matching the dict.

JujuAssertionError: Found: {u'storage': {u'data/0': {u'kind': u'filesystem', u'attachments': {u'units': {u'dummy-storage-fs/0': {u'life': u'alive', u'location': u'/srv/data'}}}, u'life': u'alive'}}, u'filesystems': {u'0/0': {u'status': {u'current': u'attached', u'since': u'03 Mar 2017 08:25:07Z'}, u'life': u'alive', u'provider-id': u'0/0', u'Attachments': {u'units': {u'dummy-storage-fs/0': {u'machine': u'0', u'life': u'alive', u'location': u'/srv/data'}}, u'machines': {u'0': {u'mount-point': u'/srv/data', u'life': u'alive', u'read-only': False}}}, u'storage': u'data/0', u'pool': u'rootfs', u'size': 7924}}}
Expected: {'storage': {'data/0': {'kind': 'filesystem', 'attachments': {'units': {'dummy-storage-fs/0': {'location': '/srv/data'}}}}}}

[Curtis Hovey (sinzui)]

Juju 2.2 officially includes the "life" field to inform users about the state of the storage. CI should fail Juju if the storge life is in a bad state. We do not want to change the test to ignore "life", when the client is 2.2+, it should expect "life: alive".

[Curtis Hovey (sinzui)]

Support for block/disk life also landed. The test needs to expect life: alive for both filesystem and block types.