On 8/27/19 2:21 PM, Kevin Fenzi wrote:
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 31
Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 31 Beta 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:
git clone
https://infrastructure.fedoraproject.org/infra/ansible.git
ansible/scripts/freezelist -i inventory
I had a problem with this because I didn't have python2 libraries
for ansible installed so the `import ansible.inventory` failed.
Switching the script to python3 worked. Should we apply this?
$ git diff
diff --git a/scripts/freezelist b/scripts/freezelist
index 89856ea09..b1c99054c 100755
--- a/scripts/freezelist
+++ b/scripts/freezelist
@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/python3
# skvidal
# doteast: porting to ansible 2.0
# dump out the hosts marked with 'freezes: true' in their vars
Any hosts listed as freezes is frozen until 2019-09-17 (or later if
release slips or uses the secondary target). 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.
I see the openshift nodes listed as frozen. What about applications that
are running in openshift? Can I commit changes to my apps that are for
CoreOS without a review?