touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Ah right, that makes more sense. By definition, "shutdown -h now" or
"poweroff" etc. are racy -- sometimes it "survives" and comes back,
sometimes the shutdown of the machine is too fast. It seems that with
systemd it's just a bit faster. I suggest calling "shutdown -h +1", or
if you don't want to wait for a minute, perhaps "(sleep 3; poweroff )
&"?

** Summary changed:

- stopping ssh.service closes existing ssh connections
+ reboot does not return under systemd

** Package changed: openssh (Ubuntu) => systemd (Ubuntu)

** Changed in: systemd (Ubuntu)
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1429938

Title:
  reboot does not return under systemd

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  On Trusty and Utopic, when you run `apt-get remove openssh-server`
  over an SSH connection, your existing SSH connection remains open, so
  it's possible to run additional commands afterward.

  However, on Vivid now that the switch to systemd has been made,  `apt-
  get remove openssh-server` closes the existing SSH connection
  immediately, causing your SSH client to exit with a non-zero status. I
  have a hunch there's a lot of automation tooling out there that relies
  on the old behavior.

  For what it's worth, this change breaks the internal image mastering
  tools that System76 uses. Prior to exporting an image tarball, I spin
  up a golden VM with qemu, rysnc a script to it, and then execute this
  script over SSH.

  The important step is that I need to remove openssh-server prior to
  shutting down the VM, so these scripts always end with something like
  this:

  apt-get -y purge openssh-server ssh-import-id
  apt-get -y autoremove
  shutdown -h now

  As far as I can tell, this behavior change will likewise be a problem
  when running `do-release-upgrade` on a remote server over SSH. Or more
  generally, anytime you run "apt-get upgrade/dist-upgrade" via SSH, it
  seems this would be a problem whenever the openssh-server package
  happens to be updated.

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