unit ports not populated by API megawatcher

[mahmoh]

jujuGuiVersionInfo=['1.3.0', '6b394ad'];
AWS
Chromium, Version 39.0.2171.65 Ubuntu 14.04 (64-bit)

The latest Juju-Gui has lost the handy hyperlinks in the unit pane along with the port numbers the service listens on:

BEFORE: (similar to)

IP Address: 172.31.46.239 :80
Status: started
Public Address: 52.0.110.230 :80

NOW: (https://<URL>/juju-ui/version.js = var jujuGuiVersionInfo=['1.3.0', '6b394ad']; )

IP Address: 172.31.46.239
Status: started
Public Address: 52.0.110.230

[Brad Crittenden (bac)]

Thanks for the bug report. We are investigating.

[Brad Crittenden (bac)]

Did the version of juju in use change? What version are you currently using?

[mahmoh (mahmoh)]

It might have but this is related to juju-gui, right?

1.21.1-trusty-amd64

[Brad Crittenden (bac)]

The GUI talks to juju to get information about the deployed environment. So changes in juju can affect the GUI and that seems to be what has happened here.

I tested deploying environments with 1.22-beta, 1.21.1-0ubuntu1~14.10.1~juju, and 1.20.10-0ubuntu1.

The latest two show the behavior you describe while with the 1.20 version the open port information is correctly gotten from juju and displays properly in the unit detail page.

[Francesco Banconi (frankban)]

This is indeed related to a change in juju-core.
The Ports field of the mega-watcher for units is no longer being populated.
juju-core started using port ranges for opened ports.
We can react by:
- allow port ranges to be included in the mega-watcher for units;
- change the GUI so that it handles both port.Number (for backward compatibility) and a pair of (port.FromPort/port.ToPort).
In the second case, perhaps the GUI could keep showing a link to a single port if FromPort != 0 && FromPort == ToPort.

[Francesco Banconi (frankban)]

Actually, as suggested by Dimiter, it is possible to handle this just on the juju-core side.

[Dimiter Naydenov (dimitern)]

Sorry, I meant to remove juju-gui from the affected projects, as this is a juju-core problem only, but I can't do it apparently.

I'm working on a fix to restore the API wire-format of megawatcher changes reported for units to include Ports (converted from port ranges where fromPort=toPort and drop the rest, as it's how older juju versions had it, before port ranges were introduced), and also add a PortRanges slice for the complete list of port ranges. Once this fix lands (and it needs to be forward ported to 1.22 and 1.23) juju-gui will start working the same way as before.

[Brad Crittenden (bac)]

Dimiter, you can't remove projects from a bug report. I've set the status to 'Invalid' for juju-gui.