azure provider does not appear to be opening ports

[Cheryl Jennings]

Created from: https://github.com/juju/juju/issues/3999

Using a hand-built juju 1.26-alpha3-wily-amd64 from 40b2cae I am able to bootstrap onto Azure and deploy the juju-gui. The charm opens and exposes ports 80 and 443. juju status shows them to be open. (See below)

The steps I followed are:

juju bootstrap --upload-tools
cd ~/git/juju-gui-charm
make deploy
Attempting to hit the public IP address in a browser yields no response. Using nmap to scan shows only port 22 open:

$ nmap -Pn 138.91.252.121

Starting Nmap 6.47 ( http://nmap.org ) at 2015-12-18 12:33 AST
Nmap scan report for 138.91.252.121
Host is up (0.11s latency).
Not shown: 999 filtered ports
PORT STATE SERVICE
22/tcp open ssh
juju status output:

  juju-gui:
    charm: local:trusty/juju-gui-0
    exposed: true
    service-status:
      current: unknown
      since: 18 Dec 2015 11:38:40-04:00
    units:
      juju-gui/0:
        workload-status:
          current: unknown
          since: 18 Dec 2015 11:38:40-04:00
        agent-status:
          current: idle
          since: 18 Dec 2015 12:30:30-04:00
          version: 1.26-alpha3.1
        agent-state: started
        agent-version: 1.26-alpha3.1
        machine: "1"
        open-ports:
        - 80/tcp
        - 443/tcp
        public-address: 138.91.252.121

[Cheryl Jennings (cherylj)]

Brad - if you can attach machine-0.log, that would help in debugging.

[Brad Crittenden (bac)]

I'll attach the full machine log but this looks interesting:

2015-12-18 15:38:43 ERROR juju.worker runner.go:226 exited "firewaller": internal network address not found
2015-12-18 15:38:46 ERROR juju.worker.firewaller firewaller.go:439 failed to lookup "machine-1", skipping port change

[Cheryl Jennings (cherylj)]

I was hoping to see the api call to open the ports and see if it returned an error or not, but that's logged at the DEBUG level, and the log you attached was at WARNING.

[Cheryl Jennings (cherylj)]

Brad - can you confirm if this is still a problem on the released 1.26-alpha3?

[Brad Crittenden (bac)]

I have installed alpha3 from the PPA and can confirm the problem still exists.

[Andrew Wilkins (axwalk)]

Something's changed, it *was* working before. I can repro though.

[Andrew Wilkins (axwalk)]

A few issues:
 - seems there was a case change in one of the results from Azure. I've adjusted, but also made the check case-insensitive.
 - there was a latent bug in worker/firewaller, due to ignoring an error
 - we seem to be recreating network security group rules when we don't need to, looking into it now.

[Brad Crittenden (bac)]

I was able to perform a deploy of the new Juju GUI on azure, the task that I was attempting when I found this bug. It all works now. Thanks.

[Andrew Wilkins (axwalk)]

Thanks for confirming, Brad.