fails if network is not yet configured at runlevel 2
Bug #1027081 reported by
Serge Hallyn
This bug report is a duplicate of:
Bug #972845: fails if network is not yet configured at runlevel 2 (i.e. no ifupdown-managed network connection).
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tftp-hpa (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
If network is not yet configured at runlevel 2, then the upstart job thinks tftpd is running, but ps -ef shows it is not. This happens on my laptop which normally comes up with wireless, and on which I set up wired by hand later. It can trivially be reproduced with a container where the lxc.network bits are replaced with
lxc.network.type = empty
If I then try
'sudo start tftpd-hpa'
this fails because it thinks it is running, but if I do
sudo restart tftpd-hpa
that works.
Changed in tftp-hpa (Ubuntu): | |
importance: | Undecided → Medium |
To post a comment you must log in.
more detailed reproduction instructions:
lxc-create -t ubuntu -n 1 lxc/q1/ config lxc/q1/ config
lxc-start -n q1
(inside container) sudo apt-get -y install tftpd-hpa; sudo poweroff
sudo sed -i '/lxc.network/d' /var/lib/
echo "lxc.network.type = empty" | sudo tee -a /var/lib/
sudo lxc-start -n q1
(inside container) sudo status tftpd-hpa; ps -ef | grep tftp; sudo start tftpd-hpa; sudo restart tftp-hpa