FBR for 0-day release actions - infrastructure - Fedora mailing-lists

10 Nov 2017

As per 0-day Release Actions under https://infrastructure.fedoraproject.org/infra/docs/docs/sysadmin-guide/sops... SOP, I made the following changes:

diff --git a/roles/bodhi2/backend/templates/atomic-config.py.j2 b/roles/bodhi2/backend/templates/atomic-config.py.j2
index d75269c..c355e96 100644
--- a/roles/bodhi2/backend/templates/atomic-config.py.j2
+++ b/roles/bodhi2/backend/templates/atomic-config.py.j2
@@ -6,6 +6,60 @@ rhel6 = dist[0] == 'redhat' and int(float(dist[1])) == 6
config = dict(
     releases={
+        'f27-updates': {
+            'name': 'f27-updates',
+            'repo': 'updates',
+            'version': '27',
+            'arch': 'x86_64',
+
+            # OSTree treefile configuration
+            # https://github.com/projectatomic/rpm-ostree/blob/master/doc/treefile.md
+            'tree': 'docker-host',
+            'treefile': {
+                'include': 'fedora-atomic-host.json',
+                'ref': 'fedora/27/x86_64/updates/atomic-host',
+                'repos': ['fedora-27', 'fedora-27-updates', 'updates'],
+                'packages': [],
+            },
+
+            # The name of the mock container to build and maintain
+            'mock': 'fedora-27-updates-x86_64',
+
+            # The git branch to use in the `git_repo` for the parent
+            # treefile & repo configurations
+            'git_branch': 'f27',
+
+            # Add or overwrite yum repository name:urls. This lets you
+            # compose trees against your own repositories.
+            'repos': {},
+        },
+        'f27-updates-testing': {
+            'name': 'f27-updates-testing',
+            'repo': 'updates-testing',
+            'version': '27',
+            'arch': 'x86_64',
+
+            # OSTree treefile configuration
+            # https://github.com/projectatomic/rpm-ostree/blob/master/doc/treefile.md
+            'tree': 'docker-host',
+            'treefile': {
+                'include': 'fedora-atomic-host.json',
+                'ref': 'fedora/27/x86_64/testing/atomic-host',
+                'repos': ['fedora-27', 'fedora-27-updates', 'updates-testing'],
+                'packages': [],
+            },
+
+            # The name of the mock container to build and maintain
+            'mock': 'fedora-27-updates-testing-x86_64',
+
+            # The git branch to use in the `git_repo` for the parent
+            # treefile & repo configurations
+            'git_branch': 'f27',
+
+            # Add or overwrite yum repository name:urls. This lets you
+            # compose trees against your own repositories.
+            'repos': {},
+        },
         'f26-updates': {
             'name': 'f26-updates',
             'repo': 'updates',
diff --git a/roles/bodhi2/base/templates/production.ini.j2 b/roles/bodhi2/base/templates/production.ini.j2
index 1629e2d..5b22659 100644
--- a/roles/bodhi2/base/templates/production.ini.j2
+++ b/roles/bodhi2/base/templates/production.ini.j2
@@ -10,7 +10,7 @@ filter-with = proxy-prefix
 # Release status
 # pre-beta enforces the 'Pre Beta' policy defined here:
 # https://fedoraproject.org/wiki/Updates_Policy
-f27.status = pre_beta
+f27.status = post_beta
f27.post_beta.mandatory_days_in_testing = 7
 f27.post_beta.critpath.num_admin_approvals = 0
Once the patch is approved, I will commit the changes and push it to the ansible and some one should run the bodhi playbook as I dont have the permissions.
Once thats done I will run
bodhi-manage-releases edit --name F27 --state current --username mohanboddu
to change the F27 state from pending to current.

    