As I explained, the notion of "the last thing during boot" is not well-
defined with a partially ordered and parallel init system like systemd
or upstart (or even sysvinit+startpar).
So as long as cloud-init.service declares itself to run after rc-
local.service, then rc-local.service necessarily can't be "the" last
thing even accidentally. This is something to decide in cloud-
init.service.
** Changed in: systemd (Ubuntu)
Importance: High => Undecided
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468103
Title:
rc.local runs earlier than cloud-init.service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1468103/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
