Bug 2032043
Summary: | Upgrading from RHV-H 4.4.8 to 4.4.9 fails with nerror: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch\nerror: cannot open Pac | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | amashah |
Component: | redhat-virtualization-host | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED DUPLICATE | QA Contact: | peyu |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4.9 | CC: | arachman, cshao, lsvaty, lveyde, mavital, mkalinin, ngarrett, peyu, sanja, sbonazzo, schandle, weiwang, yaniwang |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-04-08 16:15:01 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
amashah
2021-12-13 22:25:31 UTC
QE did not reproduce this bug. Test Version: RHVH: upgrade RHVH from rhvh-4.4.8.1-0.20210903.0+1 to rhvh-4.4.9.2-0.20211117.0+1 RHVM: 4.4.10-0.17.el8ev Test Steps: 1. Install redhat-virtualization-host-4.4.8-20210903.0.el8_4 2. Download "redhat-virtualization-host-image-update-4.4.9-202111172338_8.5.x86_64.rpm" 3. Add RHVH to RHVM 4. Set RHVH to "Maintenance" in RHVM 5. Upgrade RHVH via CLI # yum install redhat-virtualization-host-image-update-4.4.9-202111172338_8.5.x86_64.rpm Test Result: The upgrade was successful, there are no db5 related errors in /var/log/imgbased.log ~~~~~~ # yum install redhat-virtualization-host-image-update-4.4.9-202111172338_8.5.x86_64.rpm Updating Subscription Management repositories. Unable to read consumer identity This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Dependencies resolved. ============================================================================================================================== Package Architecture Version Repository Size ============================================================================================================================== Installing: redhat-virtualization-host-image-update x86_64 4.4.9-202111172338_8.5 @commandline 995 M replacing redhat-virtualization-host-image-update-placeholder.noarch 4.4.8-1.el8ev Transaction Summary ============================================================================================================================== Install 1 Package Total size: 995 M Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Running scriptlet: redhat-virtualization-host-image-update-4.4.9-202111172338_8.5.x86_64 1/2 Installing : redhat-virtualization-host-image-update-4.4.9-202111172338_8.5.x86_64 1/2 Running scriptlet: redhat-virtualization-host-image-update-4.4.9-202111172338_8.5.x86_64 1/2 Obsoleting : redhat-virtualization-host-image-update-placeholder-4.4.8-1.el8ev.noarch 2/2 Verifying : redhat-virtualization-host-image-update-4.4.9-202111172338_8.5.x86_64 1/2 Verifying : redhat-virtualization-host-image-update-placeholder-4.4.8-1.el8ev.noarch 2/2 Unpersisting: redhat-virtualization-host-image-update-placeholder-4.4.8-1.el8ev.noarch.rpm Installed products updated. Installed: redhat-virtualization-host-image-update-4.4.9-202111172338_8.5.x86_64 Complete! ~~~~~~ But when RHVH was upgraded from 4.4.8 to 4.4.9, we had a known db5 related bug: Bug 1930550 I don’t know if the root causes of this bug is the same as that of https://bugzilla.redhat.com/show_bug.cgi?id=1930550#c14, but they are all db5 related errors. Reducing severity as rebuilding the rpmdb as workaround fixes the issues. (In reply to Sandro Bonazzola from comment #5) > Reducing severity as rebuilding the rpmdb as workaround fixes the issues. Well, it still fails the upgrade. So I think it should be high. Sorry about that. *** This bug has been marked as a duplicate of bug 1930550 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days |