All, My team is in a different department than Dell / ESG (the group that develops/maintains OMSA & DSU). As such, we are consumers of DSU & OMSA.
We encountered this situation early on in our RHEL8 build development. While we did report this situation back, from my notes -- I realize the resolution is not quite that bad. Libssh2 RPM is available in the Appstream8.latest RHN channel. The current version is libssh2-1.8.0-8.module+el8.0.0+5339+ebcc8ca7.1.x86_64.rpm. (I just checked). This does present our RHEL8 build with a small "chicken and egg" problem. Our initial base install is RHEL8.1 based. Inexplicably, the libssh2 RPM does not appear to be in the RHEL81.based channel, but only in the Appstream8.latest channel. We lay down a base build, then apply dsu (if physical), then at a very late build stage -- we update to latest & greatest (whatever is current this month). Update to latest & greatest is a glorified yum update -- against RHEL8.latest and Appstream8.latest. So we have to stage some initial version of libssh2 RPM in one of our (company-internal) custom yum repos for the initial dsu install/invocation. However, if there's a later version available in Appstream8.latest, it'll pick that up (during the "upgrade to latest & greatest"). I believe we've grabbed that libssh2-1.8.0-8.module+el8.0.0+5339+ebcc8ca7.1.x86_64.rpm from AppStream8.latest and we've staged it. So while I agree that it'd be best for the dsu RPM do not have an RPM dependency on the libssh2 RPM, the required resolution is not as drastic as described -- no need to mirror the entire EPEL. (That bad boy is huge!!) If you had the AppSteam8.latest channel definition already set up prior to your dsu install, then our miniscule tap-dance above would not even be necessary. You could immediately just do a 'yum install dsu'. Spike White Dell I/T ---------------------------------------------------------------------- Message: 1 Date: Thu, 2 Jul 2020 06:49:59 +0000 From: Ben Argyle <[email protected]> To: "[email protected]" <[email protected]> Subject: Re: [Linux-PowerEdge] Dell DSU for Linux (RHEL8/CentOS8) now requires EPEL Message-ID: <lnxp265mb124460522252f130112980828b...@lnxp265mb1244.gbrp265.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" [EXTERNAL EMAIL] That's a good catch. Hopefully Dell will act soon... However, wasn't there some discussion of OMSA/dsu moving away from libssh2? Did anything come of that? I can't think all customers of Dell would be happy to enable EPEL on their servers to get official Dell support functionality working. Ben -----Original Message----- From: Linux-PowerEdge <[email protected]> On Behalf Of Hanby, Mike Sent: 01 July 2020 16:54 To: [email protected] Subject: [Linux-PowerEdge] Dell DSU for Linux (RHEL8/CentOS8) now requires EPEL [EXTERNAL EMAIL] Howdy, If anyone monitoring this mailing list has edit perms for https://linux.dell.com/repo/hardware/dsu/ , please add a note that the EPEL repository is now required for RHEL8/CentOS8. Red Hat stopped providing libssh2 in the RHEL8 repos (CentOS has mirrored the behavior as expected). The package maintenance has now moved to EPEL. libssh2 is the only library required by /usr/sbin/dsu that isn't available in the official repositories. Thanks, Mike ---------------- Mike Hanby mhanby @ uab.edu Systems Analyst III - Enterprise IT Research Computing Services The University of Alabama at Birmingham _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge ------------------------------ Subject: Digest Footer _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge ------------------------------ End of Linux-PowerEdge Digest, Vol 188, Issue 2 *********************************************** _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
