Container networking busted by commit 5fbe9c6

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

Reverting the commit to unbreak CI, and re-opening https://bugs.launchpad.net/juju/+bug/1666198 until we can get a proper fix that doesn't break other things.

'Fix Released' for us means that we have included a fix in a particular release.
It's a funny situation here, since technical to fix this bug we had to revert the code which once landed is, indeed, in the same state as whatever code we have previously released.
I'll mark this as "Fix Committed' for now to reflect that the revert, i.e. the PR that has fixed this failure, has landed.

We've generally followed the pattern that bugs that only exist in a
development branch (not in a stable release) are considered fix released if
they are fixed in that branch, since nobody is waiting for a fix to a bug
that has never been released. (Put another way all the people who have been
affected by the bug have gotten the fix in the same channel that gave them
the bug.)

That said, I don't really care that much how dev only bugs are triaged, as
they are a minority and if it makes bug tracking more consistent...

John
=:->

On Apr 3, 2017 5:50 PM, "Anastasia" <email address hidden> wrote:

> 'Fix Released' for us means that we have included a fix in a particular
> release.
> It's a funny situation here, since technical to fix this bug we had to
> revert the code which once landed is, indeed, in the same state as whatever
> code we have previously released.
> I'll mark this as "Fix Committed' for now to reflect that the revert, i.e.
> the PR that has fixed this failure, has landed.
>
> ** Changed in: juju
> Status: Fix Released => Fix Committed
>
> --
> You received this bug notification because you are a bug assignee.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1678110
>
> Title:
> Container networking busted by commit 5fbe9c6
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1678110/+subscriptions
>