The familiar (and long-standing) Yum package manager is gone.
In its place is the much more powerful and intelligent Dandified Yum (DNF).
Instead of just marching forward, as if DNF were there all along, let’s take a look at why this happened, why it’s a good thing, and how the new package management system is used.
Before we do this, understand those of you who never touch the command line (which on a Fedora system might be a bare minimum) will not see anything different.
After installing upgraded packages you must run a few more steps to complete the upgrade.
These are the basic steps to upgrading own Cloud: Your Linux package manager only downloads the current own Cloud packages.
So, be sure to deploy the packages for the shared libraries from My SQL on those systems.
You can do this by adding the My SQL Yum repository to the systems (see Adding the My SQL Yum Repository) and install the latest shared libraries using the instructions given in Installing Additional My SQL Products and Components with Yum.
As typical with new versions of shared libraries where there are differences or additions in symbol versioning between the newer and older libraries (for example, between the newer, standard 5.6 shared client libraries and some older—prior or variant—versions of the shared libraries shipped natively by the Linux distributions' software repositories, or from some other sources), any applications compiled using the updated, newer shared libraries will require those updated libraries on systems where the applications are deployed.
And, as expected, if those libraries are not in place, the applications requiring the shared libraries will fail.
It is best to update your own Cloud installation with every new point release (e.g.