Verification on Xenial.

Repeating test case from description.

- Test case 1 - libvirtd

alias service : libvirtd
aliased service : libvirt-bin

# ls -la libvirtd.service 
lrwxrwxrwx 1 root root 39 Mar 21 16:27 libvirtd.service -> 
/lib/systemd/system/libvirt-bin.service

# systemctl is-active libvirtd
active

# systemctl is-active libvirt-bin
active

- Test case 2 - sshd

alias service : sshd
aliased service : ssh

# ls -la sshd.service 
lrwxrwxrwx 1 root root 31 Mar 21 14:39 sshd.service -> 
/lib/systemd/system/ssh.service

# systemctl is-active sshd
active

# systemctl is-active ssh
active


# dpkg -l | grep systemd
ii  libpam-systemd:amd64                         229-4ubuntu21.22               
                 amd64        system and service manager - PAM module
ii  libsystemd0:amd64                            229-4ubuntu21.22               
                 amd64        systemd utility library
ii  systemd                                      229-4ubuntu21.22               
                 amd64        system and service manager
ii  systemd-sysv                                 229-4ubuntu21.22               
                 amd64        system and service manager - SysV links


** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  systemctl - alias service reports inactive while aliased is active

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  'systemctl is-active' command reports an alias service as inactive even 
though the aliased service
  is active.
  Currently the 'systemctl is-active' command does not load units to minimise 
its effect on the system (i.e. that a monitoring command does not itself alter 
the state of the system).
  However, this behaviour leads to inconsistencies when services are aliased.

  [Test case]

  - Test case 1 - libvirtd

  alias service : libvirtd
  aliased service : libvirt-bin

  /etc/systemd/system$ ls -la libvirtd.service 
  lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> 
/lib/systemd/system/libvirt-bin.service

  $ systemctl is-active libvirtd
  inactive

  $ systemctl is-active libvirt-bin
  active

  
  - Test case 2 - sshd

  alias service : sshd
  aliased service : ssh

  /ect/systemd/system$ ls -la sshd.service 
  lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> 
/lib/systemd/system/ssh.service

  $ systemctl is-active sshd
  inactive

  $ systemctl is-active ssh
  active

  
  [Regression Potential]

  This fix may result into systemctl reporting inconsistent information
  concerning the status of a service.

  [Other]

  Upstream issue : https://github.com/systemd/systemd/issues/7875
  Upstream fix : https://github.com/systemd/systemd/pull/7997

  Xenial is affected, fix exists on Bionic onward.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.6 LTS
  Release:      16.04

  $ apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu21.21
    Candidate: 229-4ubuntu21.21

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to