manual provider allow specifying private address for connecting back to state-server
Bug #1303204 reported by
Kapil Thangavelu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Medium
|
Unassigned |
Bug Description
the addressed passed to other machines in a manual env, is the addressed used to ssh/bootstrap, but if there are other address on the machine (ie. all the machines share a private network) then its effectively picking a public address even when a private one exists. an option to specify the state-server address to connect to would help ensure that traffic is routed on the private network. The env machines can be registered with an address map on the inject_machine/api to the state server, its more just the state server communication to its env machines as it must be bootstrapped with a public address for ssh.
description: | updated |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.20.0 |
tags: | added: improvement manual-provider |
Changed in juju-core: | |
milestone: | 1.20.0 → next-stable |
Changed in juju-core: | |
importance: | High → Medium |
milestone: | next-stable → none |
tags: | added: manual-story |
To post a comment you must log in.
this might already be solved, juju preferentially reconnects back on
cloud-local. That can result in other issues like agent suicide if that
cloud-local address doesn't work but that's a separate issue.
On Mon, May 12, 2014 at 10:35 AM, Canonical Juju QA Bot <
<email address hidden>> wrote:
> ** Changed in: juju-core /bugs.launchpad .net/bugs/ 1303204 /bugs.launchpad .net/juju- core/+bug/ 1303204/ +subscriptions
> Milestone: 1.20.0 => next-stable
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> manual provider allow specifying private address for connecting back
> to state-server
>
> To manage notifications about this bug go to:
> https:/
>