Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using juju 1.16.3 and I am attempting to use juju add-machine to get a MaaS node ready for a service deployment. I want to get Ubuntu installed and ready so service deployment takes less time. The machine is started and the OS installed, and the agent-state is "started". However, when I deploy a service, it decideds to start a new machine anyway and ignores the one already started.

When I deploy the service without doing add-machine beforehand, then a new machine is automatically allocated from MaaS and the service deploys to it just fine. The ONLY difference is that when I do juju add-machine prior to deploying the service, it won't deploy to that machine.

Am I misunderstanding the purpose of add-machine? If so, what is the proper method for preparing a machine with a base OS prior to service deployment?

share|improve this question

If you're using constraints at all, I think you've hit a consequence of this bug -- none of the existing machines will be matched.

You can work around it with the --to parameter to deploy or add-unit:

$ juju deploy mysql --to 3
$ juju add-unit mysql --to 4
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.