December 2015 - infrastructure - Fedora mailing-lists

Technical Debt Fighters, Assemble!
by Ralph Bean 15 Jan '16

15 Jan '16

At Flock, we talked about scheduling some kind of regular technical-debt-fighting week to happen every so often - some period of time where we don't do any new features (and even try to de-prioritize interrupt-driven stuff) and focus on shoring up, cleaning up, tightening the bolts, etc[1]. Here are some things broadly to think about: - Add unit tests where there are none. Increase "code coverage". - Write docs (and make diagrams!) where there are none. - Reduce code duplication, and increase code re-use where appropriate. - Break up ultra long methods, classes, and files into more understandable chunks. - Remove half-implemented features! - Remove dead code!! - Add comments where there are none, and correct inaccurate comments. - Deal with the existential questions facing the code that none of us wants to touch. - Increase happiness and general zest for life. Time-wise, how about we try and schedule a week to try this on the first week back from the holiday break -- a New Year, a New Infrastructure(!) That would be January 4-8th[2]. Here's a question I have. It seems like we could approach this in two different ways: - We could select one or two projects we want to prioritize, and try to do *all* of the best-practices things to them. - We could select one or two of the best-practices things, and try to do them to *all* of our projects. Or.. something inbetween. If you have a preferences here, chime in on the list, or we can take this up in our IRC meeting at the beginning of December, too. As an aside, it would be especially fun if we could keep track of our collective damage on some kind of scoreboard (it doesn't have to be automatic, even manual pen-and-paper would work) so we can produce a nice summary blogpost at the end and thus herald in 2016, a year of working code, less fires, and quiet mornings where we sip our coffee and read email. -Ralph [1] - http://threebean.org/presentations/debt-services-flock15/ [2] - https://apps.fedoraproject.org/calendar/meeting/3183/

3 6

How to deal with endoflife AT fedoraproject DOT org service account ?
by Jan Kurik 04 Jan '16

04 Jan '16

Hi infrastructure team, I am in doubt how to deal with "endoflife" service account. In fact, it is not really an account, it is just an email alias. This email address has been used for maintaining and housekeeping of old bugs in Bugzilla. The background: This email alias used to be forwarded to triage@ mailing list. Some time ago password policy of Bugzilla has changed and this email/account become unavailable due to a weak password. To make this email/account available again I had to request password reset of the Bugzilla account. The password reset in Bugzilla is made via email and the email to confirm the password reset had been sent to the publicly available triage@ mailing list. Then I have realized that anybody can hijack the account, using the password reset. To avoid this, I redirected the endoflife Bugzilla account to my private email address. However I to not think this is a good solution and I would like to find a way how to solve this problem properly. Currently, the best way I see, is to make the "endoflife" email alias as a full-blown account in FAS, instead of email alias only. However as far as I know, we are using FAS for real people only. So, my question is, whether there is a better way how to deal with this service email/account ? Thanks for pointing me to the right direction :) Best Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

2 2

[release] bodhi: 2.1.5
by Luke Macken 22 Dec '15

22 Dec '15

Hi folks, I just spun up a new bugfix release of bodhi and pushed it to production. The last release contained a bug that caused a snowball effect and a number of updates were ejected from the last couple of pushes. This issue should hopefully be resolved. 2.1.5 ----- Pull Requests - (@trishnaguha) #723, Sorts the list of test cases https://github.com/fedora-infra/bodhi/pull/723 - (@lmacken) #728, updates: Disable the ability to set a request for an archived release… https://github.com/fedora-infra/bodhi/pull/728 - (@lmacken) #731, overrides: Gracefully handle duplicate submissions (fixes #713) https://github.com/fedora-infra/bodhi/pull/731 - (@lmacken) #733, models: Don't delete Bugs that have BugKarma https://github.com/fedora-infra/bodhi/pull/733 - (@lmacken) #736, models: Query the wiki for tests with a limit of 500 instead of the default of 10 https://github.com/fedora-infra/bodhi/pull/736 - (@lmacken) #737, email: Send comment notifications to the update submitter https://github.com/fedora-infra/bodhi/pull/737 - (@lmacken) #738, models: Obsolete unlocked updates, even if they have an open request … https://github.com/fedora-infra/bodhi/pull/738 - (@cgwalters) #739, ini: Link to wiki page for how to get updates instead of inline cmd https://github.com/fedora-infra/bodhi/pull/739 - (@ralphbean) #742, Remove unnecessary encoding of bug titles. https://github.com/fedora-infra/bodhi/pull/742 Commits - d801e07ff Sorts the list of test cases https://github.com/fedora-infra/bodhi/commit/d801e07ff - 6c4023390 updates: Disable the ability to set a request for an archived release (issue #725) https://github.com/fedora-infra/bodhi/commit/6c4023390 - 6879f0d02 overrides: Gracefully handle duplicate submissions (fixes #713) https://github.com/fedora-infra/bodhi/commit/6879f0d02 - 65794626b models: Don't delete Bugs that have BugKarma (fixes #732) https://github.com/fedora-infra/bodhi/commit/65794626b - b99c0f1a0 bootstrap: Add a hack for PIL to link the Pillow egg-info into our virtualenv https://github.com/fedora-infra/bodhi/commit/b99c0f1a0 - c4ba820da models: Query the wiki for tests with a limit of 500 instead of the default of 10 https://github.com/fedora-infra/bodhi/commit/c4ba820da - c1a2247a7 email: Send comment notifications to the update submitter (fixes #726) https://github.com/fedora-infra/bodhi/commit/c1a2247a7 - 8ecf380a5 models: Obsolete unlocked updates, even if they have an open request (fixes #724) https://github.com/fedora-infra/bodhi/commit/8ecf380a5 - da17ec271 ini: Link to wiki page for how to get updates instead of inline cmd https://github.com/fedora-infra/bodhi/commit/da17ec271 - 05e992d46 tests: Fix up some bugs from PR#739 https://github.com/fedora-infra/bodhi/commit/05e992d46 - e7c363a41 tests: Fix the name of a unit test https://github.com/fedora-infra/bodhi/commit/e7c363a41 - 5d2a2b14f Remove unnecessary encoding of bug titles. https://github.com/fedora-infra/bodhi/commit/5d2a2b14f - 1ca762d0e Fix test case. https://github.com/fedora-infra/bodhi/commit/1ca762d0e - d54c77b94 masher: Minor tweaks to the sync/async tagging https://github.com/fedora-infra/bodhi/commit/d54c77b94 - d6300ae90 util: Ensure updates aren't listen in both the sync/async batches https://github.com/fedora-infra/bodhi/commit/d6300ae90 - 5722929fe util: Clean up some logging output https://github.com/fedora-infra/bodhi/commit/5722929fe

1 0

Infrastructure Holiday Freeze now in effect
by Patrick Uiterwijk 21 Dec '15

21 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, As agreed during last meeting, and as done in previous years, we are now in an infrastructure soft-freeze until 2016-01-04. This means that hosts that are marked as freezing should not have any changes made to them except as part of a freeze break request (see below). We do this to make sure that our infrastructure is stable and prevent unnecessary alerts to the sysadmins while they are off. This freeze will end on the first working day of the new year (2016-01-04). For soft freezes, freeze breaks should be discussed either on this list, or discussed on IRC. Freeze breaks can be applied when either they got a +1 from anyone in the sysadmin-main group, or an ack from one of the main sysadmin people (nirik, smooge, puiterwijk). You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script: git clone http://infrastructure.fedoraproject.org/infra/ansible.git scripts/freezelist -i inventory - -- With kind regards, Patrick Uiterwijk Fedora Infra -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJWeABQAAoJEIZXmA2atR5QJ9YQAI09YaS5N4aNI9yM7e1Xrwqd Hu7QlMhvcOVcXeWrex0puzqCHnFOYbGXwuJlidK/sfsnQzh2rk4a3TWI8lM/aPq7 8GDbTpdecERjTC8hlaEUUbWFfMA2oGAyrGtn/h0ZrSZZQywBFZ+2rXM3er9U22Mn u6+9NLGKxOZHrTx81cYdxq4EclUiNzVkiEu54oaujpp9r1btHKt3ULcEIw0QK9// +QHWd6Zxn0VCqyJ+Dk/m5LTXCGAV0dzGnmZ0MvnOQDD0y2OjdnQQqKi+4fDPBFaF 5UfMtvOriXgUiTHF6/6IfyooQX4lFH2JtPVfdAW+OZ9w4fAy1ny0Bl26SYG+uUQ6 YQxc3PlNtatoVDr/wERxZm8L+pz0w3YIwC/6YE8zxaGnbXF6nJS2yByZxI8x3XpG 9Tfa4+g108fZN5+KjYEMRldTCiBwVZ+RrgbPaQupWJv7tNMaWMJeWa5bkaIO+XiU q3sNdlw72ylxMaz16RaqDsAGozUneOeItmkuhbCnhZ5Y00FEbup4dBu8fOZmza7K JpQseo+kzFLT93KZzAKvJD+5LJkRgqUeAqEZ+lyl7mTkvBTeUlnwC7ghhvvhbYi8 GK87uTlNSMQrQyEGB1tFJLmaWpYqf/VUZEf4CwQiKf+9ezNUv3V98jEH3i1/V3EC UrZnI+Ibz0RwDc2Tqniq =wYrq -----END PGP SIGNATURE-----

1 0

[release] pkgdb2: 2.0.2
by Pierre-Yves Chibon 21 Dec '15

21 Dec '15

Good Morning everyone, I just cut a new pkgdb release: 2.0.2 Here is the changelog: * Mon Dec 21 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.0.2-1 - Update to 2.0.2 - Fix the opensearch integration I just really wanted to fix this one before the holidays as it kinda really bothered me :) Now I can finally type `pkgdb <foo>` in my web-browser and get the results I want. Happy packaging, Pierre

1 0

[release] pkgdb2: 2.0.1
by Pierre-Yves Chibon 18 Dec '15

18 Dec '15

Good morning everyone, I just cut a new pkgdb release: 2.0.1, fixing bugs of the 2.0 release. Here is the changelog: * Fri Dec 18 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.0.1-1 - Update to 2.0.1 - Fix typo in a variable name that was making requesting a new package fail (Patrick Uiterwijk) - Fix giving ACLs to someone - Fix editing a new package request (where the request is not associated to any package) All the changes were made with new unit-tests to prevent future regression. Happy packaging, Pierre

1 0

[release] pkgdb2: 2.0
by Pierre-Yves Chibon 17 Dec '15

17 Dec '15

Good Morning everyone, I just cut a new pkgdb2 release: 2.0 The changelog is short but the PR leading to it pretty large: * Thu Dec 17 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.0-1 - Update to 2.0 - Add the concept of namespace to all the packages present in pkgdb2 And the PR (for the curious): https://github.com/fedora-infra/pkgdb2/pull/293 This is currently happily running in stg and is scheduled to be updated in prod later today. Happy packaging, Pierre

1 0

[release] MirrorManager2: 0.6 and 0.6.1
by Pierre-Yves Chibon 17 Dec '15

17 Dec '15

Good morning everyone, I just cut a new MirrorManager2 release: 0.6.1 which follows the 0.6 release of yesterday. Here is the changelog: * Thu Dec 17 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.6.1-1 - Update to 0.6.1 - Fix mirrorlist to access info from the just loaded pickle (Patrick Uiterwijk) * Wed Dec 16 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.6-1 - Update to 0.6 - Really ensure that new host is admin_active (Seth Jennings) - Add the possibility to kill rsync after some time - Add headers to the table listing the mirrors - Cascade deletion and bring back the rsyncFilter endpoint - Fix to the crawler (Adrian Reber) - Improved documentation and validation - Optionally exclude certain protocols from MM (Adrian Reber) - Import generate-worldmap from MM1 (Adrian Reber) - Optionally display mirrorlist statistics (Adrian Reber) - mirrorlist: Remove --debug option (Adrian Reber) - More mirrorlist statistics changes and spec file integration (Adrian Reber) - Switch the MirrorList server to use threading rather than forking (Patrick Uiterwijk) 0.6 is running in stg and Adrian is working on update it to 0.6.1. Happy mirroring, Pierre

1 0

Plan for tomorrow's Fedora Infrastructure meeting - 2015-12-17
by Kevin Fenzi 17 Dec '15

17 Dec '15

The infrastructure team will be having it's weekly meeting tomorrow, 2015-12-17 at 18:00 UTC in #fedora-meeting on the freenode network. 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 today is included in this email. If you have something to discuss, add the topic to the discussion area with your name. If you would like to teach other folks about some application or setup in our infrastructure, please add that topic and your name to the learn about section. 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-12-17) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson #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 [release] pkgdb2: 1.33.3 - Pierre-Yves - http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro… #info [release] pagure: 0.1.36 - Pierre-Yves - http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro… #info [release] fedmsg_meta_fedora_infrastructure: 0.15.6 - Ralph - http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro… #info New fedmsg message types - nagios and pungi-koji - Ralph #info Namespacing in pkgdb planned to go live on Thursday - Pierre-Yves/Ralph - http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro… #info more work on ansible 2.0 compatibility. Will likely switch to it full time once callback_plugins are working - kevin #info more work on making playbooks idempotent - kevin #info Many people on vacation next few weeks, check the vacation calendar before you look for someone - kevin #info No meetings on 24th and 31st. #info Smooge and Kevin at phx2 second week in jan - kevin/smooge = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus or decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use #topic your discussion topic - your username) #topic Technical Debt-Fighting Week 2016-01-05 through 2016-01-08 - Ralph #link https://fedoraproject.org/wiki/Infrastructure/Debt Just wanted to give another chance here to brainstorm things we want to work on. #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. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) Schedule: 2015-12-18 - ???? 2015-12-24 - no meeting 2015-12-31 - no meeting #topic Learn about: = Meeting end stuff = #topic Open Floor #endmeeting

1 0

[release] fedmsg_meta_fedora_infrastructure: 0.15.6
by Ralph Bean 16 Dec '15

16 Dec '15

Hello all! I'm cutting a new release of our fedmsg.meta plugins package. Notably it contains: - A new processor for the new pungi-koji messages that releng is publishing. - A new processor for the nagios messages we're publishing. - Some various bits and pieces that we'll end up using in fedora-hubs. 0.15.6 ------ Pull Requests - (@ralphbean) #343, Change text of mdapi subtitle. https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/343 - (@ralphbean) #344, Add some preliminary processors for the new pungi-koji compose stuff. https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/344 - (@ralphbean) #347, Remove the "markup" stuff. https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/347 - (@ralphbean) #346, Add a conglomerator for mailman3 messages. https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/346 - (@ralphbean) #348, Processor and handler for new nagios messages. https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/348

1 0

Namespacing in pkgdb
by Pierre-Yves Chibon 15 Dec '15

15 Dec '15

Hello everyone, The Fedora infrastructure and the release-engineering teams have worked together to begin to add namespacing to our infrastructure. The idea is that in a near future Fedora will distribute more than just rpms, such as docker containers but also other technologies that might arise [1]. For this, we have been working on a new version of pkgdb2 and a few adjustments to dist-git allowing to have a docker and a rpm with the same name but under different namespace. On Thursday December 17th, we would like to roll out this new release of pkgdb2. Currently, all your tools: fedpkg, pkgdb-cli, pkgdb-admin should work as they do today, all changes being backward compatible, but as for everything, there might be bugs. So we would appreciate if you could let us know as early as possible if you think you ran into one, either - here - on #fedora-admin on irc.freenode.net - via a ticket on https://fedorahosted.org/fedora-infrastructure/ If you want to see how the new pkgdb2 looks like, feel free to test our staging instance: https://admin.stg.fedoraproject.org/pkgdb/ Thank you for your help and understanding, Happy packaging, Pierre for the Fedora Infrastructure team [1] https://lists.fedoraproject.org/archives/list/devel%40lists.fedoraproject.o…

1 0

December status update for Fedora Infrastructure Apprentices
by Kevin Fenzi 15 Dec '15

15 Dec '15

Greetings. You are getting this email because you are in the 'fi-apprentice' group in the fedora account system (or are reading this on the infrastructure list). Feel free to reply just directly to me, or cc the infrastructure list for everyone to see and comment on. https://fedoraproject.org/wiki/Infrastructure_Apprentice At the first of every month(or so), I am going to be sending out an email like this one. I would like feedback on how things are going for you. I'd like to ask for everyone to send me a quick reply with the following data or anything related you can think of that might help us make the apprentice program more useful. 0. Whats your fedora account system login? 1. Have you logged in and used your fi-apprentice membership to look at our machines/setup in the last month? Do you plan to? 2. Has it helped you decide any area you wish to focus on or contribute to more? 3. Have you looked at or been able to work on any of the fi-apprentice 'easyfix' tickets? https://fedorahosted.org/fedora-infrastructure/report/14 4. Do you still wish to be a member of the group? If not (for whatever reason) could you provide any hints to help others down the road? 5. Is there any help or communication or ideas you have that would help you do any of the above? 6. What do you find to be the hardest part of getting involved? Finding things to work on? Getting attention from others to help you? Finding tickets in your interest area? 7. Have you been able to make any weekly irc meetings? Do you find them helpful or interesting? 8. Have you logged into our Gobby instance and read/seen/added to our meeting agenda? https://fedoraproject.org/wiki/Gobby 9. Did you know that we are going to be doing a 'technical debt cleanup' week on 2016-01-06 to 2016-01-09? See: https://fedoraproject.org/wiki/Infrastructure/Debt and come join us. Any other general feedback is also quite welcome, including improvements to this email, the wiki page, etc. Any folks I do not hear from in the next week will be removed from the group. (Note that it's easy to be readded when you have time or whatever and it's nothing at all personal, we just want to keep the group up to date with active folks). Thanks, and looking forward to your feedback! kevin

14 13

Re: Captcha is pretty hard to read
by Robert Mayr 14 Dec '15

14 Dec '15

2015-12-14 21:38 GMT+01:00 Joe Brockmeier <jzb(a)redhat.com>: > Hey all, > > So I encouraged a friend to sign up for a FAS account recently and the > feedback I got was that the captcha is nigh-unreadable. Example here: > > http://i.imgur.com/AasqKK8.png > > Since most of us don't sign up for new accounts on a regular basis I was > wondering if folks were aware how abstract the captcha has become? > > Best, > > jzb > -- > Joe Brockmeier | Community Team, OSAS > jzb(a)redhat.com | http://community.redhat.com/ > Twitter: @jzb | http://dissociatedpress.net/ > > > -- > websites mailing list > websites(a)lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org > Yes, I agree it's probably hard to read for a new Fedora user who wants to start contributing, and I also had to look twice to understand the math. Not sure how much we can do to improve the actual captcha without substituting it completely, so I'm copying in the Infra folks too to see if we can improve the readabilty in some way. Thanks. -- Robert Mayr (robyduck)

4 4

host_category_url_private
by Adrian Reber 14 Dec '15

14 Dec '15

This is mainly a question for Matt. Currently it seems there is a problem with newly added private mirrors that they never seem to appear in the mirrorlist. I am tracking this for the last few weeks, but I have not found the cause for this yet. As this problem does not yet seem very widely spread I did not spent too much time on it. Recently dl.phx2.fedoraproject.org has been added as a private mirror and it does not appear in the mirrorlist. I have now seen that a few URLs have the private flag set in host_category_url and I am wondering what it exactly means. I see that these URLs are not added to the mirrorlist servers as opposed to mirror sites/hosts which have the private flag set. I also do not see in MM2 where this flag can actually be changed and that's why I am wondering if we somehow set this flag by accident in certain situations and that maybe it had some different meaning in MM1. That's why I am hoping that maybe Matt remembers the idea behind this flag which enables marking URls as private. In MM2 it seems to be unused, besides that once it is enabled it cannot be disabled and URLs using it are therefore for ever blocked from the mirrorlist server. Adrian

1 1

[release] pagure: 0.1.36
by Pierre-Yves Chibon 14 Dec '15

14 Dec '15

Good morning everyone, I just cut and push a new pagure release: 0.1.36 Here is the corresponding changelog: * Mon Dec 14 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.36-1 - Update to 0.1.36 - Add the ssh info on the front page if the repo is empty - Make the code handling exception be python3 compatible - Make pagure compatible with F23 (ie: pygit2 0.23.0) - Fix pagination when rendering the repo blocks (Gaurav Kumar) - Make the SHOW_PROJECTS_INDEX list what should be showing in the index page - Adjust pagure to work on recent version of psutils as well as the old one - Added 'projects' to the blacklisted list of projects (Gaurav Kumar) - Removed delete icons for non group members on the group info page (Gaurav Kumar) - Fixed forbidden error for PR title editing (Gaurav Kumar) This might very well be the last release before 1.0. Happy hacking, Pierre

1 0

[release] pkgdb2: 1.33.3
by Pierre-Yves Chibon 11 Dec '15

11 Dec '15

Good Morning everyone, I just cut a new pkgdb2 release: 1.33.3. It's a simple bug fix release fixing processing new package requests in pkgdb (via pkgdb-admin). Here is the changelog: * Fri Dec 11 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.33.3-1 - Update to 1.33.3 - Fix processing new package requests Happy packaging! Pierre

1 0

Meeting Agenda Item: Introduction Jairo Chaves B.
by Jairo Chaves Brenes 10 Dec '15

10 Dec '15

Hello. My name is Jairo Chaves Brenes, and my irc handle is jchaves. I live in Costa Rica. I'm joining the project because I want to help to maintain a great distro as Fedora, also I want to increase my technical skills by learning new things at the same time I can put these skills in practice while I help the project and work alongside a very talented group of people. I just have only 2 years working on Linux as Jr. Sysadmin, I know a little bit of bash scripting, python, ansible, linux, nagios and some information security principles. I can contribute 3 hours at day. Best regards.

1 0

[release] pkgdb2: 1.33.2
by Pierre-Yves Chibon 10 Dec '15

10 Dec '15

Good Morning everyone, I just cut a new pkgdb2 release: 1.33.2. It's a simple bug fix release making the integration with bugzilla when requesting a new package work properly. Here is the changelog: * Thu Dec 10 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.33.2-1 - Update to 1.33.2 - Fix the bugzilla integration when requesting a new package in pkgdb Currently happily running in prod. Happy packaging, Pierre

1 0

Plan for tomorrow's Fedora Infrastructure meeting - 2015-12-10
by Kevin Fenzi 09 Dec '15

09 Dec '15

The infrastructure team will be having it's weekly meeting tomorrow, 2015-12-10 at 18:00 UTC in #fedora-meeting on the freenode network. 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 today is included in this email. If you have something to discuss, add the topic to the discussion area with your name. If you would like to teach other folks about some application or setup in our infrastructure, please add that topic and your name to the learn about section. 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-12-10) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson #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 [release] supybot-fedmsg: 0.2.0 - Ralph #link http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro… #info [release] nuancier 0.9.0 and 0.10.0 - Pierre-Yves #link http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro… #link http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro… #info [release] pkgdb2: 1.33.0 and 1.33.1 - Pierre-Yves #link http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro… #link http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro… #info Installed a rhel7 hosted01, we need to work on getting it ready to migrate hosted03 to - kevin #info New arm koji/db is ready to migrate to, hopefully soon - kevin #info Equalogics outage, all data safe and now we are updated on firmware - patrick #info REMINDER: no meetings on the 24th or 31st - everyone #info REMINDER: technical debt work week jan 5th to 8th - everyone #info REMINDER: smooge and nirik will be at phx jan 11th to 15th - nirik/smooge #info All Fedora hosts will now auto apply security updates daily - kevin #info ntp in phx2 now uses bastion01/02 everything else uses public rhel pool - kevin #info Our playbook almost all ansible 2.0 ready - kevin #info = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus or decision or just brainstorm a problem or issue. If there are none of these we skip this section. (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. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) Schedule: 2015-12-10 - ansible 2.0 - kevin 2015-12-18 - ???? 2015-12-24 - no meeting 2015-12-31 - no meeting #topic Learn about: ansible 2.0 - kevin = Meeting end stuff = #topic Open Floor About cloud sig group in infra cloud - kushal #endmeeting

1 0

Blog on Fedora Planet
by Dan Mossor 08 Dec '15

08 Dec '15

Ryan, I am writing to you in regards to your 'whatthefuck.computer' blog on the Fedora Planet aggregate blog. Fedora as a project aims to be family friendly, and I as a parent try to shield my kids as best I can from profanity (which seems to get harder every day). My children are being raised as open source advocates, and I have Fedora Magazine and Fedora Planet set as their home pages in their browsers. The problem is that when there is something from your blog posted on the Planet, the page is blocked due to key word filtering. I am respectfully requesting for you to either change the name of your blog, or voluntarily remove it from the Fedora Planet. Regards, Dan Mossor -- Dan Mossor, RHCSA Systems Engineer Fedora Server WG | Fedora KDE WG | Fedora QA Team Fedora Ambassador | Fedora CommOps FAS: dmossor IRC: danofsatx San Antonio, Texas, USA

1 0

[release] nuancier 0.10.0
by Pierre-Yves Chibon 08 Dec '15

08 Dec '15

Good morning everyone, I just cut a new release of nuancier: 0.10.0 Here is the changelog: * Tue Dec 08 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.10.0-1 - Update to 0.10.0 - Added progress bar when uploading candidates file (Gaurav Kumar) - Fix the URLs pointing where jquery and lightbox (broken with the lightbox update) With the work of Gaurav, the list of tickets opened against nuancier is down to: 1 \ó/. Nuancier 0.10.0 is happily running in stg and prod. Happy wallpaper hunting! Pierre

1 0

[release] pkgdb2: 1.33.1
by Pierre-Yves Chibon 07 Dec '15

07 Dec '15

Good morning everyone, I just cut a new pkgdb2 release: 1.33.1. Here is the changelog: * Mon Dec 07 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.33.1-1 - Update to 1.33.1 - Fix the API listing the packages to make it return the ACLs if asked to This fix was discovered when hacking on pdc-updater and fixing it will make writing tests for pdc-updater much easier :) Happy packaging! Pierre

1 0

hyperkitty thinks trac@fedorahosted.org is "fedora-badges" ... or is it "FESCo Trac"?
by Matthew Miller 07 Dec '15

07 Dec '15

See https://lists.fedoraproject.org/archives/list/council-discuss%40lists.fedor… confusingly attributed to "fedora-badges". But click on that name, and now it's "FESCo Trac". Obviously none of these are correct. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

3 2

[PATCH] Add defaults var for fas_client
by Nicolas Chauvet 07 Dec '15

07 Dec '15

--- roles/fas_client/defaults/main.yml | 8 ++++++++ roles/fas_client/templates/fas.conf.j2 | 8 ++++---- 2 files changed, 12 insertions(+), 4 deletions(-) create mode 100644 roles/fas_client/defaults/main.yml diff --git a/roles/fas_client/defaults/main.yml b/roles/fas_client/defaults/main.yml new file mode 100644 index 0000000..f0983d2 --- /dev/null +++ b/roles/fas_client/defaults/main.yml @@ -0,0 +1,8 @@ +--- +# defaults file for fas_client +# + +fas_url: https://admin.fedoraproject.org/accounts/ +fas_staging_url: https://admin.stg.fedoraproject.org/accounts/ +fas_home: /home/fedora +fas_home_backup_dir: "{{ fas_home }}.bak" diff --git a/roles/fas_client/templates/fas.conf.j2 b/roles/fas_client/templates/fas.conf.j2 index a27f0ef..995c8e1 100644 --- a/roles/fas_client/templates/fas.conf.j2 +++ b/roles/fas_client/templates/fas.conf.j2 @@ -1,9 +1,9 @@ [global] ; url - Location to fas server {% if env == "staging" %} -url = https://admin.stg.fedoraproject.org/accounts/ +url = {{ fas_url }} {% else %} -url = https://admin.fedoraproject.org/accounts/ +url = {{ fas_staging_url }} {% endif %} ; temp - Location to generate files while user creation process is happening @@ -59,11 +59,11 @@ aliases_template = /etc/aliases.template shell = /bin/bash ; home - the location for fas user home dirs -home = /home/fedora +home = {{ fas_home }} ; home_backup_dir - Location home dirs should get moved to when a user is ; deleted this location should be tmpwatched -home_backup_dir = /home/fedora.bak +home_backup_dir = {{ fas_home_backup_dir }} ; ssh_restricted_app - This is the path to the restricted shell script. It ; will not work automatically for most people though through alterations it -- 1.7.2.1

2 4

State of python3 in our infrastructure
by Pierre-Yves Chibon 05 Dec '15

05 Dec '15

Good morning everyone, I would like to start gathering our thoughts about python3 in our apps. To my knowledge, we currently have two applications that are python3 (only): - Mailman3 core (as in hyperkitty is still py2) - mdapi Both are *not* running via apache/mod_wsgi. MM3 runs on RHEL7 while mdapi runs on a Fedora node for the moment. So, what do we think about python3 app in our infrastructure? Are we ok with it? Do we want to avoid them for the moment? Do we want to split 'backend' vs 'frontend' (ie web-apps)? What brings me to raise these questions is that I have spent my morning getting pagure to run on pygit2 0.23.0 (the version present on F23) so that I can upgrade my laptop still running F21 atm. The result of this work is not pretty: https://pagure.io/pagure/pull-request/516 (and might still require some work, just the tests are passing at the moment, I would not be surprised if I missed some things in the templates). I am more and more thinking about replacing pygit2 and a friend of mine is developing a potentially really interesting alternative: maggit: https://gitlab.com/maggit/maggit However, maggit is python3 only. But the pain of dealing with pygit2 is such that I have been considering looking more into maggit and maybe porting pagure to it (which means porting pagure to python3, already checked, all of its dependencies are py3 ready). Before I consider such effort (which would be a 2.0 release), I want to clarify the status of python3 web-apps. So what do you folks think? :) Thanks, Pierre

9 12

Meeting Agenda Item: Introduction Matthew McCleary
by Matthew S. McCleary 04 Dec '15

04 Dec '15

Greetings, Infrastructure folks. I'm interested in contributing time to the effort. Family and work are both okay with the idea. My IRC nick is flainn. I'm a (well, really "the") Linux sysadmin for the US Bureau of Indian Affairs (contractor, not a Fed), doing almost exclusively CentOS work, but running Fedora on my own systems. I'm a fairly strong Linux admin, and not much of a programmer. I do a lot of patch management work (mostly with Spacewalk), monitoring (Zabbix), provisioning new VMs, and other stuff as needed here at BIA. I'd be interested in storage work, patching, virtualization, or really wherever I can help out. Looking forward to helping. Thanks, Matthew -- Matthew McCleary KF5VUD voice 505.886.1732

2 1

[release] pkgdb2: 1.33.0
by Pierre-Yves Chibon 04 Dec '15

04 Dec '15

Good morning everyone, Because releases on a Friday evening is always a good idea, I just cut a new pkgdb2 release: 1.33.0 Here is the changelog: * Fri Dec 04 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.33.0-1 - Update to 1.33.0 - Strip the input (if there is one) when a new package is requested (avoids trailing spaces typo) - Add a link to the package once the action has been approved (trishnaguha & pingou) - Improve the checks to the package review on bugzilla before letting it through - Limit the size of the content section (avoids the overlap with the options box) - When un-retiring a package, request the review_url - Mention postgresql-devel dependency (Till Maas and Ralph Bean) - Let the user update request to unretire to `Awaiting Review` - Restrict the branches proposed to un-retire to the last two Fedora releases - Perform more checks around the fedora-review flag when syncing info from bugzilla - Making sure admins are made aware that changing a status does not process the request - When approving a new package, process the new Fedora branch requests as well Seems to be happily running in stg, will update prod later. Happy packaging! Pierre

1 0

[release] nuancier 0.9.0
by Pierre-Yves Chibon 04 Dec '15

04 Dec '15

Good morning everyone, I just cut a new release of nuancier: 0.9.0 Here is the changelog: * Fri Dec 04 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.9.0-1 - Update to 0.9.0 - Adjust the url to faitout for the tests - Fix incorrect FAS URLs in the templates (Micah Abbott) - Show the end of the submission period on the contribute page (farhaanbukhsh) - Order the election by the date of publication of their results (Vivek Anand) - Adjust the header of the table listing the elections - Near the vote button show the end date of the election - Update the "Denied submissions" page to become a "Your submissions" page - Have one page per submissions status, allowing easier come-back - Limit the number of uploads per person - Bug fixes from Gaurav Kumar and Sayan Chowdhury - Change behavior on the voting page (Default to zoom, don't remove candidate when voting on it) - Update to the latest lightbox Currently happily running in stg, will update prod later. Thanks, Pierre

1 0

[release] supybot-fedmsg: 0.2.0
by Ralph Bean 04 Dec '15

04 Dec '15

Here's a fix for the supybot fedmsg plugin that was written back in June(!) but never got released or deployed. The bug: whenever we start up zodbot, there's a race condition big enough to drive a truck through. The fedmsg plugin tries to wrap the meetbot plugin, but often the meetbot plugin gets loaded after fedmsg.. and so it fails. This patch causes the fedmsg plugin to retry indefinitely (every 60s) until it succeeds. As a side-effect, this will likely help address many of the complaints we've had recently about meeting logs not being available in the new 'mote' web interface. They tend to not show up because zodbot didn't produce a fedmsg which didn't force mote to flush its cache. 0.2.0 ----- Pull Requests - (@ralphbean) #10, Try again later when we're unable to wrap meetbot. https://github.com/fedora-infra/supybot-fedmsg/pull/10 Commits - e0d52bc23 Try again later when we're unable to wrap meetbot. https://github.com/fedora-infra/supybot-fedmsg/commit/e0d52bc23

2 1

[release] bodhi: 2.1.4
by Luke Macken 03 Dec '15

03 Dec '15

Hi folks, I pushed a new version of Bodhi to production yesterday. This contains a few small bug fixes, additional {submitted,modified,approved,pushed}_before query parameters, as well as a masher enhancement to fix a tagging bug that can happen when 2 builds for the same package get pushed at the same time. Happy hacking, luke 2.1.4 ----- Pull Requests - (@AdamWill) #716, query: add _before params matching the _since params https://github.com/fedora-infra/bodhi/pull/716 - (@ralphbean) #719, client - handle case where "total" not in the response. https://github.com/fedora-infra/bodhi/pull/719 - (@lmacken) #720, masher: Iterate over the status results generator https://github.com/fedora-infra/bodhi/pull/720 - (@lmacken) #721, models: Don't reset the `pushed` and `date_pushed` flags upon request. https://github.com/fedora-infra/bodhi/pull/721 - (@lmacken) #722, Tag multiple builds for the same package synchronously. https://github.com/fedora-infra/bodhi/pull/722 Commits - bc322093b query: add _before params matching the _since params https://github.com/fedora-infra/bodhi/commit/bc322093b - bc8a4220a No longer need the old createrepo system lib. https://github.com/fedora-infra/bodhi/commit/bc8a4220a - 0ffa0de05 client - handle case where "total" not in the response. https://github.com/fedora-infra/bodhi/commit/0ffa0de05 - 64d71354d masher: Iterate over the status results generator https://github.com/fedora-infra/bodhi/commit/64d71354d - 9d8d79afc models: Don't reset the `pushed` and `date_pushed` flags upon request. https://github.com/fedora-infra/bodhi/commit/9d8d79afc - 9e6e825a3 models: Don't reset the `pushed` and `date_pushed` flags upon request. https://github.com/fedora-infra/bodhi/commit/9e6e825a3 - b65514bde Merge branch 'develop' of github.com:fedora-infra/bodhi into develop https://github.com/fedora-infra/bodhi/commit/b65514bde - 9b6996981 masher: Tag multiple builds for the same package synchronously. https://github.com/fedora-infra/bodhi/commit/9b6996981 - 21a49ef32 bootstrap: Try linking in the system PIL, which might fix our Jenkins builds? https://github.com/fedora-infra/bodhi/commit/21a49ef32

1 0

Request for resources: Bugyou
by Sayan Chowdhury 03 Dec '15

03 Dec '15

Hi, I have filed a RFR[0] for Bugyou Bugyou files issues for failed tests from autocloud. Bugyou is part of Fedora Project. It listens to autocloud messages from fedmsg and files bug for images which have failed the tests. Bugyou keeps updating the status of the images in the bug and closes the issue once the tests are successful. The documentation can seen here[1] [0] https://fedorahosted.org/fedora-infrastructure/ticket/5012 [1] http://bugyou.readthedocs.org/en/latest/ -- Sayan Chowdhury sayanchowdhury.dgplug.org | sayan.chowdhury2012(a)gmail.com

1 0

[PATCH] Add defaults var for fas_client
by Nicolas Chauvet 03 Dec '15

03 Dec '15

v2: fix inverted fas_staging_url/fas_url --- roles/fas_client/defaults/main.yml | 8 ++++++++ roles/fas_client/templates/fas.conf.j2 | 8 ++++---- 2 files changed, 12 insertions(+), 4 deletions(-) create mode 100644 roles/fas_client/defaults/main.yml diff --git a/roles/fas_client/defaults/main.yml b/roles/fas_client/defaults/main.yml new file mode 100644 index 0000000..f0983d2 --- /dev/null +++ b/roles/fas_client/defaults/main.yml @@ -0,0 +1,8 @@ +--- +# defaults file for fas_client +# + +fas_url: https://admin.fedoraproject.org/accounts/ +fas_staging_url: https://admin.stg.fedoraproject.org/accounts/ +fas_home: /home/fedora +fas_home_backup_dir: "{{ fas_home }}.bak" diff --git a/roles/fas_client/templates/fas.conf.j2 b/roles/fas_client/templates/fas.conf.j2 index a27f0ef..2824339 100644 --- a/roles/fas_client/templates/fas.conf.j2 +++ b/roles/fas_client/templates/fas.conf.j2 @@ -1,9 +1,9 @@ [global] ; url - Location to fas server {% if env == "staging" %} -url = https://admin.stg.fedoraproject.org/accounts/ +url = {{ fas_staging_url }} {% else %} -url = https://admin.fedoraproject.org/accounts/ +url = {{ fas_url }} {% endif %} ; temp - Location to generate files while user creation process is happening @@ -59,11 +59,11 @@ aliases_template = /etc/aliases.template shell = /bin/bash ; home - the location for fas user home dirs -home = /home/fedora +home = {{ fas_home }} ; home_backup_dir - Location home dirs should get moved to when a user is ; deleted this location should be tmpwatched -home_backup_dir = /home/fedora.bak +home_backup_dir = {{ fas_home_backup_dir }} ; ssh_restricted_app - This is the path to the restricted shell script. It ; will not work automatically for most people though through alterations it -- 1.7.2.1

1 0

Badges for translations contribution
by Alex Eng 03 Dec '15

03 Dec '15

Hi I'm Alex from Zanata team. We've recently discussed on getting Zanata webhook to trigger event for Fedora badges. Just wondering who is the best person to talk to? 1) What sort of details does Zanata need to include in the event? 2) Any test instance which we can test the event on? --------------------------------------------- Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com

3 5

Group vars for tasktotron- prod stg and dev
by David Shier 02 Dec '15

02 Dec '15

Patches attached. Thanks, Dave Shier

3 6

Migration to HyperKitty / Mailman 3
by Aurelien Bompard 02 Dec '15

02 Dec '15

Hi people! Since it's Friday evening, I just unilateraly decided to migrate all the lists to Mailman3 without telling you anything in advance... Nah just kidding :-) However, I think the best time to migrate the rest of the lists would be the week before Thanksgiving. That would give me some time with you all around to fix the most urgent problems, and time for me during a week with less activity in the US to fix the lower priority ones. Some lists are still using the two features that are not yet ported, namely the filters and the topics. Those lists would stay on the current server for now, but migrating the rest would still be an improvement. This would mean migration would start on November 16th. What do you think? I'm also trying to write an announcement for the lists (like devel-announce), but I'm looking for a native english speaker to help me with that. It would be something like : ---------------- Dear list users, The Fedora Engineering team has been working on a new system for our mailing lists. Mailman 3 came out earlier this year and it has a new shiny web UI: HyperKitty. The Fedora project lists will be migrated starting November 16th. You on't have to use the new UI to keep participating in the mailing-lists, but the change to Mailman 3 may cause issues with the way you filter your email. Here are a few things you should expect after this change, especially if you're using procmail for filtering: http://fedoraproject.org/wiki/Mailman3_Migration. But it should mostly work as before. A link to HyperKitty will be included in the email footers when your list is migrated. Some lists which use Mailman 2.1's advanced filtering capabilities (by header or by topic) will remain on the current version until these features are ported to Mailman 3. If you have any questions, feel free to ask on the infrastructure list: infrastructure(a)lists.fedoraproject.org. ------------------ Am I missing important information? Feel free to reword things if they are not clear or if it's just bad style. Thanks ! Aurélien

8 15

Looks like EOL script was run with the wrong close reason
by Matthew Miller 02 Dec '15

02 Dec '15

Seems like everything got "CLOSED:WONTFIX" instead of "CLOSED:EOL". I suppose it's not worth creating double churn to correct that, but it makes me sad. What needs to change to make sure it happens the right way next time? -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

[Meetbot] Links to HTML reports are broken
by Charles-Antoine Couret 01 Dec '15

01 Dec '15

Hi all, Since one week, links to meetbot logs were broken. Only the full text page was correct. For example, after this evening meeting: https://meetbot.fedoraproject.org/fedora-meeting-1/2015-11-30/fedora-fr.201… https://meetbot.fedoraproject.org/fedora-meeting-1/2015-11-30/fedora-fr.201… https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2015-11-30/fedora-fr… Before the 2 last meetings, I don't have a similar issue. Do you think it's a infra trouble or a meetbot upstream bug? I don't find a recent opened bug about that. Thank you in advance. Charles-Antoine Couret

3 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure December 2015