infra/tickets

Fork 2

Planned Outage - Updates/Reboots - 2026-10-01 20:00 UTC #13563

New issue

Closed

opened 2026-09-16 17:29:51 +00:00 by james · 3 comments

james commented

2026-09-16 17:29:51 +00:00

Member

planned outage

Planned Outage - Updates/Reboots - 2026-10-01 20:00 UTC

There will be an outage starting at 2026-10-01 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 '2026-10-01 20:00 UTC'

Reason for outage:

We will be applying all updates to servers and rebooting them.

Affected Services:

Many services will be affected, most should only be down for a short time as their particular resources are rebooted HOWEVER some may be down for a non-trivial amount of time due to firmware upgrades.

Ticket Link:

https://forge.fedoraproject.org/infra/tickets/issue/13563

Please join #admin:fedoraproject.org / #noc:fedoraproject.org on matrix.
or add comments to this ticket for more information or feedback.

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

### planned outage Planned Outage - Updates/Reboots - 2026-10-01 20:00 UTC There will be an outage starting at 2026-10-01 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 '2026-10-01 20:00 UTC' Reason for outage: We will be applying all updates to servers and rebooting them. Affected Services: Many services will be affected, most should only be down for a short time as their particular resources are rebooted HOWEVER some may be down for a non-trivial amount of time due to firmware upgrades. Ticket Link: https://forge.fedoraproject.org/infra/tickets/issue/13563 Please join #admin:fedoraproject.org / #noc:fedoraproject.org on matrix. or add comments to this ticket for more information or feedback. Updated status for this outage may be available at https://www.fedorastatus.org/

james added the

outage

label

2026-09-16 17:29:51 +00:00

james self-assigned this

2026-09-16 17:30:07 +00:00

james added the

points

Priority

Medium

labels

2026-09-16 17:30:22 +00:00

kevin commented

2026-09-16 17:53:41 +00:00

Owner

I'd like to do:

firmware upgrades
make sure everything that can enable secureboot is. ie, all the x86 bare metal machines. Unfortunately, that means going into the bios on the mgmt console and enabling it and another reboot cycle, so anoying, but would be good to do. We can get a list of affected hosts with a 'mokutil --sb-state'
database migrations. At least db01, db03, db-fas01, db-openqa01, db-koji01, db-riscv-koji01. I also hope to do db-datanommer02, but it's still under investigation how best to do it.

I'd like to do: 1) firmware upgrades 2) make sure everything that can enable secureboot is. ie, all the x86 bare metal machines. Unfortunately, that means going into the bios on the mgmt console and enabling it and another reboot cycle, so anoying, but would be good to do. We can get a list of affected hosts with a 'mokutil --sb-state' 3) database migrations. At least db01, db03, db-fas01, db-openqa01, db-koji01, db-riscv-koji01. I also hope to do db-datanommer02, but it's still under investigation how best to do it.

james added this to the Sprint ( 2026-09-20 to 2026-10-04 ) project

2026-09-21 13:40:54 +00:00

smoliicek changed title from ~~Planned Outage - Updates/Reboots - 2026-10-01 21:00 UTC~~ to Planned Outage - Updates/Reboots - 2026-10-01 20:00 UTC

2026-09-21 19:12:34 +00:00

james commented

2026-09-28 17:41:51 +00:00

Author

Member

We can pretend this was on time ;)

https://hackmd.io/ZMYWDFrhSG20TTkoOFDdew

We can pretend this was on time ;) https://hackmd.io/ZMYWDFrhSG20TTkoOFDdew

james commented

2026-10-02 00:22:30 +00:00

Author

Member