[bitbake-devel] pseudo interfering with git fetcher?

[Jef.Driesen at niko.eu]

Hi,

I'm occasionally experiencing problems when fetching code from git
repositories over ssh. The error is always this one:

bb.fetch2.FetchError: Fetcher failure: Fetch command export
DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-1YNmotxj3i"; export
SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export
PATH="/home/jgo/develop/yocto/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/jgo/develop/yocto/scripts:/home/jgo/develop/yocto/build/tmp/work/armv7ahf-neon-poky-linux-gnueabi/project/fetcheravoidrecurse-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi:/home/jgo/develop/yocto/build/tmp/work/armv7ahf-neon-poky-linux-gnueabi/project/fetcheravoidrecurse-r0/recipe-sysroot/usr/bin/crossscripts:/home/jgo/develop/yocto/build/tmp/work/armv7ahf-neon-poky-linux-gnueabi/project/fetcheravoidrecurse-r0/recipe-sysroot-native/usr/sbin:/home/jgo/develop/yocto/build/tmp/work/armv7ahf-neon-poky-linux-gnueabi/project/fetcheravoidrecurse-r0/recipe-sysroot-native/usr/bin:/home/jgo/develop/yocto/build/tmp/work/armv7ahf-neon-poky-linux-gnueabi/project/fetcheravoidrecurse-r0/recipe-sysroot-native/sbin:/home/jgo/develop/yocto/build/tmp/work/armv7ahf-neon-poky-linux-gnueabi/project/fetcheravoidrecurse-r0/recipe-sysroot-native/bin:/home/jgo/develop/yocto/bitbake/bin:/home/jgo/develop/yocto/build/tmp/hosttools";
export HOME="/home/jgo"; git -c core.fsyncobjectfiles=0 ls-remote
ssh://git@server:port/sw/project.git  failed with exit code 128, output:
Could not create directory '/home/root/.ssh'.
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

It appears that for some reason ssh believes it's running as root. But
that's certainly not the case. It's running as a regular user, and hence
accessing /home/root/.ssh fails. In order to find out what's wrong, I
replaced ssh with a script that logs its environment and then executes
the real ssh binary in verbose mode.

I've attached two such example logs. One from a successful attempt
(ssh.good.log), and one from a failed attempt (ssh.bad.log). The main
difference between the two appears to be that in the bad one, ssh is
being executed under 'pseudo'.

I have absolutely no idea why ssh is sometimes run under pseudo.

Jef
Disclaimer

This e-mail and its attachments is intended only for the person(s) or entity to which it is addressed. If you receive this e-mail by mistake, please delete this e-mail from your system and destroy all copies of it. It may contain confidential and/or privileged information. You should not copy it or use it for any purpose nor disclose its contents to any person unless allowed by a written document between the sender and the addressee.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ssh.bad.log
Type: text/x-log
Size: 5168 bytes
Desc: ssh.bad.log
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20180702/8b6fc0e1/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ssh.good.log
Type: text/x-log
Size: 5177 bytes
Desc: ssh.good.log
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20180702/8b6fc0e1/attachment-0005.bin>