Hi Scott, I think we would actually like to move to a world where cloud-init can function independently of the agent and does not start it. The walinuxagent service can then start after cloud-init is finished, and function as a guest agent to handle things like VM extensions, etc.
This behavior of cloud-init starting walinuxagent was needed early on to allow the agent to communicate with the wire server so that the provisioning ISO could be attached to the VM. That's no longer needed. All cloud-init needs to do is obtain the certificates for the SSH public key and post 'ready' to the fabric once it has processed its cloud- config. Steve -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623570 Title: Azure: cannot start walinux agent (Transaction order is cyclic.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1623570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
