Upgrade of Copr servers - 2019-12-05 06:00 UTC (Thursday)

[Pavel Raiskup]

There will be an outage, starting at:

    $ date --date='2019-12-05 06:00 UTC'

which will last approximately 1 hour.

Reason for outage
=================

Upgrade of copr packages on Copr servers, to get in bug-fixes and new features.


Affected Services
=================

copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/
copr-dist-git - https://copr-dist-git.fedorainfracloud.org/

Though the yum/dnf repositories (the copr-backend part which is consumed by
end-user by 'dnf copr enable ...') should stay available during this outage.

Ticket Link
===========

https://pagure.io/fedora-infrastructure/issue/8439


Contact Information
===================

@praiskup

Please join #fedora-admin in irc.freenode.net or add comments to the ticket for
this outage above.

Highlights from the latest Copr release

[Pavel Raiskup]

Hello,

recently (on Dec 5, 2019) a new Copr release landed production.
Here is the list of visible changes:

- Projects can be marked as "providing module hotfixes".  This hack is
  needed to give the packages distributed by copr preference over packages
  provided from modules (they ignore repo priority and NVR checks
  otherwise).  More in this blog post
  http://frostyx.cz/posts/module-hotfixes-in-copr
- The links in UI pointing to live-logs should be fixed now, even for
  re-submitted builds.
- Project forking was fixed, and should work reliably now.  The fork
  action is still handled by copr frontend (the copr database), so we copy
  the last successful package build in each chroot - given by build-ID,
  not NVR.
- The Pagure event reader was ported from fedmsg to fedora-mesaging, so
  from now - no part of copr code depends on fedmsg, and we should not
  miss relevant events anymore.
- Package build fails when the main copr repository isn't available at
  build time (for any, even temporary reason).  We were able to configure
  there skip_if_unavailable=False because we always create (empty)
  repository - before we build the first package there.
- The backend code was optimized (lower redis trafic, faster job grabber,
  minimized builder<->backend<->frontend communication).
- The builder again defines %copr_username and %copr_projectname RPM
  macros.

Happy building!
Pavel