devel November 2019

devel@lists.centos.org

44 participants
34 discussions

[Meeting] CentOS Cloud SIG meeting (2019-11-14)
by Alfredo Moralejo Alonso 14 Nov '19

14 Nov '19

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2019-11-14) ====================================================== Meeting started by amoralej at 15:01:21 UTC. The full logs are available athttps://www.centos.org/minutes/2019/November/centos-meeting.2019-11-14-15… . Meeting summary --------------- * roll call (amoralej, 15:01:53) * altarch synchronization still broken https://bugs.centos.org/view.php?id=16590 (amoralej, 15:06:28) * ACTION: amoralej to request kb for updates (amoralej, 15:07:57) * status of OpenStack on CentOS8 (amoralej, 15:08:14) * CloudSIG is waiting for CBS to provide centos8 buildroot to start building dependencies - no ETA provided (amoralej, 15:09:33) * LINK: https://review.rdoproject.org/etherpad/p/moving-rdo-to-centos8 (amoralej, 15:09:37) * -candidate tags cleanup (amoralej, 15:11:18) * old packages that never were promoted have been cleaned up in -candidate tags in cloudsig (amoralej, 15:11:57) * LINK: https://review.rdoproject.org/etherpad/p/candidate-only (ykarel, 15:12:42) * feature has been added in graffiti to report old unpromoted builds - https://softwarefactory-project.io/r/#/c/16906/ (amoralej, 15:12:42) * LINK: https://review.rdoproject.org/etherpad/p/candidate-only (amoralej, 15:12:58) * open floor (amoralej, 15:13:33) * tripleo standalone job is added to validate -release tagged builds (ykarel, 15:14:24) * LINK: https://review.rdoproject.org/r/#/q/topic:cloudsig-containers (ykarel, 15:14:44) * ci jobs and views have been reorganized in ci.centos.org for CloudSIG https://ci.centos.org/view/rdo/view/CloudSIG%20periodic%20validation/ (amoralej, 15:17:12) * ACTION: amoralej to create a trello card to track status of cloudsig validation using tripleo in ci.centos.org (amoralej, 15:20:47) Meeting ended at 15:32:21 UTC. Action Items ------------ * amoralej to request kb for updates * amoralej to create a trello card to track status of cloudsig validation using tripleo in ci.centos.org Action Items, by person ----------------------- * amoralej * amoralej to request kb for updates * amoralej to create a trello card to track status of cloudsig validation using tripleo in ci.centos.org * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * amoralej (58) * ykarel (21) * centbot (5) * rbowen (5)

1 0

[SCLo SIG] new sclo-php*-php-pecl-rrd packages available for testing
by Remi Collet 14 Nov '19

14 Nov '19

Yet another package available in centos-sclo-sclo-testing PHP bindings to rrd tool system. https://pecl.php.net/package/rrd For rh-php72 * sclo-php72-php-pecl-rrd-2.0.1-1 For rh-php73 * sclo-php73-php-pecl-rrd-2.0.1-1 Remi. P.S.: https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

CentOS 8 Live ISO?
by Fredrik Mikker 11 Nov '19

11 Nov '19

Good evening, I'm looking for at CentOS 8 Live ISO, but I fail to find one. Is there anyone that can point me in the right direction? -- Med vänlig hälsning / Best regards Fredrik Mikker fredrik(a)mikker.se

8 9

[SCLo SIG] new PHP 7.3 available for testing
by Remi Collet 11 Nov '19

11 Nov '19

Hi, RHSCL 3.4 Beta is released and provides some new Software Collections including PHP version 7.3 For RHEL 7 users rh-php73 packages are available in the rhel-server-rhscl-7-beta-rpms channel: For CentOS 7 users rh-php73 packages are available in the centos-sclo-rh-testing repository: rh-php73-1-1.el7 rh-php73-php-7.3.7-2.el7 rh-php73-php-pear-1.10.9-1.el7 rh-php73-php-pecl-apcu-5.1.17-1.el7 rh-php73-php-pecl-xdebug-2.7.2-1.el7 Additional packages: sclo-php73 packages are available in the centos-sclo-sclo-testing repository: sclo-php73-php-ast-1.0.3-1.el7 sclo-php73-php-imap-7.3.7-1.el7 sclo-php73-php-pecl-amqp-1.9.4-2.el7 sclo-php73-php-pecl-apcu-bc-1.0.5-2.el7 sclo-php73-php-pecl-apfd-1.0.1-5.el7 sclo-php73-php-pecl-geoip-1.1.1-4.el7 sclo-php73-php-pecl-http-3.2.2-1.el7 sclo-php73-php-pecl-igbinary-2.0.8-2.el7 sclo-php73-php-pecl-imagick-3.4.4-2.el7 sclo-php73-php-pecl-lzf-1.6.7-2.el7 sclo-php73-php-pecl-memcached-3.1.4-1.el7 sclo-php73-php-pecl-mongodb-1.6.0-1.el7 sclo-php73-php-pecl-msgpack-2.0.3-1.el7 sclo-php73-php-pecl-propro-2.1.0-1.el7 sclo-php73-php-pecl-raphf-2.0.1-1.el7 sclo-php73-php-pecl-redis5-5.1.0-1.el7 sclo-php73-php-pecl-selinux-0.4.2-1.el7 sclo-php73-php-pecl-solr2-2.5.0-1.el7 sclo-php73-php-pecl-ssh2-1.2-1.el7 sclo-php73-php-pecl-uploadprogress-1.0.3.1-5.el7 sclo-php73-php-pecl-uuid-1.0.4-4.el7 sclo-php73-php-pecl-xattr-1.3.0-4.el7 sclo-php73-php-phpiredis-1.0.0-3.el7 sclo-php73-php-smbclient-1.0.0-2.el7 sclo-php73-php-sodium-7.3.7-2.el7 sclo-php73-php-tidy-7.3.7-1.el7 sclo-php73-unit-php-1.12.0-1.el7 Thanks for testing, Remi. P.S.: https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

Re: [CentOS-devel] Request to join Cloud Instance SIG (Ben Hosmer)
by Ben Hosmer 09 Nov '19

09 Nov '19

Hey Karanbir, I was never able to find an official CentOS base image in the Azure marketplace. I saw a lot of references to the bitnami one, but I was hesitant to use something that didn't have the CentOS project's label on it. I wanted a bare minimum image. I wound up building my own and uploading a VHD. I assumed one didn't exist and wanted to help work towards that goal. If there is one that I wasn't able to find, could you point me in the right direction?

2 1

Request to join Cloud Instance SIG
by Ben Hosmer 08 Nov '19

08 Nov '19

I'd like to contribute with an official CentOS image in Azure.

2 1

CPE Weekly: 2019-11-08
by Aoife Moloney 08 Nov '19

08 Nov '19

Hi everyone, Welcome to the CPE team weekly project update mail! Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. For increased communication between our communities, we have created #redhat-cpe on Freenode! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. Note: This document is currently built from individual reports rolled into a google document which we edit and copy into a final document. We are aware that this causes problems with some email readers, and are working on a method to make this less problematic. High Level Project Updates: CentOS: RHEL 8.1 announced Tuesday, team are busy tackling this Workaround to help automatically restart repospanner 7.8 beta push has 3 packages left Fedora: Rawhide Gating: We are working towards deployment of Bodhi 5.0 to production Testing & Staging are both going fine Synching with centos.ci.org New ci-resultsdb-listener due in production this week More work is going into docs for rawhide gating repoSpanner Discovered a new bottleneck that appears due to network latency that wasn’t present in local testing. We are also further analysing core dumps for unexplained hanging of the app Tested pushing the Ansible repo to a local repospanner cluster to see how it performed with new 83x patch. It pushed in 4 minutes. Network bottleneck is prenventing real numbers. We are also working on improving testing. Additional developer docblocks landed Application Retirements Elections Blocking issue was fixed (https://pagure.io/fedora-infrastructure/issue/8253) Fedocal jlanda hitting permission error in communishift https://pagure.io/fedora-infrastructure/issue/8274 Nuancier Benson Muite is now working on OIDC authentication We are emailing him to check the progress and if he needs any help Fpaste Updated fpaste CLI appears to have landed in EPEL. Writing a commblog about it Sunset date: 1 December 2019 Badges GDPR query under investigation Misc Some of the team attended the OpenAlt conference in Brno. Watch out for blogs about our experience! The team are exploring smaller end of year initiatives, and we would welcome any thoughts or feedback. Comments? Suggestions? Feedback? Let Us Know! Kind regards & have a great weekend! Aoife -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

PowerTools sources missing?
by Leon Fauster 05 Nov '19

05 Nov '19

Looking for a SRPM I noticed that http://vault.centos.org/8.0.1905/PowerTools/Source/SPackages/ is empty (BTW: also no entry in CentOS-Sources.repo)? Are they merged elsewhere? -- Thanks Leon

2 1

Re: [CentOS-devel] Kernel Panic: CentOS 7.4
by Trevor Hemsley 05 Nov '19

05 Nov '19

Looking at kernel bugs on bugs.centos.org is not very useful. CentOS does not make code changes, it only rebuilds packages that are released for RHEL and publishes them. We really have no idea what code changes have been made by Red Hat. The current CentOS 7.7 kernel is 3.10.0-1062.4.1.el7.x86_64 and there are over 32,000 entries in `rpm -q --changelog kernel-3.10.0-1062.4.1.el7.x86_64` before you reach any mention of the 3.10.0-693.* 7.4-series kernels. That's 32,000 potential bugs that could have fixed your problem. If someone who had that problem had updated to a newer kernel and reported it as fixed then we would probably have closed that bug. Since no-one has, that either means they didn't care enough to update the bug report or no-one has tested it or it's not fixed. It would appear that you'll be the one to find out... Trevor On 05/11/2019 18:57, sumit gambhir wrote: > https://bugs.centos.org/view.php?id=14265#history. is still in the > open state. > Or Is it fixed in CentOS 7.7? > > On Wed, Nov 6, 2019 at 12:20 AM Trevor Hemsley > <trevor.hemsley(a)ntlworld.com <mailto:trevor.hemsley@ntlworld.com>> wrote: > > Run `yum update`. You are more than 2 years out of date. > > Only the current version - 7.7 at present - is supported, any > other version, the answer is update. > > Trevor > > On 05/11/2019 18:20, sumit gambhir wrote: >> >> There was a power cycle during the upgrade. >> >> We got following trace during kernel panic. >> >> Cannot login after software upgrade – system initializing message >> on Portal; on cli login prompt is seen following messages: >> >> >> System crashing due to >> [ 8780.678167] Hardware name: Cisco Systems, Inc. >> ENCS5412/K9/ENCS5412/K9, BIOS ENCS54_2.7.020620190951 02/06/2019 >> [ 8780.800565] Workqueue: events flush_to_ldisc >> [ 8780.853390] task: ffff9707f4bf30c0 ti: ffff9707f4448000 >> task.ti: ffff9707f4448000 >> [ 8780.944588] RIP: 0010:[<ffffffff83874b73>] >> [<ffffffff83874b73>] uart_write_room+0x13/0x50 >> [ 8781.045274] RSP: 0018:ffff9707f444bc60 EFLAGS: 00010286 >> [ 8781.110468] RAX: 0000000000000800 RBX: 000000000000000a RCX: >> ffff9707f444bfd8 >> [ 8781.197509] RDX: ffffffff83874b60 RSI: ffff970ed8206c00 RDI: >> ffff970ed8205000 >> [ 8781.284540] RBP: ffff9707f444bc70 R08: ffff970ec1e6ec00 R09: >> a3c427ffdbc3c000 >> [ 8781.371561] R10: a3c427ffdbc3c000 R11: 0000000000000001 R12: >> 0000000000000000 >> [ 8781.458579] R13: ffff970ed8205000 R14: ffff970ed8206c00 R15: >> ffff970ec1e6ecf6 >> [ 8781.545589] FS: 0000000000000000(0000) >> GS:ffff970edf000000(0000) knlGS:0000000000000000 >> [ 8781.644060] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 >> [ 8781.714429] CR2: 0000000000000150 CR3: 000000085b2be000 CR4: >> 00000000003607f0 >> [ 8781.801442] DR0: 0000000000000000 DR1: 0000000000000000 DR2: >> 0000000000000000 >> [ 8781.888437] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: >> 0000000000000400 >> [ 8781.975407] Call Trace: >> [ 8782.006205] [<ffffffff8385c730>] tty_write_room+0x20/0x30 >> [ 8782.073406] [<ffffffff8385966e>] process_echoes+0x6e/0x2e0 >> [ 8782.141642] [<ffffffff83b65e92>] ? mutex_lock+0x12/0x2f >> [ 8782.206744] [<ffffffff8385c14c>] n_tty_receive_char+0xd4c/0xe30 >> [ 8782.280188] [<ffffffff8385c3dc>] n_tty_receive_buf+0x1ac/0x470 >> [ 8782.352569] [<ffffffff8385f1ff>] flush_to_ldisc+0x10f/0x160 >> [ 8782.421832] [<ffffffff834b9d4f>] process_one_work+0x17f/0x440 >> [ 8782.493188] [<ffffffff834bade6>] worker_thread+0x126/0x3c0 >> [ 8782.561412] [<ffffffff834bacc0>] ? >> manage_workers.isra.25+0x2a0/0x2a0 >> [ 8782.641074] [<ffffffff834c1c31>] kthread+0xd1/0xe0 >> [ 8782.700887] [<ffffffff834c1b60>] ? insert_kthread_work+0x40/0x40 >> [ 8782.775363] [<ffffffff83b74c37>] >> ret_from_fork_nospec_begin+0x21/0x21 >> [ 8782.855038] [<ffffffff834c1b60>] ? insert_kthread_work+0x40/0x40 >> [ 8782.929516] Code: 01 00 00 81 e3 ff 0f 00 00 e8 0a 56 2f 00 89 >> d8 5b 41 5c 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 41 54 53 4c >> 8b a7 18 02 00 00 <49> 8b bc 24 50 01 00 00 e8 50 59 2f 00 41 8b >> 9c 24 48 01 00 00 >> [ 8783.165634] RIP [<ffffffff83874b73>] uart_write_room+0x13/0x50 >> [ 8783.238184] RSP <ffff9707f444bc60> >> [ 8783.281471] CR2: 0000000000000150 >> >> >> >> >> >> While going through the list of cases on centos, we found this >> similar case - https://bugs.centos.org/view.php?id=14265#history. >> However, there has been no activity on it since long. >> >> Can you please help us out to find out if there is an ongoing fix >> for it? >> >> >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel(a)centos.org <mailto:CentOS-devel@centos.org> >> https://lists.centos.org/mailman/listinfo/centos-devel >

1 0

Kernel Panic: CentOS 7.4
by sumit gambhir 05 Nov '19

05 Nov '19

There was a power cycle during the upgrade. We got following trace during kernel panic. Cannot login after software upgrade – system initializing message on Portal; on cli login prompt is seen following messages: System crashing due to [ 8780.678167] Hardware name: Cisco Systems, Inc. ENCS5412/K9/ENCS5412/K9, BIOS ENCS54_2.7.020620190951 02/06/2019 [ 8780.800565] Workqueue: events flush_to_ldisc [ 8780.853390] task: ffff9707f4bf30c0 ti: ffff9707f4448000 task.ti: ffff9707f4448000 [ 8780.944588] RIP: 0010:[<ffffffff83874b73>] [<ffffffff83874b73>] uart_write_room+0x13/0x50 [ 8781.045274] RSP: 0018:ffff9707f444bc60 EFLAGS: 00010286 [ 8781.110468] RAX: 0000000000000800 RBX: 000000000000000a RCX: ffff9707f444bfd8 [ 8781.197509] RDX: ffffffff83874b60 RSI: ffff970ed8206c00 RDI: ffff970ed8205000 [ 8781.284540] RBP: ffff9707f444bc70 R08: ffff970ec1e6ec00 R09: a3c427ffdbc3c000 [ 8781.371561] R10: a3c427ffdbc3c000 R11: 0000000000000001 R12: 0000000000000000 [ 8781.458579] R13: ffff970ed8205000 R14: ffff970ed8206c00 R15: ffff970ec1e6ecf6 [ 8781.545589] FS: 0000000000000000(0000) GS:ffff970edf000000(0000) knlGS:0000000000000000 [ 8781.644060] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 8781.714429] CR2: 0000000000000150 CR3: 000000085b2be000 CR4: 00000000003607f0 [ 8781.801442] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 8781.888437] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 8781.975407] Call Trace: [ 8782.006205] [<ffffffff8385c730>] tty_write_room+0x20/0x30 [ 8782.073406] [<ffffffff8385966e>] process_echoes+0x6e/0x2e0 [ 8782.141642] [<ffffffff83b65e92>] ? mutex_lock+0x12/0x2f [ 8782.206744] [<ffffffff8385c14c>] n_tty_receive_char+0xd4c/0xe30 [ 8782.280188] [<ffffffff8385c3dc>] n_tty_receive_buf+0x1ac/0x470 [ 8782.352569] [<ffffffff8385f1ff>] flush_to_ldisc+0x10f/0x160 [ 8782.421832] [<ffffffff834b9d4f>] process_one_work+0x17f/0x440 [ 8782.493188] [<ffffffff834bade6>] worker_thread+0x126/0x3c0 [ 8782.561412] [<ffffffff834bacc0>] ? manage_workers.isra.25+0x2a0/0x2a0 [ 8782.641074] [<ffffffff834c1c31>] kthread+0xd1/0xe0 [ 8782.700887] [<ffffffff834c1b60>] ? insert_kthread_work+0x40/0x40 [ 8782.775363] [<ffffffff83b74c37>] ret_from_fork_nospec_begin+0x21/0x21 [ 8782.855038] [<ffffffff834c1b60>] ? insert_kthread_work+0x40/0x40 [ 8782.929516] Code: 01 00 00 81 e3 ff 0f 00 00 e8 0a 56 2f 00 89 d8 5b 41 5c 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 41 54 53 4c 8b a7 18 02 00 00 <49> 8b bc 24 50 01 00 00 e8 50 59 2f 00 41 8b 9c 24 48 01 00 00 [ 8783.165634] RIP [<ffffffff83874b73>] uart_write_room+0x13/0x50 [ 8783.238184] RSP <ffff9707f444bc60> [ 8783.281471] CR2: 0000000000000150 While going through the list of cases on centos, we found this similar case - https://bugs.centos.org/view.php?id=14265#history. However, there has been no activity on it since long. Can you please help us out to find out if there is an ongoing fix for it?

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel November 2019