devel August 2020

devel@lists.centos.org

27 participants
20 discussions

Re: [CentOS-devel] Centos 8.x, dlm Package unavailable
by Judd O'Bannon 18 Sep '20

18 Sep '20

> On 8/25/20 11:21 AM, Theodor Mittermair wrote: >> Hello, >> >> I'd like to inquire about the status of the "dlm" package on Centos 8, >> which is required for using 'lvmlockd', replacement of 'clvmd'. >> I also asked on #centos irc channel and was directed to this mailing list >> There is a corresponding bug ticket [2] for this issue for quite some >> time, but since the end-of-life of CentOS 6 grows closer, some people >> would like to replace their CentOS 6 Cluster with a CentOS 8 one, which >> is why I ask on this mailing list now. >> >> With the release of CentOS 8.0 it seems there were some issues with >> HighAvailability in general [1], but seem to have been resolved with >> CentOS 8.1. >> >> However, as already mentioned there is a separate ticket [2], for the >> dlm package, which is unresolved as far ( 2020-08-25, Centos8.2 ) as i >> am aware. >> This prevents the use of clustered lvm and gfs2 out of the box, not an >> uncommon use when configuring a HA Cluster, also described by RedHat >> documentation [3]. >> In that tickets' conversation, it is mentioned that "that package is not >> in RHEL .. we have released what is in RHEL", however someone else >> seemed to have been in contact with RedHat and received information that >> "...this package is in fact part of a RedHat repository and then CentOS >> members should be able to take a look into it again...". >> >> I'd also like to bring attention to the following explicitly: >> * dlm-lib and dlm seem to be built from the same source rpm, dlm-lib is >> available while dlm is not. >> * apparently at some point in time dlm could be downloaded from koji >> [4], but no more. For testing purposes we built dlm ourselves, locally >> as well as on copr [5], which seems to work thus far. >> * fedora (however much this might mean) provides dlm. >> * It might just be a configuration error on the build system, if I >> understood correctly, there was/is larger amounts of restructuring. Also >> see chders' post from 2020-08-21 [2], which provides a possible >> explanation and solution. >> >> For completeness, you should be able reproduce the absence of that >> package with: >> "yum --disablerepo='*' >> --enablerepo=BaseOS,AppStream,HighAvailability,epel,cr,centosplus,PowerTools,Devel,extras,fasttrack >> list available | grep dlm" >> or simply attempt to >> "yum install dlm" >> on your CentOS 8.x Installation. >> >> Therefore, I would like to ask: >> Is this an error on my end, am I doing something wrong or missing a >> configuration? >> If no, is there actually any political/technical/administrative/law >> based reason for the unavailability of the "dlm" package? >> If no, according to recent posts on the ticket [2], there might be a >> rather simple solution (simplified, declaring the package to be included >> in a repository), is it valid and who could do this if applicable? >> >> with best regards >> Theodor Mittermair >> <https://koji.mbox.centos.org/koji/buildinfo?buildID=4801> >> [1] https://bugs.centos.org/view.php?id=16553 >> [2] https://bugs.centos.org/view.php?id=16939 >> [3] >> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ht… >> [4] https://koji.mbox.centos.org/koji/buildinfo?buildID=145 >> [5] https://copr.fedorainfracloud.org/coprs/astra/dlm/ >> >> >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel at centos.org >> https://lists.centos.org/mailman/listinfo/centos-devel >> > Hi Folks, > > Some clarity will follow on how we plan to deliver Addon repositories > like ResilientStorage, HighAvailability and NFV. > > Because of Red Hat’s desire to develop Addons along with the next minor > release of RHEL our plan is to enable ResilientStorage and NFV in CentOS > Stream for direct consumption. > > If you think a package belongs in another repository, we encourage you > to open a CentOS Stream bugzilla to discuss with RHEL maintainers: > > https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20… > > We do not plan to expand the portfolio of Addons for CentOS Linux. > > If there is a group of interested folks who wish to maintain extra > content built against CentOS Linux, you may apply for a Special Interest > Group: https://wiki.centos.org/SIGGuide > > Cheers! > --Brian My apologies as I just subscribed to this list, I'll likely break the thread up. I did my best to contain relevance above. First question, the statement ""...Resilient Storage is not base...". There has been a shift from 7 to 8 that I don't understand. RHEL 7 provides dlm in ResilientStorage, then CentOS 7 provides dlm in base [1]. The dlm package is still part of ResilientStorage in RHEL 8, but can't be provided? I wasn't able to find any answer to why that was changed. Can you provide any insight to the shift? Second question, the current advice seems to be "dlm will be in centos-stream and you should use that." However, tdawson made a pretty explicit statement: "If people are running their production machines on CentOS Stream ... well, in my opinion, that's their problem."[2] These statements appear contradictory. Just trying to piece this all together so I can explain to my peers the business and community decisions going on here. Currently someone that set up a cluster with gfs2 in 7 can't do the same thing in 8 due to the dlm package missing. That is a loss of functionality and seems to indicate it's a bug or intentional reduction in feature set. If I'm misunderstanding any of this please educate me. Thank you, Judd [1] http://mirror.centos.org/centos-7/7/os/x86_64/Packages/dlm-4.0.7-1.el7.x86_… [2] https://lists.centos.org/pipermail/centos-devel/2020-July/037034.html

8 11

plasma has moved from epel into playground causing update conflicts
by Andy Hall 29 Aug '20

29 Aug '20

Can the below be fixed ? I guess this package should not be in both repos... # yum update Last metadata expiration check: 0:10:02 ago on Fri 28 Aug 2020 23:47:51 BST. Error: Problem 1: package plasma-workspace-geolocation-5.18.4.1-2.epel8.playground.x86_64 requires libgps.so.24()(64bit), but none of the providers can be installed - cannot install both gpsd-libs-3.18.1-2.epel8.playground.1.x86_64 and gpsd-libs-3.19-4.el8.1.x86_64 - cannot install the best update candidate for package plasma-workspace-geolocation-5.18.4.1-2.el8.x86_64 - cannot install the best update candidate for package gpsd-libs-3.19-4.el8.1.x86_64 Problem 2: problem with installed package gpsd-libs-3.19-4.el8.1.x86_64 - cannot install both gpsd-libs-3.18.1-2.epel8.playground.1.x86_64 and gpsd-libs-3.19-4.el8.1.x86_64 - cannot install both gpsd-libs-3.19-4.el8.1.x86_64 and gpsd-libs-3.18.1-2.epel8.playground.1.x86_64 - package plasma-workspace-geolocation-5.18.4.1-2.epel8.playground.x86_64 requires libgps.so.24()(64bit), but none of the providers can be installed - package plasma-workspace-geolocation-libs-5.18.4.1-2.epel8.playground.x86_64 requires plasma-workspace-geolocation = 5.18.4.1-2.epel8.playground, but none of the providers can be installed - cannot install the best update candidate for package plasma-workspace-geolocation-libs-5.18.4.1-2.el8.x86_64 # yum info plasma-workspace-geolocation Last metadata expiration check: 0:14:17 ago on Fri 28 Aug 2020 23:47:51 BST. Installed Packages Name : plasma-workspace-geolocation Version : 5.18.4.1 Release : 2.el8 Architecture : x86_64 Size : 206 k Source : plasma-workspace-5.18.4.1-2.el8.src.rpm Repository : @System >From repo : epel Summary : Plasma5 geolocation components URL : https://cgit.kde.org/plasma-workspace.git License : GPLv2+ Description : Plasma5 geolocation components. Available Packages Name : plasma-workspace-geolocation Version : 5.18.4.1 Release : 2.epel8.playground Architecture : x86_64 Size : 87 k Source : plasma-workspace-5.18.4.1-2.epel8.playground.src.rpm Repository : epel-playground Summary : Plasma5 geolocation components URL : https://cgit.kde.org/plasma-workspace.git License : GPLv2+ Description : Plasma5 geolocation components.

2 1

Update announcement question (6, 7, and 8)
by BC 28 Aug '20

28 Aug '20

I have noticed some email announcements missing recently. Just to mention a few, the 3.10.0-1127.19.1.el7, 2.6.32-754.31.1.el6, and 2.6.32-754.33.1.el6 kernels. I'm just wondering if there was a reason behind this I wasn't aware of or if it was a fluke or whatever. As to the RSS feed for 8, I'm using feeds.centos.org/ via liferea and some updates come weeks after. Is this a known issue or is my setup perhaps broken? Does anyone else see the same behavior? Thanks for all the hard work!

2 1

Scheduled RDU2 Network Maintenance 03-Sept-2020 12:00-13:00 UTC
by Brian Stinson 27 Aug '20

27 Aug '20

Hi Folks, We'd like to announce an outage window from Noon to 13:00 UTC on Thursday, 03-Sept-2020 for our services in the RDU2 Community Cage. This includes ci.centos.org, apps.ci.centos.org, apps.ocp.ci.centos.org, and cbs.centos.org During this period we expect intermittent network disconnects while our switches receive firmware upgrades. Thank you for your patience while we complete this maintenance. --Brian

1 0

8.2+Xeon: qemu-kvm: error: failed to set MSR 0x48e to 0xfff9fffe04006172
by Anthony Alba 26 Aug '20

26 Aug '20

On 8.2, with modular virt installed OR switching to centos-release-advanced-virtualization I am seeing qemu-kvm: error: failed to set MSR 0x48e to 0xfff9fffe04006172 when trying to create a VM with virt-install on a Dell PowerEdge R630 with a Xeon E5-2640. The command works on a desktop Haswell. There was such a bug in RH bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1738741 but that is about nested virtualisation and L1->L1 migration with a L2 guest. I am not doing any such magick, just a plain L1 VM. I tried reloading kvm_intel with pml=0 but got the same error. qemu-kvm-4.2.0-19.el8.x86_64 libvirt-6.0.0-17.el8.x86_64 Any ideas? (See below, does intel_iommu have to be on?) The CPU type is processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 63 model name : Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz stepping : 2 microcode : 0x43 cpu MHz : 2809.143 cache size : 20480 KB physical id : 0 siblings : 16 core id : 0 cpu cores : 8 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 15 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc dtherm ida arat pln pts md_clear flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips : 5200.46 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: # virt-host-validate QEMU: Checking for hardware virtualization : PASS QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for device assignment IOMMU support : PASS QEMU: Checking if IOMMU is enabled by kernel : WARN (IOMMU appears to be disabled in kernel. Add intel_iommu=on to kernel cmdline arguments)

2 1

Centos 8.x, dlm Package unavailable
by Theodor Mittermair 25 Aug '20

25 Aug '20

Hello, I'd like to inquire about the status of the "dlm" package on Centos 8, which is required for using 'lvmlockd', replacement of 'clvmd'. I also asked on #centos irc channel and was directed to this mailing list There is a corresponding bug ticket [2] for this issue for quite some time, but since the end-of-life of CentOS 6 grows closer, some people would like to replace their CentOS 6 Cluster with a CentOS 8 one, which is why I ask on this mailing list now. With the release of CentOS 8.0 it seems there were some issues with HighAvailability in general [1], but seem to have been resolved with CentOS 8.1. However, as already mentioned there is a separate ticket [2], for the dlm package, which is unresolved as far ( 2020-08-25, Centos8.2 ) as i am aware. This prevents the use of clustered lvm and gfs2 out of the box, not an uncommon use when configuring a HA Cluster, also described by RedHat documentation [3]. In that tickets' conversation, it is mentioned that "that package is not in RHEL .. we have released what is in RHEL", however someone else seemed to have been in contact with RedHat and received information that "...this package is in fact part of a RedHat repository and then CentOS members should be able to take a look into it again...". I'd also like to bring attention to the following explicitly: * dlm-lib and dlm seem to be built from the same source rpm, dlm-lib is available while dlm is not. * apparently at some point in time dlm could be downloaded from koji [4], but no more. For testing purposes we built dlm ourselves, locally as well as on copr [5], which seems to work thus far. * fedora (however much this might mean) provides dlm. * It might just be a configuration error on the build system, if I understood correctly, there was/is larger amounts of restructuring. Also see chders' post from 2020-08-21 [2], which provides a possible explanation and solution. For completeness, you should be able reproduce the absence of that package with: "yum --disablerepo='*' --enablerepo=BaseOS,AppStream,HighAvailability,epel,cr,centosplus,PowerTools,Devel,extras,fasttrack list available | grep dlm" or simply attempt to "yum install dlm" on your CentOS 8.x Installation. Therefore, I would like to ask: Is this an error on my end, am I doing something wrong or missing a configuration? If no, is there actually any political/technical/administrative/law based reason for the unavailability of the "dlm" package? If no, according to recent posts on the ticket [2], there might be a rather simple solution (simplified, declaring the package to be included in a repository), is it valid and who could do this if applicable? with best regards Theodor Mittermair <https://koji.mbox.centos.org/koji/buildinfo?buildID=4801> [1] https://bugs.centos.org/view.php?id=16553 [2] https://bugs.centos.org/view.php?id=16939 [3] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ht… [4] https://koji.mbox.centos.org/koji/buildinfo?buildID=145 [5] https://copr.fedorainfracloud.org/coprs/astra/dlm/

3 3

CPE Feedback Survey
by Ant Carroll 21 Aug '20

21 Aug '20

Hey folks, CPE <https://docs.fedoraproject.org/en-US/cpe/>need your help :) Over the last several months we've been trying to improve how we interact and share information with you all. From the blog posts, to mails and how we work on the tickets you send us. Here is a link to a very short survey we've put together to learn how we can give you the best experience possible going forward by understanding the experiences you've had recently. If you could take the time (5mins max) to complete it for us it would be hugely valuable as we work on this continuous improvement - https://fedoraproject.limequery.com/696793?lang=en <https://meet.google.com/linkredirect?authuser=0&dest=https%3A%2F%2Ffedorapr…> Cheers, Ant -- Ant Carroll Associate Manager, CPE Team Red Hat Waterford <http://www.redhat.com> Communications House Cork Road, Waterford City ancarrol(a)redhat.com M: +353876213163 IM: ancarrol @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://www.redhat.com/>

1 1

Missing -devel packages
by Orion Poplawski 16 Aug '20

16 Aug '20

Is there anything I can do to help out with missing -devel packages in CentOS 8? I'm waiting for a number of them, e.g.: https://bugs.centos.org/view.php?id=17401 Thanks, Orion -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 https://www.nwra.com/

5 10

CPE Weekly: 2020-08-14
by Aoife Moloney 14 Aug '20

14 Aug '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-08-14 Background: The Community Platform Engineering group, or CPE for short, 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. See our wiki page here for more information:https://docs.fedoraproject.org/en-US/cpe/ ## General Project Updates The CPE team are working on the following projects for Quarter 3, which is the months of July, August & September: * Data Centre Move - Final Works * CentOS Stream Phase 3 * Noggin Phase 3 * Packager Workflow Healthcare * Fedora Messaging Schemas Details of the above projects, and of projects currently in progress, done and what projects are in our backlog, can be found on our taiga board per project card: https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null We also have an updated initiative timetable for briefing in new projects to our team & key dates here:https://docs.fedoraproject.org/en-US/cpe/time_tables/ *Note: Initiatives are large pieces of work that require a team of people and weeks/months to complete. Please continue to open tickets in the normal way for bugs, issues, etc. ### CPE Product Owner Office Hours #### #fedora-meeting-1 * Weekly on Thursdays @ 1300 UTC on #fedora-meeting-1 * Next Meeting: 2020-08-20 #### #centos-meeting * Every second Tuesday @ 1500 UTC on #centos-meeting * Next Meeting: 2020-08-18 ### Misc #### Nest With Fedora Note Thank you to everyone who attended Nest With Fedora over the weekend and engaged with us during our talks and social sessions. It was a fantastic event, very well put together and run by the Fedora team and it was both my pleasure and honour to have been a part of what was a fantastic schedule! I cant wait to catch up on talks I missed when they are uploaded, and the CPE team, with thanks to Michal Konecny who put the structure of our piece together, will be submitting a collaborative blog post to the Community blog space in the coming weeks, recapping our experience at Nest this year. Well done Marie Nordin, Matthew Miller and the wider team, and our very own Vipul Siddarth, on what was a very successful and enjoyable event! #### Engagement Email Feedback At the beginning of July I sent an email to devel-announce requesting feedback from the community on changes I and the wider CPE team have made when scheduling projects to work on, in an effort to find the balance between work and life. We are still searching :) However, I got some very good tips that I will definitely be incorporating which I shared at Nest during the CPE AMA Session and in reply to the original mail. The link to the mails are here for full reading https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… But the suggestions and actions are here for quicker reference: Continue to communicate regularly on projects & updates - Will do, weekly emails have been a bit more sporadic lately as I have had some time off Less acronyms & abbreviations in comms :) - Sure, that's an easy fix on my end and makes sense Publish team members timezone on docs.fpo/cpe to help define our ‘working hours’ - Will do, I hope to get to this by end of August and they will be reflected on docs.fpo/cpe Publish the workflow diagram to docs.fpo/cpe and add filtered versions that are user specific - Same as above, publishing it on docs.fpo/cpe-initiatives Office Hours on IRC are a useful way to contact team Product Owner - Great to hear, please feel free to stop by when you can/want to. They are on Thursdays @ 1300 UTC on #fedora-meeting-1 and every second Tuesday @ 1500 UTC on #centos-meeting Public tracker for bugs - Our team meets twice a day, every day on IRC to review tickets and issues to work on. They meet @ 0830 UTC on #centos-meeting and again @ 1800 UTC on #fedora-admin. These are public meetings so please feel free to attend. If you would like to offer any further suggestions or feedback on the Community Platform Engineering team, please feel free to complete our survey which is open until August 30th https://fedoraproject.limequery.com/696793?lang=en ## Fedora Updates ### Data Centre Move * Nearly done!!!!!! * Firewalls for staging are going up this week * Last of the hardware has been set up for networking changes * The bringup of Communishift is being made into a dedicated project for work as soon as the team have capacity to do so - this may be in late September as the members of the colo team will (hopefully) take some very well deserved time off work before tackling this one :) ### AAA Replacement * Some of the Noggin team have been enjoying some very well deserved time off work over the last week or two so work has, naturally slowed. * The code is currently being security audited by Patrick Uiterwijk, thank you Patrick! * Next steps will be to successfully deploy Noggin to staging when it has been brought back up - we are estimating this to be late next week * Once Noggin has been deployed to staging, we would love some community feedback on the application and its performance. We will be emailing the infra/devel lists on when to test and how to give us feedback when we are fully deployed in stg. * In the meantime. Please feel free to check out the team kanban board for more information on the features the team are working on and have already completed here https://github.com/orgs/fedora-infra/projects/6 ### Fedora Messaging Schemas * This project is being worked on by the same team as Noggin, so there has been some progress made but not a lot as team members enjoy some holidays * The team have already built a list of applications that require messaging schemas, list can be found here https://hackmd.io/@nilsph/H1i8CAbkP/edit * They also have completed a readme which contains documentation on messaging schemas, a cookie-cutter template to create the schema and a definition of Done for writing a schemas https://github.com/fedora-infra/fedora-messaging-schemas-issues * The board they are working from can be viewed here https://github.com/orgs/fedora-infra/projects/7 ### Packager Workflow Healthcare * Project information: This is an investigative project that aims to look at the entire packager workflow as a single piece of tooling to identify where failures happen, and try to identify when and why packages fail at different points within the workflow. We hope to have two possible outcomes from this project at the end of the quarter (September): * The workflow breaks at X point and we will work on a solution to fix * OR * The workflow works fine, but we will need better monitoring on the pipeline so we will work on a solution for this * The team are using this Monitor-Script https://pagure.io/fedora-ci/monitor-gating/ and are making improvements to it on resiliency/reliability. * They are finishing the investigation phase of the project and are going to document the packager workflow (with graphs I have been promised!) showcasing how the different systems interact with one another * And are working on an outline of the workflow steps (from packager PoV) and systems involved (CPE team PoV), identifying metrics to be measured * The teams work is being tracked here https://teams.fedoraproject.org/project/cpe-cicd/kanban ## CentOS Updates ### CentOS * CentOS-infra team have created a ticket board, check it out here https://pagure.io/centos-infra/boards/CentOS%20CI%20Infra * CBS Koji x86 builders moved to new(er) infrastructure (https://lists.centos.org/pipermail/centos-devel/2020-August/055988.html) * The team also caught up C6, C7 and C8 Linux .. 2 outstanding Bootstrap Modules for C8 Linux (eclipse and the latest rust-toolset). ### CentOS Stream * Not too much to report this week - The team are mostly working on developing utility scripts that will ease the CentOS 8 and CentOS Stream packaging workflow and business as usual updates to CentOS Stream. As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great week! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Infra Pre-Announce : moving CI ssh jump host soon, please read !
by Fabian Arrotin 13 Aug '20

13 Aug '20

Hi, As you noticed recently, we started to refresh the infra used for CentOS CI (not the hardware, still the same, but the software stack and the way to control/manage it). One of the identified nodes still being used and that needs to be converted to the new infra layout is the ssh jumphost (see https://wiki.centos.org/QaWiki/CI/GettingStarted#How_to_use_it) Normally, some of you have switched to OpenShift workload, (including to the new Openshift 4/OCP setup that went live recently) but some Projects are still on the old setup with sometimes a need to reach dedicated/shared VMs acting as Jenkins agent[s], connected to Jenkins behind https://ci.centos.org. We have already provisioned a new VM in the new setup (that can reach the whole CI subnet and VLAN) but here are some points to consider, reason why we wanted to pre-announce long time in advance before we do the real switch) : * New ssh jump host is CentOS 8 based, versus CentOS 6, meaning that if you used ssh-dss key (instead of ssh-rsa), you'll *not* be able to connect through that new host. We already identified such keys and Vipul will try (when it's tied to a real email address for the project) to reach out. But better to announce it here too, so that you have time to ask us to reflect a change (through ticket on https://pagure.io/centos-infra/issues) * Old VM allowed shell access, but it will be disallowed on the new one (there is no need for shell on that intermediate node anyway). Reminder that you can configure your ssh config to directly use ProxyCommand or even now ProxyJump (on recent openssh-client). See https://wiki.centos.org/TipsAndTricks/SshTips/JumpHost) * Because the host has a new sshd_host_key, it will come with a new fingerprint too, so if you have automation and that you don't trust our CA already, the fingerprint for new host will be : [fingerprint] rsa=3072 SHA256:n7y0qZS/FvhjaskOBds3TTKQh5EtgNQ25E7cmTNBATg (RSA) rsa_md5=3072 MD5:9e:83:46:d0:c5:8a:a0:94:50:10:58:9d:af:ca:50:19 (RSA) ecdsa=256 SHA256:ZQacwDsWkKBYL9HJJYwHr94Ny1sMhHMDnz9GiLFb8Uc (ECDSA) ecdsa_md5=256 MD5:dd:24:ea:6a:fd:8b:29:3d:1d:d0:a9:32:8c:b2:ea:62 (ECDSA) As we know that it's August and that some of you are probably on PTO (coming back or leaving soon), after discussion with Vipul , David and myself, we considered that we'll probably go live around beginning of September. Should you have any question around that migration, feel free to reply to this thread (ideally on dedicated ci-users mailing list), or on irc.freenode.net (#centos-ci) On behalf of the CentOS CI infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel August 2020