Bug 1244720
| Summary: | pg_restore: [archiver (db)] could not execute query: ERROR: language "plpgsql" already exists after upgrade | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Petr Matyáš <pmatyas> | ||||
| Component: | Setup.Engine | Assignee: | Yedidyah Bar David <didi> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Matyáš <pmatyas> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 3.6.0 | CC: | bugs, didi, ecohen, gklein, lsurette, pstehlik, rbalakri, sbonazzo, yeylon, ylavi | ||||
| Target Milestone: | ovirt-3.6.1 | Flags: | rule-engine:
ovirt-3.6.z+
ylavi: planning_ack+ sbonazzo: devel_ack+ pstehlik: testing_ack+ |
||||
| Target Release: | 3.6.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | integration | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-12-16 12:19:37 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1244630 | ||||||
| Bug Blocks: | 1078871 | ||||||
| Attachments: |
|
||||||
The error causing upgrade to fail is unrelated here ('column "v_dedicated_vm_for_vds" does not exist'). To reproduce/verify, you can fail upgrade in other ways (e.g. add an invalid upgrade script to dbscripts/upgrade/ ).
I assume the reported bug is that once upgrade failed, rollback failed too.
Changed the subject accordingly. Dropped the specific error message because we probably want to verify a bit more than that.
Currently pushed patch fixes only the specific error encountered here. We should probably check others too, although most existing ones are historic and probably irrelevant.
What is the status of this issue? (In reply to Yaniv Dary from comment #2) > What is the status of this issue? No update - still didn't verify the patch. Soon. Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone. Verified on 3.6.0-22 According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release. |
Created attachment 1053836 [details] setup log Description of problem: After upgrade setup fails to restore db with ERROR: language "plpgsql" already exists Version-Release number of selected component (if applicable): ovirt-engine-3.6.0-0.0.master.20150719172450.git2c84bb6.el6.noarch How reproducible: always on my setup Steps to Reproduce: 1. install earlier version of oVirt 2. upgrade to aforementioned version 3. Actual results: db restore error Expected results: correct db restore Additional info: