Apparently conntrackd is part of the stated design of Neutron's L3 HA implementation. However, it seems that this does not in fact exist in current Neutron master code. In addition, even if it was implemented and being used by Neutron, that definitely does not involve running the service with the stock package config files outside of router namespaces in agent containers, and double definitely does not involve constantly logging the copious conntrack state changes.
My suggestion is to remove the package installation entirely for the time being, and everyone will be a lot happier for it.
Apparently conntrackd is part of the stated design of Neutron's L3 HA implementation. However, it seems that this does not in fact exist in current Neutron master code. In addition, even if it was implemented and being used by Neutron, that definitely does not involve running the service with the stock package config files outside of router namespaces in agent containers, and double definitely does not involve constantly logging the copious conntrack state changes.
My suggestion is to remove the package installation entirely for the time being, and everyone will be a lot happier for it.