devel August 2018

devel@lists.centos.org

30 participants
25 discussions

Problems with qemu-img when generating Vagrant images
by Laurentiu Pancescu 02 Oct '18

02 Oct '18

Hello everyone, we switched from using qemu-img from CentOS 7.x to qemu-img-ev from the Virt SIG several months ago, to allow us to generate Hyper-V images. My attempts to build Vagrant images are failing the automated tests since the beginning of July, apparently due to corrupt filesystems. I see XFS metadata corruption in the CentOS 7 images when using qemu-img-ev, as well as ext4 superblock corruption in the CentOS 6 images.[1] The distro installer runs just once and the resulting disk image is converted by Image Factory to different formats, depending on the virtualization target. Since the VirtualBox images are working as expected, while the libvirt images don't even boot due to filesystem corruption, I would assume that the installation produces a valid image, but the conversion of the disk images for libvirt-kvm fall prey to bugs in qemu-img-ev and the stock qemu-img. If anyone has the possibility to test with VmWare or Hyper-V, please write me off-list. I noticed that qemu-img-ev is at version 2.1.2, while Debian Stable has version 2.8 and Fedora 28 has version 2.11. Maybe such bugs, if real, were already fixed upstream - would it be possible to use a newer version than what qemu-img-ev provides? We reverted to using the EL7 qemu-img, but this still produces broken libvirt images and wețd have to drop the Hyper-V images as well. Any help or suggestions are appreciated. Best regards, Laurențiu [1] https://people.centos.org/bstinson/vagrant/c6-vagrant.png

2 4

Authorization to use CentOS logo in GNOME Boxes
by Fabiano Fidêncio 19 Sep '18

19 Sep '18

People, Firstly, sorry for the cross-list post (centos-devel and centos-docs). I'd like to reach you in order to ask for a formal authorization to use CentOS logo on GNOME Boxes[0]. GNOME Boxes already shows a few other distro's logos as you can check here[1]. Would be possible to get the explicit confirmation that we could use CentOS logo as well? [0]: https://wiki.gnome.org/Apps/Boxes [1]: https://gitlab.gnome.org/GNOME/gnome-boxes/raw/master/README.logos Best Regards, -- Fabiano Fidêncio

4 5

SecureBoot : rolling out new shim pkgs for CentOS 7.5.1804 in CR repository - asking for testers/feedback
by Fabian Arrotin 30 Aug '18

30 Aug '18

When we consolidated all CentOS Distro builders in a new centralized setup, covering all arches (so basically x86_64, i386, ppc64le, ppc64, aarch64 and armhfp those days), we wanted also to add redundancy where it was possible to. The interesting "SecureBoot" corner case came on the table and we had to find a different way to build the following packages: - shim (both signed and unsigned) - grub2 - fwupdate - kernel The other reason why we considered rebuilding it is that the cert we were using has expired : curl --location --silent https://github.com/CentOS/sig-core-SecureBoot/raw/master/CentOS_7/kernel/SO… | openssl x509 -inform der -text -noout|grep -A2 Validity While technically it doesn't really matter for Secureboot itself, it was better to get a new key/cert rolled-in and use the new one for new builds. That's where it's interesting as because shim embeds the certs in the Machine Owner Key (MOK), and that each other component used in the boot chain is validated against that (so grub2 first, then kernel and kernel modules) that means that once deployed , the new shim would not be able to boot previous grub2/kernel. But there is a solution for that : instead of "embedding" only the new cert, we can have both the old one and new one, permitting us to still boot older kernels but also the new ones we'll build/push soon (built on the new build system), and that's what we used for that new shim package. That's where we'd like you (SecureBoot users) to give us feedback about that new shim pkg. It was already validated on some hardware nodes, passed some QA tests, but we'd prefer to have more feedback. Worth noting that such rebuild has also a patch that should fix an issue we had with shim not allowing to import key in MOK through mokutil (see https://bugs.centos.org/view.php?id=14050) How can you test ? If you're using UEFI with SecureBoot enabled , we have signed/pushed those pkgs to the CR repository (see https://wiki.centos.org/AdditionalResources/Repositories/CR) That repo is by default disabled, but following command would let you update shim : yum update shim --enablerepo=cr Then reboot and it should work like before, so validating the boot chain (while still using grub2/kernel packages signed with previous key) We'd appreciate feedback on this list, or #centos-devel on irc.freenode.net I'd like to thank Patrick Uiterwijk and Peter Jones for their help for the patch and validation for that shim -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

LinchPin v1.6.0 (enhancement release) has been released
by Clint Savage 29 Aug '18

29 Aug '18

We are happy to announce that LinchPin v1.6.0 has been released. This release marks some useful enhancements and features: * Jenkins releases to pypi #578 / #567 * CI tests allow for ignoring, provider, and more #587 / #528 / #576 * Beaker enhancement #614 * Introduce support for 'family' and 'tag' fields in bkr topology files #612 * Allow boolean expressions on hostrequire #611 * Generate a unique name if one isn't specified. #629 / #575 / 564 * Linchpin Container Build in Jenkins #613 / #602 / #304 * Replace inventory generation role with python code #601 / #599 / #448 / #624 * Rework credentials expansion in tests #632 / #620 * Updates to os_server module & additional volumes to os_server topologies #622 / #329 / #544 / #330 * Integrate virt-customize to make linchpin work with generic images #610 / #532 Additional bugs were also fixed along the way: * Make linchpin work with Ansible 2.5.x #564 - Fixes #516 * Allow absolute path to resources. #624 - Fixes #623 * Beaker hostrequires force no longer working #616 - Fixed by #614 All in all, over 30 Issues and Pull Requests were closed on Github with this release, that's a mighty large release. Future releases will be smaller, and should occur about every 3 weeks. Alpha, beta or full releases should occur each 3 week cycle. Check https://pypi.org/project/linchpin/#history for the latest package updates. The official release notes are available at https://github.com/CentOS-PaaS-SIG/linchpin/releases/tag/v1.6.0 This update is available via PyPI: https://pypi.org/project/linchpin/ If you discover any errors or regressions, please open a Github issue ( https://github.com/CentOS-PaaS-SIG/linchpin/issues). Cheers, Clint Savage Senior Software Engineer, Red Hat twitter: @herlo, github: herlo, IRC: herlo, #linchpin (freenode)

1 0

git19 from sclo-rh missing from repodata
by BC 29 Aug '18

29 Aug '18

http://mirror.centos.org/centos/6/sclo/x86_64/rh/repodata/ On 28-Jun-2018 09:07 git19 was in the repodata. On 03-Jul-2018 it was not. Is this package no longer supported?

4 8

rpm-ostree local updates
by Harry Mallon 29 Aug '18

29 Aug '18

Hello all, I am looking at using rpm-ostree and CentOS atomic. Is it possible to update rpm-ostree with a usb stick? As in provide a version as a download for updating offline devices. Best, Harry Harry Mallon Senior Software Engineer T+44 203 7000 989 60 Poland Street | London | England | W1F 7NT

2 1

rh-postgresql95-postgresql-9.5.14-1.el7 works for me
by Sandro Bonazzola 29 Aug '18

29 Aug '18

Hi, not sure how to rpovide feedback to scl sig, but for what it's worth, rh-postgresql95-postgresql-9.5.14-1.el7 which is in testing works for me. Looking forward to see this released. 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://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

1 0

Sftp connections timing out in Centos 7
by Veetil, Vyshnav 28 Aug '18

28 Aug '18

Hi, We are facing some issues in Centos 7. When we create sftp connection and sync data from server to client and vice-versa. Whenever we are running load on the setup SFTP connections are frequently getting timed out. Resulting in unnecessary sftp processes on system. Is there any known issue related to sftp timeout. Please let us know your suggestions to overcome this issue. Thanks and Regards, Vyshnav

2 1

In place upgrade to Centos 7
by Akshar Kanak 28 Aug '18

28 Aug '18

Dear team Is there any standard documnet released for upgrading from Centos 6.5 (Final) to Centos & version . The upgrade tool (https://wiki.centos.org/TipsAndTricks/CentOSUpgradeTool) is not available . Thanks and regards Akshar

2 1

Missing Dependency of Openshift 3.10 (Ansible 2.4.3) in repo
by Robert.Grumann＠t-online.de 26 Aug '18

26 Aug '18

On a virgin system CentOS 7.5 can, unfortunately, after the command #yum install centos-release-openshift-origin" the following command not be executed without error. # yum install openshift-ansible There is a dependency to Ansible 2.4.3 in Openshift 3.10, which unfortunately is not in the repo (Only Ansible 2.4.2). Can you please include Ansible 2.4.3 in the rpm repo? Thanks. Robert

7 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel August 2018