'mounted' events are handled synchronously in mountall, and the 'filesystem' isn't emitted until they're all done. Prelim tests seem to confirm that this is working correctly (and if it wasn't that would be a very bad bug, that I think we would have caught before now).
In a test instance from smoser, I've confirmed that a file touched directly by /etc/init/cloud-config.conf persists, whereas a file touched from within /var/lib/cloud/instance/scripts/runcmd is not created. As I'm not really familiar with the cloud-init architecture I can't effectively debug this further, but it's definitely not mountall causing the issue. ** Package changed: mountall (Ubuntu) => cloud-init (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: cloud-init parses yaml incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
