Containerized deployment fails when using SwiftRawDisk

[Christian Schwede]

The overcloud deployment fails when using the SwiftRawDisk parameter in an containerized environment. For example, using the following extra parameter (and assuming vdb exists on the node):

parameter_defaults:
  SwiftRawDisks: {"vdb": {}}

It fails with:

2017-11-16 10:52:25Z [overcloud-AllNodesDeploySteps-xphavjpwjygo-ObjectStorageHostPrepDeployment-3g5i3zt5h7rt.0]: UPDATE_FAILED Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
2017-11-16 10:52:25Z [overcloud-AllNodesDeploySteps-xphavjpwjygo-ObjectStorageHostPrepDeployment-3g5i3zt5h7rt]: UPDATE_FAILED Resource UPDATE failed: Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
2017-11-16 10:52:26Z [overcloud-AllNodesDeploySteps-xphavjpwjygo.ObjectStorageHostPrepDeployment]: UPDATE_FAILED Error: resources.ObjectStorageHostPrepDeployment.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2
2017-11-16 10:52:26Z [overcloud-AllNodesDeploySteps-xphavjpwjygo]: UPDATE_FAILED Resource UPDATE failed: Error: resources.ObjectStorageHostPrepDeployment.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2
2017-11-16 10:52:27Z [AllNodesDeploySteps]: UPDATE_FAILED Error: resources.AllNodesDeploySteps.resources.ObjectStorageHostPrepDeployment.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2
2017-11-16 10:52:27Z [overcloud]: UPDATE_FAILED Resource UPDATE failed: Error: resources.AllNodesDeploySteps.resources.ObjectStorageHostPrepDeployment.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2

 Stack overcloud UPDATE_FAILED

overcloud.AllNodesDeploySteps.ObjectStorageHostPrepDeployment.0:
  resource_type: OS::Heat::SoftwareDeployment
  physical_resource_id: 5cd7e1aa-f23f-4987-8f26-6a9743d9c37a
  status: UPDATE_FAILED
  status_reason: |
    Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
  deploy_stdout: |
    ...
    TASK [swift logs readme] *******************************************************
    ok: [localhost]

    TASK [Format and mount devices defined in SwiftRawDisks] ***********************
    failed: [localhost] (item=vdb) => {"changed": false, "failed": true, "item": "vdb", "msg": "Error mounting /srv/node/vdb: mount: wrong fs type, bad option, bad superblock on /dev/vdb,\n missing codepage or helper program, or other error\n\n In some cases useful info is found in syslog - try\n dmesg | tail or so.\n"}
     to retry, use: --limit @/var/lib/heat-config/heat-config-ansible/c2d2d354-aa77-4d10-8be2-e62c7e5a8351_playbook.retry

    PLAY RECAP *********************************************************************
    localhost : ok=3 changed=0 unreachable=0 failed=1

    (truncated, view all with --long)
  deploy_stderr: |

Heat Stack update failed.

This is due to the fact that the device is not formatted when running in a containerized environment.

A fix has already been proposed upstream: https://review.openstack.org/#/c/516436/1

[Christian Schwede (cschwede)]

This has been merged months ago (https://review.openstack.org/#/c/516436/), closing.