Cannot deploy to multiple containers on a host using -n

[Aaron Bentley]

$ juju --show-log deploy -e test-release-hp-new -n 2 --to lxc:1 ubuntu ubuntu1
error: cannot use --num-units > 1 with --to

This could work, because it means "deploy 2 containers as machines on host 1". The error makes sense for --to targets that are a single machine, but that is not the case with lxc:n syntax.

[Aaron Bentley (abentley)]

Why is this won't fix?

[Anastasia (anastasia-macmood)]

@Aaron Bentley,
"juju-core" is an old Juju 1 project. We only accept Critical bugs here that may still need to be addressed in 1.25 series.

"juju" is the new project for bugs/issues/suggestions for Juju 2. An email went out couple of months ago saying that we will be moving some bugs over, the rest will be closed "eventually" unless people are interested in having us addressing their concerns in Juju 2. "Eventually" is now :D since Juju 2 was released last week \o/

I am happy to re-target this to "juju" if you would like us to keep it.

[Richard Harding (rharding)]

This is a bug against 1.25 which is in critical fix only mode. So any bugs
that we're not going to address on juju-core are getting marked "won't
fix".

On Mon, Oct 17, 2016 at 9:27 AM Aaron Bentley <email address hidden>
wrote:

> Why is this won't fix?
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1384350
>
> Title:
> Cannot deploy to multiple containers on a host using -n
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1384350/+subscriptions
>

[Aaron Bentley (abentley)]

Yes, please re-target.

On 2016-10-17 09:32 AM, Anastasia wrote:
> @Aaron Bentley,
> "juju-core" is an old Juju 1 project. We only accept Critical bugs here that may still need to be addressed in 1.25 series.
>
> "juju" is the new project for bugs/issues/suggestions for Juju 2. An
> email went out couple of months ago saying that we will be moving some
> bugs over, the rest will be closed "eventually" unless people are
> interested in having us addressing their concerns in Juju 2.
> "Eventually" is now :D since Juju 2 was released last week \o/
>
> I am happy to re-target this to "juju" if you would like us to keep it.
>

[Aaron Bentley (abentley)]

Okay, so why wasn't it moved over to juju 2?

[Anastasia (anastasia-macmood)]

The logistics of what bugs where moved over to juju2 was kindly undertaken by QA team 2 months ago.
There was a grace period for everyone else to re-target the bugs that people cared about.

I will re-target this one to 'juju' for you.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.