RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2023805 - [DDF] This isn't sufficient.
Summary: [DDF] This isn't sufficient.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: Documentation
Version: 8.0
Hardware: All
OS: All
high
unspecified
Target Milestone: rc
: ---
Assignee: Filip Hanzelka
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-16 15:36 UTC by Direct Docs Feedback
Modified: 2021-11-29 11:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-29 11:26:13 UTC
Type: ---
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-102940 0 None None None 2021-11-16 15:53:59 UTC

Description Direct Docs Feedback 2021-11-16 15:36:33 UTC
This isn't sufficient.

If the server being uninstalled is the 'CA renewal server' then some other server should be set as the 'CA renewal server'.

If the server being uninstalled is the 'CRL publisher' then the server being uninstalled should have CRL publication disabled, and another server needs to have the role enabled.

Instructions for both of this are present in other chapters but I think they should be linked to here, because it's possible to be unaware that you need to do those extra steps if the server you're removing performs either of those roles.

The docs could link to https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_identity_management/managing-topology#server-roles-promote-to-ca (which itself links to chapters 57.2 to cover the CA renewal server and 59 for the CRL publisher.

But there's also chapter 60, "DECOMMISSIONING A SERVER THAT PERFORMS THE CA RENEWAL SERVER AND CRL PUBLISHER ROLES" which duplicates both those individual chapters. So maybe that would be better to link to instead.

Reported by: staticyrro7

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/installing_identity_management/uninstalling-an-ipa-server_installing-identity-management#annotations:85873507-2f26-4d3a-93e9-755126e8e76e


Note You need to log in before you can comment on or make changes to this bug.