group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1342580@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package tftp-hpa -
5.2+20150808-1ubuntu1.16.04.1

---------------
tftp-hpa (5.2+20150808-1ubuntu1.16.04.1) xenial; urgency=medium

  * Replace the default value of TFTP_ADDRESS to :69 instead of [::]:69.
    The previous default caused a failure to start when the NIC is not
    available at startup time (LP: #1342580)

 -- Louis Bouchard <louis.bouchard@xxxxxxxxxx>  Tue, 07 Mar 2017
12:00:08 +0100

** Changed in: tftp-hpa (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

** Changed in: tftp-hpa (Ubuntu Yakkety)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1342580

Title:
  tftpd-hpa fails to start when the NIC is not available at startup time

Status in tftp-hpa package in Ubuntu:
  Fix Released
Status in tftp-hpa source package in Trusty:
  Fix Released
Status in tftp-hpa source package in Xenial:
  Fix Released
Status in tftp-hpa source package in Yakkety:
  Fix Released
Status in tftp-hpa package in Debian:
  New

Bug description:
  [SRU justification]
  This fix is required in order to make sure that the tftpd daemon will be started even if the Network Interface is not yet available.

  [Impact]
  The daemon fails to start if the NIC is not enable at startup time

  [Fix]
  Remove IPv6's [::] portion of the address. The blank value is adequate as an accept-all address for both v4 & v6

  [Test Case]
  With the previous version installed, TFTP_ADDRESS reads :

  # grep -i address /etc/default/tftpd-hpa
  TFTP_ADDRESS="[::]:69"

  With the new package it reads :

  TFTP_ADDRESS=":69"

  Running the reproducer as identified in comment #18 leads to a working
  tftpd daemon even when the NIC is not yet started.

  [Regression]
  None expected. This is the solution suggested by the upstream developer (hpa) in the debian bug of the same topic :

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771441#176

  >Now, what I want to know is why you are specifying the accept-all
  >address explicitly as 0.0.0.0 instead of an empty string.
  >
  >	-hpa

  Tests were done also with a user modified TFTP_ADDRESS which lead to
  the same content before and after the upgrade. A version barrier was
  included in the postinst script to avoid rewriting the value once it
  has been changed once

  [Original description of the problem]

  It is new version of Bug 522509 https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/522509
  Since old bug was fixed for previous system. I report a new one against 14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: tftpd-hpa 5.2-7ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 16 10:12:42 2014
  InstallationDate: Installed on 2014-06-04 (41 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: tftp-hpa
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.tftpd.hpa.conf: 2014-07-16T10:11:56.364626

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