juju gui giving non-resolvable internal address

[Antonio Rosales]

I am setting up a new juju client in AWS to which I will then deploy applications from. I did this by first deploying the ubuntu charm from my laptop:

http://paste.ubuntu.com/24242440/

I then `juju ssh ubuntu/0` to set up the juju client. From there I deploy spark-processing bundle:

http://paste.ubuntu.com/24242489/

I can successfully expose and access ganglia @ http://52.14.227.183/ganglia/. However, I could not access the GUI @ the specified address:

https://172.31.9.240:17070/gui/u/admin/spark

I issued a `juju status -m controller` to see what address the controller was running on, and then using that IP I could access the gui, so:

https://52.14.181.137:17070/gui/u/admin/spark/

Thus, seems the GUI was using the internal 172.x address for the browser URL rather than the external 52.x one.

[Anastasia (anastasia-macmood)]

I wonder if this is related to bug # 1673265

[Tim Penhey (thumper)]

How did you get the specified address: https://172.31.9.240:17070/gui/u/admin/spark ?

[Francesco Banconi (frankban)]

Does "juju gui" work when invoked from the machine on which you originally bootstrapped the aws controller? How did you configure the new client in the ubuntu/0 unit? It is surely possible that the address returned by NewControllerAPIRoot()[0].Addr() is reachable from the point of view of the ubuntu/0 unit, but not from the browser.

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]