#12928 Planned Outage - pagure.io migration - 2025-12-03 21:00 UTC
Closed: Fixed by kevin. Opened by kevin.

Planned Outage - pagure.io migration - 2025-12-03 21:00 UTC

There will be an outage starting at 2025-12-03 21:00UTC,
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 '2025-12-03 21UTC'

Reason for outage:

We will be migrating pagure.io to a new network in our rdu3 datacenter. All services on pagure.io will be taken down, all data synced, and then services will be restored on the new server/datacenter.
IP addresses for pagure.io, docs.pagure.org will be updated. We will try and keep the outage as short as possible.

Affected Services:

pagure.io
docs.pagure.org

Ticket Link:

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

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/


Once this is reviewed, we need to send it to infrastructure and devel-announce and update status with the planned outage.

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

It's Thanksgiving, so I can send this out today

Announcements sent, https://github.com/fedora-infra/statusfpo/pull/76 for status.

Issue tagged with: sprint-0

The outage is now over.

It didn't go smoothly sadly. ;(

The data sync was fine, but then testing ssh pushes failed to work... finally I tracked that down to the pagure key checker checking pagure.io, which was not yet moved in dns. ;(
Once that was fixed, fedora-messaging wasn't working. The new pagure01 didn't have network acls to connect to rabbitmq either on the external or internal networks.
I got networking to add an allow around this and then that started working.

I'm going to keep this open for a few in case there's any last minute blowups, but hopefully we are done.

ok. Please report any issues you find in the normal process. :)

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

We cannot upload release tarballs for FreeIPA project. An upload goes on for a while but then the only thing we get is 'Upload failed" message with no additional infomartion.

image3.png

Also, mirroring hook is broken. FreeIPA git repo did not mirror to github

@kevin any chance to fix up the issues above? We need to do FreeIPA release today...

Yeah, I can... but was asleep. ;)

  1. Try the release upload again? it was a selinux issue.

  2. For mirroring, pagure does a ssh push, but ssh isn't allowed in the new network. I have requested it from networking folks. Hopefully fixed soon.

Thanks, both issues are addressed now.

Metadata Update from @zlopez:
- Issue untagged with: sprint-0

Metadata