Hello,
today there will be a COPR outage lasting approximately for 1 hour starting at 1 a.m. UTC. We will be upgrading most of the machines to the latest released Fedora version.
COPR Team
I am very sorry. I meant 1pm UTC today.
Best regrads On behalf of COPR team clime
On Mon, Dec 18, 2017 at 10:03 AM, Michal Novotny clime@redhat.com wrote:
Hello,
today there will be a COPR outage lasting approximately for 1 hour starting at 1 a.m. UTC. We will be upgrading most of the machines to the latest released Fedora version.
COPR Team
While the outage was planned to last only 1 hour, it lasted three. Sorry for this but we encountered errors that we didn't exactly account for :(. There is much more room for improvement here in the preparation process.
There were problems with builder images that were initially prepared on staging machine which caused staging repos being enabled on them. We needed to prepare x86_64 image from scratch. Also copr-keygen was not singing for a while due to change IP after we deployed it on f27 from scratch. The affected builds by this were the following:
https://copr.fedorainfracloud.org/coprs/teknoraver/Netperf/build/688726/ https://copr.fedorainfracloud.org/coprs/teknoraver/Netperf/build/688714/ https://copr.fedorainfracloud.org/coprs/g/rubygems/rubygems/build/688728/ https://copr-be.cloud.fedoraproject.org/results/hobbes1069/EPEL/epel-6-i386/... https://copr-be.cloud.fedoraproject.org/results/monotykamary/RetroArch/fedor...
I reran the first three builds from scratch. The second two builds were partially succeeded so I just deleted the unsigned rpms for the failed chroots. They will need to be rerun for the complete results
Sorry for the problems With apology COPR Team
P.S.: there seems to be a problem with epel-7-ppc64le builds but that is a separate problem and we will take a look at it.
copr-devel@lists.fedorahosted.org