Planned Outage: 2020-11-11 21:00 UTC Fedora Services
There will be an outage starting at 2020-11-11 21:00UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2017-05-03 21:00UTC' Reason for outage: Apply updates and new kernels for all systems running RHEL7/RHEL8 and Fedora 32 Affected Services: Most services in IAD2 will see downtime as we run updates and reboot systems. Ticket Link: https://pagure.io/fedora-infrastructure/issue/ Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Turning off keys.fedoraproject.org
Fedora has been part of an GPG sks service[1] for a number of years running off of keys.fedoraproject.org. Last year, there were a number of attacks made on the service which due to its 'write-only' nature makes it impossible to clean up [2] [3]. When the attacks came up, and it was clear it was not easily fixable, we moved keys to a proxy only mode. However this mode has not been too stable and caused other issues. Fedora Infrastructure has tried to figure out ways to run a service replacement, but currently has not found one which we can with the resources we have available. We plan to turn off and decommission keys.fedoraproject.org on 2020-02-10. We currently recommend people to use https://keys.openpgp.org/ which offers lookup capabilities. [1] https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Home [2] https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f [3] https://www.zdnet.com/article/openpgp-flooded-with-spam-by-unknown-hackers/ -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Outage for 2020-01-15: Fedora Prod Environment
#8506 Planned Outage - Fedoraproject.org - 2020-01-15 21:00 UTC Opened a day ago by smooge. Modified a day ago Open Planned Outage - Fedoraproject.org - 2020-01-15 21:00 UTC There will be an outage starting at 2020-01-15 21:00UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2020-01-15 21:00UTC' Reason for outage: Update all production servers to latest kernels and glibc. Get any associated security fixes pushed into production Affected Services: All Fedora websites will see short term outages as reboots occur. Other services will be impacted during updates and reboots. Ticket Link: https://pagure.io/fedora-infrastructure/issue/8506 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Outage for 2020-01-14: Fedora Build Environment
8505 Planned Outage - Fedora Build Systems - 2020-01-14 21:00 UTC Opened a day ago by smooge. Modified 2 minutes ago Open Planned Outage - Fedora Build Systems - 2020-01-14 21:00 UTC There will be an outage starting at 2020-01-14 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2020-01-14 21:00UTC' Reason for outage: Update build systems to latest kernel and glibc. Get associated security fixes Affected Services: koji and related services in fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/8505 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Outage for 2020-01-13: Fedora Infrastructure Staging Environment
#8504 Planned Outage - Fedora Staging - 2020-01-13 21:00 UTC Opened a day ago by smooge. Modified 4 hours ago Open There will be an outage starting at 2020-01-13 21:00UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2020-01-13 21:00UTC' Reason for outage: Update servers and services to newest glibc and kernels. Get any other security fixes onto systems also. Affected Services: All of *.stg.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/8504 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Planned Outage - Fedora Staging/Build Updates/Reboots 2019-08-20 20:00 UTC
=== Planned Outage - Staging/Build - 2019-08-20 20:00 UTC There will be an outage starting at 2019-08-20 20:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-08-20 20:00UTC' Reason for outage: RHEL-7.7 came out and a lot of other updates for various Fedora issues will need updates and reboots of systems. Affected Services: All staging and build and related services will be affected. Ticket Link: https://pagure.io/fedora-infrastructure/issue/8106 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Planned Outage - PHX2-Production - 2019-08-21 20:00 UTC
=== Planned Outage - PHX2-Production - 2019-08-21 20:00 UTC There will be an outage starting at 2019-08-21 20:00 UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-08-21 20:00UTC' Reason for outage: RHEL-7.7 came out and a lot of other updates for various Fedora issues will need updates and reboots of systems. Affected Services: All staging/production and related services will be affected. Ticket Link: https://pagure.io/fedora-infrastructure/issue/8107 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Announcing EPEL-8.0 Release
The EPEL Steering Committee is pleased to announce that the initial EPEL-8 is ready for release. We would like to thank everyone in the community for helping us get the initial set of builds out to mirrors and to consumers worldwide. Special thanks go to Patrick Uiterwijk, Jeroen van Meeuwen, Robert Scheck, and many others in the community who helped in the last 6 months to get this release done. EPEL-8.0 has packages for the x86_64, ppc64le, aarch64, and now the s390x platforms. ## What is EPEL? EPEL stands for Extra Packages for Enterprise Linux and is a subcommunity of the Fedora and CentOS projects aimed at bringing a subset of packages out of Fedora releases ready to be used and installed on various Red Hat Enterprise Linux (RHEL). It is not a complete rebuild of Fedora or even of previous EPEL releases. EPEL is also a community and not a product. As such we need community members to help get packages into the repository more than done in Fedora. If you are interested in getting a package into EPEL, contact the package maintainer through bugzilla. This way the request can be tracked, and if the primary maintainer is not interested in branching to EPEL, others can step in and do so. Optionally you can send a request to the epel-de...@lists.fedoraproject.org mailing list. If you do so, please include why the package is needed, to help other volunteers decide whether they can support it. ## What is new? ### Playground for Rawhide like things We have added an additional set of channels for EPEL-8 called playground. It is similar to Fedora Rawhide so packagers can work on versions of software that are too fast moving or will have large API changes compared to versions in the regular channel. To make this purpose transparent, when a package is built in epel8, it will normally also be built in epel8-playground. This is done via a packages.cfg file which lists the targets for fedpkg to build against. A successful package build will then go through two different paths: * epel8 package will go into bodhi to be put into epel8-testing * epel8-playground will bypass bodhi and go directly into epel8-playground the next compose. If a packager needs to focus only on epel8 or epel8-playground they can edit packages.cfg to change the target=epel8 epel8-playground to target=epel8. Packages in epel8-playground are intended to be used in the following manner: * To test out a new version of the package that might not be stable yet. * To test out new packaging of the package * To test a major version change of the package intended for the next EPEL-8 minor release. * To build a package that will never be stable enough for EPEL-8, but still could be useful to some. At minor RHEL releases (ie, 8.1, 8.2) people can pull in big changes from playground to the main EPEL-8 packages. Since people will be upgrading and paying more attention than usual anyhow at those points, it’s a great chance to do that change, but you can test beforehand in the playground to make sure these changes work. Consumers should be aware that packages in EPEL8-playground are without any Service Level Expectations. You may want to only cherry pick packages from the playground as needed. ### New Architecture: s390x We have added the s390x platform to builds. Some consumers have wanted this platform for many years but we did not have the time to integrate necessary changes. We have done this with EPEL-8, and hope to be able to do so for EPEL-7 if there are continued requests for it. ## What is next? (Why is it called EPEL-8.0?) The goal for EPEL-8.1 will be implementing modules into the repository, which allows builds for packages that depend on non-shipped devel packages. It also allows maintainers to supplement and replace other packages they could not under standard EPEL rules. ## Known Issues: 1. EPEL-8.0 does not come with modules. Packages built for perl, python and other modules are only built against “default” modules. For example installing a perl library from EPEL will work with the perl-5.26 but not with the perl-5.24 module. 2. RHEL-8.0 and RHEL-8.1 beta do not come with the same packages in all architectures. There are 720 ‘desktop’ packages which were only shipped for x86_64 and ppc64le. Packagers looking to deliver GNOME, KDE, or other platforms will need to exclude s390x and aarch64 at this time. 3. The dnf in RHEL-8.1 beta does not work with the EPEL repository due to zchunk code. This has been opened as an upstream bug as https://bugzilla.redhat.com/show_bug.cgi?id=1719830 4. Until modularity and module builds are implemented in EPEL, there will be many packages which can not be built for EPEL. This is mainly due to RHEL-8 not shipping many -devel packages and the need for us to rebuild those packages in a module to make those -devel available to build against. When running into this please open a ticket with https://pagure.io/epel/new_issue for us to put in a request for it to be added to Red Hat’s Code Ready Builder. Please
Rescheduled: Planned Outage - Fedora Core Services 2019-05-23 21:00 UTC
Due to multiple personnel conflicts today, we are rescheduling this to the 23rd. On Mon, 20 May 2019 at 08:22, Stephen John Smoogen wrote: > > There will be an outage starting at 2019-05-23 21:00 UTC , > which will last approximately 5 hours. > > To convert UTC to your local time, take a look at > http://fedoraproject.org/wiki/Infrastructure/UTCHowto > or run: > > date -d '2019-05-23 21:00UTC' > > Reason for outage: > > There have been a number of kernel and low level library updates which > require a system reboot to put into place. We will be rebooting > productions servers which do require a full outage and downtime. > > Affected Services: > > koji.fedoraproject.org > src.fedoraproject.org > *.phx2.fedoraproject.org > > Ticket Link: > > https://pagure.io/fedora-infrastructure/issue/7810 > > Please join #fedora-admin or #fedora-noc on irc.freenode.net > or add comments to the ticket for this outage above. > > -- > Stephen J Smoogen. > > -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
CORRECTION: Planned Outage - Fedora Core Services 2019-05-22 21:00 UTC
There will be an outage starting at 2019-05-22 21:00 UTC , which will last approximately 5 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-05-22 21:00UTC' Reason for outage: There have been a number of kernel and low level library updates which require a system reboot to put into place. We will be rebooting productions servers which do require a full outage and downtime. Affected Services: koji.fedoraproject.org src.fedoraproject.org *.phx2.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/7810 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
Planned Outage - Fedora Staging Services 2019-05-20 21:00 UTC
There will be an outage starting at 2019-05-20 21:00 UTC , which will last approximately 5 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-05-20 21:00UTC' Reason for outage: There have been a number of kernel and low level library updates which require a system reboot to put into place. We will be rebooting staging and several non-PHX2 servers which do not require a full outage due to redundancy or low service level expectations. Affected Services: *.stg.fedoraproject.org *.stg.phx2.fedoraproject.org osuosl02.fedoraproject.org pagure-stg01.fedoraproject.org osuosl02.fedoraproject.org proxy09.fedoraproject.org osuosl02.fedoraproject.org smtp-mm-osuosl01.fedoraproject.org osuosl02.fedoraproject.org unbound-osuosl01.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/7808 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
Planned Outage - Fedora Proxies and Remote Servers Updates/Reboots - 2019-05-21 21:00 UTC
There will be an outage starting at 2019-05-21 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-05-21 21:00UTC' Reason for outage: We have come to chew gum and reboot servers, and we have all run out of gum. There have been a number of kernel and low level library updates which require a system reboot to put into place. We will be rebooting staging and non-PHX2 servers which do not require a full outage due to redundancy or low service level expectations. Affected Services: proxy05.fedoraproject.org coloamer01.fedoraproject.org:proxy08.fedoraproject.org:running:1 dedicatedsolutions01.fedoraproject.org:proxy11.fedoraproject.org:running:1 ibiblio01.fedoraproject.org:download-ib01.fedoraproject.org:running:1 ibiblio01.fedoraproject.org:noc02.fedoraproject.org:running:1 ibiblio01.fedoraproject.org:pagure-proxy01.fedoraproject.org:running:1 ibiblio01.fedoraproject.org:proxy04.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:ns02.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:people02.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:proxy12.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:smtp-mm-ib01.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:torrent02.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:unbound-ib01.fedoraproject.org:running:1 internetx01.fedoraproject.org:ns05.fedoraproject.org:running:1 internetx01.fedoraproject.org:proxy02.fedoraproject.org:running:1 osuosl01.fedoraproject.org:pagure01.fedoraproject.org:running:1 osuosl01.fedoraproject.org:proxy06.fedoraproject.org:running:1 osuosl01.fedoraproject.org:repospanner-osuosl01.fedoraproject.org:running:1 osuosl02.fedoraproject.org:keys01.fedoraproject.org:running:1 osuosl02.fedoraproject.org:pagure-stg01.fedoraproject.org:running:1 osuosl02.fedoraproject.org:proxy09.fedoraproject.org:running:1 osuosl02.fedoraproject.org:smtp-mm-osuosl01.fedoraproject.org:running:1 osuosl02.fedoraproject.org:unbound-osuosl01.fedoraproject.org:running:1 virthost-cc-rdu01.fedoraproject.org:ci-cc-rdu01.fedoraproject.org:running:1 virthost-cc-rdu01.fedoraproject.org:proxy14.fedoraproject.org:running:1 virthost-cc-rdu01.fedoraproject.org:smtp-mm-cc-rdu01.fedoraproject.org:running:1 virthost-cc-rdu02.fedoraproject.org:infinote.fedoraproject.org:running:1 virthost-cc-rdu02.fedoraproject.org:proxy03.fedoraproject.org:running:1 virthost-cc-rdu02.fedoraproject.org:repospanner-cc-rdu01.fedoraproject.org:running:1 virthost-cc-rdu02.fedoraproject.org:unbound-cc-rdu01.fedoraproject.org:running:1 virthost-cc-rdu03.fedoraproject.org:download-cc-rdu01.fedoraproject.org:running:1 virthost-cc-rdu03.fedoraproject.org:ipv6-test.fedoraproject.org:running:1 virthost-rdu01.fedoraproject.org:bastion13.fedoraproject.org:running:1 virthost-rdu01.fedoraproject.org:batcave13.rdu2.fedoraproject.org:running:1 virthost-rdu01.fedoraproject.org:ns13.rdu2.fedoraproject.org:running:1 virthost-rdu01.fedoraproject.org:proxy13.fedoraproject.org:running:1 data-analysis01.phx2.fedoraproject.org dl.fedoraproject.org (service has multiple front ends so outages should be short per) Ticket Link: https://pagure.io/fedora-infrastructure/issue/7809 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
Planned Outage - Fedora Core Services 2019-04-10 21:00 UTC
Planned Outage - Fedora Core Services 2019-04-10 21:00 UTC There will be an outage starting at 2019-04-10 21:00 UTC , which will last approximately 5 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-04-10 21:00UTC' Reason for outage: There have been a number of kernel and low level library updates which require a system reboot to put into place. We will be rebooting staging and non-PHX2 servers which do not require a full outage due to redundancy or low service level expectations. Affected Services: koji.fedoraproject.org src.fedoraproject.org fedorapeople.org pagure.io *.phx2.fedoraproject.org ibiblio01.fedoraproject.org download-ib01.fedoraproject.org ibiblio01.fedoraproject.org noc02.fedoraproject.org ibiblio01.fedoraproject.org pagure-proxy01.fedoraproject.org ibiblio01.fedoraproject.org proxy04.fedoraproject.org ibiblio05.fedoraproject.org ns02.fedoraproject.org ibiblio05.fedoraproject.org people02.fedoraproject.org ibiblio05.fedoraproject.org proxy12.fedoraproject.org ibiblio05.fedoraproject.org smtp-mm-ib01.fedoraproject.org ibiblio05.fedoraproject.org torrent02.fedoraproject.org ibiblio05.fedoraproject.org unbound-ib01.fedoraproject.org osuosl01.fedoraproject.org pagure01.fedoraproject.org osuosl01.fedoraproject.org proxy06.fedoraproject.org osuosl01.fedoraproject.org repospanner-osuosl01.fedoraproject.org virthost-cc-rdu02.fedoraproject.org infinote.fedoraproject.org virthost-cc-rdu02.fedoraproject.org proxy03.fedoraproject.org virthost-cc-rdu02.fedoraproject.org repospanner-cc-rdu01.fedoraproject.org virthost-cc-rdu02.fedoraproject.org unbound-cc-rdu01.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/ Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
EPEL: Python34 moving to Python36
Over the last 5 days, Troy Dawson, Jeroen van Meeuwen, Carl W George, and several helpers have gotten nearly all of the python34 packages moves over to python36 in EPEL-7. They are being included in 6 Bodhi pushes because of a limitation in Bodhi for the text size of packages in an include. The current day for these package groups to move into EPEL regular is April 2nd. We would like to have all tests we find in the next week or so also added so that the updates can occur in a large group without too much breakage. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f2d195dada https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9e9f81e581 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0d62608bce https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5be892b745 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0f4cca7837 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ed3564d906 Please heavily test them by doing the following: Stage 1 Testing Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. Install or enable the EPEL repository for this system Install various packages you would normally use yum --enablerepo=epel-testing update Report problems to epel-de...@lists.fedoraproject.org Stage 2 Testing Check for any updated testing instructions on this blog or EPEL-devel list. Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. Install or enable the EPEL repository for this system yum install python34 yum --enablerepo=epel-testing update Report problems to epel-de...@lists.fedoraproject.org Stage 3 Testing Check for any updated testing instructions on this blog or EPEL-devel list. Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. Install or enable the EPEL repository for this system yum install python36 yum --enablerepo=epel-testing update Report problems to epel-de...@lists.fedoraproject.org This should cover the three most common scenarios. Other scenarios exist and will require some sort of intervention to work around. We will outline them as they come up. Many Many Thanks go to Troy, Jeroen, Carl, and the many people on the python team who made a copr and did many of the initial patches to make this possible. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
Planned Outage - Fedora Build Services 2019-03-01 20:00 UTC
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. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
Outage 2019-02-02 13:00 UTC -> 15:00 UTC
This outage is a replacement of an earlier one in December which had to be cancelled. There will be an outage starting at 2019-02-02 13:00 UTC, which will last approximately 2 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-02-02 13:00UTC' Reason for outage: Various switches at the colocation are needing updates and reboots to get latest firmware working. While the outage should not take the entire 2 hours, it is being blocked out in case there are problems which are not realized and need backing out or other changes. Affected Services: dl.fedoraproject.org all build services most web services copr and all other cloud services. Ticket Link: https://pagure.io/fedora-infrastructure/issue/7535 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
Re: OUTAGE: Koji system 2019-01-11 -> 2019-01-14
This is a reminder that this begins this Friday and will probably be in place for 4 days. If there are increased downtimes, we will update the data when we know it. On Fri, 7 Dec 2018 at 14:51, Stephen John Smoogen wrote: > Planned Outage - Koji Services - 2019-01-11 22:00 UTC > > There will be an koji outage starting at 2019-01-11 22:00 UTC, which > will last approximately 4 days. > > To convert UTC to your local time, take a look at > http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: > > date -d '2019-01-11 22:00UTC' > > Reason for outage: > > The facility that houses the Fedora s390 server will have a major > power outage starting 2019-01-11 22:00 UTC and ending 2019-01-14 22:00 > UTC. During this time the s390 builders will not be available and all > builds will be queued up until they are available and will not > complete. > > Affected Services: > > koji and related services which make composes and builds > > Ticket Link: > > https://pagure.io/fedora-infrastructure/issue/7429 > > Please join #fedora-admin or #fedora-noc on irc.freenode.net or add > comments to the ticket for this outage above. > > -- > Stephen J Smoogen. > -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
Planned Outage - PHX2 Colocation- 2018-12-13 23:00 UTC
There will be an outage starting at 2018-12-13 23:00 UTC, which will last approximately 5 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2017-05-03 21:00UTC' Reason for outage: Various switches at the colocation are needing updates and reboots to get latest firmware working. While the outage should not take the entire 5 hours, it is being blocked out in case there are problems which are not realized and need backing out or other changes. Affected Services: dl.fedoraproject.org all build services most web services copr and all other cloud services. Ticket Link: https://pagure.io/fedora-infrastructure/issue/7433 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
OUTAGE: Koji system 2019-01-11 -> 2019-01-14
Planned Outage - Koji Services - 2019-01-11 22:00 UTC There will be an koji outage starting at 2019-01-11 22:00 UTC, which will last approximately 4 days. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-01-11 22:00UTC' Reason for outage: The facility that houses the Fedora s390 server will have a major power outage starting 2019-01-11 22:00 UTC and ending 2019-01-14 22:00 UTC. During this time the s390 builders will not be available and all builds will be queued up until they are available and will not complete. Affected Services: koji and related services which make composes and builds Ticket Link: https://pagure.io/fedora-infrastructure/issue/7429 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
Fedora Infrastructure Planned Outage 2018-10-03
l;dr: All Fedora Infrastructure systems will be updated and rebooted over this week. Systems that can be done outside of the planned outage. 2018-10-01 21:00 UTC Staging and downloads 2018-10-02 throughout the 'day' single proxies will be updated/rebooted. 2018-10-03 production systems including all build servers will be rebooted. === Planned Outage - Build/Production - 2018-10-03 21:00 UTC There will be an outage starting at 2018-10-03 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2018-10-03 21:00UTC' Reason for outage: Various kernel, library, and general security updates need to be applied to all servers. Due to the kernel, glibc, and other updates.. all systems will be rebooted afterwords Affected Services: All build, production and related services will be affected. Ticket Link: https://pagure.io/fedora-infrastructure/issue/7272 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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/devel-announce@lists.fedoraproject.org
Planned Outage - Ibiblio Servers (fedorapeople.org, torrent01.fedoraproject.org) 2018-05-09 12:00 UTC
Planned Outage - Server updates - 2018-05-09 12:00 UTC There will be an outage starting at 2018-05-09 12:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2018-05-09 12:00UTC' Reason for outage: Ibiblio is moving systems to a newer rack with 10G SFP+ networks. Systems will need to be powered down, moved over to the new racks, powered back up, configured to use the new networks in failover mode. Affected Services: download-ib01.fedoraproject.org pagure-proxy01.fedoraproject.org proxy04.fedoraproject.org noc02.fedoraproject.org unbound-ib01.fedoraproject.org ns02.fedoraproject.org people02.fedoraproject.org proxy12.fedoraproject.org smtp-mm-ib01.fedoraproject.org torrent02.fedoraproject.org Torrent and people will be down during that time. Systems configured to use download-ib02 will also be. Ticket Link: https://pagure.io/fedora-infrastructure/issue/6915 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Planned Outage: 2016-11-29 21:00 UTC Build Environment
There will be an outage starting at 2016-11-29 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-11-29 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ Package Database - https://admin.fedoraproject.org/pkgdb/ Unaffected Services: BFO - https://boot.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/5579 Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Planned Outage: Cloud Environment - 2016-12-01 21:00 UTC
There will be an outage starting at 2016-12-01 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-12-01 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Cloud Environment - *.fedorainfracloud.org Unaffected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ Package Database - https://admin.fedoraproject.org/pkgdb/ BFO - https://boot.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/5581 Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Planned Outage: General Services Environment - 2016-11-30 21:00 UTC
There will be an outage starting at 2016-11-30 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-11-30 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ Package Database - https://admin.fedoraproject.org/pkgdb/ BFO - https://boot.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Unaffected Services: Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Ticket Link: TBA Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Planned Outage: Staging Environment - 2016-11-28 21:00 UTC
There will be an outage starting at 2016-11-28 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-11-28 21:00 UTC' Reason for outage: We have been in a freeze for the release of Fedora 25 and have multiple updates across the systems needed to occur. Part of these are to bring RHEL-7 systems to 7.3 and others are to bring some systems to Fedora 25. Affected Services: Staging - .stg.fedoraproject.org, .stg.phx2.fedoraproject.org Unaffected Services: BFO - https://boot.fedoraproject.org/ Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - https://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - https://fedorapeople.org/ Main Website - https://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ QA Services Secondary Architectures Spins - https://spins.fedoraproject.org/ Start - https://start.fedoraproject.org/ Torrent - https://torrent.fedoraproject.org/ Translation Services - https://translate.fedoraproject.org/ Wiki - https://fedoraproject.org/wiki/ Ticket Link: TBA Contact Information: infrastructure @lists.fedoraproject.org Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Outage Notification: Red Hat Bugzilla 2010-05-04 16:00UTC - 16:40 UTC
Outage Notification: Red Hat Bugzilla Red Hat Bugzilla has currently an planned outage that is taking longer than expected, and is causing various Fedora services not to be functional. We are working with upstream on recovering services as fast as possible To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2009-01-09 HH:MM UTC' Affected Services: fedora community fedora pkgdb -- Stephen J Smoogen. “The core skill of innovators is error recovery, not failure avoidance.” Randy Nelson, President of Pixar University. "We have a strategic plan. It's called doing things."" — Herb Kelleher, founder Southwest Airlines ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
Outage Notification - 2010-02-10 17:00 UTC
There will be an outage starting at 2010-02-10 17:00 UTC, which will last approximately X hours. Outages will be small but noticeble for small segments as systems are updated and rebooted. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2010-02-10 17:00 UTC' Affected Services: All systems will be rebooted, but services should only be impacted in small increments as we take down things in a loop. Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/1965 Reason for Outage: Monthly updates and security updates. Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage. Note that the Fedora Infrastructure team does not run bugzilla.redhat.com, though. -- Stephen J Smoogen. Ah, but a man's reach should exceed his grasp. Or what's a heaven for? -- Robert Browning ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
