Comment 23 for bug 1686514

Revision history for this message
Joshua Powers (powersj) wrote :

Zesty Steps to reproduce
1. Launch an L32s instance with 17.04 (Zesty)
2. Verify /mnt is mounted (mount or lsblk)
3. Update to proposed
4. From Azure console, redeploy the instance
5. Login and look if /mnt is mounted. If it is mounted, GOTO 4

I have seen it work properly before, so a second redeploy got the issue to appear.

cloud-init.log http://paste.ubuntu.com/24926325/
cloud-init-output.log http://paste.ubuntu.com/24926327/
journal http://paste.ubuntu.com/24926328/
syslog http://paste.ubuntu.com/24926329/