[Bug 2087949] Re: "systemctl status sshd" does not work in noble

[Tobias Heider]

This looks like a regression caused by sshd socket activation.

The man page at
https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html
suggests Alias= makes systemd automatically symlink the service to the
alias name when enabled. Previously this would have worked because
ssh.service was actually enabled. With socket activation the service is
disabled by default and gets started on-demand by the socket.

We might have to symlink the service manually.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2087949

Title:
  "systemctl status sshd" does not work in noble

Status in openssh package in Ubuntu:
  New

Bug description:
  "systemctl status ssh" and "systemctl status sshd" both work in jammy, but only "systemctl status ssh" works in noble.
  Expected behavior is that "systemctl status sshd" should work on noble too. 
  The ssh.service file contains "Alias=sshd.service" but this does not seem to be effective on noble.

  If this is intentional, directions to where this is documented would
  be helpful.

  Thanks,
  Ankush

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