Hello Leann, 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.1 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 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! ** Changed in: ubuntu-fan (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1584092 Title: Docker misconfigured when using non-default overlay/underlay netmask size Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: Fix Committed Bug description: Fan allows for variable sized subnet map sizes. For example, if I want to map a /24 to a /16 instead of the default /16 to /8, Fan supports this. However, when configuring this via fanatic, I see that docker configuration fails. In /etc/default/docker, the --fixed-cidr flag is defined incorrectly. $ sudo fanatic Welcome to the fanatic fan networking wizard. This will help you set up an example fan network and optionally configure docker and/or LXD touse this network. See fanatic(1) for more details. Configure fan underlay (hit return to accept, or specify alternative) [192.168.0.0/16]: 192.168.1.0/24 Configure fan overlay (hit return to accept, or specify alternative) [250.0.0.0/8]: 250.99.0.0/16 Create LXD networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 [Yn]: Y Profile fan-250-99 created Create docker networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 [Yn]: Y Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. Test LXD networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16 (NOTE: potentially triggers large image downloads) [Yn]: n Test docker networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16 (NOTE: potentially triggers large image downloads) [Yn]: n This host IP address: 192.168.1.10 Remote test host IP address (none to skip): /usr/sbin/fanatic: Testing skipped $ grep "DOCKER_OPTS" /etc/default/docker # Use DOCKER_OPTS to modify the daemon startup options. #DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4" DOCKER_OPTS=" -b fan-250-99 --mtu=1450 --iptables=false --fixed-cidr=250.99.10.0/40" May 20 05:15:30 macbook docker[27364]: time="2016-05-20T05:15:30.411933688-07:00" level=fatal msg="Error starting daemon: Error initializing network controller: invalid CIDR address: 250.99.10.0/40" === [Impact] Non default network splits are not honoured correctly. [Test Case] Setup fan with non /8 /16 split, as per reporter. [Regression Potential] Low, as these currently do not work correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584092/+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
