The database the servers won't let you upgrade
A manufacturer runs MongoDB 4.4 replica sets on plant-floor virtual machines whose hypervisor exposes a generic CPU model without AVX. MongoDB 5.0 and later require AVX, so the databases cannot move until the hosts are replaced.
Challenge
The hardware refresh is budgeted over two years. Until then, 4.4 is past end of life and any post-EOL patches from MongoDB are discretionary, with no commitment the next one will come.
Environment
Self-managed MongoDB 4.4 Community Server on on-premises hypervisors, no AVX exposed to guests.
Approach
OSSeva provides committed security coverage for 4.4 on the existing hardware, then plans the sequence of 5.0, 6.0 and 7.0 upgrades host by host as the refresh lands.
What this delivers
Patched databases on hardware the plant already owns, and an upgrade plan tied to the refresh schedule.