Re: crowdsourcing an interview on git
On 03/31/2015 10:48 PM, Matthew Miller wrote: * What is your favorite pro tip for using git? Sometimes git pull takes long time. Sometimes git start garbage collecting in situation, where I was under time pressure. After this line in crontab I have no such problems any more: 40 3 * * * locate --regex /\\\.git\$ | while read a; do ( cd $a; git fetch --all -t; git gc --aggressive; ) done /dev/null 2/dev/null And this in .gitconfig: [alias] lol = log --graph --decorate --pretty=oneline --abbrev-commit Is great to quickly get overview of history (credits goes to jesusr). -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Freeze Break Request: add db for execdb-stg to db-qa01.qa
We had intended to do this before freeze but managed to miss it. One of the upcoming features for taskotron that we've deployed to dev and want to deploy to staging is execdb - task execution tracking for Taskotron. This requires adding a database to db-qa01.qa which is the db host for the production Taskotron instance but no other changes to production or frozen systems. The only change in the frozen bits of ansible is: +++ b/inventory/host_vars/db-qa01.qa.fedoraproject.org @@ -22,6 +22,7 @@ dbs_to_backup: - fakefedorainfra - fakefedorainfra_stg - dev_fakefedorainfra +- execdb_stg - execdb_dev - resultsdb - resultsdb_stg pgppyyfggns12.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Freeze break: sudoers on koji01/02
I'd like to allow sysadmin-releng (which already has shell access) sudo also on the koji hubs. This will allow us to have mikem able to debug our kojiria issues. +1s? kevin pgpf0b_Snpsw9.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break: sudoers on koji01/02
On Wednesday, April 01, 2015 09:24:28 AM Kevin Fenzi wrote: I'd like to allow sysadmin-releng (which already has shell access) sudo also on the koji hubs. This will allow us to have mikem able to debug our kojiria issues. +1s? kevin +1 Dennis ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze Break Request: add db for execdb-stg to db-qa01.qa
On Wed, 1 Apr 2015 09:37:50 -0600 Tim Flink tfl...@redhat.com wrote: On Wed, 1 Apr 2015 17:16:27 +0200 Pierre-Yves Chibon pin...@pingoured.fr wrote: On Wed, Apr 01, 2015 at 08:47:43AM -0600, Tim Flink wrote: We had intended to do this before freeze but managed to miss it. One of the upcoming features for taskotron that we've deployed to dev and want to deploy to staging is execdb - task execution tracking for Taskotron. This requires adding a database to db-qa01.qa which is the db host for the production Taskotron instance but no other changes to production or frozen systems. So you want a stg application to run against a db located on a production environment? That's how it's been setup since we first deployed Taskotron - all the dev, stg and prod dbs are on the same host. Right. We can split them out later, but I didn't want 3 more instances running so super tiny db's would be seperate. Wouldn't it be more logical to have a db-qa01.qa.stg or so? I can see the argument for doing that but I'm not sure that separating them out would provide enough benefit to justify the overhead of (an) additional database host(s) since the Taskotron bits don't really hit the db very hard. I'm not against the idea of having separate db servers for prod and dev/stg but I'd rather not muck around with that during freeze. Right. I didn't think these very small databases justified new sperate hosts. I'm +1 to the request for now. kevin pgphyDQ50Z_Ac.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Freeze break: run some playbooks
I'd like to run a few playbooks to roll up changes made just before
freeze. These should only change the indicated stuff thats already in
git below. If it causes any issues, we should find out now, instead of
later in the freeze, and also will clean up the check/diff report and
make sure we are running exactly whats in git.
1. proxies
I made a fix to fix mirrorlist.stg before freeze. This change also
needs to be made in production configs, but actually doesn't do
anything there:
07.10.44proxy01.phx2.fedoraproject.org Apr 01 2015 07:18:4223
CHECK_DIFF:CHANGED Copy over primary template for {{name}} task_userid:root
07.10.44proxy02.fedoraproject.org Apr 01 2015 07:18:4523
CHECK_DIFF:CHANGED Copy over primary template for {{name}} task_userid:root
07.10.44proxy03.fedoraproject.org Apr 01 2015 07:18:4323
CHECK_DIFF:CHANGED Copy over primary template for {{name}} task_userid:root
07.10.44proxy04.fedoraproject.org Apr 01 2015 07:18:4323
CHECK_DIFF:CHANGED Copy over primary template for {{name}} task_userid:root
07.10.44proxy05.fedoraproject.org Apr 01 2015 07:18:4523
CHECK_DIFF:CHANGED Copy over primary template for {{name}} task_userid:root
07.10.44proxy06.fedoraproject.org Apr 01 2015 07:18:4323
CHECK_DIFF:CHANGED Copy over primary template for {{name}} task_userid:root
07.10.44proxy07.fedoraproject.org Apr 01 2015 07:18:4623
CHECK_DIFF:CHANGED Copy over primary template for {{name}} task_userid:root
07.10.44proxy08.fedoraproject.org Apr 01 2015 07:18:4223
CHECK_DIFF:CHANGED Copy over primary template for {{name}} task_userid:root
07.10.44proxy09.fedoraproject.org Apr 01 2015 07:18:4323
CHECK_DIFF:CHANGED Copy over primary template for {{name}} task_userid:root
07.10.44proxy10.phx2.fedoraproject.org Apr 01 2015 07:18:4323
CHECK_DIFF:CHANGED Copy over primary template for {{name}} task_userid:root
07.10.44proxy11.fedoraproject.org Apr 01 2015 07:18:4323
CHECK_DIFF:CHANGED Copy over primary template for {{name}} task_userid:root
2. master playbook with -t fedmsgmonitor
This should fix some permissions on fedmsg sockets so nrpe can montor:
value
05.21.08value01.phx2.fedoraproject.org Apr 01 2015 05:23:0097
CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
05.21.08value01.stg.phx2.fedoraproject.org Apr 01 2015 05:23:00
97 CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
summershum
05.37.56summershum01.phx2.fedoraproject.org Apr 01 2015 05:39:41
6 CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
05.37.56summershum01.stg.phx2.fedoraproject.org Apr 01
2015 05:39:40 6 CHECK_DIFF:CHANGED ensure that
nrpe has rights to monitor us task_userid:root
notifs-backend
05.39.48notifs-backend01.phx2.fedoraproject.org Apr 01 2015 05:41:26
6 CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
05.39.48notifs-backend01.stg.phx2.fedoraproject.org Apr
01 2015 05:41:266 CHECK_DIFF:CHANGED ensure that
nrpe has rights to monitor us task_userid:root
hotness
06.04.30hotness01.phx2.fedoraproject.orgApr 01 2015 06:06:28
6 CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
06.04.30hotness01.stg.phx2.fedoraproject.orgApr 01 2015 06:06:28
6 CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
fedimg
06.11.07fedimg01.phx2.fedoraproject.org Apr 01 2015 06:13:026
CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
06.11.07fedimg01.stg.phx2.fedoraproject.org Apr 01 2015
06:13:026 CHECK_DIFF:CHANGED ensure that nrpe has
rights to monitor ustask_userid:root
busgateway
06.26.45busgateway01.phx2.fedoraproject.org Apr 01 2015 06:28:51
6 CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
06.26.45busgateway01.phx2.fedoraproject.org Apr 01 2015 06:28:56
11 CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
06.26.45busgateway01.phx2.fedoraproject.org Apr 01 2015 06:28:58
14 CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
06.26.45busgateway01.stg.phx2.fedoraproject.org Apr 01 2015 06:28:51
6 CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
06.26.45busgateway01.stg.phx2.fedoraproject.org Apr 01
Re: Freeze Break Request: add db for execdb-stg to db-qa01.qa
On Wed, Apr 01, 2015 at 08:47:43AM -0600, Tim Flink wrote: We had intended to do this before freeze but managed to miss it. One of the upcoming features for taskotron that we've deployed to dev and want to deploy to staging is execdb - task execution tracking for Taskotron. This requires adding a database to db-qa01.qa which is the db host for the production Taskotron instance but no other changes to production or frozen systems. So you want a stg application to run against a db located on a production environment? Wouldn't it be more logical to have a db-qa01.qa.stg or so? The only change in the frozen bits of ansible is: +++ b/inventory/host_vars/db-qa01.qa.fedoraproject.org @@ -22,6 +22,7 @@ dbs_to_backup: - fakefedorainfra - fakefedorainfra_stg - dev_fakefedorainfra +- execdb_stg - execdb_dev - resultsdb - resultsdb_stg +1 on the change per say, but see my comment above :) Pierre pgpAUqLX96pYt.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break: sudoers on koji01/02
On Wed, 1 Apr 2015 09:24:28 -0600 Kevin Fenzi ke...@scrye.com wrote: I'd like to allow sysadmin-releng (which already has shell access) sudo also on the koji hubs. This will allow us to have mikem able to debug our kojiria issues. +1s? +1 from me as well pgpv_fl_UDOOL.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze Break Request: add db for execdb-stg to db-qa01.qa
On Wed, 1 Apr 2015 17:16:27 +0200 Pierre-Yves Chibon pin...@pingoured.fr wrote: On Wed, Apr 01, 2015 at 08:47:43AM -0600, Tim Flink wrote: We had intended to do this before freeze but managed to miss it. One of the upcoming features for taskotron that we've deployed to dev and want to deploy to staging is execdb - task execution tracking for Taskotron. This requires adding a database to db-qa01.qa which is the db host for the production Taskotron instance but no other changes to production or frozen systems. So you want a stg application to run against a db located on a production environment? That's how it's been setup since we first deployed Taskotron - all the dev, stg and prod dbs are on the same host. Wouldn't it be more logical to have a db-qa01.qa.stg or so? I can see the argument for doing that but I'm not sure that separating them out would provide enough benefit to justify the overhead of (an) additional database host(s) since the Taskotron bits don't really hit the db very hard. I'm not against the idea of having separate db servers for prod and dev/stg but I'd rather not muck around with that during freeze. Tim pgp405qMXFw0G.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Freeze break: fix log sync script on log01
log01 pulls httpd logs from proxys. When it was added, proxy11 wasn't right, this corrects it and saves us a cron email every night with the error: diff --git a/roles/base/files/syncHttpLogs.sh b/roles/base/files/syncHttpLogs.sh index 11a6d3a..ad25e01 100644 --- a/roles/base/files/syncHttpLogs.sh +++ b/roles/base/files/syncHttpLogs.sh @@ -38,7 +38,7 @@ syncHttpLogs proxy07.vpn.fedoraproject.org syncHttpLogs proxy08.vpn.fedoraproject.org syncHttpLogs proxy09.vpn.fedoraproject.org syncHttpLogs proxy10.phx2.fedoraproject.org -syncHttpLogs proxy11.phx2.fedoraproject.org +syncHttpLogs proxy11.vpn.fedoraproject.org syncHttpLogs proxy01.stg.phx2.fedoraproject.org syncHttpLogs app01.stg.phx2.fedoraproject.org syncHttpLogs bapp02.phx2.fedoraproject.org +1s? kevin pgp03xleJ3MmM.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Plan for tomorrow's Fedora Infrastructure meeting (2015-04-02)
The infrastructure team will be having it's weekly meeting tomorrow, 2015-04-02 at 18:00 UTC in #fedora-meeting on the freenode network. This week we are continuing to try something new. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. Please try and review and edit that document before the meeting and we will use it to have our agenda of things to discuss. A copy as of this morning is included in this email. kevin -- = Introduction = This shared document is for the next fedora infrastructure meeting. We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. = Meeting start stuff = #startmeeting Infrastructure (2015-04-02) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk #topic New folks introductions / Apprentice feedback = Status / information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info the thing - your name) #topic announcements and information #info askbot upgraded to 0.7.51 - patrick #info All machines updated before the freeze - kevin / smooge #info New release of the releng dash out with previously missing components and smarter pkgdb integration - ralph #link https://apps.fedoraproject.org/releng-dash #info New release of the-new-hotness out with more feedback on bugzilla tickets (patches, srpm failures) and two-way syncing between anitya and pkgdb - ralph #info new pkgdb2 release (mostly bug fixes) - pingou #info new fedocal release (with some very nice new features by rtnpro) - pingou #info new anitya release (with bug fixes and new features) - pingou #info Lots of misc freeze breaks fixing minor stuff for the most part - kevin = Things we should discuss = (Use #topic your discussion topic - your username) #topic = Learn about some application or setup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the info in this section) #topic Learn about koji - kevin = Meeting end stuff = #topic Open Floor #endmeeting pgpCEkwNPVj92.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: FYI retroactive freeze break: koji ssl connection timeout increase hotfix
Retroactive +1 On 1 April 2015 at 11:35, Kevin Fenzi ke...@scrye.com wrote: A few times in the last week we have hit a state where kojira on koji02 times out and doesn't run newrepo tasks for buildroots. Restarting the httpd on koji01 seems to unstick it, but this is not a good even stop gap as we would then have to manually do that and people would get small windows when koji was down. So, some investigation from koji developers at least for now the solution is to increase the ssl timeout. It's currently 60s, but I have increased it to 180 in a hotfix. http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=ebb160dceef8ede2ce97b3b940987b798380dfea and http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=f99e19b0244cd7ff8be570a6df6b78f494eceb57 This is already applied on koji02 to get us out of an outage situation (no new buildroots means no new fedora), but with +1s, I will apply to koji01 as well and make sure the playbooks sync with the hosts kevin ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure -- Stephen J Smoogen. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: FYI retroactive freeze break: koji ssl connection timeout increase hotfix
On Wed, 1 Apr 2015 11:35:32 -0600 Kevin Fenzi ke...@scrye.com wrote: A few times in the last week we have hit a state where kojira on koji02 times out and doesn't run newrepo tasks for buildroots. Restarting the httpd on koji01 seems to unstick it, but this is not a good even stop gap as we would then have to manually do that and people would get small windows when koji was down. So, some investigation from koji developers at least for now the solution is to increase the ssl timeout. It's currently 60s, but I have increased it to 180 in a hotfix. http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=ebb160dceef8ede2ce97b3b940987b798380dfea and http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=f99e19b0244cd7ff8be570a6df6b78f494eceb57 This is already applied on koji02 to get us out of an outage situation (no new buildroots means no new fedora), but with +1s, I will apply to koji01 as well and make sure the playbooks sync with the hosts Seems to be a relatively low risk change to me +1 pgphgn304oOYP.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: crowdsourcing an interview on git
On Tue, 31 Mar 2015 16:48:17 -0400 Matthew Miller mat...@fedoraproject.org wrote: Hi everyone! Linux Foundation is running a series on Git for its 10th anniversary. They asked me a few questions, and I thought it might be even better to get a community answer from the whole infrastructure team. So, if you have anything interesting to say to any of these, say it, and I'll wrap up the responses into a unified Fedora Whole. I need to respond by Friday. * Why does Fedora use Git? It's known by most all developer/free software types these days, it's distributed and it's got a lot of docs and folks that can help with issues. * What makes Git such a great tool? For simple things/workflows it's pretty simple. * How many developers do you have collaborating on git? I guess that depends on what the question means by you here. ;) We have had 45 people commit at one time or another to our ansible repo, and 163 to our old puppet repo. There's 1633 people in the fedora packager group and 19857 package repos. (But some of those are dead.packaged). * How much do you personally use it? (estimates are great) Many times a day. * What's Fedora's most active git repo right now and why? Thats hard to say, we don't have a central place for all of them... http://pkgs.fedoraproject.org/cgit/?s=idle I suspect kernel gets updates most days. The infrastructure ansible repo gets updates most days. * What is your favorite pro tip for using git? Always run 'git status' and 'git diff' before commiting/pushing. That can show you that you have unrelated other changes you might not want to push. kevin pgpsz1GDhROCX.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break: run some playbooks
+1 to this change.
On 1 April 2015 at 10:34, Kevin Fenzi ke...@scrye.com wrote:
I'd like to run a few playbooks to roll up changes made just before
freeze. These should only change the indicated stuff thats already in
git below. If it causes any issues, we should find out now, instead of
later in the freeze, and also will clean up the check/diff report and
make sure we are running exactly whats in git.
1. proxies
I made a fix to fix mirrorlist.stg before freeze. This change also
needs to be made in production configs, but actually doesn't do
anything there:
07.10.44proxy01.phx2.fedoraproject.org Apr 01 2015 07:18:42
23 CHECK_DIFF:CHANGED Copy over primary template for {{name}}
task_userid:root
07.10.44proxy02.fedoraproject.org Apr 01 2015 07:18:45
23 CHECK_DIFF:CHANGED Copy over primary template for {{name}}
task_userid:root
07.10.44proxy03.fedoraproject.org Apr 01 2015 07:18:43
23 CHECK_DIFF:CHANGED Copy over primary template for {{name}}
task_userid:root
07.10.44proxy04.fedoraproject.org Apr 01 2015 07:18:43
23 CHECK_DIFF:CHANGED Copy over primary template for {{name}}
task_userid:root
07.10.44proxy05.fedoraproject.org Apr 01 2015 07:18:45
23 CHECK_DIFF:CHANGED Copy over primary template for {{name}}
task_userid:root
07.10.44proxy06.fedoraproject.org Apr 01 2015 07:18:43
23 CHECK_DIFF:CHANGED Copy over primary template for {{name}}
task_userid:root
07.10.44proxy07.fedoraproject.org Apr 01 2015 07:18:46
23 CHECK_DIFF:CHANGED Copy over primary template for {{name}}
task_userid:root
07.10.44proxy08.fedoraproject.org Apr 01 2015 07:18:42
23 CHECK_DIFF:CHANGED Copy over primary template for {{name}}
task_userid:root
07.10.44proxy09.fedoraproject.org Apr 01 2015 07:18:43
23 CHECK_DIFF:CHANGED Copy over primary template for {{name}}
task_userid:root
07.10.44proxy10.phx2.fedoraproject.org Apr 01 2015 07:18:43
23 CHECK_DIFF:CHANGED Copy over primary template for {{name}}
task_userid:root
07.10.44proxy11.fedoraproject.org Apr 01 2015 07:18:43
23 CHECK_DIFF:CHANGED Copy over primary template for {{name}}
task_userid:root
2. master playbook with -t fedmsgmonitor
This should fix some permissions on fedmsg sockets so nrpe can montor:
value
05.21.08value01.phx2.fedoraproject.org Apr 01 2015 05:23:00
97 CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
05.21.08value01.stg.phx2.fedoraproject.org Apr 01 2015
05:23:0097 CHECK_DIFF:CHANGED ensure that nrpe has rights to
monitor us task_userid:root
summershum
05.37.56summershum01.phx2.fedoraproject.org Apr 01 2015
05:39:416 CHECK_DIFF:CHANGED ensure that nrpe has rights to
monitor us task_userid:root
05.37.56summershum01.stg.phx2.fedoraproject.org Apr 01
2015 05:39:40 6 CHECK_DIFF:CHANGED ensure that
nrpe has rights to monitor us task_userid:root
notifs-backend
05.39.48notifs-backend01.phx2.fedoraproject.org Apr 01 2015
05:41:266 CHECK_DIFF:CHANGED ensure that nrpe has rights to
monitor us task_userid:root
05.39.48notifs-backend01.stg.phx2.fedoraproject.org Apr
01 2015 05:41:266 CHECK_DIFF:CHANGED ensure that
nrpe has rights to monitor us task_userid:root
hotness
06.04.30hotness01.phx2.fedoraproject.orgApr 01 2015
06:06:286 CHECK_DIFF:CHANGED ensure that nrpe has rights to
monitor us task_userid:root
06.04.30hotness01.stg.phx2.fedoraproject.orgApr 01 2015
06:06:286 CHECK_DIFF:CHANGED ensure that nrpe has rights to
monitor us task_userid:root
fedimg
06.11.07fedimg01.phx2.fedoraproject.org Apr 01 2015 06:13:02
6 CHECK_DIFF:CHANGED ensure that nrpe has rights to monitor us
task_userid:root
06.11.07fedimg01.stg.phx2.fedoraproject.org Apr 01 2015
06:13:026 CHECK_DIFF:CHANGED ensure that nrpe has
rights to monitor ustask_userid:root
busgateway
06.26.45busgateway01.phx2.fedoraproject.org Apr 01 2015
06:28:516 CHECK_DIFF:CHANGED ensure that nrpe has rights to
monitor us task_userid:root
06.26.45busgateway01.phx2.fedoraproject.org Apr 01 2015
06:28:5611 CHECK_DIFF:CHANGED ensure that nrpe has rights to
monitor us task_userid:root
06.26.45busgateway01.phx2.fedoraproject.org Apr 01 2015
06:28:5814 CHECK_DIFF:CHANGED ensure that nrpe has rights to
monitor us task_userid:root
06.26.45busgateway01.stg.phx2.fedoraproject.org Apr 01 2015
06:28:516 CHECK_DIFF:CHANGED ensure that nrpe has rights to
Re: Freeze break: fix log sync script on log01
Woops my bad. +1 On 1 April 2015 at 10:37, Kevin Fenzi ke...@scrye.com wrote: log01 pulls httpd logs from proxys. When it was added, proxy11 wasn't right, this corrects it and saves us a cron email every night with the error: diff --git a/roles/base/files/syncHttpLogs.sh b/roles/base/files/syncHttpLogs.sh index 11a6d3a..ad25e01 100644 --- a/roles/base/files/syncHttpLogs.sh +++ b/roles/base/files/syncHttpLogs.sh @@ -38,7 +38,7 @@ syncHttpLogs proxy07.vpn.fedoraproject.org syncHttpLogs proxy08.vpn.fedoraproject.org syncHttpLogs proxy09.vpn.fedoraproject.org syncHttpLogs proxy10.phx2.fedoraproject.org -syncHttpLogs proxy11.phx2.fedoraproject.org +syncHttpLogs proxy11.vpn.fedoraproject.org syncHttpLogs proxy01.stg.phx2.fedoraproject.org syncHttpLogs app01.stg.phx2.fedoraproject.org syncHttpLogs bapp02.phx2.fedoraproject.org +1s? kevin ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure -- Stephen J Smoogen. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: FYI retroactive freeze break: koji ssl connection timeout increase hotfix
Applied. Note that we may roll out new packages with this change at some point so we don't have to worry about the hotfix messing things up. kevin pgp7fTONLwWjr.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break: fix log sync script on log01
On Wed, 1 Apr 2015 10:37:33 -0600 Kevin Fenzi ke...@scrye.com wrote: log01 pulls httpd logs from proxys. When it was added, proxy11 wasn't right, this corrects it and saves us a cron email every night with the error: +1 pgpwab4ehf8xy.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break: run some playbooks
On Wed, 1 Apr 2015 10:34:40 -0600 Kevin Fenzi ke...@scrye.com wrote: I'd like to run a few playbooks to roll up changes made just before freeze. These should only change the indicated stuff thats already in git below. If it causes any issues, we should find out now, instead of later in the freeze, and also will clean up the check/diff report and make sure we are running exactly whats in git. +1 pgpDjL2el7kpm.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Bugzilla components of retired packages
On 04/01/2015 03:29 PM, Cole Robinson wrote: But if someone from pkgdb side could give an example of how to query for fully retired packages, that would help. Even if it's not part of pkgdb in the short term, if there's a way to do that query now I'd be happy to send a request to bugzilla admins to manually hide all the long retired components. I was bored and came up with this: http://fpaste.org/206204/92520914/ I let it run for a few minutes and saw it was going to take a long time. I'll let it run overnight and post the list when it's done. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
FYI retroactive freeze break: koji ssl connection timeout increase hotfix
A few times in the last week we have hit a state where kojira on koji02 times out and doesn't run newrepo tasks for buildroots. Restarting the httpd on koji01 seems to unstick it, but this is not a good even stop gap as we would then have to manually do that and people would get small windows when koji was down. So, some investigation from koji developers at least for now the solution is to increase the ssl timeout. It's currently 60s, but I have increased it to 180 in a hotfix. http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=ebb160dceef8ede2ce97b3b940987b798380dfea and http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=f99e19b0244cd7ff8be570a6df6b78f494eceb57 This is already applied on koji02 to get us out of an outage situation (no new buildroots means no new fedora), but with +1s, I will apply to koji01 as well and make sure the playbooks sync with the hosts kevin pgpq85XMURQAv.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break: fix log sync script on log01
Applied. Thanks. kevin pgp3WCyVstkV_.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze Break Request: add db for execdb-stg to db-qa01.qa
On Wed, 1 Apr 2015 08:47:43 -0600 Tim Flink tfl...@redhat.com wrote: We had intended to do this before freeze but managed to miss it. One of the upcoming features for taskotron that we've deployed to dev and want to deploy to staging is execdb - task execution tracking for Taskotron. This requires adding a database to db-qa01.qa which is the db host for the production Taskotron instance but no other changes to production or frozen systems. Changes applied. pgp14V4KQl6E_.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Bugzilla components of retired packages
On Mon, 30 Mar 2015 10:34:35 -0500 Michael Cronenworth mike at cchtml.com wrote: Can we get retired packages out of the active Bugzilla component list? If they are completely retired, yeah, this might be possible. I just created a bug for a retired package and had to fix it... Bugzilla allows components to be disabled rather than deleted in case the bugs need to be searched for or a package comes out of retirement. Unfortunately the only way I see to automate this process is the REST API in 5.0. FWIW I've requested the same 2+ years ago: https://fedorahosted.org/packagedb/ticket/240 Currently tracked at: https://github.com/fedora-infra/pkgdb2/issues/59 This is a particular pet peeve for me since 5-10 times a year we get bugs incorrectly filed against the long dead 'kvm' component when reporters really want qemu or kernel. We use python-bugzilla to interface with bugzilla. Specfically this script: http://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/pkgdb2/files/pkgdb-sync-bugzilla So, we would need to enhance this script to handle the case of a package being retired in all branches in a product. Note that if they have any active branches we can't do this as at least the change I see via the interface is per component. Anyhow, if someone can see how to do this/provide patches sounds like a great idea. If we have to wait for 5.0, that would be good to know too. One of the difficulties in someone else providing a patch for this is that it's difficult to test unless you have admin bugzilla privileges. The github issue above gives some simple psuedo code for how the implementation should look. The python-bugzilla/bugzilla XMLRPC side is correct AFAICT (I'm python-bugzilla maintainer and can help if there's any issues). But if someone from pkgdb side could give an example of how to query for fully retired packages, that would help. Even if it's not part of pkgdb in the short term, if there's a way to do that query now I'd be happy to send a request to bugzilla admins to manually hide all the long retired components. Thanks, Cole ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Freeze break: run some playbooks
All run. Please let me know if you see any problems. kevin pgpGtFbQAwMVf.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
