When starting Ambari where Kerberos authentication is enabled (authentication.kerberos.enabled=true), Ambari validates the relevant configuration properties. If a sever issue is found, an exception is thrown. This causes issues in installations where Ambari is expected to be able to perform Kerberos authentication but all of the data is available for since this is it expected to be provided later. For example, the SPNEGO keytab file will be created when Kerberos is enabled sometime after Ambari starts up.
To prevent Ambari from shutting down when all the required data is not available, thrown exceptions should be removed from org.apache.ambari.server.configuration.Configuration#createKerberosAuthenticationProperties.