@Pengpeng, Looking at the logs, the core of the issue seems to be the error in journal.txt and cloud-init-output.log: IsADirectoryError: [Errno 21] Is a directory: '/var/lib/cloud/instance'
I'm not really sure how that got that way. I had seen a bug like this before but have never been able to reproduce or understand where it comes from. /var/lib/cloud/instance should always be a symbolic link. Also, I think the logs show 2 boots. the 'modules:config' and 'modules:final' of one boot and then the 'init-local' and 'init' of a second boot. It seems like the clock was set backwards after the first. The best evidence of that is status.json. It is collected from /run, which is tmpfs filesystem, so it will only ever have a single boot in it. There we see: init started at 982.966233 init-local started at 861.9958138 modules-config started at 985.3238215 modules-final started at 985.8770518 for readability i cut off the '1539336' prefix from each of the times above. Ie, init logged it started at '1539336982.966233'. I suspect if you run 'cloud-init clean' the problem would resolve itself, but I'm not /var/lib/cloud/instance got to be a directory. Any ideas? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796875 Title: cloud-init and cloud-init-local services boot sequence does not obey dependency settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
