On Wed, Nov 20, 2019 at 08:19:04AM +0100, Pavel Raiskup wrote: > 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?
Yeah, I noticed the time was off on the virthost (sometime in 2001?) and fixed it. I wasn't aware it was causing this issue at the time... kevin
signature.asc
Description: PGP signature
_______________________________________________ copr-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected]
