Created attachment 892268 [details] setup log + answer file Description of problem: Using 3 parts upgrade process (engine, dwh & reoprts frfom 3.3.2), craeting snapshot after each phase, the dwh patrs fails using the answer file, created before due to bad credentials (it works when rthe questions are answer manually): [root@fire33-rep yum.repos.d]# rhevm-setup --config-append=dwh2.conf [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-dwh.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf', '/etc/yum.repos.d/dwh2.conf'] Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20140504135223.log Version: otopi-1.2.0 (otopi-1.2.0-1.el6ev) [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to DWH database using existing credentials: engine_history@None:None [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140504135223.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20140504135228-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed Version-Release number of selected component (if applicable): av8.1 How reproducible: 100% Steps to Reproduce: 1. install 3.3.2, engine, dwh & reports. 2. upgarde engine to 3.4 (yum update rhevm-setup + rhevm-setup) and create snapshot 3. upgarde dwh to 3.4 (yum install rhevm-dwh-setup + rhevm-setup) & save answer file in different machine 4. restore 3.4 engine snapshot 5. upgarde dwh to 3.4 using answefile craeted in step 3 Actual results: installation fails Expected results: Successfull installation Additional info: Step 5 pass by manual installtion
Not sure this requires doc text as it was already solved in the quite-old 3.4.1, see 3.4 clone bug 1100281.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-0177.html