You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In cases where zypper migration is being run in a host environment targeting a mounted file system hierarchy, such as when being used by the SUSE DMS solution, if the host system environment's rpm backend is not compatible, this can lead to zypper migration failures leaving the target system in an inconsistent state.
...
( 1/1681) Removing: libgdata-lang-0.17.5-5.4.noarch [..
warning: Found BDB Packages database while attempting ndb backend: using bdb_ro backend.
warning: Found BDB Packages database while attempting ndb backend: using bdb_ro backend.
error: cannot open Packages index using unknown db - Operation not permitted (1)
error: cannot open Packages database in /system-root/var/lib/rpm
Removal of (60889)libgdata-lang-0.17.5-5.4.noarch(@System) failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
error]
Abort, retry, ignore? [a/r/i] (a): a
warning: Found BDB Packages database while attempting ndb backend: using bdb_ro backend.
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.
command '/usr/bin/zypper --root /system-root --non-interactive --releasever 15.3 --no-refresh dist-upgrade --auto-agree-with-licenses --auto-agree-with-licenses --replacefiles --allow-vendor-change' failed
Error: zypper returned 8 with 'warning: Found BDB Packages database while attempting ndb backend: using bdb_ro backend.
warning: Found BDB Packages database while attempting ndb backend: using bdb_ro backend.
warning: Found BDB Packages database while attempting ndb backend: using bdb_ro backend.
warning: Found BDB Packages database while attempting ndb backend: using bdb_ro backend.
Removal of (60889)libgdata-lang-0.17.5-5.4.noarch(@System) failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
warning: Found BDB Packages database while attempting ndb backend: using bdb_ro backend.
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.' (exit status 8)
Migration failed.
The migration to the new service pack has failed. The system is most
likely in an inconsistent state.
...
This scenario can arise if the host environment is using ndb backend, as is the case with the rpm-ndb package, used in SUSE SLE cloud images since SLE 15 SP2 and SLE BCI images since 15 SP3.
The check rpm -E "%{_db_backend}" can be used to determine the backend, e.g.
% rpm -E "%{_db_backend}"
bdb
NOTE: If the rpm version is too old, the response will be %{_db_backend} which equates to the bdb backend.
The text was updated successfully, but these errors were encountered:
In cases where zypper migration is being run in a host environment targeting a mounted file system hierarchy, such as when being used by the SUSE DMS solution, if the host system environment's rpm backend is not compatible, this can lead to zypper migration failures leaving the target system in an inconsistent state.
This scenario can arise if the host environment is using
ndb
backend, as is the case with the rpm-ndb package, used in SUSE SLE cloud images since SLE 15 SP2 and SLE BCI images since 15 SP3.The check
rpm -E "%{_db_backend}"
can be used to determine the backend, e.g.NOTE: If the rpm version is too old, the response will be
%{_db_backend}
which equates to thebdb
backend.The text was updated successfully, but these errors were encountered: