Hello Stefan, or anyone else affected,

Accepted ubuntu-fan into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubuntu-
fan/0.12.8~17.04.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 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-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. 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 Zesty)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-zesty

-- 
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/1732747

Title:
  Add additional checks and information to testbed setup

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 Zesty:
  Fix Committed
Status in ubuntu-fan source package in Artful:
  Fix Released

Bug description:
  There are cases (main reason is to have more info when using the
  built-in fanatic tests for dep8 ADT tests) when additional info about
  the primary network interface used for Fan and about the DNS setup
  outside and inside the containers is useful. This gets added to the
  __payload_prepare function of fanatic which is used by both host and
  container setup.

  SRU justification:

  Impact: This changes only the built-in local docker and lxd test
  functionality of fanatic. It has no impact on normal operation. At the
  same time the additional code will be used for the changes which allow
  to make the docker test more robust in case of using systemd-resolvd
  as sole local resolver.

  Fix: Adding checks to __payload_prepare which print information but
  also will optionally wait if DNS seems not ready, yet.

  Testcase: Either running the build-in tests manually or checking the log 
files of ADT testing for statements like:
  - detected primary route through <iface>
  - DNS: (systemd(<ip>)|<ip>)

  Regression risk: low (verified by passing ADT testing)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1732747/+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