devel

devel@lists.centos.org

9 participants
4617 discussions

Ceph Day Netherlands: CFP closes June 3rd
by Rich Bowen 28 May '19

28 May '19

Hi, folks, Sorry for the late notice, but you still have a few days. Ceph will be holding Ceph Days Netherlands on July 2nd, and the CFP closes on June 3rd, which is Monday. If you are interested in presenting, please submit your proposals *now*, at https://ceph.com/cephdays/holland-2019/ Thanks! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

CRI-O rpm not published to public repo hence not signed
by Daniel Comnea 28 May '19

28 May '19

Hi Lokesh, If i'm not mistaken i guess you are still building/ maintaining the CRI-O rpms ? If so could you please let me know where is the CI job which builds the rpms [1] which are tagged into [2] ? The reason i'm bringing this up is because folks in K8s community are using the cri-o rpms published to [3] and that should have never happened. Now with Fabian (@arrfab) help we manage to track down that there was no request being made by you(or the SIG chair under which the cri-o falls into) to sign and publish the rpm to mirror.centos.org and that backs the issue folks raised [3]. As a solution, i can suggest one (if you are willing to accept it): 1. you follow the process and 1. tag and promote the rpms from -candidate to -testing and then to paas7-crio-114-release 2. create a ticket on bugs.c.o so our Infra folks can sign and publish the rpm which i guess will end up in [4] 2. or we can try to get it under PaaS SIG and then publish it under [5] Once all that is done then i'm happy to even announce on K8s/ CRI mailer as projects like kubespray are using it/ consuming the rpm. Cheers, Dani [1] https://cbs.centos.org/koji/buildinfo?buildID=25889 [2] https://cbs.centos.org/koji/taginfo?tagID=1704 [3] https://github.com/kubernetes-sigs/kubespray/pull/4781#issuecomment-4938274… [4] http://mirror.centos.org/centos/7/os/x86_64/Packages/ [5] http://mirror.centos.org/centos/7/paas/x86_64/

1 1

snmp walk not working in FIPS compliant algorithms
by Maheshwari, Shagun 24 May '19

24 May '19

Hi, When we attempt to do SNMP walk v3 in CentOS7 when its FIPS enabled, we get the below error: aes_misc.c(74): OpenSSL internal error, assertion failed: Low level API call to cipher AES forbidden in FIPS mode! FIPS support SHA and AES. This error is coming internally and it needs changes from rpm level. When we try the same scenario in RHEL 6 servers, we don't get this error and we get output successfully. The SNMP rpm we use is net-snmp-5.7.2-28.el7.x86_64 Please let us know how we can resolve this error? Any patch is available for this or not. Regards, Shagun

2 1

libXvMC-devel EL8
by Leon Fauster 22 May '19

22 May '19

I can't find libXvMC-devel for EL8 - any ideas? -- Thanks LF

2 2

Drafting the June newsletter, contributors welcome
by Rich Bowen 21 May '19

21 May '19

I'm in the process of drafting the June newsletter, which I hope to post on Tuesday, June 4th. If you would like to contribute to it in any way, please let me know. In response to last month's newsletter, I received the following comment: "Newsletter is great if medium to expert but it’s all Greek to newbie. How about a newbie articles?" To that end, if any of you would like to contribute articles, either to the newsletter, or to the blog in general, on any topic of interest to people of any skill level, please do let me know. It's also worth noting that if you have a CentOS developer account, you can post drafts to the blog - instructions are here: https://wiki.centos.org/SpecialInterestGroup/Promo/Blog -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

[URGENT] CBS builds for ppc64le and aarch64 not landing on mirrors
by Sandro Bonazzola 16 May '19

16 May '19

Hi, yesterday I built adn released qemu-kvm-ev with fixes for Microarchitectural Store Buffer Data CVE. The build landed correctly on x86_64 at http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/?C=M;O=D but it's still missing on ppc64le at http://mirror.centos.org/altarch/7/virt/ppc64le/kvm-common/?C=M;O=D and on aarch64 at http://mirror.centos.org/altarch/7/virt/aarch64/kvm-common/?C=M;O=D the build is https://cbs.centos.org/koji/buildinfo?buildID=26025 and the mappings looks correct: https://git.centos.org/centos/cbs-content-control/blob/master/f/sign_list.p… https://git.centos.org/centos/cbs-content-control/blob/master/f/sign_list.a… Since this is an important CVE fix, can you please prioritize work on this issue? Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

Microarchitectural Store Buffer Data
by Thomas Stephen Lee 15 May '19

15 May '19

Hi All, For your information https://www.intel.com/content/www/us/en/architecture-and-technology/mds.html https://access.redhat.com/security/vulnerabilities/mds thanks --- Thomas Stephen Lee

2 2

Re: [CentOS-devel] Help needed to Install CentOS on Zynq ZC706 ARM cortex A9
by Piyush Jadhav 14 May '19

14 May '19

No worries, I hope to understand the SPL boot properly though. I will go through some reading and in any case, I will wait when you can look into it. For now, *I managed to boot centOS* using the kernel made with petalinux/yocto, and yes I had problems with rights and properly copying all the files. You have been a great help and thank you for that! Regards, Piyush D Jadhav On Tue, May 14, 2019 at 10:28 PM Pablo Sebastián Greco < pablo(a)fliagreco.com.ar> wrote: > Hi, I've been trying to answer your mail all day, but hasn't been easy ;) > El 13/5/19 a las 19:26, Piyush Jadhav escribió: > > Hi Pablo, > > Sorry for the late reply and thank you for pushing us for getting the > serial port repaired, the port was not functioning. Now that we have it > working, I have started to debug through the serial communication, but I > want to raise some doubts in the process. In the blog, > https://wiki.centos.org/SpecialInterestGroup/AltArch/armhfp, the last > step is to *dd* the *u-boot-with-spl.bin* file as follows, > >> dd if=/usr/share/uboot/${boardmodel}/u-boot-sunxi-with-spl.bin of=${sdcard} bs=1024 seek=8 conv=fsync,notrunc >> >> Yeah, that applies to sunxi devices > > But is missing how to load the *u-boot-spl.bin *and* u-boot.img. *Could > you please shine some light on this for us? I understand that the order has > to be ROM code -> SPL -> u-boot -> kernel. Does it means that I have to > also dd u-boot.img, like here, > >> dd if=u-boot-spl.bin of=/dev/sdX bs=1024 seek=8 >> dd if=u-boot.img of=/dev/sdX bs=1024 seek=*X (?)* >> >> > That is a good question, that I don't know the answer to. At the moment I > have my hands full with the preparation for 8, and my simple google queries > haven't yielded anything interesting. > > On the other hand, I also tried to boot with another method using only the > centOS Rootfs file (in the root ext4 partition), and the Boot.bin and > image.ub files (in boot partitions) which I created using petalinux/yocto. > The kernel boots up but falls into the kernel panic, with errors as *cant > execute the /sbin/init - (error -8)* -> which refers as permission > denied. Please let us know what you think of this too! > > That is a good test, and you could try mixing things to see if it boots > (maybe that permission denied is caused by a missing driver) > > Thanks a ton in advance! > > > > Regards, > Piyush > > > > On Thu, Apr 11, 2019 at 10:23 PM Pablo Sebastián Greco < > pablo(a)fliagreco.com.ar> wrote: > >> >> El 10/4/19 a las 09:27, Piyush Jadhav escribió: >> >> Hi Pablo, >> >> Thank you very much for the help. >> Though I performed the same steps from the wiki link, ( >> https://wiki.centos.org/SpecialInterestGroup/AltArch/armhfp) for Zynq >> ZC706 using the uboot files you provided and the generic userland image >> (also the old version with kernel 4.14), but the device *does not* boot >> up. The DONE leds on the device does not light up at all. >> >> Debugging these things without a serial console tend to be hard, because >> you're flying blind. >> >> >> At this point I tried the generic userland image files on also the >> raspberry pi3b+, even the raspberry *does not* boot up. Although >> userland image provided for particularly raspberry works as expected and >> boot into the device. >> >> Yeah, the rasbperrypi images are really specific for those rpi, it would >> be a miracle if those worked on other devices. >> >> >> I also see that the userland generic image creates three partitions on >> the drive, two of which are for boot, which does some procedure to detect >> the board automatically. I was wondering, if it is possible for you to >> guide me how I can create single boot partition, using the files you >> provided. >> >> There should be 4 partitions actually >> 1 vfat, for rpi boot with generic kernel >> 2 /boot >> 3 swap >> 4 / >> >> >> There is high possibility that I am doing something wrong. Please let me >> know what you think, >> >> As I said before, the first thing would be getting the serial console >> working, with any distribution, just to be able to see the device booting. >> Then, I'd try just to make uboot work, even without an OS image, just an >> SD card without any other data or partitions. >> Only after all that is working, it should be easier to start testing an >> OS. >> >> >> Regards, >> Piyush D Jadhav >> >> >> >> On Tue, Apr 9, 2019 at 2:49 AM Pablo Sebastián Greco < >> pablo(a)fliagreco.com.ar> wrote: >> >>> >>> El 8/4/19 a las 12:28, Piyush Jadhav escribió: >>> >>> I am a begineer in using the Zynq 7000 ZC706 SoC. I have already booted >>> linux made with Yocto project with meta-xilinx and PREEMPT-RT layers. >>> Everything is working as expected. Though we are not satisfied with the >>> real time performance on Scheduler and Latency tests, however alternatively >>> it could be interesting to compare with another OS like CentOS. >>> >>> I have followed the procedure on described here to install CentOS using >>> the rootfs files made with yocto and the files in /boot (boot.bin + UImage >>> + dtb).https://github.com/umiddelb/aarch64/wik ... ch64-board >>> <https://github.com/umiddelb/aarch64/wiki/Install-CentOS-7-on-your-favourite…> >>> >>> But I am not able to successfully create the OS. I am not having a >>> serial communication with the board, so I cant debug further. I will/can >>> only have a SSH communication once the OS boots up. >>> >>> Does anyone guide me how can I take this ahead? >>> >>> I could not find anything aarch64 for that device, all I found was 32 >>> bits. >>> That said, it seems to have mainline uboot and kernel support >>> (zynq-zc706.dts), so it could be installed using the steps here >>> https://wiki.centos.org/SpecialInterestGroup/AltArch/armhfp >>> Since we usually don't build uboot for that device, I made a version for >>> you to test, and left it here >>> https://people.centos.org/pgreco/zynq-zc706/ >>> The normal images provided by CentOS use kernel 4.14, but if you need an >>> image with a newer version, we have this test image here >>> https://armv7.dev.centos.org/repos/images/CentOS-Userland-7-armv7hl-generic… >>> which uses 4.19 >>> >>> Please let us know how it went. >>> >>> Thanks. >>> Pablo. >>> >> >> HTH. >> Pablo. >> > Pablo. >

1 0

CentOS 8.0.1905 build status
by Fabian Arrotin 14 May '19

14 May '19

Hi, As everybody is probably aware now, RHEL 8.0 was released earlier this week . Instead of publishing multiple blog posts here and then point to updated content, we decided this time to have a dedicated wiki page that can be used to track our current status : https://wiki.centos.org/About/Building_8 So now you can look at that page while we're busy on those tasks, and refresh from time to time. Let's spread the news about the wiki page and point people (on mailing-lists, irc, forums, etc) to that page to get all latest news about CentOS 8.0.1905 build status ! Cheers ! -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

7 8

Preliminary RHEL 8 review
by Nico Kadel-Garcia 14 May '19

14 May '19

I've noticed a few things that may help other people setting up test environments. 1) The RPMs on the installation media are split into two distinct repositories, "BaseOS" and "AppStream", for no reason I can discern. This means that if you try, like me, to mount a DVD image and use it as local yum repo for testing out kickstart setups and mock builds, you need to address the multiple necessary repositories with the new names. 2) For Virtualbox, it absolutely needs more than 1 GB of RAM.With only 1 GB, it hands during hte firstboot setups. 3) Mock is going to be.... awkward to port, due to multiple python dependencies in on the DVD.

6 18

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel