Bug 1376425 - [RFE] IPA server installation with successful message
Summary: [RFE] IPA server installation with successful message
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Florence Blanc-Renaud
QA Contact: Kaleem
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-15 12:06 UTC by Abhijeet Kasurde
Modified: 2019-08-16 14:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-16 14:02:23 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Abhijeet Kasurde 2016-09-15 12:06:09 UTC
Description of problem:
It would be nice, if user/administrator is presented with information about successful IPA installation and other details. Info message can be like this 

======================================================
IPA server installation successful 

You can access Web UI using https://ipaserver1.testrelm.test/ipa/ui 

Obtain a Kerberos Ticket for issuing IPA command.

Server is installed with following roles :

* CA Server
* DNS Server
...

For troubleshooting and errors : 
Please visit : https://www.redhat.com/en

For documentation :
Please visit : <url_to_official_documentation>
======================================================

Comment 2 Petr Vobornik 2016-09-23 16:58:01 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/6355

Comment 3 Petr Vobornik 2017-04-06 16:12:32 UTC
IdM team doesn't have capacity to implement this RFE for RHEL 7.4. Moving to next RHEL version. Implementing the RFE there will depend on capacity of FreeIPA upstream. Without sufficient justification there is a chance that it will be moved again later.

Comment 6 Amy Farley 2019-08-16 14:02:23 UTC
This will be taken care of as part of the work we are doing with ansible. Closing  this bug for now.


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