From e70bfc2c68f108e2ff5e506015c5015f2df3772b Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Mon, 27 Jun 2022 16:05:37 -0400 Subject: [PATCH] sysadmin_guide: add SOP for deploying new coreos-cincinnati version This adds the step needed after building the new image to actually roll it out. --- .../sysadmin_guide/pages/coreos-cincinnati.adoc | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/modules/sysadmin_guide/pages/coreos-cincinnati.adoc b/modules/sysadmin_guide/pages/coreos-cincinnati.adoc index ca3289e..e7e562f 100644 --- a/modules/sysadmin_guide/pages/coreos-cincinnati.adoc +++ b/modules/sysadmin_guide/pages/coreos-cincinnati.adoc @@ -66,6 +66,20 @@ a new container image: * schedule a new build by running `sudo rbac-playbook -t build openshift-apps/coreos-cincinnati.yml` +=== Deploying a new version + +Once the target commit has been built into a container image, these are +the steps to deploy the new image: + + * update the `fcos_cincinnati_deploy_git_sha` playbook variable in + `roles/openshift-apps/coreos-cincinnati/vars/staging.yml` + * update the `fcos_cincinnati_deploy_git_sha` playbook variable in + `roles/openshift-apps/coreos-cincinnati/vars/production.yml` + * commit and push the update to the `fedora-infra/ansible` repository + * SSH to `batcave01.iad2.fedoraproject.org` + * run `sudo rbac-playbook openshift-apps/coreos-cincinnati.yml` using + your FAS password and your second-factor OTP + == Things that could go wrong === Application build is stuck