Hello Stefan, or anyone else affected,

Accepted ubuntu-fan into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubuntu-fan/0.9.2 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1656875

Title:
  fanatic enable/disable docker broken with docker.io >= 1.12

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Yakkety:
  Fix Committed

Bug description:
  The way docker handles networks changed when moving to newer docker
  versions. Networks are now created/deleted by "docker network"
  commands (similar to LXD). This needs to be handled by fanatic when
  doing docker related tasks.

  SRU Justification:

  Impact: fanatic was written when an older version of docker.io was in
  the archive for Yakkety and Xenial. However docker.io does SRU the
  latest version back into older releases. Docker.io 1.12 replaced the
  interface to declare networks so now most (if not all) docker related
  subcommands of fanatic are broken in Yakkety/Xenial.

  Fix: The new version adds compat code to run docker subcommands differently, 
depending on the docker.io version installed. In case docker.io were not 
upgraded, nothing changes. This should minimize regression potential.
  The only other change to the upload is adding a dep8 test against docker to 
allow detection of future breakage sooner. As this is not part of the binary 
packages, this should neither add any regressions.

  Testcase:
  - fanatic enable -u <underlay> -o <overlay>
  - fanatic enable-docker -u <underlay> -o <overlay>
  - fanatic test-local-docker -u <underlay> -o <overlay>
  - fanatic disable-docker -u <underlay> -o <overlay>
  - <check fan bridge still is configured here>
  - fanatic disable -u <underlay> -o <overlay>

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1656875/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to