Comment 3 for bug 1513204

@jamespage

This is odd. I added udevadm settle like so, so that it is called before the storage operations:
lp:~openstack-charmers/charms/trusty/swift-storage/next

The udevadm command itself errored.

When I went back into the unit, I was able to do the udevadm commands and such without error.

I've not dug deeper than that. I'll hold on this, pending your input.

FWIW, when I arrived at the unit, a previous deployment's ceph gpt was still present on /dev/sdb:

root@decisive-punishment:/var/log# sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
└─sda1 8:1 0 465.8G 0 part /
sdb 8:16 0 465.8G 0 disk
├─sdb1 8:17 0 464.8G 0 part
└─sdb2 8:18 0 1023M 0 part
sr0 11:0 1 1024M 0 rom

root@decisive-punishment:/var/log# sudo parted -l
Model: ATA ST9500620NS (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 1049kB 500GB 500GB primary ext4 boot

Model: ATA ST9500620NS (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
 2 1049kB 1074MB 1073MB ceph journal
 1 1075MB 500GB 499GB xfs ceph data