+ Depending on the order of the found available packages the wrong rdma
package may be installed. Use the proper variable to identify the
package version to install
+ Fix comparison issue that causes the installed RDMA package to not
be detected. Tris triggers a re-install of the package which in turn
triggers a reboot. Thus we end up in a endless reboot loop.
Ubuntu packages multiple versions of RDMA driver in the kernel. This adds support for resolving the correct driver based on the host ND version, and to update kernel if none is found.
+ When the online repo is not available zypper could hang on waiting for
user confirmation about skipping the repo, we also tried to refresh
the repo again after we already knew it was not available.
+ Code generated an error on zypper return code 106, which only indicates
that repos were skipped but does not mean package install failed.
* Fix RDMA package version matching
The pattern matching for the RPM naming is too strict:
- We actually have a 4.1.3.2 bugfix release now, but pattern only allows
3-digit naming
- We may have multi-digit version numbers in the future
* Fix RDMA update regex as well
* Return failure if module is already loaded at the time of probe
* Return failure when module is not present in lsmod
* CentOS: Reboot the system when newly installed RDMA module fails to probe or load
* SUSE: Reboot the system when newly installed RDMA module fails to probe or load
* rdma/common: add kvpd check
Signed-off-by: Ahmet Alp Balkan <ahmetalpbalkan@gmail.com>
* rdma/centos: install kvpd if missing
Signed-off-by: Ahmet Alp Balkan <ahmetalpbalkan@gmail.com>
* rdma: resequence device operations, add log
* - Integrate RDMA handling
* - RDMA Integration
+ Fix syntax errors
+ Use the full distro name to differentiate properly between openSUSE
(which has currently no RDMA driver build) and SLES
* - RDMA integration
+ Do not stop the execution of the agent work flow by throwing an
exception if the RDMA handler is not specialized. Simply log an error
to indicate that the handler is not supported although it has been
configured with OS.EnableRDMA=y. The configuration in this case is in
error.
* - RDMA integration
+ Document he new OS.EnableRDMA configuration setting
Robert Schweikert