We don't actually support the azure instance-id syntax, but I was wondering
if we could enable that syntax and if it would lead to better experience
for you.
On Fri, Jun 8, 2018 at 1:42 PM, Nick Moffitt <email address hidden>
wrote:
> Manual provisioning was necessary because juju add-unit does not add new
> machines to an existing Availability Set, and Azure does not allow us to
> change the Availability Set of a given VM.
>
> Is it possible to manually provision via azure:<instance-id>? We have
> only ever used ssh:<ip-address>, and yes we used the public IP address
> because that was the only one reachable on port 22 from the system where
> we run juju.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1773359
>
> Title:
> Cluster relation reporting public IP instead of internal network IP on
> manually added machine
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1773359/+subscriptions
>
We don't actually support the azure instance-id syntax, but I was wondering
if we could enable that syntax and if it would lead to better experience
for you.
On Fri, Jun 8, 2018 at 1:42 PM, Nick Moffitt <email address hidden>
wrote:
> Manual provisioning was necessary because juju add-unit does not add new instance- id>? We have /bugs.launchpad .net/bugs/ 1773359 /bugs.launchpad .net/juju/ +bug/1773359/ +subscriptions
> machines to an existing Availability Set, and Azure does not allow us to
> change the Availability Set of a given VM.
>
> Is it possible to manually provision via azure:<
> only ever used ssh:<ip-address>, and yes we used the public IP address
> because that was the only one reachable on port 22 from the system where
> we run juju.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> Cluster relation reporting public IP instead of internal network IP on
> manually added machine
>
> To manage notifications about this bug go to:
> https:/
>