Fix bug 1735684: Don't watch manual machines from the firewaller. #8244

Merged
merged 1 commit into from Dec 20, 2017

Conversation

Projects
None yet
3 participants
Member

hmlanigan commented Dec 19, 2017

Description of change

Since juju shouldn't be touching ports on a manually provisioned machine, don't start watching them.

QA steps

  1. bootstrap an openstack cloud with debug logging-config
  2. Create a container which can be added to juju
  3. juju add-machine ssh:ubuntu@
  4. juju deploy ghost --to
  5. juju export ghost
  6. look at debug-log from controller

No provider or firewater error like those in bug should be seen. There should be a debug message: "not watching machine-#".

Documentation changes

N/A

Bug reference

https://bugs.launchpad.net/juju/+bug/1735684

Contributor

jujubot commented Dec 19, 2017

Can one of the admins verify this patch?

Looks good, one suggestion about moving logging inside startMachine.

worker/firewaller/firewaller.go
if err != nil {
return err
}
- logger.Debugf("started watching %q", tag)
+ if watching {
@babbageclunk

babbageclunk Dec 20, 2017

Member

If you're only using the bool return for logging, it would be better to log inside startMachine and lose the bool (and then you can have different log messages for the different not watching cases).

@hmlanigan

hmlanigan Dec 20, 2017

Member

updated.

Member

hmlanigan commented Dec 20, 2017

$$merge$$

Contributor

jujubot commented Dec 20, 2017

Status: merge request accepted. Url: http://ci.jujucharms.com/job/github-merge-juju

@jujubot jujubot merged commit c899e00 into juju:2.3 Dec 20, 2017

1 check passed

continuous-integration/jenkins/pr-merge This commit looks good
Details

@hmlanigan hmlanigan deleted the hmlanigan:bug1735684 branch Dec 20, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment