devel

devel@lists.centos.org

2 participants
4695 discussions

Experimentation with the centos namespace on gitlab
by Brian Stinson 07 Apr '22

07 Apr '22

Hi Folks! We had a thread a few weeks ago about the usage of the “centos” namespace on gitlab: https://lists.centos.org/pipermail/centos-devel/2022-February/120216.html The authentication angle is progressing up to the point that we would like to open up the opportunity for a couple of SIGs to onboard with gitlab and help us round the edges. The idea being to open this up to all the SIGs interested in a few weeks once we have clearer documentations and guidelines around the usage of GitLab. We are currently working on that set of best-practices that SIGs which would like to use the centos namespace on gitlab will need to agree and follow. If you are interested, please let us know (just not everyone at once!) :) Thanks, Brian

6 5

Re: [CentOS-devel] [CentOS] ansible upgrade
by Leon Fauster 06 Apr '22

06 Apr '22

Am 23.02.22 um 13:47 schrieb Fabian Arrotin: > On 22/02/2022 22:37, Leon Fauster via CentOS wrote: >> Am 21.02.22 um 16:24 schrieb Fabian Arrotin: >>> On 21/02/2022 15:49, Leon Fauster via CentOS wrote: >>>> Hey all, back from vacation and seeing ansible 2.12 in the repos now. >>>> Anything to be aware of when upgrading from 2.9 to 2.12 in CS8? >>>> >>> >>> You'd be lucky if it works directly , as there were some semantic >>> changes in ansible, so you'll probably have to review all the >>> changes, and if ansible-core just has the modules (it's a stripped >>> down version of ansible, as you're supposed to download the >>> collections yourself) , and use FQCN (Fully Qualified Collection >>> Names) for modules ... >>> >>> FWIW, CentOS Infra still on ansible 2.9.27 from our own configuration >>> management SIG and ansible-core excluded in yum/dnf to ensure that >>> our automation still runs fine (until we have time to test/convert >>> all our roles/tasks/playbooks to run on ansible 5 - aka ansible-core >>> 2.12.x) >>> >> >> Thanks Fabian for the insights. I was planning such tests for May but >> that seems to be to late now. >> >> I remember that someone wanted to provide a meta package that pull >> additional ansible collections to give a similar experience like 2.9? >> Maybe more an EPEL question ... >> >> -- >> Leon > > There is indeed a an effort to have an ansible meta-package that would > pull both ansible-core and would contain collections (see > https://fedoraproject.org/wiki/Changes/Ansible5) > > I already had a look myself to see how to rebuild/provide it through > configmanagement SIG eventually, as we now have ansible-core availble > Some packages for ansible 5.x are already built on > koji.fedoraproject.org (see > https://koji.fedoraproject.org/koji/packageinfo?packageID=13842) but not > yet available for epel8, due to lack of ansible-core in RHEL 8 (for now, > but coming as it's in 8-stream, so in advance) > > Other introduced problem with ansible-core is the dep on python 3.8, > meaning that while we had ara (Ansible Records Ansible dashboard) > available in configmanagement SIG, it needs to be using same python > interpreter version for the callback, and previous one was built > against/for python 3.6 (like ansible 2.9.x) , so quite some changes ... > Moved this from #centos to #centos-devel: I am using an "ansible community package" (5.5.0) for testing internally now and noticed following behaviour: "yum update" obsoletes "ansible-2.9.27-1.el8.noarch" and installs ansible-core-2.12.2-2.el8.x86_64. A second "yum update" updates to ansible-core-2.12.3-1.el8.x86_64. We have the "ansible community package" as "ansible" in the repos. When doing a "yum install ansible" then dnf downgrades ansible-core to 2.12.2-2.el8. That is caused by the "Obsoletes: ansible" statement in that version but it is changed now to a "Conflicts: ansible < 2.10.0" in the newer version of ansible-core "2.12.3-1.el8.x86_64". IMO - the cs8 compose should remove the intermediate package ansible-core-2.12.2-2.el8.x86_64 to allow installing newer "ansible community package" rpms ... if it comes from the internal or in the future from the EPEL repo is irrelevant. test # rpm -q ansible-core ansible-core-2.12.3-1.el8.x86_64 test # yum install ansible Last metadata expiration check: 0:27:35 ago on Mon Apr 4 16:54:41 2022. Dependencies resolved. ================================================================================================================== Package Architecture Version Repository Size ================================================================================================================== Downgrading: ansible-core x86_64 2.12.2-2.el8 appstream 2.4 M Transaction Summary ================================================================================================================== Downgrade 1 Package Total download size: 2.4 M Is this ok [y/N]: ^COperation aborted. test # yum --exclude ansible-core-2.12.2-2.el8.x86_64 install ansible Last metadata expiration check: 0:27:49 ago on Mon Apr 4 16:54:41 2022. Dependencies resolved. ================================================================================================================== Package Architecture Version Repository Size ================================================================================================================== Installing: ansible noarch 5.5.0-1.el8 is-ws-tools 42 M Transaction Summary ================================================================================================================== Install 1 Package Total download size: 42 M Installed size: 305 M Is this ok [y/N]: Operation aborted. -- Leon

2 1

CentOS Hyperscale SIG Quarterly Report for 2022Q1
by Davide Cavalca 05 Apr '22

05 Apr '22

Hello, I've published our quarterly update for the Hyperscale SIG activities on the CentOS Blog: https://blog.centos.org/2022/04/centos-hyperscale-sig-quarterly-report-for-… Cheers Davide

3 2

9 - ? - all *release* packages
by lejeczek 05 Apr '22

05 Apr '22

Hi guys Why are *release* packages are still absent in 9? We (admins/users) read docs - take recently mentioned here Hyperscale SIG - do dns this *release* do dnf that *release* - dnf install centos-hyperscale-release - but, those are nowhere to be found or.. have I gone blind? If this all is delayed deliberately - may I ask why? many thanks, L.

4 7

repomd.xml.asc outdated for extras
by Leon Fauster 30 Mar '22

30 Mar '22

In some kind related to https://pagure.io/centos-infra/issue/550 repomd.xml and repomd.xml.asc out of "sync" for http://mirror.centos.org/centos/8-stream/extras/x86_64/os/repodata/ [TXT] repomd.xml 2022-03-28 13:52 2.9K [TXT] repomd.xml.asc 2022-03-24 00:40 811 I believe that a repo sync would sync the entire directory. So, the origin is already providing a signed file that is outdated, thought ... -- Leon

2 2

announcing "extras-common" repo for Stream 8 , managed by SIGs
by Fabian Arrotin 30 Mar '22

30 Mar '22

Following what was already implement for CentOS Stream 9 (see the https://lists.centos.org/pipermail/centos-devel/2021-November/098666.html thread), we have also created new tags on cbs.centos.org to let SIG build/push their centos-release-* pkg (containing their public gpg key, and .repo files for dnf/yum) for CentOS Stream 8. While the extras8s-extras-common-{candidate,testing,release} tags were all created some time ago (and some SIGs already tried this for -testing tag, with pkgs landing on https://buildlogs.centos.org/centos/8-stream/extras/) the -release tag itself was still locked, until the same mechanism that was implemented for Stream 9 would be working for Stream 8. Now that newer centos-gpg-keys-8-6.el8.noarch and centos-stream-repos- 8-6.el8.noarch packages are available in CentOS Stream 8 BaseOS, that means that we have now unlocked the extras8s-extras-common-release tag and so SIGs can from now on just build and tag their centos-release* packages directly through cbs and not having to ask a CentOS Stream core member to just rebuild it through distro koji (aka https://koji.mbox.centos.org) PS : as you can see the /8-stream/extras/<basearch>/os/ repo is still there,and still available on every installed CentOS 8s, but is also "frozen" from now on. The new extras-common will be populated with new builds coming from cbs.centos.org koji exclusively (as it's the case for CentOS Stream 9) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

Announcement: livesys-scripts v0.1.0
by Neal Gompa 28 Mar '22

28 Mar '22

Hello all, Over the past few months, I've been working on building new image build descriptions for the CentOS Hyperscale SIG and Fedora Cloud WG so we can migrate away from Oz/ImageFactory[0]. One detour that I took as part of doing this is an attempt to simplify the creation of live media. The tool I'm using for the Hyperscale SIG live media for CentOS Stream 9 is called kiwi[1] and it notably does not support the same script merging+inheritance model that Lorax[2] and livecd-tools[3] support that we rely on for correctly assembling the livesys init script (!!!) used to bootstrap the live environment correctly. I took a day to analyze the scripts across all the live media we have right now and made an initial attempt to convert them into more regular scripts that are invoked from systemd services. The result is livesys-scripts, which just landed in Fedora and EPEL 8/9. The project sources for livesys-scripts is here: https://pagure.io/livesys-scripts The livesys-scripts package should be agnostic to the image build tool. If you're previously relying on assembling the init script (e.g. fedora-kickstarts), the way to switch over is: 1. Delete the init script assembly logic from your kickstarts 2. Add livesys-scripts to %packages section 3. Enable livesys.service and livesys-late.service in services stanza 4. If your live ISO has a desktop environment in it, set livesys_session in /etc/sysconfig/livesys to load the correct subscript in %post. (The choices currently are: gnome, kde, cinnamon, mate, xfce, lxqt, lxde, soas, i3) If more desktops need to be supported, contribution via pull request is welcome! :) The intent of this is to make it easier to support building Fedora(ish) live media across a wider range of tools and also to synchronize what it does with improvements in dracut over time. The livesys-scripts are old and much of its functionality belongs in dracut itself. This is something that will hopefully be corrected in the near future... So, give it a try and let me know how it goes! :) [0]: https://imgfac.org/ [1]: http://osinside.github.io/kiwi/ [2]: https://weldr.io/lorax/ [3]: https://github.com/livecd-tools/livecd-tools -- 真実はいつも一つ！/ Always, there's only one truth!

1 0

CPE Weekly Update – Week of March 21st – 25th
by Michal Konecny 25 Mar '22

25 Mar '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/) If you wish to read this in form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-of-march-21s… # Highlights of the week ## Infrastructure & Release Engineering Goal of this Initiative ----------------------- Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work. It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Link to planning board: https://zlopez.fedorapeople.org/I&R-23-03-2022.pdf Update ------ ### Fedora Infra * Fixed cert generation in ipa staging (needed upgrade run) * Found problem with proxies that stopped processing, was an apache bug. Downgraded back to previous stable version. * Good progress on testing ansible upgrade. Successfully run playbooks with python3.8/ansible-core-2.12.3. * Usual business. ### CentOS Infra including CentOS CI * Kicked off work for the ansible [2.9.x => 5.x](https://pagure.io/centos-infra/issue/496) (good progress so far) * WIP : new lookaside structure and [building from gitlab](https://pagure.io/centos-infra/issue/645) (working but need now just last steps like centpkg-minimal) * Last [centos-repos](https://pagure.io/centos-infra/issue/698) should enable the extras-common repo for SIGs (autonomous from koji.mbox.centos.org koji builds) * Multiple 1:1 with phsmoura for infra onboarding * Working on [image-build issue](https://pagure.io/centos-infra/issue/708) as first ticket * Bussiness as usual: new koji tags , projects on git.centos.org/rpms ### Release Engineering * F36 Beta 1.4 * Work on SCM request automation should be finished this week - [PR](https://pagure.io/fedora-infra/toddlers/pull-request/93) ## CentOS Stream Goal of this Initiative ----------------------- This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream. Updates ------- * Troubleshooting CCCC service issues * Build & pushing Extras repos for CentOS Stream 8, once built, tags will be available * Content resolver can now differentiate between warnings (when a workload lists packages that don't exist) and failures (actual dependency problems). * DC move went well, all systems operational again ## CentOS Duffy CI Goal of this Initiative ----------------------- Duffy is a system within CentOS CI Infra which allows tenants to provision and access bare metal resources of multiple architectures for the purposes of CI testing. We need to add the ability to checkout VMs in CentOS CI in Duffy. We have OpenNebula hypervisor available, and have started developing playbooks which can be used to create VMs using the OpenNebula API, but due to the current state of how Duffy is deployed, we are blocked with new dev work to add the VM checkout functionality. Updates ------- * Focusing on documentation this week https://github.com/CentOS/duffy/issues/253 ## Bodhi Goal of this Initiative ----------------------- This initiative is to separate Bodhi into multiple sub packages, fix integration and unit tests in CI, fix dependency management and automate part of the release process. Read ARC team findings in detail at: https://fedora-arc.readthedocs.io/en/latest/bodhi/index.html Updates ------- * Got rid of the DeclEnumType warning with SQLAlchemy 1.4+ * Use namespace packages in accordance with current recommendations (avoiding needless .pth files) * Copy severity when obsoleting a security update * Updated Vagrant docs * Dependency management (ongoing) * Added procedure for pushing the snapshots to staging ## EPEL Goal of this initiative ----------------------- Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL). EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more. Updates ------- * EPEL9 up to 2187 source packages (increase of 39 from last week) * Notable EPEL9 packages now available: * [KDE Plasma](https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedo… * openvpn and NetworkManager-openvpn * Several ansible collections (general, mysql, rabbitmq, podman) Kindest regards, CPE Team

1 0

KDE ready for testing in RHEL9Beta / CentOS Stream 9
by Troy Dawson 22 Mar '22

22 Mar '22

For those of you who want to use KDE on RHEL9 Beta, or CentOS Stream 9, it is available via EPEL. It is currently plasma 5.23.5, kf5 5.90.0, qt5 5.15.2. There might be an update before RHEL 9.0 is released. There is currently a critical selinux bug[1] that prevents KDE from starting. That is the reason I have not sent this out earlier. When that get's fixed, I'll update these instructions. Note: All these steps should be done as sudo or root. Step 0 - Manually fix selinux bug setsebool -P selinuxuser_execmod 1 Step 1 - Enable CRB and Install epel-release [2] # RHEL 9 Beta subscription-manager repos --enable codeready-builder-beta-for-rhel-9-$(arch)-rpms dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm # CentOS Stream 9 dnf config-manager --set-enabled crb dnf install epel-release epel-next-release Step 2 - Install KDE dnf group install "KDE Plasma Workspaces" or dnf group install kde-desktop Step 2.a - (Optional) Install other kde groups dnf group install kde-media dnf group install kde-apps dnf install okular Step 2.b - (Optional) Set sddm as desktop manager dnf install sddm\* -y systemctl enable sddm -f Step 3 - Ensure you boot into graphical mode systemctl set-default graphical.target Step 4 - Reboot and enjoy It is recommended that you log into the Plasma (X11) vs Plasma (Wayland). There are several non-critical wayland bugs. These bugs are being addressed but aren't expected to be fixed until the RHEL 9.1 timeframe. Troy Dawson [1] - https://bugzilla.redhat.com/show_bug.cgi?id=2058657 [2] - https://docs.fedoraproject.org/en-US/epel/#_el9

3 3

CentOS Stream 9 Build environment outage today
by Brian Stinson 21 Mar '22

21 Mar '22

Hi Folks, We have a migration in progress for the CentOS Stream 9 environment today. This will affect access to kojihub.stream.centos.org while we work on this. I'll post a note here when our outage is clear. Mirror content will remain available, composes.stream.centos.org may be affected periodically throughout the day. --Brian

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel