[Bug 1659719] Re: ssh can't call a binary from a snap without the full path

[Michael Hudson-Doyle]

And verified on xenial:

(client-server-5)mwhudson at anduril:~/src/subiquity$ ssh ubuntu at 10.187.142.193 "sh -c 'dpkg-query -W libpam-modules; type go '"
libpam-modules:amd64	1.1.8-3.2ubuntu2.1
go: not found
(client-server-5)mwhudson at anduril:~/src/subiquity$ lxc exec lp1659719-xenial -- apt install -y libpam-modules/xenial-proposed
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Selected version '1.1.8-3.2ubuntu2.3' (Ubuntu:16.04/xenial-proposed [amd64]) for 'libpam-modules'
Selected version '1.1.8-3.2ubuntu2.3' (Ubuntu:16.04/xenial-proposed [amd64]) for 'libpam-modules-bin' because of 'libpam-modules'
The following packages were automatically installed and are no longer required:
  libfreetype6 motd-news-config
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libpam-modules-bin
Recommended packages:
  update-motd
The following packages will be upgraded:
  libpam-modules libpam-modules-bin
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 281 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 libpam-modules-bin amd64 1.1.8-3.2ubuntu2.3 [36.9 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 libpam-modules amd64 1.1.8-3.2ubuntu2.3 [244 kB]
Fetched 281 kB in 2s (123 kB/s)         
Preconfiguring packages ...
(Reading database ... 25804 files and directories currently installed.)
Preparing to unpack .../libpam-modules-bin_1.1.8-3.2ubuntu2.3_amd64.deb ...
Unpacking libpam-modules-bin (1.1.8-3.2ubuntu2.3) over (1.1.8-3.2ubuntu2.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libpam-modules-bin (1.1.8-3.2ubuntu2.3) ...
(Reading database ... 25804 files and directories currently installed.)
Preparing to unpack .../libpam-modules_1.1.8-3.2ubuntu2.3_amd64.deb ...
Unpacking libpam-modules:amd64 (1.1.8-3.2ubuntu2.3) over (1.1.8-3.2ubuntu2.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libpam-modules:amd64 (1.1.8-3.2ubuntu2.3) ...
(client-server-5)mwhudson at anduril:~/src/subiquity$ ssh ubuntu at 10.187.142.193 "sh -c 'dpkg-query -W libpam-modules; type go '"
libpam-modules:amd64	1.1.8-3.2ubuntu2.3
go is /snap/bin/go


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

-- 
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:
  Won't Fix
Status in pam source package in Xenial:
  Fix Committed
Status in livecd-rootfs source package in Bionic:
  New
Status in openssh source package in Bionic:
  Won't Fix
Status in pam source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Focal:
  New
Status in openssh source package in Focal:
  Won't Fix
Status in pam source package in Focal:
  Fix Released
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