Comment 2 for bug 1988355

Hi Alberto, thanks for looking into this!

So, I'm not entirely sure about how the jenkins user is set up initially. This is on an ephemeral node (focal, amd64) on aws running for a regular CI checks for a PR. Here's the whole output, might be helpful:

https://pastebin.canonical.com/p/nSjC7tvk2c/plain/

I went ahead and manually created an ephemeral node and ran the same CI job and I was able to recreate the problem. So I may be able to test it manually if you could make a snapd binary with the fix. I also checked the user jenkins on the same machine:

jenkins@ip-172-31-23-203:~$ ps -fe | grep userd
jenkins 11843 1409 0 17:34 pts/0 00:00:00 grep --color=auto userd