juju logs about relations already existing should not be errors

[Thomi Richards]

When deploying services with mojo/juju-deployer, juju often logs error messages such as:

```
ERROR cannot add relation "landscape:container store-fe:juju-info": relation landscape:container store-fe:juju-info already exists (already exists)
```

This may seem benign, but in a production context, a screen full of ERROR level messages is really scary, and doesn't leave the user feeling like they can trust the tool.

I'm aware that there's an interplay here between mojo, juju-deployer, and juju, but I really don't think this should be an error message: the relation already exists, juju has nothing to do. To my mind this should be an INFO or DEBUG level message.

[Witold Krecicki (wpk)]

Could you provide a larger piece of logs with this message?

[John A Meinel (jameinel)]

I think you could just look for "cannot add relation" and/or
"relation.*already exists".

On Thu, Jun 8, 2017 at 4:14 PM, Witold Krecicki <email address hidden>
wrote:

> Could you provide a larger piece of logs with this message?
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1696647
>
> Title:
> juju logs about relations already existing should not be errors
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1696647/+subscriptions
>

[Ian Booth (wallyworld)]

@witold, the place you want to change is the add-relation CLI.
That's what prints the error message referred to in the bug.

[John A Meinel (jameinel)]

https://github.com/juju/juju/pull/7614

[Anastasia (anastasia-macmood)]

I suspect that the fix for this has been already ported into 2.3 (develop) as part of one of the larger merges we have undertaken recently.