infrastructure January 2019

infrastructure@lists.fedoraproject.org

37 participants
41 discussions

Outage 2019-02-02 13:00 UTC -> 15:00 UTC
by Stephen John Smoogen 30 Jan '19

30 Jan '19

This outage is a replacement of an earlier one in December which had to be cancelled. There will be an outage starting at 2019-02-02 13:00 UTC, which will last approximately 2 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-02-02 13:00UTC' Reason for outage: Various switches at the colocation are needing updates and reboots to get latest firmware working. While the outage should not take the entire 2 hours, it is being blocked out in case there are problems which are not realized and need backing out or other changes. Affected Services: dl.fedoraproject.org all build services most web services copr and all other cloud services. Ticket Link: https://pagure.io/fedora-infrastructure/issue/7535 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

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

30 Jan '19

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

1 0

Mirror Syncing Problem
by Riseops 28 Jan '19

28 Jan '19

We've been trying to sync using the quick-fedora-mirror script but we're getting the error below: - When syncing from dl.fedoraproject.org rsync: link_stat "/fedora-epel/fullfiletimelist-fedora-epel" (in fedora-buffet) failed: No such file or directory (2) delta-transmission enabled @ .d fedora/ @ .f fedora/fullfiletimelist-fedora rsync[13676] (receiver) heap statistics: arena: 135168 (bytes from sbrk) ordblks: 2 (chunks not in use) smblks: 0 hblks: 2 (chunks from mmap) hblkhd: 532480 (bytes from mmap) allmem: 667648 (bytes from sbrk + mmap) usmblks: 0 fsmblks: 0 uordblks: 61744 (bytes used) fordblks: 73424 (bytes free) keepcost: 64080 (bytes in releasable chunk) rsync[13674] (generator) heap statistics: arena: 135168 (bytes from sbrk) ordblks: 2 (chunks not in use) smblks: 0 hblks: 2 (chunks from mmap) hblkhd: 532480 (bytes from mmap) allmem: 667648 (bytes from sbrk + mmap) usmblks: 0 fsmblks: 0 uordblks: 61680 (bytes used) fordblks: 73488 (bytes free) keepcost: 64080 (bytes in releasable chunk) Number of files: 2 Number of files transferred: 0 Total file size: 207662866 bytes Total transferred file size: 0 bytes Literal data: 0 bytes Matched data: 0 bytes File list size: 66 File list generation time: 0.295 seconds File list transfer time: 0.000 seconds Total bytes sent: 120 Total bytes received: 221 sent 120 bytes received 221 bytes 75.78 bytes/sec total size is 207662866 speedup is 608982.01 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1518) [generator=3.0.9] +do_rsync:43> rvbash='' rvzsh=23 rr=23 +do_rsync:55> (( rr == 0 )) +do_rsync:57> (( rr == 24 )) +do_rsync:60> (( rr == 5 || rr == 10 || rr == 23 || rr == 30 || rr == 35 )) +do_rsync:62> (( runcount >= MAXRETRIES )) +do_rsync:68> sleep=32 +do_rsync:69> logit e 'rsync returned 23 (retryable), sleeping for 32' +logit:2> local 'item=e' +logit:3> shift +logit:4> local 'err=' +logit:5> [[ e == E ]] +logit:6> [[ e == e ]] +logit:6> err=Err: +logit:8> [[ $LOGITEMS -regex-match $item ]] +logit:9> logwrite Err: 'rsync returned 23 (retryable), sleeping for 32' +logwrite:2> [[ -n '' ]] +logwrite:4> [[ -n /var/log/mirror/quick-fedora-mirror.log && -w /var/log/mirror/quick-fedora-mirror.log ]] +logwrite:5> date '+%b %d %T' +logwrite:5> echo 'Jan 25 00:32:00' Err: 'rsync returned 23 (retryable), sleeping for 32' +logit:11> (( VERBOSE >= 3 )) +logit:12> db3 Log: Err: 'rsync returned 23 (retryable), sleeping for 32' +db3:0> (( VERBOSE >= 3 )) +db3:0> echo '>>' Log: Err: 'rsync returned 23 (retryable), sleeping for 32' >> Log: Err: rsync returned 23 (retryable), sleeping for 32 +do_rsync:70> db2 rsync failed: sleeping for 32 +db2:0> (( VERBOSE >= 2 )) +db2:0> echo rsync failed: sleeping for 32 rsync failed: sleeping for 32 - When syncing from a Tier1 mirror with a fedora-buffet module, e.g. mirrors.kernel.org opening tcp connection to mirrors.kernel.org port 873 sending daemon args: --server --sender -vvlHogDtpRSze.Lsf --files-from=- --from0 . fedora-buffet/ MOTD: MOTD: Welcome to the Linux Kernel Archive. MOTD: MOTD: Due to U.S. Exports Regulations, all cryptographic software on this MOTD: site is subject to the following legal notice: MOTD: MOTD: This site includes publicly available encryption source code MOTD: which, together with object code resulting from the compiling of MOTD: publicly available source code, may be exported from the United MOTD: States under License Exception "TSU" pursuant to 15 C.F.R. Section MOTD: 740.13(e). MOTD: MOTD: This legal notice applies to cryptographic software only. MOTD: Please see the Bureau of Industry and Security, MOTD: http://www.bis.doc.gov/ for more information about current MOTD: U.S. regulations. MOTD: rsync: link_stat "/fedora-epel/fullfiletimelist-fedora-epel" (in fedora-buffet) failed: No such file or directory (2) delta-transmission enabled @ .d fedora/ @ .f fedora/fullfiletimelist-fedora rsync[14041] (receiver) heap statistics: arena: 135168 (bytes from sbrk) ordblks: 2 (chunks not in use) smblks: 0 hblks: 2 (chunks from mmap) hblkhd: 532480 (bytes from mmap) allmem: 667648 (bytes from sbrk + mmap) usmblks: 0 fsmblks: 0 uordblks: 61728 (bytes used) fordblks: 73440 (bytes free) keepcost: 64080 (bytes in releasable chunk) rsync[14039] (generator) heap statistics: arena: 135168 (bytes from sbrk) ordblks: 2 (chunks not in use) smblks: 0 hblks: 2 (chunks from mmap) hblkhd: 532480 (bytes from mmap) allmem: 667648 (bytes from sbrk + mmap) usmblks: 0 fsmblks: 0 uordblks: 61664 (bytes used) fordblks: 73504 (bytes free) keepcost: 64080 (bytes in releasable chunk) Number of files: 2 Number of files transferred: 0 Total file size: 207662866 bytes Total transferred file size: 0 bytes Literal data: 0 bytes Matched data: 0 bytes File list size: 66 File list generation time: 0.217 seconds File list transfer time: 0.000 seconds Total bytes sent: 120 Total bytes received: 221 sent 120 bytes received 221 bytes 136.40 bytes/sec total size is 207662866 speedup is 608982.01 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1518) [generator=3.0.9] +do_rsync:43> rvbash='' rvzsh=23 rr=23 +do_rsync:55> (( rr == 0 )) +do_rsync:57> (( rr == 24 )) +do_rsync:60> (( rr == 5 || rr == 10 || rr == 23 || rr == 30 || rr == 35 )) +do_rsync:62> (( runcount >= MAXRETRIES )) +do_rsync:68> sleep=8 +do_rsync:69> logit e 'rsync returned 23 (retryable), sleeping for 8' +logit:2> local 'item=e' +logit:3> shift +logit:4> local 'err=' +logit:5> [[ e == E ]] +logit:6> [[ e == e ]] +logit:6> err=Err: +logit:8> [[ $LOGITEMS -regex-match $item ]] +logit:9> logwrite Err: 'rsync returned 23 (retryable), sleeping for 8' +logwrite:2> [[ -n '' ]] +logwrite:4> [[ -n /var/log/mirror/quick-fedora-mirror.log && -w /var/log/mirror/quick-fedora-mirror.log ]] +logwrite:5> date '+%b %d %T' +logwrite:5> echo 'Jan 25 00:33:58' Err: 'rsync returned 23 (retryable), sleeping for 8' +logit:11> (( VERBOSE >= 3 )) +logit:12> db3 Log: Err: 'rsync returned 23 (retryable), sleeping for 8' +db3:0> (( VERBOSE >= 3 )) +db3:0> echo '>>' Log: Err: 'rsync returned 23 (retryable), sleeping for 8' >> Log: Err: rsync returned 23 (retryable), sleeping for 8 +do_rsync:70> db2 rsync failed: sleeping for 8 +db2:0> (( VERBOSE >= 2 )) +db2:0> echo rsync failed: sleeping for 8 rsync failed: sleeping for 8

2 2

Development brainstorming for Tahrir / Badges (was: Fedora-badges)
by Justin W. Flory 28 Jan '19

28 Jan '19

Hi Clement, thanks for this detailed feedback. I agree focusing on CI/CD and improving development environment instructions is helpful and a good goal for the hackfest; I'm replying in-line with some other thoughts. On 1/17/19 3:39 AM, Clement Verna wrote: > Hi Justin, > > I am replying here to your IRC questions :-) > > So I think that indeed setting up basic CI/CD and maybe a container > based development environment would be a good start. > The Infra team is meeting next week in Brno and one item of the long > agenda we have is to move applications to Openshift so maybe we will > have the time to do that for badges. This would allow to use a much > nicer workflow. > Running Tahrir/Badges in OpenShift would be awesome. I saw some commits from Randy this week. Was there any success on running Badges in OpenShift? > About migrating to another framework, I think this is an hard task (I > don't know much of the tahrir code base tho) since it usually mean you > need someone that knows well the current code base and framework and > that also knows well the new framework this sounds difficult for me. > Although as I mentioned in the council ticket, the technology stack > does not sound very appealing for someone that wishes to learn new > skills or develop existing one which is one of the main factor for > people to dedicate time to help maintain a Opens Source project. > > All that to say that I think that for your FAD you should focus on > adding new feature, I would choose maybe 1 or 2 features that are > really longed for and try to break them down in smaller items so that > you have kind of plan to develop them. > I agree. > You could write something like that > > Technical work breakdow : > > # Development Environment setup > > ## Create container environment to run application locally > (application, database, etc ..) > ## Document how to use the container base development environment > ## Add basic test framework and make it possible to run test in the > container environment > ## Add code linting, code formatting checks, etc ... > ## Configure Travis CI or CentOS CI to run tests and checks > I think this is achievable for a hackfest. In #fedora-badges, Sayan and I were discussing this. Vagrant is set up already for Tahrir. I am curious of the value in migrating to a container-based environment from Vagrant. If migrating to a container environment from Vagrant offered benefits to how Badges is deployed (in addition to lower overhead for a dev environment), I think it would be worthwhile? > # Feature Development > > ## Implement ticket number X using Test Driven Development > ### Create new page template > ### Create new HTTP enpoint to serve the new page template > > ## Implement ticket number XX using Test Driven Development > ### Investigate and document how YYY feature works > ### Add new feature to YYY > .... > > Using TDD is a nice way to start adding test to the application, you > also imaging doing some pair programming if that work well during the > FAD that can be a nice way to on-board new contributor inviting them > to a pair-programming TDD session. > This approach makes sense too. Some of the work we want to do is to identify and prioritize which features to focus on. > > Hope that helps, I ll try to push for us to move badges to openshift > next week so that should make things a little easier later on to > deploy changes to staging and production :-) > Thanks for your helpful feedback and support! -- Cheers, Justin W. Flory jflory7(a)gmail.com

3 2

Ben Cotton Invoice # EP329947-932
by Ben Cotton 25 Jan '19

25 Jan '19

Sorry for the delay…. Please submit the new documents as soon as possible. Missing Documents: Invoice EP329947-932 (previous version is attached) Thank you for your business! Ben Cotton bcotton(a)redhat.com -

1 0

Mirror Syncing Problem
by Riseops 24 Jan '19

24 Jan '19

1 0

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

23 Jan '19

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

1 0

Anitya 0.14.1 (release-monitoring.org) deployed on production
by Michal Konecny 18 Jan '19

18 Jan '19

Hi everybody, I want to announce that the Anitya 0.14.1 was deployed on production (https://release-monitoring.org/) You can see changelog here https://github.com/release-monitoring/anitya/releases/tag/0.14.1 This version is just a hotfix for few issues that were found after deployment of 0.14.0. As a bonus I was able to solve the issue with fedmsg, so no message should be missing in datagrepper now. This means, that the notifications about new versions should work again. \o/ Regards, mkonecny

1 0

bodhi-3.13.0 beta deployed to staging
by Randy Barlow 17 Jan '19

17 Jan '19

Greetings! I've deployed bodhi 3.13.0 beta0 to staging: https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html

1 0

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

16 Jan '19

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

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure January 2019