#7501 Failure to properly upgrade named.conf in ipa-server-upgrade
Opened 6 years ago by simo. Modified 6 years ago

I tried an upgrade from an dolder f25 server. After upgrade it blew up because named-pkcs11 didn;t want to start, after messing with an attempt to fix things by further upgradeing to f27 I set to read the upgrade code to see if I could figure out what is going on.

A recent upgrade in bind-dyndb-ldap in F26 now requires the options "server_id" to be set in named.conf and if it is not set the whole of named fails to start with a generic "not found" right after the ipa driver is loaded. No indication of what is worng is given, and this is bad enough.

But even worse, when I manually tried ipa-server-upgrade, it turns our it blows up trying to restart named-pkcs11 before fixing its configuration ... This happens still in current F27 packages (so 4.6) and it is a major upgrade issue as it is very hard to figure out what is wrong.


Metadata Update from @fbarreto:
- Issue priority set to: normal (was: important)

6 years ago

Metadata Update from @fbarreto:
- Issue tagged with: robustness

6 years ago

Login to comment on this ticket.

Metadata