Comment 1 for bug 1633249

Just ran into this while looking at another bug. Specifying a pysical_block_size doesn't seem to work any longer so you end up with a boot failure. The annoying things are that first off even though boot failed the Instance is listed as Active and Up, and then after deteting the failure, and deleting the Instance as reported in this bug the volume is never detached.

Looking at the logs it appears that the cleanup never issues any of the Cinder calls to clean things up.