Planned Outage - Fedora Build Services 2019-03-01 20:00 UTC There will be an outage starting at 2019-03-01 20:00 UTC, which will last approximately 4-6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-03-01 20:00UTC' Reason for outage: Fedora Infrastructure would like to update and reboot all QA and build systems and services. This will update kernels, glibc, and systemd plus many other services on the affected systems. Affected Services: All build and QA systems under fedoraproject.org will be affected. Friday Hosts to Update/Reboot: buildhw-01.phx2 - buildhw-02.phx2 - buildhw-03.phx2 - buildhw-04.phx2 - buildhw-05.phx2 - buildhw-06.phx2 - buildhw-07.phx2 - buildhw-08.phx2 - buildhw-09.phx2 - buildhw-10.phx2 - buildvmhost-01.phx2 - buildvmhost-02.phx2 - buildvmhost-03.phx2 - buildvmhost-04.phx2 - bvirthost01.phx2 - bvirthost04.phx2 - bvirthost05.phx2 - bvirthost08.phx2 - bvirthost12.phx2 - bvirthost13.phx2 - bvirthost14.phx2 - bvirthost15.phx2 - ppc8-01.ppc - ppc8-02.ppc - ppc8-03.ppc - ppc8-04.ppc - aarch64-c01n1.arm - aarch64-c02n1.arm - aarch64-c03n1.arm - aarch64-c04n1.arm - aarch64-c05n1.arm - aarch64-c06n1.arm - aarch64-c07n1.arm - aarch64-c08n1.arm - aarch64-c09n1.arm - aarch64-c10n1.arm - aarch64-c11n1.arm - aarch64-c12n1.arm - aarch64-c13n1.arm - aarch64-c14n1.arm - aarch64-c15n1.arm - aarch64-c16n1.arm - aarch64-c17n1.arm - aarch64-c18n1.arm - aarch64-c19n1.arm - aarch64-c20n1.arm - aarch64-c21n1.arm - aarch64-c22n1.arm - aarch64-c23n1.arm - aarch64-c24n1.arm - aarch64-c25n1.arm - buildhw-aarch64-01.arm - buildhw-aarch64-02.arm - buildhw-aarch64-03.arm - buildhw-aarch64-04.arm - buildhw-aarch64-05.arm - buildhw-aarch64-06.arm - buildhw-aarch64-07.arm - buildhw-aarch64-08.arm - buildhw-aarch64-10.arm - buildvm-s390x-01.s390 - buildvm-s390x-01.stg.s390 - buildvm-s390x-02.s390 - buildvm-s390x-03.s390 - buildvm-s390x-04.s390 - buildvm-s390x-05.s390 - buildvm-s390x-06.s390 - buildvm-s390x-07.s390 - buildvm-s390x-08.s390 - buildvm-s390x-09.s390 - buildvm-s390x-10.s390 - buildvm-s390x-11.s390 - buildvm-s390x-12.s390 - buildvm-s390x-13.s390 - buildvm-s390x-14.s390 - sign-vault03.phx2 - sign-vault04.phx2 - sign-vault05.phx2 - sign-vault06.phx2 - bkernel01.phx2 - bkernel02.phx2 - bkernel03.phx2 - bkernel04.phx2 - qa05.qa - qa07.qa - qa09.qa - qa10.qa - qa11.qa - qa12.qa - qa13.qa - qa14.qa - virthost-comm01.qa - virthost-comm03.qa - virthost-comm04.qa - aarch64-c26n1-oqa.arm - aarch64-c27n1-oqa.arm - aarch64-c28n1-oqa.arm - aarch64-c29n1-oqa.arm - aarch64-c30n1-oqa.arm - kernel01.qa - kernel02.qa - retrace01.qa - retrace02.qa - Ticket Link: https://pagure.io/fedora-infrastructure/issue/7602 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
