Closed SilleBille closed 4 years ago
Posted by rcritten on 2019-09-30:
Perhaps NSS should not initiate a migration when opened with NSS_INIT_NOMODDB. I'm not sure this is a bug in certmonger.
Posted by slev on 2019-09-30:
I could open a ticket against NSS. But looks like the migration process is not standardized.
This issue was migrated from Pagure Issue #3104.Originally filed by slev on 2019-08-13
During FreeIPA upgrade from an old version (4.3.3) to a new one (4.7.2)
pki-tomcatdpki-tomcat.service
fails with:There is a partially upgraded NSS db. As it's known, ( https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql ) an implicit migration takes place on
write
open.certmonger during the same RPM upgrade process restarted and re-read the tracked certs. https://pagure.io/certmonger/blob/master/f/src/certread-n.c#_103 The root cause of this issue is
NSS_INIT_NOMODDB
flag, used by certmonger in NSS_InitContext. Actually, certmonger just triggers the issue.The very simple reproducer in pytest is attached.