Running yum update on 4.5 appliance before configuration creates a v2_key
Issue
- When deploying a 4.5.0 appliance and then running yum update it to 4.5.1 before you configure it the v2_key gets created. If you then attempt to configure the appliance through the
appliance_console
it will error and state that it found a v2_key and to use the--force-key flag
.
Environment
- Red Hat CloudForms 4.5 (CFME 5.8)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.