#7699 Planned Outage - Fedora Staging/Proxies Updates/Reboots 2019-04-09 21:00 UTC
Closed: Fixed 2 years ago by kevin. Opened 2 years ago by smooge.

Planned Outage - Fedora Staging/Proxies Updates/Reboots - 2019-04-09 21:00 UTC

There will be an outage starting at 2019-04-09 21:00 UTC,
which will last approximately 4 hours.

To convert UTC to your local time, take a look at
or run:

date -d '2019-04-09 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:

coloamer01.fedoraproject.org proxy08.fedoraproject.org
dedicatedsolutions01.fedoraproject.org proxy11.fedoraproject.org
internetx01.fedoraproject.org ns05.fedoraproject.org
internetx01.fedoraproject.org proxy02.fedoraproject.org
osuosl02.fedoraproject.org keys01.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
virthost-cc-rdu01.fedoraproject.org ci-cc-rdu01.fedoraproject.org
virthost-cc-rdu01.fedoraproject.org proxy14.fedoraproject.org
virthost-cc-rdu01.fedoraproject.org smtp-mm-cc-rdu01.fedoraproject.org
virthost-rdu01.fedoraproject.org bastion13.fedoraproject.org
virthost-rdu01.fedoraproject.org batcave13.rdu2.fedoraproject.org
virthost-rdu01.fedoraproject.org ns13.rdu2.fedoraproject.org
virthost-rdu01.fedoraproject.org proxy13.fedoraproject.org

Ticket Link:


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

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

2 years ago

This outage is over.


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

2 years ago

Login to comment on this ticket.