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

Andreas Hasenack 2087949 at bugs.launchpad.net
Mon Nov 18 14:13:23 UTC 2024


This was merged in plucky, and is outstanding in noble. It doesn't look
like it's worth an SRU on its own, but would make sense together with
another fix. Adjusting tasks.

** Also affects: openssh (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: openssh (Ubuntu Oracular)
   Importance: Undecided
       Status: New

** Also affects: openssh (Ubuntu Plucky)
   Importance: Low
     Assignee: Nick Rosbrook (enr0n)
       Status: Triaged

** Changed in: openssh (Ubuntu Plucky)
       Status: Triaged => Fix Committed

-- 
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:
  Fix Committed
Status in openssh source package in Noble:
  New
Status in openssh source package in Oracular:
  New
Status in openssh source package in Plucky:
  Fix Committed

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




More information about the foundations-bugs mailing list