Thank you Albourne for the additional information!
I was able to confirm this bug.
We are not specifying the full path to the `canonical-livepatch` executable every time we call it, so if it is not in your PATH you will get the error described here.
To reproduce the bug: `sudo env PATH="/usr/bin" ua refresh` on an attached bionic machine.
`canonical-livepatch` is located at `/snap/bin/canonical-livepatch`. So if `/snap/bin` is not in PATH then the command will fail. `/snap/bin` is in the PATH by default which is why we haven't noticed this yet.
Workaround:
Adding `/snap/bin` to your path should allow you to run the command until we get this fixed:
Thank you Albourne for the additional information!
I was able to confirm this bug.
We are not specifying the full path to the `canonical- livepatch` executable every time we call it, so if it is not in your PATH you will get the error described here.
To reproduce the bug: `sudo env PATH="/usr/bin" ua refresh` on an attached bionic machine.
`canonical- livepatch` is located at `/snap/ bin/canonical- livepatch` . So if `/snap/bin` is not in PATH then the command will fail. `/snap/bin` is in the PATH by default which is why we haven't noticed this yet.
Workaround:
Adding `/snap/bin` to your path should allow you to run the command until we get this fixed:
sudo env PATH="$ PATH:/snap/ bin" ua refresh