infrastructure October 2019

infrastructure@lists.fedoraproject.org

42 participants
59 discussions

FBR: F31 Final is GO, bodhi config changes
by Mohan Boddu 24 Oct '19

24 Oct '19

Hi, Now that F31 is GO, I would like the make the necessary changes to bodhi configs. "vars/all/Frozen.yaml" 1L, 15C written [mohanboddu@batcave01 ansible][PROD]$ git diff diff --git a/vars/all/00-FedoraCycleNumber.yaml b/vars/all/00-FedoraCycleNumber.yaml index 22476b0..4bd0d46 100644 --- a/vars/all/00-FedoraCycleNumber.yaml +++ b/vars/all/00-FedoraCycleNumber.yaml @@ -1 +1 @@ -FedoraCycleNumber: 30 +FedoraCycleNumber: 31 diff --git a/vars/all/FedoraBranched.yaml b/vars/all/FedoraBranched.yaml index 42ac534..0bbcc1d 100644 --- a/vars/all/FedoraBranched.yaml +++ b/vars/all/FedoraBranched.yaml @@ -1 +1 @@ -FedoraBranched: True +FedoraBranched: False diff --git a/vars/all/FedoraBranchedBodhi.yaml b/vars/all/FedoraBranchedBodhi.yaml index 380f61d..76ba14d 100644 --- a/vars/all/FedoraBranchedBodhi.yaml +++ b/vars/all/FedoraBranchedBodhi.yaml @@ -1,2 +1,2 @@ #options are: prebeta, postbeta, current -FedoraBranchedBodhi: postbeta +FedoraBranchedBodhi: current diff --git a/vars/all/FedoraPreviousPrevious.yaml b/vars/all/FedoraPreviousPrevious.yaml index a8e3d3b..a061e04 100644 --- a/vars/all/FedoraPreviousPrevious.yaml +++ b/vars/all/FedoraPreviousPrevious.yaml @@ -1 +1 @@ -FedoraPreviousPrevious: False +FedoraPreviousPrevious: True diff --git a/vars/all/Frozen.yaml b/vars/all/Frozen.yaml index 97d3bc3..7578a88 100644 --- a/vars/all/Frozen.yaml +++ b/vars/all/Frozen.yaml @@ -1 +1 @@ -Frozen: True +Frozen: False diff --git a/vars/all/RelEngFrozen.yaml b/vars/all/RelEngFrozen.yaml index bd7553f..72af779 100644 --- a/vars/all/RelEngFrozen.yaml +++ b/vars/all/RelEngFrozen.yaml @@ -1 +1 @@ -RelEngFrozen: True +RelEngFrozen: False Thanks.

4 7

Working on adding ansible-report to our ansible repo
by Clement Verna 24 Oct '19

24 Oct '19

Hi all, Tomorrow I am planning to work on the following ticket ( https://pagure.io/fedora-infrastructure/issue/8157 ). If there are people interested to work on this with me or just to tag along I will be starting to work on that in #fedora-admin at 12:00 UTC. Thanks Clément

1 0

My self introduction
by Álvaro Castillo 24 Oct '19

24 Oct '19

Good morning, My name is Alvaro Castillo, I'm 25 years old. I'm from Canary Islands, but currently, I'm m living in Mallorca (Spain). I have a blog https://echemosunbitstazo.es where I write howtos, articles and more about operative systems world and web development like PHP, Python, JS... or system shell scripts likes as Bash or Python. I've worked with Ansible, IDM (Red Hat Identity Management), KVM, VMware Virtual Center, Nagios, Red Hat Enterprise Linux, Commvault and much more. Actually, I work in RIU Hotels & Resorts as system administrator. I hope collaborate with this fantastic community. My username is sincorchetes. Cheers!

2 1

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 23 Oct '19

23 Oct '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-10-24 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before. Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

Re: communishift reinstall
by Kevin Fenzi 22 Oct '19

22 Oct '19

On Sat, Oct 19, 2019 at 07:38:04PM -0400, Neal Gompa wrote: > On Sat, Oct 19, 2019 at 7:37 PM Kevin Fenzi <kevin(a)scrye.com> wrote: > > > > Greetings communishift group (and infrastructure list). > > > > I was working on the communishift cluster trying to fix it's failing to > > upgrade as well as some cert issues, and managed to munge up the cluster > > but good. ;( It's a tribute to the resillance of OpenShift that it's up > > and serving applications still. :) > > > > In any event, I think the easiest way to clean things up and get back to > > normal is for us to just reinstall it. With that in mind, I am planning > > to do so starting at 21UTC on 2019-10-21 (monday). > > > > If everyone could oc export any config or data they wish to save before > > then that would be great. > > > > Sorry for the trouble, but hopefully we will be back on track after > > that. > > > > Out of curiosity, is there some documentation somewhere of how this > process is being handled? Which process? The re-install? Basically just: https://docs.openshift.com/container-platform/4.2/installing/installing_bar… Then after the install we run a few things (setup our idp, storage, certs and users). kevin

2 5

Big Freeze Break Request: replicate db-koji01
by Kevin Fenzi 22 Oct '19

22 Oct '19

Greetings folks. As you may know, currently database backups on db-koji01 are causing very heavy load, disrupting our users builds ( https://pagure.io/fedora-infrastructure/issue/8292 ) so, they are currently disabled. However, not having current backups is not a good thing, IMHO. So, I am considering the idea of adding a db-koji02 vm (also rhel7 using the same postgres version that db-koji01 is) and enabling streaming replication from db-koji01 -> db-koji02 and then once thats working, run the database backups on db-koji02. It turns out this doesn't require that many changes on db-koji01: * adding a replication user * Setting 3 new lines of postgresql config and restarting: wal_level = 'hot_standby' max_wal_senders = 10 wal_keep_segments = 100 (May need to adjust senders and keep segments) All the other changes are on db-koji02: * create/setup the vm * run pg_basebackup to pull all the current data from 01 * setup postgresql.conf and recovery.conf files * start server and confirm it keeps up with 01 * run pg_dump and confirm it keeps up with 01 This is, of course a really big change in a freeze to a criticial service, so I'd like to get thoughts from others about it. Should we wait until after freeze and do without backups until then (note, that we have never had to restore this db from backups in the past, although we have dumped/restored it to move to newer postgres versions)? Is there something else we can do thats easier to mitigate the issues right now? Thoughts? ideas? Rotten fruit? kevin

6 10

FBR: Update pungi on compose-x8-01.phx2.fp.o
by Mohan Boddu 22 Oct '19

22 Oct '19

Hi, The current RC compose is failing due to a bug in pungi which got fixed recently. I would like to update pungi on compose-x86-01-.phx2.fp.o to fix this issue. Issue: https://pagure.io/releng/failed-composes/issue/328 Fix: https://pagure.io/pungi/pull-request/1281# Pungi Build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1401917 Note: its already available in infra repos and tested on rawhide. +1's please. Thanks.

3 3

[FBR] bastion: Add sysadmin-odcs to fas_client_groups
by Mikolaj Izdebski 22 Oct '19

22 Oct '19

--- inventory/group_vars/bastion | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/inventory/group_vars/bastion b/inventory/group_vars/bastion index aeacc87e4..8e63d1a11 100644 --- a/inventory/group_vars/bastion +++ b/inventory/group_vars/bastion @@ -23,7 +23,7 @@ custom_rules: [ # TODO - remove modularity-wg membership here once it is not longer needed: # https://fedorahosted.org/fedora-infrastructure/ticket/5363 -fas_client_groups: sysadmin-ask,sysadmin-atomic,sysadmin-web,sysadmin-main,sysadmin-cvs,sysadmin-noc,sysadmin-releng,sysadmin-dba,sysadmin-hosted,sysadmin-tools,sysadmin-spin,sysadmin-cloud,fi-apprentice,sysadmin-badges,sysadmin-troubleshoot,sysadmin-qa,sysadmin-centos,sysadmin-ppc,sysadmin-koschei,sysadmin-secondary,sysadmin-fedimg,sysadmin-veteran,sysadmin-mbs,modularity-wg,pungi-devel,sysadmin-upstreamfirst,sysadmin-releasemonitoring,sysadmin-gnome,sysadmin-copr,sysadmin-coreos,sysadmin-dbgserver,sysadmin-osbs +fas_client_groups: sysadmin-ask,sysadmin-atomic,sysadmin-web,sysadmin-main,sysadmin-cvs,sysadmin-noc,sysadmin-releng,sysadmin-dba,sysadmin-hosted,sysadmin-tools,sysadmin-spin,sysadmin-cloud,fi-apprentice,sysadmin-badges,sysadmin-troubleshoot,sysadmin-qa,sysadmin-centos,sysadmin-ppc,sysadmin-koschei,sysadmin-secondary,sysadmin-fedimg,sysadmin-veteran,sysadmin-mbs,modularity-wg,pungi-devel,sysadmin-upstreamfirst,sysadmin-releasemonitoring,sysadmin-gnome,sysadmin-copr,sysadmin-coreos,sysadmin-dbgserver,sysadmin-osbs,sysadmin-odcs # # This is a postfix gateway. This will pick up gateway postfix config in base -- 2.21.0

4 3

[FBR 0/1] Enable new mirrorlist server on proxy14
by Adrian Reber 22 Oct '19

22 Oct '19

This is a freeze break request to enable the new mirrorlist server on proxy14 as discussed on the mailing list. I hope my conditionals are correct for the Ansible and Jinja2 files. If this freeze break request gets accepted someone needs to run the playbook against proxy14. Before running the playbook, proxy14 should be removed from DNS to make sure, that the old mirrorlist containers are correctly stopped and deleted and that the new mirrorlist containers are correctly running. Adrian Reber (1): Enable new mirrorlist server on proxy14 roles/mirrormanager/backend/files/backend.cron | 8 +++++--- .../backend/templates/sync_pkl_to_mirrorlists.sh | 2 +- roles/mirrormanager/mirrorlist_proxy/tasks/main.yml | 2 +- .../mirrorlist_proxy/templates/mirrorlist.service.j2 | 4 ++-- 4 files changed, 9 insertions(+), 7 deletions(-) -- 2.23.0

4 12

Freeze break request: backport Flatpak installation fixes
by Owen Taylor 22 Oct '19

22 Oct '19

One of the main goals for Fedora 31 Silverblue was to have core applications that were removed a few releases ao from the Silverblue fixed image because they could be installed as Flatpaks actually pre-installed when you install Silverblue. The anaconda feature landed this cycle, and we have all the applications available as Fedora-infrastructure built Flatpaks, so the last missing piece was getting the ostree-installer config updated appropriately We tried to squeeze this in before the final freeze, but there were some bugs in the configuration and templates that didn't quite work - those are all fixed and tested in rawhide, and we'd like to backport to F31. There are three things that we need: * Backport fixes to the lorax template: https://pagure.io/fedora-lorax-templates/pull-request/44 * Backport fixes to the Pungi config: https://pagure.io/pungi-fedora/pull-request/783 * Update Pungi on the F31 compose VM to a version that includes the patch from https://pagure.io/pungi/pull-request/1278 - this was already done on the VM that runs rawhide composes. Note that Silverblue is *not* a release-blocking deliverable for Fedora 31. I think the risk to the overall compose is pretty small, given that everything here is a direct backport from Rawhide, and caused no problems there. Owen

4 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure October 2019