---> Package rdma.noarch 0:7.3_4.7_rc2-6.el7_3 will be obsoleted
---> Package rdma-core.i686 0:13-7.el7 will be obsoleting
--> Processing Dependency: libudev.so.1(LIBUDEV_183) for package: rdma-core-13-7.el7.i686
--> Processing Dependency: libudev.so.1 for package: rdma-core-13-7.el7.i686
--> Processing Dependency: libc.so.6(GLIBC_2.16) for package: rdma-core-13-7.el7.i686
---> Package rdma-core.x86_64 0:13-7.el7 will be obsoleting
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for systemd-libs which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of systemd-libs of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude systemd-libs.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of systemd-libs installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
3. You have duplicate versions of systemd-libs installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
Protected multilib versions: systemd-libs-219-42.el7_4.1.i686 != 100:systemd-libs-219-42.an3.x86_64
Error: Protected multilib versions: pam-1.1.8-18.el7.i686 != 1:pam-1.1.8-18.an3.x86_64