infrastructure April 2017

infrastructure@lists.fedoraproject.org

50 participants
45 discussions

Start a nNew thread

Meeting Agenda Item: Michael O'Brien
by Michael OBrien 19 Apr '17

19 Apr '17

1 0

Bodhi 2.6.0 beta 0
by Randy Barlow 17 Apr '17

17 Apr '17

Bodhi 2.6.0b0 has been deployed to staging[0]. Release notes are available in its docs[1]. Enjoy! [0] https://bodhi.stg.fedoraproject.org/ [1] https://bodhi.stg.fedoraproject.org/docs/release_notes.html#id1

1 0

Weekly Koji Infra Tag Report
by Nobody 16 Apr '17

16 Apr '17

This is a list of packages in the various infrastructure koji tags Please check and make sure there are not any that can be removed/dropped epel6-infra (no matching packages) epel7-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- freeipa-ktutils epel7-infra puiterwijk compose-utils epel7-infra ausil fedmsg-beaker-repoupdate epel7-infra tflink anitya epel7-infra jcline the-new-hotness epel7-infra jcline fedocal epel7-infra pingou python-IPy epel7-infra kevin python-robosignatory epel7-infra puiterwijk pdc-updater epel7-infra ralph python-pdc epel7-infra ralph glusterfs epel7-infra kevin mirrormanager2 epel7-infra puiterwijk blockerbugs epel7-infra tflink python-django-jsonfield epel7-infra ralph f23-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- libphutil, f23-infra tflink arcanist, f23-infra tflink phabricator f23-infra tflink phabricator-extension-ipsilonauth f23-infra tflink libphutil f23-infra tflink arcanist f23-infra tflink f24-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- mediawiki-openid f24-infra kevin phabricator-extension-oauth f24-infra tflink python-twill f24-infra codeblock stickynotes2modernpaste f24-infra codeblock python-flask-testing f24-infra codeblock modern-paste f24-infra codeblock mediawiki-skin-fedora f24-infra puiterwijk mediawiki-FedoraBadges f24-infra kevin basset f24-infra puiterwijk phabricator f24-infra tflink mediawiki-Lockdown f24-infra kevin libphutil f24-infra tflink arcanist f24-infra tflink mediawiki-RSS f24-infra kevin mirrormanager2 f24-infra puiterwijk f25-infra Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- python-flask-testing f25-infra codeblock modern-paste f25-infra codeblock python-coveralls f25-infra codeblock mdapi f25-infra pingou basset f25-infra puiterwijk mediawiki-FedoraBadges f25-infra kevin mediawiki-Lockdown f25-infra kevin mediawiki-RSS f25-infra kevin mediawiki-openid f25-infra kevin plus-plus-service f25-infra pingou python-pdc f25-infra ralph python-django-cors-headers f25-infra ralph python-django-rest-framework-composed-permissions f25-infra ralph patternfly1 f25-infra ralph fas f25-infra kevin libphutil, f25-infra tflink arcanist, f25-infra tflink phabricator f25-infra tflink phabricator-extension-ipsilonauth f25-infra tflink libphutil f25-infra tflink arcanist f25-infra tflink python-twill f25-infra codeblock stickynotes2modernpaste f25-infra codeblock mediawiki-skin-fedora f25-infra kevin f26-infra (no matching packages) f27-infra (no matching packages)

1 0

Re: Subscription lists
by Misha S. 16 Apr '17

16 Apr '17

It is still happening. Error 503 Backend fetch failed Backend fetch failed Guru Meditation: XID: 16073665 Varnish cache server Also, "Automatic responses" settings won't save. "An error occured: A server error occurred. Please contact the administrator.” Also, “Mailman settings” in the profile drop-down won’t open for me. Best regards, Misha https://fedoraproject.org/wiki/User:Shnurapet English / Español / Italiano / Русский

1 0

Re: April status update for Fedora Infrastructure Apprentices
by Aurelie Deromedis 14 Apr '17

14 Apr '17

Hi, I guess my reply it's a bit too late. I've started in a new role (Salesforce) last week and I've been quite busy since then. I guess my apprentice account has been disabled? I hope not tbh. I should be able to get back on track in the next few weeks. Have a good day, Aurelie On 3 April 2017 at 19:04, Kevin Fenzi <kfenzi(a)redhat.com> wrote: > 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://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix > > > 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. Have you used any containers in the last week or so? > (docker, rocket, etc) > > Any other general feedback is also quite welcome, including improvements > to this email, the wiki page, etc. Note that we recently revamped the > getting started and other pages. Please do take a minute to re-read them > and let me know if they are more clear or need further adjustments. > > 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 >

2 1

Plans for a new mirrormanager release
by Adrian Reber 14 Apr '17

14 Apr '17

I would like to update MirrorManager to the latest version before the next freeze to get the some of the fixes in git and new features running in production. The biggest change is the change in update-master-directory-list to support master server scanning based on fullfiletimelist-* Basically this remove the need of any I/O on the master mirror as it relies on the information provided in the fullfiletimelist-* files. This reduces the scan time of the master mirror from multiple hours to 20 minutes: https://github.com/fedora-infra/mirrormanager2/pull/207 The changes in this PR are probably hard to review but I tested it in staging and it seems to do the right thing. So if anyone could have a look at this PR to see if there are any obvious errors I could merge this PR and make a release to get it running in production some time before the beta freeze to make sure it works as desired before the freeze. Adrian

1 0

Fwd: reuse space on retrace02 for retrace01
by Miroslav Suchý 13 Apr '17

13 Apr '17

FYI -------- Přeposlaná zpráva -------- Předmět: reuse space on retrace02 for retrace01 Datum: Thu, 13 Apr 2017 16:07:37 +0200 Od: Miroslav Suchý <msuchy(a)redhat.com> Společnost: Red Hat Czech s.r.o. Komu: abrt-devel-list(a)redhat.com Hi, for Fedora we have two servers: retrace01.qa.fedoraproject.org retrace02.qa.fedoraproject.org retrace.fedoraproject.org is alias for retrace01. retrace02 is used for devel purposes. And according my quick search it is not used. Well the only use is for storing daily DB backups. We have daily backups since 2015 and it takes 3.8 TB! We have two other staging servers one for faf and other for retrace. I plan to delete those daily backups. Which will give us 8 TB free space on retrace02. On the retrace01 we are all the time on 99% of used storage so we need some space. I propose to install glusterFS on retrace01,02 and use the concated space on retrace01. This will gave us more space and we would be able to enable retrace for armhpf too. Unless there is some objections I will work on that next week. -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys

1 0

Fwd: fedmsg error log badges-backend01.phx2.fedoraproject.org
by Justin W. Flory 13 Apr '17

13 Apr '17

Hi all, I had about 150-200 of these emails come in over the last few minutes. Is there any kind of action we can take to quiet these down or get to the bottom of what's causing them? This also happens intermittently outside of the past 30 minutes too. Thanks! -------- Forwarded Message -------- Subject: fedmsg error log badges-backend01.phx2.fedoraproject.org Date: Mon, 10 Apr 2017 23:41:09 -0000 From: fedmsg(a)fedoraproject.org To: sysadmin-badges-members(a)fedoraproject.org Message ------- [2017-04-10 23:41:09][moksha.hub ERROR] ```python Couldn't talk to pkgdb2 for u'mbs/mbs.fedoraproject.org', 404, u'<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">\n<title>404 Not Found</title>\n<h1>Not Found</h1>\n<p>The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.</p>\n' ``` Process Details --------------- - host: badges-backend01.phx2.fedoraproject.org - PID: 31829 - name: fedmsg-hub - command: /usr/bin/python /usr/bin/fedmsg-hub - msg_id: 2017-18d2a3e1-2cb0-45a2-97d8-aba549a4e8fb Callstack that lead to the logging statement -------------------------------------------- ```python File "/usr/lib64/python2.7/threading.py", line 784 in __bootstrap self.__bootstrap_inner() File "/usr/lib64/python2.7/threading.py", line 811 in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 764 in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/twisted/python/threadpool.py", line 167 in _worker result = context.call(ctx, function, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/twisted/python/context.py", line 118 in callWithContext return self.currentContext().callWithContext(ctx, func, *args, **kw) File "/usr/lib64/python2.7/site-packages/twisted/python/context.py", line 81 in callWithContext return func(*args,**kw) File "/usr/lib/python2.7/site-packages/moksha/hub/api/consumer.py", line 191 in _work self.consume(message) File "/usr/lib/python2.7/site-packages/fedbadges/consumers.py", line 237 in consume for recipient in badge_rule.matches(msg): File "/usr/lib/python2.7/site-packages/fedbadges/rules.py", line 236 in matches if not self.criteria.matches(msg): File "/usr/lib/python2.7/site-packages/fedbadges/utils.py", line 94 in inner return method(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/fedbadges/rules.py", line 368 in matches child.matches(msg) for child in self.children File "/usr/lib/python2.7/site-packages/fedbadges/rules.py", line 66 in <lambda> "not": lambda x: all([not item for item in x]) File "/usr/lib/python2.7/site-packages/fedbadges/rules.py", line 368 in <genexpr> child.matches(msg) for child in self.children File "/usr/lib/python2.7/site-packages/fedbadges/utils.py", line 96 in inner log.exception(e) ``` Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/fedbadges/utils.py", line 94, in inner return method(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/fedbadges/rules.py", line 371, in matches return self.specialization.matches(msg) File "/usr/lib/python2.7/site-packages/fedbadges/rules.py", line 418, in matches user=expectation['user'], File "/usr/lib/python2.7/site-packages/fedbadges/utils.py", line 145, in get_pkgdb_packages_for return _getter(user) File "/usr/lib/python2.7/site-packages/dogpile/cache/region.py", line 1053, in decorate should_cache_fn) File "/usr/lib/python2.7/site-packages/dogpile/cache/region.py", line 657, in get_or_create async_creator) as value: File "/usr/lib/python2.7/site-packages/dogpile/core/dogpile.py", line 158, in __enter__ return self._enter() File "/usr/lib/python2.7/site-packages/dogpile/core/dogpile.py", line 98, in _enter generated = self._enter_create(createdtime) File "/usr/lib/python2.7/site-packages/dogpile/core/dogpile.py", line 149, in _enter_create created = self.creator() File "/usr/lib/python2.7/site-packages/dogpile/cache/region.py", line 625, in gen_value created_value = creator() File "/usr/lib/python2.7/site-packages/dogpile/cache/region.py", line 1049, in creator return fn(*arg, **kw) File "/usr/lib/python2.7/site-packages/fedbadges/utils.py", line 143, in _getter return _get_pkgdb2_packages_for(config, user) File "/usr/lib/python2.7/site-packages/fedbadges/utils.py", line 166, in _get_pkgdb2_packages_for data = _get_page(1) File "/usr/lib/python2.7/site-packages/fedbadges/utils.py", line 159, in _get_page username, req.status_code, req.text)) IOError: Couldn't talk to pkgdb2 for u'mbs/mbs.fedoraproject.org', 404, u'<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">\n<title>404 Not Found</title>\n<h1>Not Found</h1>\n<p>The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.</p>\n'

2 2

Plan for tomorrow's Fedora Infrastructure meeting 2017-04-13
by Stephen John Smoogen 12 Apr '17

12 Apr '17

The infrastructure team will be having it's weekly meeting tomorrow, 2017-04-13 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. = Introduction = 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 (2017-04-13) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 dgilmore threebean pingou puiterwijk pbrobinson = Let new people say hello = #topic New folks introductions = 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 hosted03 has had final systems removed #info beta freeze will start 2017-05-17 = 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 /suor 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 Upcoming Hackathon #info https://fedoraproject.org/wiki/CI_and_Infrastructure_Hackathon_2017 #info core members will be less available. #info focus on modularity #topic Clean out the backlog of tickets #info Put in a day for going through old tickets #info Triage and clean out old tickets #info Goal bring it down to 40 tickets = Apprentice office hours = #topic Apprentice Open office hours Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. = Learn about some application or gsetup 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 i/nfo 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.) #topic Learn about: SSH and where its going. = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

Re: SSH Key types
by Zach Villers 12 Apr '17

12 Apr '17

Thanks Patrick! -- Zach Villers zach(a)znix.site On Wed, Apr 12, 2017, at 02:28 PM, Patrick Uiterwijk wrote: > Hi all, > > As of right now, we are allowing SSH ECDSA and ed25519 keys to be used > in the Fedora Account System. > However, I would *strongly* suggest infrastructure team members to > *not* use either of those, because that would prevent you from > accessing any of the remaining RHEL6 machines[1] we still have. > > The reason this has been changed now is because we shut off hosted03, > which was the final server that non-infra folks have SSH access to. > > Regards, > Patrick > > > [1]: https://fedoraproject.org/wiki/Infrastructure/RHEL6_hosts > _______________________________________________ > infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-leave(a)lists.fedoraproject.org

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure April 2017