fedora-infrastructure

#12293 Planned Outage - Server update/reboots - 2024-11-20 21:00 UTC
Closed: Fixed with Explanation by kevin. Opened by kevin.

Closed: Fixed with Explanation
Reopen Issue

Planned Outage - Server update/reboots - 2024-11-20 21:00 UTC

There will be an outage starting at 2024-11-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 '2024-11-20 21:00 UTC'

Reason for outage:

We will be updating and rebooting servers to pick up the recent RHEL 9.5 release as well as to move a number of instances to Fedora 41 (including hopefully builders/koji hubs)

Affected Services:

Most maintainer / contributor services will be affected for some short windows during the outage.
Package maintainers are advised to wait for the outage to be over to launch any builds.

Ticket Link:

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

Please join #admin:fedoraproject.org / #noc:fedoraproject.org on matrix.
Please add comments to the ticket for this outage above.

Updated status for this outage may be available at
https://www.fedorastatus.org/

Next steps here:

[ ] someone needs to review this and make sure it makes sense and I didn't typo anything.
[ ] send to announce, devel-announce, infra lists
[ ] add to fedorastatus.org
[ ] setup hackmd doc to track progress

+1 I don't see any typo :-)

[ ] send to announce, devel-announce, infra lists

could you please explain the second step? I don't get it
@kevin @zlopez

Edited by thisisyaash

@thisisyaash Send the announcement to relevant mailing lists.

Here is the list:

  • devel-announce@lists.fedoraproject.org
  • announce@lists.fedoraproject.org
  • infrastructure@lists.fedoraproject.org
Edited by zlopez

About the third point: [ ] add to fedorastatus.org
Here is the relevant repo on github with a guide how to make a status update: https://github.com/fedora-infra/statusfpo?tab=readme-ov-file
Edited by lenkaseg

okay, just to make sure I get that right,

  1. send the mailing lists (to the lists mentioned above)
  2. create planned outage and make PR
  3. create a new hackMD note to track progress of the outage

@thisisyaash That's correct.

I'm not familiar with the mailings lists, so let me ask you few doubts :)

  1. can I send the announcement to those mailing lists using my email (@gmail.com)
  2. Is there a template for outage announcement (if yes, please send me)

I can send the email... I have it all ready. ;)

A PR for the status update would be great!

The guide above should have info on that, or you can look in the old commits to see what it looks like.

I have raised the PR a in statusfpo repository for the status update. Please look into it let me know if I did it the right way?

also, please give me an overview of sending mails to the mailing lists,
- how it works
- how I can send mails
- do I need perms to send?

The PR looks mostly good, but needs the title updated... it says 'pagure.io outage' currently.

I already sent the emails, but:
* You have to be subscribed to the announce, devel-announce and infrastructure lists (because they will just reject emails from non subscribers)
* You just need to compose an email to those lists with the content from the orig part of the ticket
* You will need someone who is a moderator on those lists to ack the posts... if they don't know you, they may not do so.

I have created a hackmd document to track updates:

https://hackmd.io/2rlMcm4ZSwaL8WjwnydrEA

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: outage

ok, This outage is over. Thanks everyone!

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)
Metadata

medium-gain medium-trouble outage

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.