RHEV: Using a colon in the engine database password causes upgrades to be treated as fresh installs

Solution Verified - Updated -


When upgrading from RHEV 3.2 to RHEV 3.3, the upgrade is treated as a fresh install, completely wiping out the existing environment.

NOTE: This bug is being tracked in BZ#1064428


  • Red Hat Enterprise Virtualization (RHEV) 3.2
  • Red Hat Enterprise Virtualization (RHEV) 3.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In