Bug 1418883

Summary: Topology Suffix ca missing when installing CA into non-CA IDM
Product: [Fedora] Fedora Reporter: Jason H. <cakersq>
Component: freeipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 25CC: abokovoy, cakersq, ipa-maint, jcholast, jhrozek, pvoborni, rcritten, ssorce
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:31:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jason H. 2017-02-03 00:36:41 UTC
Description of problem:

When installing a CA using "ipa-ca-install" into a domain without a CA installed, the CA topology suffix does not appear.  When running "ipa topologysuffix-find", only the domain suffix appears, also in Web UI, the CA Topology suffix does not appear.

This doesn't appear to be causing any issues.

Installing the CA on a second IPA server in the domain, causes the domain to appear normally, and is shown as being managed by the second server, but not by the first.


Version-Release number of selected component (if applicable): 4.4.3-1


How reproducible: Always


Steps to Reproduce:
1. Install IPA without a CA (external signed server certificate).  "ipa-server-install --dirsrv-cert-file=server.p12 --http-cert-file=server.p12"
2. Install CA to Server.  "ipa-ca-install"
3. View topology "ipa topologysuffix-find"

Actual results:
Only the "domain" suffix will appear.


Expected results:
Both "domain" and "ca" suffixes should show.

Additional info:
Comparing the "dc=DOMAIN" tree on a server that had a CA installed after the domain, the "cn=ca,cn=topology,cn=ipa,cn=etc,dc=DOMAIN" object is missing, as well as the "ipaReplTopoManagedSuffix: o=ipaca" attribute under "cn=SERVER,cn=masters,cn=ipa,cn=etc,dc=DOMAIN".  Those values exist if a CA is installed with the initial server install, or for a replica that is installed after a CA has been added to the domain.

Comment 1 Petr Vobornik 2017-02-17 17:22:06 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/6689

Comment 2 Fedora End Of Life 2017-11-16 19:15:26 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

Comment 3 Fedora End Of Life 2017-12-12 10:31:52 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.