Bug 2171863

More detailed description of problem and how i tried to solve it:

I upgraded today (2023-02-04) from Fedora 36 to Fedora 37 on my server via Fedora Cockpit and encountered a bug in relation to a failed RPM database migration:

During the upgrade it was apparently expected that the rpmdb-migrate process would start, but it did not. I found some error in my log.

Prior advise from the mailing list and bug 2042147 to manually

> # systemctl enable rpmdb-migrate
> # systemctl start rpmdb-migrate

Did **NOT** solve the issue.

Found this discussion and had a look via `ls -la /usr/lib/sysimage/rpm`.


Found a `.migratedb` in there. Also found following files:

.rpm.lock
rpmdb.sqlite
rpmdb.sqlite-shm
rpmdb.sqlite-wal


What I did to (hopefully) fix it:

1. Deleted the `.migratedb` via `sudo rm .migratedb`.
2. Ran the `RPM database migration to /usr` Systemservice via Fedora Cockpit (This should have been equivalent to `systemctl start rpmdb-migrate`).
3. Following error was triggered: rpmdb-migrate.service - RPM database migration to /usr was skipped because of a failed condition check (ConditionPathExists=/var/lib/rpm/.migratedb).
4. Remembered, the `RPM database migration to /usr` Systemservice was supposed to run at boot, so I rebooted my machine.
5. After restart, the `RPM database migration to /usr` Systemservice` did not trigger Fedora cockpit to give a warning anymore.

So, I checked both folders (i should have checked BOTH folders before deleting stuff btw.!):

$ ls -la /var/lib/rpm
lrwxrwxrwx. 1 root root 26 Jun 25  2022 /var/lib/rpm -> ../../usr/lib/sysimage/rpm

$  ls -la /usr/lib/sysimage/rpm
total 122940
drwxr-xr-x. 2 root root       123 Feb  4 19:21 .
drwxr-xr-x. 3 root root        17 Aug  9 15:27 ..
-rw-r--r--. 1 root root         0 Jul  1  2022 .rpm.lock
-rw-r--r--. 1 root root 125857792 Feb  4 18:34 rpmdb.sqlite
-rw-r--r--. 1 root root     32768 Feb  4 19:25 rpmdb.sqlite-shm
-rw-r--r--. 1 root root         0 Feb  4 18:34 rpmdb.sqlite-wal

which seemed pretty close to a migration.

I noticed `.rpmdbdirsymlink_created` was missing, so i manually created the file via `sudo touch .rpmdbdirsymlink_created`

`-rw-r--r--. 1 root root         0 Feb  4 19:21 .rpmdbdirsymlink_created`

I am thinking about manually creating all the other symlinks.

Hopefully this was correct.
Hopefully this will help anybody encountering the same issue.

I think i did the wrong thing. Memo for myself: Use `ln -s` command to create symbolic links

https://linuxconfig.org/how-to-create-symlink-in-linux

What I found in my folders today:


```
[Thilo@server rpm]$ cd /var/lib/rpm
[Thilo@server rpm]$ ls -la
total 122940
drwxr-xr-x. 2 root root       123 Feb  4 19:21 .
drwxr-xr-x. 3 root root        17 Aug  9  2022 ..
-rw-r--r--. 1 root root         0 Jul  1  2022 .rpm.lock
-rw-r--r--. 1 root root         0 Feb  4 19:21 .rpmdbdirsymlink_created
-rw-r--r--. 1 root root 125857792 Feb 20 16:09 rpmdb.sqlite
-rw-r--r--. 1 root root     32768 Feb 20 17:59 rpmdb.sqlite-shm
-rw-r--r--. 1 root root         0 Feb 20 16:09 rpmdb.sqlite-wal



[Thilo@server rpm]$ cd /
[Thilo@server /]$ cd /usr/lib/sysimage/rpm
[Thilo@server rpm]$ ls -la
total 122940
drwxr-xr-x. 2 root root       123 Feb  4 19:21 .
drwxr-xr-x. 3 root root        17 Aug  9  2022 ..
-rw-r--r--. 1 root root         0 Jul  1  2022 .rpm.lock
-rw-r--r--. 1 root root         0 Feb  4 19:21 .rpmdbdirsymlink_created
-rw-r--r--. 1 root root 125857792 Feb 20 16:09 rpmdb.sqlite
-rw-r--r--. 1 root root     32768 Feb 20 17:59 rpmdb.sqlite-shm
-rw-r--r--. 1 root root         0 Feb 20 16:09 rpmdb.sqlite-wal

[Thilo@server rpm]$ ln -s rpmdb.sqlite /var/lib/rpm/rpmdb.sqlite
ln: failed to create symbolic link '/var/lib/rpm/rpmdb.sqlite': File exists
```

So ... now I am having TWO rpm databases? what is going on?

Pull requests opened for this.

Rawhide (and F38): https://src.fedoraproject.org/rpms/rpm/pull-request/37

This pull request, once merged, will also need to be merged back into the F38 branch.

F37: https://src.fedoraproject.org/rpms/rpm/pull-request/38
F36: https://src.fedoraproject.org/rpms/rpm/pull-request/39

These two can just be merged and built for their respective branches.

This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.