block-device doesn't accept whitelist
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
swift-storage (Juju Charms Collection) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Setting block-device to a whitelist of many possible block device names leads to a traceback in the charm.
2014-04-27 11:09:27 INFO install Traceback (most recent call last):
2014-04-27 11:09:27 INFO install File "/var/lib/
2014-04-27 11:09:27 INFO install main()
2014-04-27 11:09:27 INFO install File "/var/lib/
2014-04-27 11:09:27 INFO install hooks.execute(
2014-04-27 11:09:27 INFO install File "/var/lib/
2014-04-27 11:09:27 INFO install self._hooks[
2014-04-27 11:09:27 INFO install File "/var/lib/
2014-04-27 11:09:27 INFO install setup_storage()
2014-04-27 11:09:27 INFO install File "/var/lib/
2014-04-27 11:09:27 INFO install for dev in determine_
2014-04-27 11:09:27 INFO install File "/var/lib/
2014-04-27 11:09:27 INFO install return [ensure_
2014-04-27 11:09:27 INFO install File "/var/lib/
2014-04-27 11:09:27 INFO install if not is_block_
2014-04-27 11:09:27 INFO install File "/var/lib/
2014-04-27 11:09:27 INFO install return S_ISBLK(
2014-04-27 11:09:27 INFO install OSError: [Errno 2] No such file or directory: '/dev/vdb'
I would expect either is_block_device() to return False if the path doesn't exist, or the call is guarded around a exists() check.
tags: | added: cloud-installer |
tags: | added: openstack |
Changed in swift-storage (Juju Charms Collection): | |
status: | Triaged → Fix Released |
milestone: | none → 15.01 |
We implemented such a feature into the /next branch on rev 30; I'll see if that's SRU'able.