 
            All, I have been working on this issue for a few weeks now. I am moving off old fiber-channel storage to new iSCSI, and the last device to move is the hosted-engine. From everything I have read, the standard procedure/mentality on migrating this should look as follows for 4.5, which is the version I am on: 1.) Backup existing hosted engine 2.) Set cluster into global maintenance 3.) Re-install hosted engine from backup taken in step 1 (this step fails, never gets to the point to select a new storage backend. Can't seem to find anything on why it fails reading the logs) 4.) Select new storage backend 5.) Decommission/cleanup legacy storage I have run into a few issues, mostly self-inflicted that have caused issues with upgrades, specifically using custom/external certificates for the management console instead of the default out of the box certificate set from initial install. This was done by the book, so to speak using the well documented approach on it. That is the only real customization that was done with the solution, though. This also caused issues with keycloak install/setup. As part of my continued troubleshooting with this, is there a way to revert the Apache certificates back to the internally setup/initially deployed SSL keys after the original ones have long expired? If anyone has any idea's that might help, I am open to that as well. Regards, Seann