I don't believe Juju expects public addresses for all machines. It
*does* expect a public address for the controller, because you need
external access to be able to connect for things like "juju status" from
your machine.
I don't know how you would have been able to bootstrap and 'ssh' into
the
The main issue is that Juju controllers need to retrieve the binaries it
runs from streams.canonical.com and that the client (typically running
on an operator laptop outside the cloud) needs to be able to reach the
controller API endpoints.
If you're getting an error during bootstrap about
Hi this is santhosh,
ran into same kind of issue. when i specify a particular vpc-id ( it is
not default so i did vpc-id-force). it bootstraps controller in that vpc
and was loosing/cannot connect to the api after that. BELOW IS THE
BOOTSTRAP COMMAND I GAVE:
ubuntu@x86inst-1a:~$ juju bootstrap
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364037
Title:
Removing 2.1 milestone as we will not addressing this issue in 2.1.
** Changed in: juju
Milestone: 2.1.0 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364037
Title:
Juju expects a
>From Dimiter:
We still assume to have public IPs in most providers and have no way of not
using them if the user doesn't want to (except for the use-floating-ips setting
for openstack)
** Also affects: juju
Importance: Undecided
Status: New
** Changed in: juju
Status: New =>
