RHEV: Using a colon in the engine database password causes upgrades to be treated as fresh installs
Issue
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
Environment
- 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.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
