iscsi error deploying overcloud

[Ben Nemec]

When deploying a two-node overcloud (one compute node and one control node), the control node deployment failed with the following error in nova-baremetal-deploy-helper.log:

2013-11-01 11:34:58.311 19256 ERROR nova.virt.baremetal.deploy_helper [-] deployment to node 1 failed
2013-11-01 11:34:58.311 19256 TRACE nova.virt.baremetal.deploy_helper Traceback (most recent call last):
2013-11-01 11:34:58.311 19256 TRACE nova.virt.baremetal.deploy_helper File "/usr/lib/python2.7/site-packages/nova/cmd/baremetal_deploy_helper.py", line 252, in run
2013-11-01 11:34:58.311 19256 TRACE nova.virt.baremetal.deploy_helper deploy(**params)
2013-11-01 11:34:58.311 19256 TRACE nova.virt.baremetal.deploy_helper File "/usr/lib/python2.7/site-packages/nova/cmd/baremetal_deploy_helper.py", line 211, in deploy
2013-11-01 11:34:58.311 19256 TRACE nova.virt.baremetal.deploy_helper root_uuid = work_on_disk(dev, root_mb, swap_mb, image_path)
2013-11-01 11:34:58.311 19256 TRACE nova.virt.baremetal.deploy_helper File "/usr/lib/python2.7/site-packages/nova/cmd/baremetal_deploy_helper.py", line 180, in work_on_disk
2013-11-01 11:34:58.311 19256 TRACE nova.virt.baremetal.deploy_helper if not is_block_device(dev):
2013-11-01 11:34:58.311 19256 TRACE nova.virt.baremetal.deploy_helper File "/usr/lib/python2.7/site-packages/nova/cmd/baremetal_deploy_helper.py", line 103, in is_block_device
2013-11-01 11:34:58.311 19256 TRACE nova.virt.baremetal.deploy_helper s = os.stat(dev)
2013-11-01 11:34:58.311 19256 TRACE nova.virt.baremetal.deploy_helper OSError: [Errno 2] No such file or directory: '/dev/disk/by-path/ip-192.0.2.67:3260-iscsi-iqn-9b34bcf9-3404-4f02-8488-ef5a056161d7-lun-1'
2013-11-01 11:34:58.311 19256 TRACE nova.virt.baremetal.deploy_helper

The compute node appears to have deployed successfully. James Slagle ran into a similar problem and said restarting iscsid resolved it for him. That doesn't seem to have done the trick for me, so I'm still looking into what's wrong in my case.

[Ben Nemec (bnemec)]

This appears to have been a memory shortage issue on my host. When I resized all of my VMs down 512 MB everything booted correctly.