[Bug 1659719] Autopkgtest regression report (pam/1.1.8-3.6ubuntu2.18.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted pam (1.1.8-3.6ubuntu2.18.04.2) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
systemd/237-3ubuntu10.41 (ppc64el)
openssh/1:7.6p1-4ubuntu0.3 (arm64, amd64, i386, armhf, s390x, ppc64el)
vsftpd/3.0.3-9build1 (arm64)
lxc/3.0.3-0ubuntu1~18.04.1 (ppc64el)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#pam

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/1659719

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  New
Status in openssh source package in Xenial:
  New
Status in pam source package in Xenial:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in openssh source package in Bionic:
  New
Status in pam source package in Bionic:
  Fix Committed
Status in livecd-rootfs source package in Focal:
  New
Status in openssh source package in Focal:
  New
Status in pam source package in Focal:
  Fix Committed
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Fix Released
Status in openssh package in Debian:
  New

Bug description:
  [impact]
  ssh can't call a binary from a snap, it will only work using the full path.

  [test case]
  Create a container. Install the go snap (and make sure golang-go is not installed). Run "ssh <container-ip> go version" and check the binary is found.

  [regression potential]
  It's a pam change an they are always a bit scary but the code follows the existing pattern for updating PATH in /etc/environment and has been tested in groovy.

  [original description]

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio at ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio at 192.168.122.24's password:
  bash: hello: command not found
  elopio at ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio at 192.168.122.24's password:
  Hello, world!

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+subscriptions