If a different port is set after deployment, it doesn't change
Bug #1306756 reported by
José Antonio Rey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| owncloud (Juju Charms Collection) |
Fix Released
|
High
|
José Antonio Rey | ||
Bug Description
If a port (let's say 80) has been set at the time of deployment, and one wants to change the port from 80 to 8080, it gets stuck in port 80 and doesn't change to port 8080.
Related branches
lp://staging/~jose/charms/precise/owncloud/port-change+repo+ssl-support
- Charles Butler (community): Approve
- Matt Bruzek (community): Needs Fixing
-
Diff: 2050 lines (+1592/-251)18 files modifiedREADME.md (+110/-33)
charm-helpers.yaml (+5/-0)
config.yaml (+28/-0)
hooks/charmhelpers/contrib/ssl/__init__.py (+78/-0)
hooks/charmhelpers/contrib/ssl/service.py (+267/-0)
hooks/charmhelpers/core/hookenv.py (+401/-0)
hooks/charmhelpers/core/host.py (+297/-0)
hooks/config-changed (+153/-9)
hooks/db-relation-changed (+9/-0)
hooks/db-relation-departed (+13/-0)
hooks/install (+45/-23)
hooks/ssl (+19/-0)
hooks/start (+6/-2)
hooks/upgrade-charm (+43/-39)
hooks/website-relation-joined (+1/-2)
metadata.yaml (+1/-1)
tests/100-deploy.py (+116/-0)
tests/100_deploy.test (+0/-142)
| Changed in owncloud (Juju Charms Collection): | |
| status: | In Progress → Fix Committed |
| Changed in owncloud (Juju Charms Collection): | |
| importance: | Undecided → High |
| Changed in owncloud (Juju Charms Collection): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
