March 2011 - infrastructure - Fedora mailing-lists

ticket#2673 - nitrate deployment
by James Laska 10 Aug '11

10 Aug '11

Greetings, I am in search of sponsorship for hosting space to deploy a test instance of nitrate [1]. Some of you may recall several years back when we deployed an instance of Testopia. That exploration was cut short when we discovered license incompatibilities between testopia and Fedora. At that time, a small group of Red Hat associates began creating a new Django-based test management system to remove the components that had conflicting licenses. That new system became nitrate [1]. The Fedora QA team would like to experiment/explore this newer Django-based test management system. At the very least, I believe we'll need a publicly accessible server where we can host the nitrate instance and a mysql database for it. I filed ticket#2673 (https://fedorahosted.org/fedora-infrastructure/ticket/2673) to track this request. Please don't hesitate with any questions/comments/concerns. Thanks, James [1] https://fedorahosted.org/nitrate/

3 7

Second rounds of lists clean-up
by Andrea Veri 07 Apr '11

07 Apr '11

hey guys, I've just finished tracking down inactive lists et all on collab01. The list can be found at [1]. Will wait 14 days from now and then clean-up the really inactive lists. I've used the following policy to avoid any problem: Lists with messages older than January 2011 or with no messages at all, will receive a mail from me asking if they still think their list is active or will be so in the near future. If no mails will be sent back to me within 14 days from today the list will be closed using the procedure explained above. (lists can be re-opened at any time later) Obviously the above didnt apply to the summer-coding lists that are inactive now since september for a valid motivation. Wow, it's finally done, it was a never-ending list! cheers! Andrea [1] http://averi.fedorapeople.org/inactive_lists_fp.txt

7 21

Meeting tomorrow (2011-03-31) at 19:00UTC in #fedora-meeting
by Kevin Fenzi 31 Mar '11

31 Mar '11

The infrastructure team will be having it's weekly meeting Tomorrow at 1900UTC in #fedora-meeting on the freenode network. * new folks introduction * Beta freeze coming up reminder. * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… * open floor Submit your agenda items, as tickets in the trac instance and/or send a note replying to this thread. Note that I will be unable to attend, so if someone else could run the meeting that would be great. :) Thanks kevin

3 2

[Bug 656076] BFO installation PITA (fwd)
by Mike McGrath 28 Mar '11

28 Mar '11

Who wants to be the BFO wrangler? :) -Mike ---------- Forwarded message ---------- Date: Mon, 28 Mar 2011 11:39:27 From: bugzilla(a)redhat.com To: mmcgrath(a)redhat.com Subject: [Bug 656076] BFO installation PITA Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=656076 Will Woods <wwoods(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |needinfo? --- Comment #15 from Will Woods <wwoods(a)redhat.com> 2011-03-28 12:39:25 EDT --- To be clear: this is not a bug in anaconda, it's a problem with the configuration used by boot.fedoraproject.org. This was fixed for Fedora 14 and earlier on February 28. As suggested in comment #12, for Fedora 15 no "method=xxx" line is necessary. Remove it and the install will proceed without the constant "Retry? message. (Apparently, whoever added the Fedora 15 configuration sections on boot.fedoraproject.org didn't see the email telling them to leave out the "append method=..." part. Oh well.) If anyone can confirm that removing "method=xxx" from the boot commandline makes the install proceed as expected, we'll change the configuration on boot.fedoraproject.org and close this bug. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

2 1

loggerhead updated for a CVE
by Toshio Kuratomi 24 Mar '11

24 Mar '11

I've updated loggerhead on hosted01/02 due to an XSS flaw. This is using the new EPEL5 builds. The changes are not large but (since el5 was on 1.17 and the fix is in 1.18.1) the changes do touch things that aren't related to the XSS fix. Likely, only projects that I'm involved in use bzr on fedorahosted (and thus loggerhead as the web viewer), but in case someone complains about problems, this is a likely culprit. PS: Thanks to ricky for making sure I saw this. -Toshio

1 0

Re: Outage: Upgrading nagios - 2011-03-25 18:00 UTC
by Stephen John Smoogen 24 Mar '11

24 Mar '11

Ugh. I put in the wrong date: The outage will be 2011-03-25 1800 UTC and last 2 hours. On Thu, Mar 24, 2011 at 16:26, Stephen Smoogen <smooge(a)gmail.com> wrote: > There will be an outage starting at 2011-03-25 18:00 UTC, which will last > approximately X hours. > > To convert UTC to your local time, take a look at > http://fedoraproject.org/wiki/Infrastructure/UTCHowto > or run: > > date -d '2011-03-25 18:00 UTC' > > Reason for outage: > > Moving from EL5 nagios to EL6 nagios > > Affected Services: > > Nagios > Zodbot > DHCP for PHX2 application network. > > Unaffected Services: > > > BFO - http://boot.fedoraproject.org/ > Bodhi - https://admin.fedoraproject.org/updates/ > Buildsystem - http://koji.fedoraproject.org/ > CVS / Source Control > DNS - ns1.fedoraproject.org, ns2.fedoraproject.org > Docs - http://docs.fedoraproject.org/ > Email system > Fedora Account System - https://admin.fedoraproject.org/accounts/ > Fedora Community - https://admin.fedoraproject.org/community/ > Fedora Hosted - https://fedorahosted.org/ > Fedora People - http://fedorapeople.org/ > Fedora Talk - http://talk.fedoraproject.org/ > Main Website - http://fedoraproject.org/ > Mirror List - https://mirrors.fedoraproject.org/ > Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ > Package Database - https://admin.fedoraproject.org/pkgdb/ > Smolt - http://smolts.org/ > Spins - http://spins.fedoraproject.org/ > Start - http://start.fedoraproject.org/ > Torrent - http://torrent.fedoraproject.org/ > Translation Services - http://translate.fedoraproject.org/ > Wiki - http://fedoraproject.org/wiki/ > > https://fedorahosted.org/fedora-infrastructure/ticket/2681#preview > > Contact Information: > > Please join #fedora-admin in irc.freenode.net or respond to this email to > track the status of this outage. > > > -- > Stephen J Smoogen. Fedora Team > "Tell me and I'll forget; show me and I may remember; involve me > and I'll understand." Mencius > “Let us be kind to one another, for most of us are fighting a > hard battle.” -- Ian MacLaren > > -- Stephen J Smoogen. "The core skill of innovators is error recovery, not failure avoidance." Randy Nelson, President of Pixar University. "Let us be kind, one to another, for most of us are fighting a hard battle." -- Ian MacLaren

1 0

Outage: Upgrading nagios - 2011-03-24 18:00 UTC
by Stephen John Smoogen 24 Mar '11

24 Mar '11

There will be an outage starting at 2011-03-24 18:00 UTC, which will last approximately X hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2011-03-24 18:00 UTC' Reason for outage: Moving from EL5 nagios to EL6 nagios Affected Services: Nagios Zodbot DHCP for PHX2 application network. Unaffected Services: BFO - http://boot.fedoraproject.org/ Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ CVS / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - http://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora People - http://fedorapeople.org/ Fedora Talk - http://talk.fedoraproject.org/ Main Website - http://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ Smolt - http://smolts.org/ Spins - http://spins.fedoraproject.org/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Translation Services - http://translate.fedoraproject.org/ Wiki - http://fedoraproject.org/wiki/ https://fedorahosted.org/fedora-infrastructure/ticket/2681#preview Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage. -- Stephen J Smoogen. Fedora Team "Tell me and I'll forget; show me and I may remember; involve me and I'll understand." Mencius “Let us be kind to one another, for most of us are fighting a hard battle.” -- Ian MacLaren

1 0

Meeting today (2011-03-24) at 19:00UTC in #fedora-meeting
by Kevin Fenzi 24 Mar '11

24 Mar '11

The infrastructure team will be having it's weekly meeting Tomorrow at 1900UTC in #fedora-meeting on the freenode network. * new folks introduction (kevin) * pkgs01 iscsi issues (kevin) * puppet reorg (skvidal) * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… * open floor Submit your agenda items, as tickets in the trac instance and/or send a note replying to this thread. Thanks

1 1

RE: Introduction
by Richard Walker 24 Mar '11

24 Mar '11

Hi Infrastructure Team, I'm an Enterprise Support Analyst from Yorkshire, United Kingdom. I have a fair amount of Linux experience and now work full time with Tru64, HP-UX and most significantly Red Hat Enterprise. Although I still have a lot to learn I will be getting formal Red Hat training at some point and more experience under my belt moving forward. I'm still finding my way around here but hope to get involved if I have anything to offer, I'm a fan of Red Hat/Fedora and hope to master everything about it - so if I can learn and help out along the way - all the better! Regards, Richard.

2 1

changing a few things in our host mgmt tools
by Seth Vidal 23 Mar '11

23 Mar '11

Hi folks, some thoughts have been slowly coalescing in my head about how we're managing our boxes/services and I have some suggestions I've passed by various folks but I wanted to check them out with everyone: 1. puppetd sucks..... memory. Right now we have puppetd running on every box and it wakes up every half hour and runs itself. This is fine but in the time where it is not doing anything it just eats memory for no good reason. I'd like to suggest we move to a cron-driven model instead of puppetd. I'd write a simple cron job that runs every half hour to run puppetd, if a lock file is not found. Pretty straightforward, of course. 2. monitoring if puppetd has run properly: two things we want to know about puppet runs: a. when they last happened per-box b. if they fell over in a horrible way. (a) can be known by looking at the $nodename.yaml file which lives on the puppetmaster. I've written a script to check if that file is older than 1 hour and report the nodename if it is. (b) can be done via the cron job - ie: taking error output from the puppet run and mailing to people until we fix it! :) 3. sign** boxes. problems here: a. These boxes are falling out of date, repeatedly, b/c they aren't in our normal updating path. b. these boxes don't email out to the same locations as the other boxes c. these boxes don't get faspassword updates properly d. these boxes don't get config changes normally via puppet (a) I'd like to suggest that they be put into a normal updating path and/or we setup a nag mail to tell us about them (b) obviously, fix their mail configs (c) fasclient is failing b/c of a missing token b/c, most likely, of (d) I'm open to suggestions on those but it is a bit annoying b/c while I understand their 'sensitivity' I think our way of treating them is making the problem WORSE not better. -sv

6 11

Sign-vault01 outage Retrospective - 2011-03-22 at 20UTC
by Kevin Fenzi 22 Mar '11

22 Mar '11

Greetings. As some of you may know, we had an outage of our signing server on friday (2011-03-18). The outage was caused by hardware failure on that physical machine, but there are a number of issues around this we should discuss and address. Due to heroic efforts from a number of folks, things were back up and functioning later friday. Thanks to all involved! We would like to hold a retrospective on this outage in #fedora-meeting at 20:00UTC on 2011-03-22. Agenda/Items to discuss: * Timeline/Background info * Setup of sensitive boxes * func/puppet/fasClient or not? * encrypted / * Updates for sensitive boxes * regular with other updates? * do not schedule on fridays? * Backups of sensitive boxes * Avoiding single points of failure * Notifications on outages like this Please join us and add input to help make things better. kevin

1 1

Removing users from sysadmin-* accounts
by Stephen John Smoogen 21 Mar '11

21 Mar '11

System administration is a privilege as it gives access and control over many users resources and data. In order to best protect those assets, it is a normal procedure to remove people who do not seem to have need for that access anymore. Fedora Infrastructure policy is to remove special access to people who have not been using it in 60 days. Having gone through the user lists in wtmp, web logs and other data the following accounts will be removed from various system administration groups. People who are removed may reapply later to the infrastructure program when they feel they need access again. Accounts will not be removed from the infrastructure mailing list. Accounts will be removed by 2011-03-17 2000 UTC. sysadmin akistler sysadmin benbeecher sysadmin billchen sysadmin ccielogs sysadmin dianam sysadmin ff4273 sysadmin ggruener sysadmin gsieranski sysadmin jasonwalsh sysadmin jaxjax sysadmin jeffreyt sysadmin jonrob sysadmin jorn sysadmin kolesovdv sysadmin marcelomgarcia sysadmin mkearey sysadmin nman64 sysadmin rordway sysadmin santosp sysadmin sbathe sysadmin thierry sysadmin valholla sysadmin wfoster sysadmin yingbull cmsadmin cyrushmh cmsadmin itbegins cmsadmin matheo cmsadmin schendje cmsadmin teb cmsadmin wonderer sysadmin-cloud arjunroy sysadmin-cloud hbrock sysadmin-cloud lutter sysadmin-cloud pmyers sysadmin-cloud sheid sysadmin-cloud slinabery sysadmin-cloud sseago sysadmin-dba mikeb sysadmin-devel davivercillo sysadmin-devel huzaifas sysadmin-devel itbegins sysadmin-devel ivazquez sysadmin-hosted huzaifas sysadmin-hosted jaxjax sysadmin-main mikeb sysadmin-noc badone sysadmin-noc billchen sysadmin-noc ggruener sysadmin-noc huzaifas sysadmin-noc jdieter sysadmin-noc jorn sysadmin-noc kanarip sysadmin-noc rigeld2 sysadmin-noc sgrubb sysadmin-noc sheid sysadmin-noc wakko666 sysadmin-noc yingbull sysadmin-spin kanarip sysadmin-spin maxamillion sysadmin-spin sandeen sysadmin-test akistler sysadmin-test anujmore sysadmin-test badone sysadmin-test drak sysadmin-test emichan sysadmin-test huzaifas sysadmin-test itbegins sysadmin-test jhutar sysadmin-test jtluka sysadmin-test kanarip sysadmin-test mapleoin sysadmin-test marcelomgarcia sysadmin-test matheo sysadmin-test mbacovsk sysadmin-test mganisin sysadmin-test schendje sysadmin-test zc00gii sysadmin-tools huzaifas sysadmin-tools santosp sysadmin-tools tgalyean sysadmin-web adrian sysadmin-web akistler sysadmin-web asgeirf sysadmin-web badone sysadmin-web glezos sysadmin-web huzaifas sysadmin-web ivazquez sysadmin-web johnp sysadmin-web jokajak sysadmin-web jorn sysadmin-web mbacovsk sysadmin-web wakko666 sysadmin-web yingbull sysadmin-web zoglesby -- Stephen J Smoogen. "The core skill of innovators is error recovery, not failure avoidance." Randy Nelson, President of Pixar University. "Let us be kind, one to another, for most of us are fighting a hard battle." -- Ian MacLaren

5 7

FAS password complexity requirements
by Ricky Zhou 21 Mar '11

21 Mar '11

Hey, so we discussed in the meeting, FAS's password requirements are currently very lax - just a minimum length of 8 characters. What do we think the requirements should be changed to? One possible strength checker that I mentioned during the meeting was: http://www.nongnu.org/python-crack/ This can use a dictionary to detect weak passwords. Thoughts? Ricky

6 7

Can I authenticate against FAS without python?
by Sean Flanigan 21 Mar '11

21 Mar '11

Hi, I'm part of a team which is working on a Java-based web translation system called Zanata (formerly Flies) which needs to authenticate against the Fedora Account System (ideally SSO). What's the state of http://fedoraproject.org/wiki/OpenID ? This seems like it would be fairly easy to integrate into Java. That page says it's in beta. Would it be a really bad idea to build a system which depends on it, even as a stop-gap? Apart from authentication, I would like to check if the user has signed a CLA before letting them enter translations. What options are available to a Java system for checking CLAs? I know there's python-fedora, but is there a documented web service underneath, which I could access from Java? I guess I'm looking for an XML/JSON version of https://admin.fedoraproject.org/accounts/user/view/{username}, preferably one which doesn't require my system to authenticate itself as a Fedora user. Also, I've been looking at the python-fedora API, and I have some questions: 1. is there an attribute which tells me the user has signed a CLA? 2. can I fetch this attribute without authenticating? 3. if I do need to authenticate, how can I get a non-human Fedora account for my web server to use? Thanks! Sean. -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat

3 3

Re: Removing users from sysadmin-* accounts
by Matt Domsch 17 Mar '11

17 Mar '11

Ack. Sent from my Dell Streak -----Original Message----- From: Adrian Reber [adrian(a)lisas.de] Received: Thursday, 17 Mar 2011, 1:55am To: Fedora Infrastructure [infrastructure(a)lists.fedoraproject.org] Subject: Re: Removing users from sysadmin-* accounts On Wed, Mar 16, 2011 at 09:59:21PM -0600, Stephen John Smoogen wrote: > sysadmin-web adrian Please do not delete my sysadmin-web account. I need for MirrorManager admin rights. Adrian _______________________________________________ infrastructure mailing list infrastructure(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure

1 0

RFR Owner Expectations
by Toshio Kuratomi 16 Mar '11

16 Mar '11

https://fedorahosted.org/fedora-infrastructure/ticket/2674 https://fedoraproject.org/wiki/Infrastructure/RFR_Responsibilities%28draft%… We're currently suffering under the weight of too many services and too few admins. Some of that is because the expectations of people submitting RFR's isn't well defined. Here's the start of a document to address that. You're welcome to brainstorm additions to that and later we can work at organization/making it better reading for people making an RFR. I've made it a meeting discussion item to gain visibility and more feedback, but there's no decisions to be made at this time. Just need to be fleshed out more. -Toshio

2 1

Meeting *Tomorrow* 2011-03-17 at 1900 UTC in #fedora-meeting **NOTE NEW TIME**
by Derek Carter 16 Mar '11

16 Mar '11

The infrastructure team will be having it's weekly meeting Tomorrow at 1900UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * RFR docs (Toshio): https://fedorahosted.org/fedora-infrastructure/ticket/2674 * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… Submit your agenda items, as tickets in the trac instance and/or send a note replying to this thread. Thanks -- Derek aka goozbach

1 0

Intro
by Marco Grigull 15 Mar '11

15 Mar '11

Dear infra team, I am based in Brisbane, Australia and spend most of my time extending and looking after engineering resources. I have some experience with templating tool cfengine (and some exposure to puppet) and nagios. I would like to help out with establishing localised resources for existing content and to keep core systems running. I look forward to participating and helping to cover during the Autralasian-Pacific hours. Regards, Marco irc: ciphernaut

2 1

mismatch_cnt on various raid's
by Kevin Fenzi 15 Mar '11

15 Mar '11

So, we have been getting weekly mismatch_cnt emails from a number of machines with raid setups. http://fedoraproject.org/wiki/Infrastructure/SOP/Raid_Mismatch_Count Describes a process to run repair and check on them, but in these cases the mismatches have come back right away. Why is that you might ask? It's because these are all raid-1 setups. There are cases where raid1 can and does have a mismatched sector setup and it's perfectly fine. It's still good to run the weekly check on them in case there is a marginal drive that drops out or otherwise shows lower layer problems. See: https://bugzilla.redhat.com/show_bug.cgi?id=566828 So, moving forward I think I will try and do a "hotfix" for /etc/cron.weekly/99-raid-check and make it not mail for raid1 mismatches. (see patch in above bug) Longer term, perhaps there will be a mdadm update for rhel5, or we will get everything moved to rhel6 (which has the fix already). kevin

1 0

Converting old fedora-git-commit-mail-hook users to gnome mail hook on hosted
by Todd Zullinger 14 Mar '11

14 Mar '11

Jim Meyering mentioned in #fedora-admin today that pushing to repos which use the fedora-git-commit-mail-hook can produce unwanted output 15:40:23 <meyering> hi guys, I've pushed two batches of c-sets, and noticed what may be a trace of a bug in a git update hook (or maybe some other): 15:40:23 <meyering> $ git push 15:40:23 <meyering> ... 15:40:27 <meyering> Total 13 (delta 10), reused 0 (delta 0) 15:40:30 <meyering> remote: git: 'refs/heads/master' is not a git command. See 'git --help'. 15:40:33 <meyering> To ssh://git.fedorahosted.org/git/iwhd.git 15:40:36 <meyering> b57b085..25ef441 master -> master 15:40:44 <meyering> Note the "remote: git: ... is not a git command." diagnostic I updated the check-perms script to look for repos using the old hook, but before I run it with the --fix option to convert them to the newer hooks we borrowed from the folks at gnome.org, it seems wise to check whether anyone has reasons to avoid doing so or suggestions on how to make sure this doesn't annoy users of fedorahosted.org. The gnome hook is what we use for the infrastructure puppet repo as well as all of the git repos for packages. The formatting should be fairly similar to what the old hook produced, and it does include similar X- headers for folks using those to filter mail. Here's the list of repos which use the old mail hook: [tmz@hosted1 ~ (master)]$ time ~/bin/git-check-perms /git/389/admin-console.git: uses old mail hook /git/389/admin.git: uses old mail hook /git/389/adminutil.git: uses old mail hook /git/389/console.git: uses old mail hook /git/389/ds-console.git: uses old mail hook /git/389/ds.git: uses old mail hook /git/389/dsgw.git: uses old mail hook /git/389/dsmlgw.git: uses old mail hook /git/389/winsync.git: uses old mail hook /git/CloudFS.git: uses old mail hook /git/OpenAPC.git: uses old mail hook /git/TinyEarth.git: uses old mail hook /git/anaconda-help.git: uses old mail hook /git/anaconda-images.git: uses old mail hook /git/anaconda.git: uses old mail hook /git/bharati.git: uses old mail hook /git/bluecurve-classic-metacity-theme: uses old mail hook /git/bluecurve-gdm-theme: uses old mail hook /git/bluecurve-gnome-theme: uses old mail hook /git/bluecurve-gtk-themes: uses old mail hook /git/bluecurve-icon-theme: uses old mail hook /git/bluecurve-kde-theme: uses old mail hook /git/bluecurve-kdm-theme: uses old mail hook /git/bluecurve-kwin-theme: uses old mail hook /git/bluecurve-metacity-theme: uses old mail hook /git/bluecurve-qt-engine: uses old mail hook /git/bluecurve-xmms-skin: uses old mail hook /git/bodhi.git: uses old mail hook /git/booty.git: uses old mail hook /git/cas.git: uses old mail hook /git/certmaster.git: uses old mail hook /git/cloud-kickstarts.git: uses old mail hook /git/comps.git: uses old mail hook /git/courses.git: uses old mail hook /git/d-feet.git: uses old mail hook /git/ding-libs.git: uses old mail hook /git/docbook-utils.git: uses old mail hook /git/docs/about-fedora.git: uses old mail hook /git/docs/elections-guide.git: uses old mail hook /git/docs/fedora-doc-utils.git: uses old mail hook /git/docs/homepage.git: uses old mail hook /git/docs/install-guide.git: uses old mail hook /git/docs/readme-burning-isos.git: uses old mail hook /git/docs/readme.git: uses old mail hook /git/docs/storage-administration-guide.git: uses old mail hook /git/docs/systemtap-beginners-guide.git: uses old mail hook /git/dorrie.git: uses old mail hook /git/elections.git: uses old mail hook /git/fas.git: uses old mail hook /git/fedora-gnome-theme: uses old mail hook /git/fedora-icon-theme: uses old mail hook /git/fedora-infrastructure.git: uses old mail hook /git/fedora-kontributor.git: uses old mail hook /git/fedora-packager.git: uses old mail hook /git/fedora-project-schedule.git: uses old mail hook /git/fedora-screensaver-theme: uses old mail hook /git/fedora-security.git: uses old mail hook /git/fedora-tour.git: uses old mail hook /git/fedora-trans-es.git: uses old mail hook /git/fedora-web.old.git: uses old mail hook /git/fedorabubbles-gdm-theme: uses old mail hook /git/fedoradna-gdm-theme: uses old mail hook /git/fedoradna-kdm-theme: uses old mail hook /git/fedoraflyinghigh-gdm-theme: uses old mail hook /git/fedoraflyinghigh-kdm-theme: uses old mail hook /git/fedorainfinity-gdm-theme: uses old mail hook /git/fedorainfinity-screensaver-theme: uses old mail hook /git/firstboot.git: uses old mail hook /git/fontpackages.git: uses old mail hook /git/freeipa.git: uses old mail hook /git/func.git: uses old mail hook /git/gnome-applet-vm.git: uses old mail hook /git/grid/carod.git: uses old mail hook /git/grid/caroniad.git: uses old mail hook /git/grid/configuration-tools.git: uses old mail hook /git/grid/job_hooks.git: uses old mail hook /git/grid/spqr.git: uses old mail hook /git/grid/wallaby.git: uses old mail hook /git/grid/win32-packaging.git: uses old mail hook /git/grubby.git: uses old mail hook /git/indic-typing-booster.git: uses old mail hook /git/isomd5sum.git: uses old mail hook /git/koji: uses old mail hook /git/libnmserver.git: uses old mail hook /git/livecd: uses old mail hook /git/liveusb-creator.git: uses old mail hook /git/mkinitrd: uses old mail hook /git/moksha.git: uses old mail hook /git/music-creation.git: uses old mail hook /git/newt-syrup.git: uses old mail hook /git/ogrechess.git: uses old mail hook /git/openussd.git: uses old mail hook /git/osutil.git: uses old mail hook /git/piranha.git: uses old mail hook /git/pirut.git: uses old mail hook /git/pyblock.git: uses old mail hook /git/pyjigdo.git: uses old mail hook /git/pykickstart.git: uses old mail hook /git/redhat-rpm-config: uses old mail hook /git/reflector.git: uses old mail hook /git/revisor: uses old mail hook /git/revista-fedora-latam.git: uses old mail hook /git/rhpl.git: uses old mail hook /git/rhq/rhq-config.git: uses old mail hook /git/rhq/rhq-manage-jboss.git: uses old mail hook /git/rhq/rhq-manage-os.git: uses old mail hook /git/rhq/rhq.git: uses old mail hook /git/sanlock.git: uses old mail hook /git/secstate.git: uses old mail hook /git/simon.git: uses old mail hook /git/smolt.git: uses old mail hook /git/snap.git: uses old mail hook /git/spacewalk.git: uses old mail hook /git/sssd.git: uses old mail hook /git/symbolic.git: uses old mail hook /git/system-config-kickstart.git: uses old mail hook /git/timpus-events.git: uses old mail hook /git/trustedcomputing.git: uses old mail hook /git/utrrs.git: uses old mail hook /git/virt_web.git: uses old mail hook /git/webzash.git: uses old mail hook /git/wikirename.git: uses old mail hook /git/xo.git: uses old mail hook 123 problems remain unfixed -- Todd ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Every actual state is corrupt. Good men must not obey the laws too well. -- Ralph Waldo Emerson

1 1

Fixes for git repos not configured as bare on hosted1
by Todd Zullinger 14 Mar '11

14 Mar '11

It was reported that with the recent update to git-1.7.4.1 that a number of the repositories on hosted1 lacked the proper core.bare setting, which caused git to refuse to allow updates. I added a check for the this to the git check-perms script and ran it with the -f option to fix up misconfigured repositories. The output: $ time sudo git check-perms -f /git/amber.git: core.bare not true /git/anaconda-help.git: core.bare not true /git/anaconda-images.git: core.bare not true /git/anaconda.git: core.bare not true /git/astronomy.git: core.bare not true /git/bluecurve: core.bare not true /git/bluecurve-classic-metacity-theme: core.bare not true /git/bluecurve-gdm-theme: core.bare not true /git/bluecurve-gnome-theme: core.bare not true /git/bluecurve-gtk-themes: core.bare not true /git/bluecurve-icon-theme: core.bare not true /git/bluecurve-kde-theme: core.bare not true /git/bluecurve-kdm-theme: core.bare not true /git/bluecurve-kwin-theme: core.bare not true /git/bluecurve-metacity-theme: core.bare not true /git/bluecurve-qt-engine: core.bare not true /git/bluecurve-xmms-skin: core.bare not true /git/booty.git: core.bare not true /git/chkconfig.git: core.bare not true /git/cobbler: core.bare not true /git/comps-extras.git: core.bare not true /git/cronie.git: core.bare not true /git/d-feet.git: core.bare not true /git/desktop-effects.git: core.bare not true /git/dhcdbd.git: core.bare not true /git/dhcpv6.git: core.bare not true /git/docs/about-fedora.git: core.bare not true /git/docs/homepage.git: core.bare not true /git/docs/install-guide.git: core.bare not true /git/docs/readme-burning-isos.git: core.bare not true /git/docs/readme-live-image.git: core.bare not true /git/docs/readme.git: core.bare not true /git/docs/release-notes.git: core.bare not true /git/dts.git: core.bare not true /git/echo-icon-theme: core.bare not true /git/eunectes.git: core.bare not true /git/fedora-gnome-theme: core.bare not true /git/fedora-icon-theme: core.bare not true /git/fedora-infrastructure.git: core.bare not true /git/fedora-screensaver-theme: core.bare not true /git/fedora-web.old.git: core.bare not true /git/fedorabubbles-gdm-theme: core.bare not true /git/fedoradna-gdm-theme: core.bare not true /git/fedoradna-kdm-theme: core.bare not true /git/fedoraflyinghigh-gdm-theme: core.bare not true /git/fedoraflyinghigh-kdm-theme: core.bare not true /git/fedorainfinity-gdm-theme: core.bare not true /git/fedorainfinity-screensaver-theme: core.bare not true /git/firstaidkit.git: core.bare not true /git/firstboot.git: core.bare not true /git/freeipa.git: core.bare not true /git/func.git: core.bare not true /git/generic-logos.git: core.bare not true /git/gnome-applet-vm.git: core.bare not true /git/hwdata.git: core.bare not true /git/idm-console-framework.git: core.sharedRepository not set /git/idm-console-framework.git/config: Not group writable (should be "0664") /git/initscripts.git: core.bare not true /git/koji: core.bare not true /git/kudzu.git: core.bare not true /git/libdhcp.git: core.bare not true /git/liberation-fonts.git: core.bare not true /git/livecd: core.bare not true /git/mash: core.bare not true /git/mirrormanager: core.bare not true /git/mkinitrd: core.bare not true /git/monkey.git: core.bare not true /git/nodoka: core.bare not true /git/olpc-vault.git: core.bare not true /git/opyum: core.bare not true /git/pam_krb5.git: core.bare not true /git/perl-rpm2.git: core.bare not true /git/pilgrim.git: core.bare not true /git/pirut.git: core.bare not true /git/presto: core.bare not true /git/pump.git: core.bare not true /git/pungi.git: core.bare not true /git/pyblock.git: core.bare not true /git/pyjigdo.git: core.bare not true /git/pykickstart.git: core.bare not true /git/pyparted.git: core.bare not true /git/pyrpm.git: core.bare not true /git/python-bugzilla.git: core.bare not true /git/pyxf86config.git: core.bare not true /git/readahead: core.bare not true /git/redhat-rpm-config: core.bare not true /git/releng: core.bare not true /git/revisor: core.bare not true /git/rhgb.git: core.bare not true /git/rhpl.git: core.bare not true /git/rhpxl.git: core.bare not true /git/rpmdevtools.git: core.bare not true /git/setuptool.git: core.bare not true /git/sigul.git: core.bare not true /git/snake: core.bare not true /git/splatbind.git: core.bare not true /git/supybot-fedora.git: core.bare not true /git/supybot-koji.git: core.bare not true /git/supybot-notify.git: core.bare not true /git/symbolic.git: core.bare not true /git/system-config-display.git.old: core.bare not true /git/system-config-firewall.git: core.bare not true /git/system-config-kickstart.git: core.bare not true /git/system-config-securitylevel.git: core.bare not true /git/system-setup-keyboard.git: core.bare not true /git/thetango: core.bare not true /git/umltester: core.bare not true /git/updatinator: core.bare not true /git/vsp.git: core.bare not true /git/wevisor: core.bare not true /git/yumex.git: core.bare not true -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ America wasn't founded so that we could all be better. America was founded so we could all be anything we damned well pleased. -- P.J. O'Rourke

2 1

Outage: Serverbeach servers downtime 2011-03-16 03:00 UTC -> 2011-03-16 09:00 UTC
by Stephen John Smoogen 11 Mar '11

11 Mar '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There will be an outage starting at 2011-03-16 03:00 UTC, which will last approximately 6 hours. [Outages should be only 10-30 minutes long but the window for the outage is 6 hours thus the large window.] To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2011-03-16 03:00 UTC' Reason for outage: Affected Services: DNS - ns1.fedoraproject.org, Fedora Hosted - https://fedorahosted.org/ Fedora Talk - http://talk.fedoraproject.org/ Email for fedoraproject.org Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage. - -- Smooge [Temporary Interim Chief Cat Wranglger] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org/ iJwEAQECAAYFAk16iskACgkQAsLqwWFAN9vihAQAhJH1+JaVMknFpopSzCFdx33w 9r/tjQDaqBb9k6Vud9fMjZAPjl14+2S6VuZvvwNnz3dVLr6KRCNbDnu04WA8K9Fp 59L+SZwhPSh6wS/S1WVaId946FlpinzsDeElN6JDoTxyo77stmRBqYXwx8xGcldW F1IQOzU3kz2TrXcI3j0= =Ddlu -----END PGP SIGNATURE-----

1 0

Meeting *TODAY* 2011-03-10 at 2000 UTC in #fedora-admin
by Derek Carter 10 Mar '11

10 Mar '11

The infrastructure team will be having it's weekly meeting today at 2000UTC in #fedora-admin on the freenode network. Suggested topics (suggested by whom): * Update on the ServerBeach Outage. (nirik et all) * Killing CVS (nirik) * Server updates -- report by (skvidal) * Meeting Time/Location We've tried to do the meeting in #fedora-admin so we can go longer than the hour we need to get everything done. This is problematic as people come to that channel to get help during the meeting and it is distracting. As next week is the change in DST for the folks in the United States, there's been a suggestion to move the meeting back to the #fedora-meeting channel, and to 1900UTC. We need to discuss this in the meeting today. * Do we want to talk about the "gathering community feedback" thing any further? (goozbach) * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… Submit your agenda items, as tickets in the trac instance and/or send a note replying to this thread. Thanks

3 3

Gathering community feedback...
by Jóhann B. Guðmundsson 10 Mar '11

10 Mar '11

As Brian mentioned in [1],[2] as in the CWG wanted to get a constructive feedback on COC and COCE proposed drafts from the whole community on the FAB list highlights one issue that the project is facing as in we don't have a good way of gathering community feedback on topics. This issue is probably know but for some reason not being worked upon? ( Feel free to correct me if I'm wrong ) Anyway to point out the obvious encase nobody was aware of this issue. ( we have been without one for now about 15 release cycles so something is amiss ) He posts the proposed drafts to a single mailing list which.. a) Has a limited number of users subscribed to it b) Requires all members of the community to be subscribed to that particular list. c) Mailing list provide the ability to see and reply to others people feed back resulting in so called *noise* as in people reassuring their feedback encase the message/meaning did get through and etc.. rather then constructive discussion. That results in an end result that is far from being effective and reaching the whole community. Coming up with a rough solution to gather the feedback is a no brainer First we need a common dominator that applies to all community members and that one is obvious FAS account. Next we need a web server with a DB backend, hooked up to FAS with an simple web page that the community member logs into that displays to him what he needs to provide his feedback and two text boxes one for the feedback and another one for any question he might have with regards to the proposal/draft itself. With the above in place all that is needed is to request the feedback via our public channels like a mail to the announce or something similar. Now the tricky part is coming up with a simple yet scalable to the total number of community members solution, to work through all that feedback I got couple of ideas up my sleeves for that but instead of reinventing the wheel I propose that existing survey tools like [1],[2] be looked at first to see how they have solved the problem we are facing. JBG 1. http://lists.fedoraproject.org/pipermail/advisory-board/2011-March/010525.h… 2. http://lists.fedoraproject.org/pipermail/advisory-board/2011-March/010526.h… 3. http://www.limesurvey.org/ 4. http://www.doodle.com

8 15

Meeting *TODAY* 2011-03-10 at 2000 UTC in #fedora-admin
by Derek Carter 10 Mar '11

10 Mar '11

The infrastructure team will be having it's weekly meeting today at 2000UTC in #fedora-admin on the freenode network. Suggested topics (suggested by whom): * Update on the ServerBeach Outage. (nirik et all) * Killing CVS (nirik) * Server updates -- report by (skvidal) * Meeting Time/Location We've tried to do the meeting in #fedora-admin so we can go longer than the hour we need to get everything done. This is problematic as people come to that channel to get help during the meeting and it is distracting. As next week is the change in DST for the folks in the United States, there's been a suggestion to move the meeting back to the #fedora-meeting channel, and to 1900UTC. We need to discuss this in the meeting today. * Do we want to talk about the "gathering community feedback" thing any further? (goozbach) * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… Submit your agenda items, as tickets in the trac instance and/or send a note replying to this thread. Thanks -- Derek aka goozbach

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure March 2011