#Anyone install ONTAP Mediator 1.6 on Rocky Linux 9.1 ?

1 messages · Page 1 of 1 (latest)

rustic iron
#

Anyone successfully installed ONTAP Mediator 1.6 on Rocky Lunix 9.1 ?

im getting this error

Package openssl-1:3.0.1-43.el9_0.x86_64 is already installed.
No match for argument: kernel-devel-5.14.0-162.6.1.el9_1.x86_64
Package libselinux-utils-3.4-3.el9.x86_64 is already installed.
Package perl-Data-Dumper-2.174-462.el9.x86_64 is already installed.
Package bzip2-1.0.8-8.el9.x86_64 is already installed.
Package efibootmgr-16-12.el9.x86_64 is already installed.
Package mokutil-2:0.4.0-9.el9.x86_64 is already installed.
Package policycoreutils-python-utils-3.4-4.el9.noarch is already installed.
Package python3-3.9.14-1.el9_1.1.x86_64 is already installed.
Error: Unable to find a match: kernel-devel-5.14.0-162.6.1.el9_1.x86_64

Error: Failed to install required OS packages. View log for details.

Error: install failed.
Script failed. Moving log file to /var/tmp/

Any hints or tips ?

rustic iron
#

fixed i added the devel repo and it seemed to picked it up.. I think its a bug in Rocky 9.1.. i find it funny NetApp have released Appliances for pretty much every other Application but the Mediator requires you to roll your own Linux release..Whats that about ?

verbal lake
#

I second that! An appliance would be so much more efficient!

runic stag
#

I think it's an update thing. Since the mediator relies on custom kernel modules that require very specific kernel versions to build against, it's tricky to update the OS. And if you keep it on lower versions, customers will complain that you don't have a recent kernel. The way it is now, they're sidestepping this problem in an elegant way 😉

#

but there is an easy solution: you can build your own appliance and distribute that to customers (that's what we did, for example, for customers who don't have Linux and/or Linux experience)

limber acorn
#

Modify /etc/redhat-release to be rhel.

runic stag
#

sadly, that won't help much if the kernel doesn't match ...

#

Another solutiuon would be for NetApp to move away from the in-kernel SCST target and move the iscsi stack into a userspace program (e.g. the mediator itself). It shouldn't matter much for the low volume of data/IO that is happening to the mailbox disks, and it would make the whole system independent of the kernel version

limber acorn
#

Actually, I did just that on Rocky Linux. Of course the packages need to be available, but there was a point during install that failed because it wasn’t a supported operating system. We looked through the install scripts and it was simply looking at /etc/redhat-release for confirmation