Description of problem: When IPA client is installed, certmonger does the renewal against the server specified in /etc/ipa/default.conf which is the original server that the client enrolled with. However, when this server is decommissioned, certmonger will stop renewing the certificates even though there are available IPA CA servers specified in IPA domain DNS SRV records. This is what "ipa" tool itself does in these cases. Certmonger should follow that part as well to allow automatic fall back when IPA has proper DNS domain and SRV records. Version-Release number of selected component (if applicable): certmonger-0.75.6-1.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. Install IPA server with CA support and with DNS 2. Install IPA client 3. Install IPA replica with CA 4. Remove old IPA replica 5. Try to do renewal on IPA client Actual results: Renewal fails as original server is not accessible Expected results: Renewal fall backs and discovers alternate IPA server via DNS SRV records. Additional info:
Additional info also here: http://www.redhat.com/archives/freeipa-devel/2014-September/msg00087.html
Does this work as desired in 0.76.6 and later?
David or Jan, can you please eventually check the new behavior?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.