peergrouper spins in local/upgraded environment

The peergrouper is intended to monitor the MongoDB replica health and make sure everything is functioning well.
However, when run in the local provider, or in an upgraded environment (while we haven't finished all the upgrade steps), it spams the log file with:
2014-04-18 09:45:38 INFO juju.worker runner.go:260 start "peergrouper"
2014-04-18 09:45:38 DEBUG juju.worker.peergrouper worker.go:421 found new machine "0"
2014-04-18 09:45:38 ERROR juju.worker.peergrouper worker.go:137 peergrouper loop terminated: cannot get replica set status: cannot get replica set status: not running with --replSet
2014-04-18 09:45:38 ERROR juju.worker runner.go:218 exited "peergrouper": cannot get replica set status: cannot get replica set status: not running with --replSet
2014-04-18 09:45:38 INFO juju.worker runner.go:252 restarting "peergrouper" in 3s
2014-04-18 09:45:38 DEBUG juju.state.apiserver apiserver.go:137 -> [1] machine-0 4.999144723s {"RequestId":71,"Response":{}} NotifyWatcher["3"].Next
2014-04-18 09:45:38 DEBUG juju.state.apiserver apiserver.go:130 <- [1] machine-0 {"RequestId":74,"Type":"NotifyWatcher","Id":"3","Request":"Next","Params":{}}
2014-04-18 09:45:38 DEBUG juju.state.apiserver apiserver.go:130 <- [1] machine-0 {"RequestId":75,"Type":"Machiner","Request":"APIHostPorts","Params":{}}
2014-04-18 09:45:38 DEBUG juju.state.apiserver apiserver.go:137 -> [1] machine-0 874.972us {"RequestId":75,"Response":{"Servers":[[{"Value":"localhost","Type":"hostname","NetworkName":"","NetworkScope":"public","Port":17070},{"Value":"10.0.3.1","Type":"ipv4","NetworkName":"","NetworkScope":"local-cloud","Port":17070},{"Value":"127.0.0.1","Type":"ipv4","NetworkName":"","NetworkScope":"local-machine","Port":17070},{"Value":"192.168.0.108","Type":"ipv4","NetworkName":"","NetworkScope":"local-cloud","Port":17070},{"Value":"192.168.122.1","Type":"ipv4","NetworkName":"","NetworkScope":"local-cloud","Port":17070},{"Value":"::1","Type":"ipv6","NetworkName":"","NetworkScope":"local-machine","Port":17070},{"Value":"fe80::221:6aff:fe5f:7c8","Type":"ipv6","NetworkName":"","NetworkScope":"","Port":17070},{"Value":"fe80::ac35:beff:fe6c:a6ae","Type":"ipv6","NetworkName":"","NetworkScope":"","Port":17070}]]}} Machiner[""].APIHostPorts
2014-04-18 09:45:39 INFO juju.worker.apiaddressupdater apiaddressupdater.go:58 API addresses updated to [["public:localhost" "local-cloud:10.0.3.1" "local-machine:127.0.0.1" "local-cloud:192.168.0.108" "local-cloud:192.168.122.1" "local-machine:::1" "fe80::221:6aff:fe5f:7c8" "fe80::ac35:beff:fe6c:a6ae"]]
2014-04-18 09:45:41 INFO juju.worker runner.go:260 start "peergrouper"
2014-04-18 09:45:41 DEBUG juju.worker.peergrouper worker.go:421 found new machine "0"
2014-04-18 09:45:41 ERROR juju.worker.peergrouper worker.go:137 peergrouper loop terminated: cannot get replica set status: cannot get replica set status: not running with --replSet
2014-04-18 09:45:41 ERROR juju.worker runner.go:218 exited "peergrouper": cannot get replica set status: cannot get replica set status: not running with --replSet
2014-04-18 09:45:41 INFO juju.worker runner.go:252 restarting "peergrouper" in 3s

If we aren't going to have upgrade working to bring up --replicaSet or if we are going to leave it disabled for local provider, we need to squelch it. Possibly it is sufficient to just note that the DB isn't in replica mode and just exit the peer grouper, as mongo can't start to be in replica mode without restarting it again anyway.