Upgrade MongoDB 5.0.18 -> 6.0.14 , RHEL 8.9 , dependency problem (yum update)

Ops and Admin Installation & Upgrades
, ,
1

Good afternoon,

I have RHEL 8.9 and MongoDB 5.0.18. Community.
I want to upgrade to latest version 6.0.14. According to documentation, yum update of packages should
be possible and pretty easy, but I get errors that complains about version of some OS libs that are only found in RHEL 9 and cannot be installed on RHEL 8.
(My question is at the bottom of this post (topic).)

Error:
Problem 1: cannot install the best update candidate for package mongodb-database-tools-100.7.0-1.x86_64

  • nothing provides libc.so.6(GLIBC_2.34)(64bit) needed by mongodb-database-tools-100.9.4-1.x86_64
    Problem 2: cannot install the best update candidate for package mongodb-org-mongos-5.0.18-1.el8.x86_64
  • nothing provides libcrypto.so.3()(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64
  • nothing provides libcrypto.so.3(OPENSSL_3.0.0)(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64
  • nothing provides libssl.so.3()(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64
  • nothing provides libssl.so.3(OPENSSL_3.0.0)(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64
  • nothing provides libc.so.6(GLIBC_2.34)(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64
  • nothing provides libm.so.6(GLIBC_2.29)(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64
    Problem 3: cannot install the best update candidate for package mongodb-org-server-5.0.18-1.el8.x86_64
  • nothing provides libcrypto.so.3()(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64
  • nothing provides libcrypto.so.3(OPENSSL_3.0.0)(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64
  • nothing provides libssl.so.3()(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64
  • nothing provides libssl.so.3(OPENSSL_3.0.0)(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64
  • nothing provides libc.so.6(GLIBC_2.34)(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64
  • nothing provides libm.so.6(GLIBC_2.29)(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64
    (try to add ‘–skip-broken’ to skip uninstallable packages or ‘–nobest’ to use not only best candidate packages)

Options --nobest and --skip dependency did not help because package would not be installed (upgraded)

with ‘nobest’: just skips…

yum update --nobest

Last metadata expiration check: 2:56:29 ago on Thu 29 Feb 2024 10:30:57 AM CET.
Dependencies resolved.

Problem 1: cannot install the best update candidate for package mongodb-org-mongos-5.0.18-1.el8.x86_64

  • nothing provides libcrypto.so.3()(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64 from mongodb-org-6.0
  • nothing provides libcrypto.so.3(OPENSSL_3.0.0)(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64 from mongodb-org-6.0
  • nothing provides libssl.so.3()(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64 from mongodb-org-6.0
  • nothing provides libssl.so.3(OPENSSL_3.0.0)(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64 from mongodb-org-6.0
  • nothing provides libc.so.6(GLIBC_2.34)(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64 from mongodb-org-6.0
  • nothing provides libm.so.6(GLIBC_2.29)(64bit) needed by mongodb-org-mongos-6.0.14-1.el9.x86_64 from mongodb-org-6.0
    Problem 2: cannot install the best update candidate for package mongodb-org-server-5.0.18-1.el8.x86_64
  • nothing provides libcrypto.so.3()(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64 from mongodb-org-6.0
  • nothing provides libcrypto.so.3(OPENSSL_3.0.0)(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64 from mongodb-org-6.0
  • nothing provides libssl.so.3()(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64 from mongodb-org-6.0
  • nothing provides libssl.so.3(OPENSSL_3.0.0)(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64 from mongodb-org-6.0
  • nothing provides libc.so.6(GLIBC_2.34)(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64 from mongodb-org-6.0
  • nothing provides libm.so.6(GLIBC_2.29)(64bit) needed by mongodb-org-server-6.0.14-1.el9.x86_64 from mongodb-org-6.0
    =====================================================================================================================
    Package Architecture Version Repository Size
    =====================================================================================================================
    Upgrading:
    mongodb-mongosh x86_64 2.1.5-1.el8 mongodb-org-6.0 51 M
    mongodb-org x86_64 6.0.14-1.el9 mongodb-org-6.0 9.3 k
    mongodb-org-database x86_64 6.0.14-1.el9 mongodb-org-6.0 9.4 k
    mongodb-org-database-tools-extra x86_64 6.0.14-1.el9 mongodb-org-6.0 14 k
    mongodb-org-tools x86_64 6.0.14-1.el9 mongodb-org-6.0 9.3 k
    Skipping packages with broken dependencies:
    mongodb-org-mongos x86_64 6.0.14-1.el9 mongodb-org-6.0 21 M
    mongodb-org-server x86_64 6.0.14-1.el9 mongodb-org-6.0 30 M

Transaction Summary

Upgrade 5 Packages
Skip 2 Packages

Total download size: 51 M
Is this ok [y/N]: N

I have overriden problem by manually downloading rpm packages for RHEL 8 from packages there had problem with dependency:

mongodb-database-tools-rhel80-x86_64-100.9.4.rpm
mongodb-org-mongos-6.0.14-1.el8.x86_64.rpm
mongodb-org-server-6.0.14-1.el8.x86_64.rpm

and installed it by using command yum install -y filename(package).rmp

yum install -y mongodb-org-mongos-6.0.14-1.el8.x86_64.rpm
yum install -y mongodb-database-tools-rhel80-x86_64-100.9.4.rpm
yum install -y mongodb-org-mongos-6.0.14-1.el8.x86_64.rpm

It was successful and what was left of version 5.0.18 I have removed with command rpm -e pkgname

rpm -qa | grep mongod

mongodb-database-tools-100.9.4-1.x86_64
mongodb-org-6.0.14-1.el9.x86_64
mongodb-org-server-6.0.14-1.el8.x86_64
mongodb-org-database-6.0.14-1.el9.x86_64
mongodb-org-mongos-6.0.14-1.el8.x86_64
mongodb-org-tools-6.0.14-1.el9.x86_64
mongodb-mongosh-2.1.5-1.el8.x86_64
mongodb-org-shell-5.0.18-1.el8.x86_64
mongodb-org-database-tools-extra-6.0.14-1.el9.x86_64

rpm -e mongodb-org-shell-5.0.18-1.el8.x86_64

rpm -qa | grep mongod

mongodb-database-tools-100.9.4-1.x86_64
mongodb-org-6.0.14-1.el9.x86_64
mongodb-org-server-6.0.14-1.el8.x86_64
mongodb-org-database-6.0.14-1.el9.x86_64
mongodb-org-mongos-6.0.14-1.el8.x86_64
mongodb-org-tools-6.0.14-1.el9.x86_64
mongodb-mongosh-2.1.5-1.el8.x86_64
mongodb-org-database-tools-extra-6.0.14-1.el9.x86_64

yum list | grep mongo

yum list | grep mongo

mongodb-database-tools.x86_64 100.9.4-1 @@commandline
mongodb-mongosh.x86_64 2.1.5-1.el8 @mongodb-org-6.0
mongodb-org.x86_64 6.0.14-1.el9 @mongodb-org-6.0
mongodb-org-database.x86_64 6.0.14-1.el9 @mongodb-org-6.0
mongodb-org-database-tools-extra.x86_64 6.0.14-1.el9 @mongodb-org-6.0
mongodb-org-mongos.x86_64 6.0.14-1.el8 @@commandline
mongodb-org-server.x86_64 6.0.14-1.el8 @@commandline
mongodb-org-tools.x86_64 6.0.14-1.el9 @mongodb-org-6.0
mongocli.x86_64 1.31.3-1 mongodb-org-6.0
mongodb-atlas.x86_64 1.15.0-1 mongodb-org-6.0
mongodb-atlas-cli.x86_64 1.15.0-1 mongodb-org-6.0
mongodb-mongosh-shared-openssl11.x86_64 2.1.5-1.el8 mongodb-org-6.0
mongodb-mongosh-shared-openssl3.x86_64 2.1.5-1.el8 mongodb-org-6.0
mongodb-org-mongos.x86_64 6.0.14-1.el9 mongodb-org-6.0
mongodb-org-server.x86_64 6.0.14-1.el9 mongodb-org-6.0

Now we are clear on 6.0.14
MONGODB 6.0.14
MONGO DATABASE TOOLS 100.9
MONGO SHELL 2.1.5

QUESTION is - what happened and is this OK as an upgrade procedure?
RHEL 8.9, according to docs, update should be successful - but missing dependencies from RHEL 9? Why, anyone knows? Mongo v6 is still possible to run on RHEL 7, 8, 9 officialy.

Thank you for answer or comments.

Best regards,
Branimir Putniković

2

Hi @Branimir_Putnikovic

Please review: Formatting code and log snippets in posts

Based on the packages that are mentioned in the output it looks like the RHEL9 repository was added to the system instead of the RHEL8 one.

It looks like the metapackages are the only el9 one remaining. There is a possibility that one of these could be updated in way that could cause issues later on.

I would recommend fixing the repo and installing the correct packages.

1 Like
3

Hi @chris ,

you are right, thank you very much. It was a tip-feller that we were not aware of.

Best regards,
Branimir