open-port barfs on a port that was just closed
Bug #908198 reported by
Mark Mims
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
Medium
|
Jim Baker |
Bug Description
With a config-changed hook:
#!/bin/sh
. /etc/default/
# Close the old port
echo "Closing old port $BITLBEE_PORT"
close-port "$BITLBEE_PORT/tcp"
PORT=
echo "Opening new port $PORT"
cat >/etc/default/
BITLBEE_
BITLBEE_
BITLBEE_
BITLBEE_
EOF
/etc/
open-port "$PORT/tcp"
the open-port throws the attached exception if it's opening the same port it just closed.
Net result is no ports open.
Related branches
lp:~jimbaker/pyjuju/close-open-port
- Kapil Thangavelu (community): Approve
-
Diff: 40 lines (+18/-1)2 files modifiedjuju/state/service.py (+1/-1)
juju/state/tests/test_service.py (+17/-0)
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → florence |
Changed in juju: | |
assignee: | nobody → Jim Baker (jimbaker) |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Released |
To post a comment you must log in.