I don't think this is Nova's responsibility - as long as the new block device shows up with `lsblk`, it's up to the guest OS/tooling to mount it (or not). I've changed the component to cloud-init in case there's something actionable for them in this bug. Thanks!
** Project changed: nova => cloud-init ** Tags removed: libvirt resize -- 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/1826519 Title: Ephemeral disk volume was not mounted after resizing from non- ephemeral flavor Status in cloud-init: New Bug description: Description =========== After resizing from m1.flavor(no ephemeral disk) to d1.flavor(with ephemeral disk), ephemeral disk does not mounted on the VM. After digging the related code, I realize there is no action to re-run cloudinit's mount module. By default, cloudinit does not rerun previously running module. Since mount module does not take action, cloudinit does not write ephemeral disk data to /etc/fstab. Steps to reproduce ================== 1. Make VM with m1.small flavor which does not have ephemeral disk 2. Resize VM with d1.small flavor which have ephemeral disk Expected result =============== 1. Ephemeral disk volume (/dev/sdb) was mounted at /mnt Actual result ============= 1. There is /dev/sdb in there by 'lsblk', but not mounted Environment =========== Stable/ocata Libvirt driver Logs & Configs ============== To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1826519/+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
