lxdbr0 spam in log file
Bug #1598127 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Bug Description
2016-07-01 11:47:04 WARNING juju.network network.go:430 cannot get "lxdbr0" addresses: route ip+net: no such network interface (ignoring)
2016-07-01 11:47:04 WARNING juju.network network.go:430 cannot get "lxdbr0" addresses: route ip+net: no
such network interface (ignoring)
2016-07-01 11:47:08 WARNING juju.network network.go:430 cannot get "lxdbr0" addresses: route ip+net: no such network interface (ignoring)
If we are ignoring it, it doesn't need to be at WARNING level. This seems more a DEBUG level message.
It does seem like once you want to deploy an LXD container, this should be more visible, but it doesn't need to be as part of the standard "filtering LXD addresses" code.
| Changed in juju-core: | |
| importance: | High → Medium |
| tags: | added: bitesize |
| Changed in juju-core: | |
| milestone: | 2.0-beta12 → none |
| affects: | juju-core → juju |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.