Is there any way to correlate modular package versions in RHEL8.x with ones from Centos8.x in any way, no matter how difficult?
For example, looking at package list for https://access.redhat.com/errata/RHSA-2020:3714:
- RedHat lists httpd-2.4.37-21.module+el8.2.0+5008+cca404a3.x86_64.rpm
- in CentOS this (probably?) matches httpd-0:2.4.37-21.module_el8.2.0+494+1df74eae.x86_64
AFAIK, the non-modular packages shared the same NEVRA between RHEL and Centos (not sure if there were exceptions, though).
Thanks,
Antal
============================================================
#centos-meeting: CentOS Storage SIG Monthly, October Edition
============================================================
Meeting started by ndevos at 13:04:08 UTC. The full logs are available
at
https://www.centos.org/minutes/2020/October/centos-meeting.2020-10-06-13.04…
.
Meeting summary
---------------
* Roll Call (ndevos, 13:04:19)
* Agenda (ndevos, 13:06:02)
* LINK: https://hackmd.io/Epc35JIESaeotoGzwu5R5w (ndevos, 13:06:06)
* Ceph Builds (ndevos, 13:08:11)
* AGREED: kkeithley stepped in to help get Ceph back on track, but
wasn't volunteering to keep doing building ceph packages for ever
(ndevos, 13:08:36)
* centos-release-gluster packages (ndevos, 13:09:30)
* hughesjr will try to include centos-release-gluster8 when 7.9 is
released (ndevos, 13:17:01)
* Open Floor (ndevos, 13:21:14)
* LINK: https://pagure.io/centos-infra/issue/50 (ndevos, 13:28:35)
Meeting ended at 13:30:28 UTC.
Yesterday (Saturday) evening we got zabbix notifications that some nodes
in CI environment were unreachable. After a quick look, I discovered
that it was an embedded network switch in a chassis hosting multiple
nodes (including but not limited to jenkins node behind ci.centos.org)
that went nuts.
I tried a remote "hardware reset" and nodes were back online after ~10min.
But this morning (sunday), I see through zabbix that same issue happened
again, and in the hour after I already did the "hardware reset", but
this time, even that doesn't work anymore.
So that means that we have a network switch not working anymore.
As that chassis (like almost *all* equipment in CI) *isn't* under
warranty, we'll see on monday what can be done and how we give priority
to try to dispatch services elsewhere (and that probably means then
powering down other services , depending on priority that will be
given), but it's easy to understand that we can't even give any ETA at
this point.
Thanks for your comprehending,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | twitter: @arrfab