On 2019-03-14 12:10:00 +0100 (+0100), Thierry Carrez wrote: [...]
During collection of the built artifacts, the following command:
/usr/bin/rsync --delay-updates -F --compress --archive --rsh=/usr/bin/ssh -S none -o Port=22 --out-format=<<CHANGED>>%i %n%L zuul@104.130.6.123:/home/zuul/zuul-output/artifacts/ /var/lib/zuul/builds/16d67fd9d85342bfabfd82292183e76c/work/artifacts/
failed host key verification:
ED25519 host key for 104.130.6.123 has changed and you have requested strict checking. [...]
Based on the log this was the Zuul executor trying to rsync files off the job node over SSH, surprised to find the SSH host key on the job node was suddenly different. We see this symptom from time to time when Nova loses track of a VM somewhere in the provider and so the IP address remains in use but also gets reassigned to a new VM for our boot request. This is almost certainly a transient failure and the build was merely "lucky" enough to win at rogue instance roulette. -- Jeremy Stanley