Hi all, attempting to build libvirt in copr on f30/f31 aarch64 fails immediately: cmd: ['git', 'clone', 'https://copr-dist-git.fedorainfracloud.org/git/@virtmaint-sig/for-kubevirt/libvirt.git', '/tmp/tmp1yl8gbk0/libvirt', '--depth', '500', '--no-single-branch'] cwd: . rc: 128 stdout: stderr: Cloning into '/tmp/tmp1yl8gbk0/libvirt'... fatal: unable to access 'https://copr-dist-git.fedorainfracloud.org/git/@virtmaint-sig/for-kubevirt/libvirt.git/': SSL certificate problem: certificate is not yet valid Cloning into '/tmp/tmp1yl8gbk0/libvirt'... fatal: unable to access 'https://copr-dist-git.fedorainfracloud.org/git/@virtmaint-sig/for-kubevirt/libvirt.git/': SSL certificate problem: certificate is not yet valid Running: git clone https://copr-dist-git.fedorainfracloud.org/git/@virtmaint-sig/for-kubevir... /tmp/tmp1yl8gbk0/libvirt https://copr-be.cloud.fedoraproject.org/results/@virtmaint-sig/for-kubevi... Anyone seen something similar? Any idea what's going on?

On Tuesday, November 19, 2019 9:41:35 PM CET Pavel Raiskup wrote: > On Tuesday, November 19, 2019 9:35:29 PM CET Cole Robinson wrote: >> stderr: Cloning into '/tmp/tmp1yl8gbk0/libvirt'... >> fatal: unable to access >> 'https://copr-dist-git.fedorainfracloud.org/git/@virtmaint-sig/for-kubevirt/libvirt.git/': >> SSL certificate problem: certificate is not yet valid >> [...] >> Anyone seen something similar? Any idea what's going on? > > It could be de-synced time on aarch64 builders. I'll take a look > tomorrow if nobody is faster. Hm, time is set fine on aarch64 builders now, chronyd is working. I don't know the reason for yesterday's build failures, maybe some temporary network issue causing chronyd to fail?