we are now in the infrastructure freeze leading up to the Fedora 39
Final release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release Fedora 39 when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2023-10-18 (or later if
release slips). Frozen hosts should have no changes made to them without
a sign-off on the change from at least 2 sysadmin-main or rel-eng
members, along with (in most cases) a patch of the exact change to be
made to this list and/or a pull-request to the infra/ansible repo.
Attention: Extended Deadline for Updating Your Access Permissions - December 11, 2023
AWS has discontinued use of old IAM permissions for Billing, Cost Management, and Accounts consoles. If you do not take
action, you may lose access to these consoles. We are granting an extension until December 11, 2023 for you to update
your IAM policies.Update your policies
or contact your organization's access administrator.For assistance, please visit the blog
,or review the policy migration utilities- Bulk Policy Migrator
,old to granular action mapping guide
The Billing does not worry us. But Cost Management and Account consoles? Is this something we should handle. Or we have
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
Good day Fedora Infrastructure team,
I'm Blake Ridgway. My IRC alias is /Zormak/ and my Matrix alias is
/@blakeridgway:fedora.im. /I am reaching out to introduce myself to the
Fedora Infrastructure team and express my enthusiasm for collaboration.
I serve as a System Administrator in the Agribusiness sector, where my
role is diverse and vital for the organization's operational efficiency.
My responsibilities encompass the maintenance of our Windows Server,
Office 365 environment, Asterisk PBX system running on CentOS, and
Ubuntu Server infrastructure. Beyond my professional duties, I'm
actively engaged in crafting a custom application suite for a non-profit
organization based in Oklahoma.
I run Fedora on all of my hardware, which includes two servers, my
desktop, and a variety of laptops. This comprehensive setup enables me
to thoroughly test and verify the Operating System's compatibility
across diverse hardware configurations.
While I've been quietly observing and familiarizing myself with how the
team operates and communicates, I'm not approaching this with a blank
slate. I plan to explore the open issues and Easyfix tasks to identify
areas where I can make a valuable contribution before tackling more
I'm genuinely eager to contribute to the Fedora community. I am excited
to both help offer my assistance and learn from the experienced members
of the Fedora Infrastructure team.
I look forward to hearing from you all.
We tried to get everything working with the new flatpak building setup
before freeze, but at the last minute we ran into some issues between
bodhi and the metadata that flatpak builds store in koji. We got several
things sorted out yesterday before freeze, but there's still an issue
with the metadata we need to fix.
So, I'd like to tag that build into f38-infra and update it on all the
builders and reload kojid.