Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
2.1 dynamic bridges log script output #6786
Conversation
added some commits
Jan 9, 2017
|
!!build!! |
jameinel
approved these changes
Jan 10, 2017
Have you tested this live and feel like it gives useful context for debugging?
|
@jameinel - yes, tested live. It show us the current configuration for things we are about to change; /e/n/i, current bridges, current routes, current state of interfaces, then same again after we have bridged. The only small caveat I would mention is that /sometimes/ it shows the state of, say, br-en3 as DOWN. This is a timing issue because if you augment the output with a |
|
$$meege$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
frobware commentedJan 9, 2017
•
Edited 1 time
-
frobware
Jan 9, 2017
We currently log the bridge script output only if there is an error. If there is no error, we still capture the output, but at trace level. It is useful to see the before/after configuration of routing and bridging when debugging problems.