edubuntu-bugs team mailing list archive

[Jan Hubený <1797839@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hi,

we are using ltsp environment in Ubuntu 18.04 LTS. Something goes wrong
with last package updates. I have fully updated the system and the
client images on September 22nd. The LTSP environment worked and
everything was fine. I made another full system update on October 13rd.
The update includes:

on ltsp server:
apt update
apt upgrade 
reboot

on client images:
ltsp-chroot -a amd64 /bin/bash
apt update 
apt upgrade
exit

on ltsp server:
ltsp-update-image amd64

after this procedure the ltsp clients boot never more. The tftp boot
works, but when the client mounts the squashfs system and runs the
systemd job Network service, the boot hangs. Until the network service
start, the ltsp thin client reply on ping, after Network service starts
the ping stops.

I tested this behaviour on two indepent ltsp instalations. The behaviour is the same on both sites. THere is no difference between thin or fat client config.
When I turned to last working image with 

ltsp-update-image -r amd64

then the clients started to boot again. Therefore I suppose, that some
update between September 22nd and October 13rd broke the Network service
in ltsp client.

** Affects: ltsp (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: boot ltsp ltsp-client network

-- 
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in Ubuntu.
https://bugs.launchpad.net/bugs/1797839

Title:
  Ubuntu 18.04 LTS - ltsp clients lost network connection after tftp
  boot and network service start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1797839/+subscriptions