Reopening this - once we've configured services to use /mnt, its a
fairly fatal error when we nova rebuild the machine (preserving the
state partition) but said services start up after cloud init but before
our workaround-hack to fix things. E.g. our hack is insufficient.
** Changed in: tripleo
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1263294
Title:
ephemeral0 of /dev/sda1 triggers 'did not find entry for sda1 in
/sys/block'
Status in Init scripts for use on cloud images:
Triaged
Status in tripleo - openstack on openstack:
Triaged
Bug description:
This is due to line 227 of ./cloudinit/config/cc_mounts.py::
short_name = os.path.basename(device)
sys_path = "/sys/block/%s" % short_name
if not os.path.exists(sys_path):
LOG.debug("did not find entry for %s in /sys/block", short_name)
return None
The sys path for /dev/sda1 is /sys/block/sda/sda1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1263294/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
