Service deployed to existing machine do not expose properly
Bug #1340756 reported by
Brad Crittenden
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
On azure, I deployed apache2 to an existing machine. 'juju status' shows port 80 open and the service is exposed however connections could not be made.
Looking on the Azure dashboard for the instance it did not show the port as being open. Ports associated with the originally deployed service were shown but the port for apache was not listed.
After manually opening the port in the dashboard the service was accessible.
| summary: |
- [azure] Service deployed to existing machine do not expose properly + Service deployed to existing machine do not expose properly |
| tags: | added: expose |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
Considering the age of the bug, I am guessing that you were using version of juju that had an old azure provider.
From Juju 2.0, we have moved to a new Azure provider.