Bug 855304
| Summary: | Inconsistent service naming in ipa-server-install | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Nikolai Kondrashov <nikolai.kondrashov> | ||||||
| Component: | freeipa | Assignee: | Rob Crittenden <rcritten> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Chandrasekar Kannan <ckannan> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 17 | CC: | abokovoy, benl, dpal, jgalipea, mkosek, rcritten, ssorce | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-10-23 01:39:38 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 610675 [details]
An ipa-server-install run output
Created attachment 610676 [details]
A compressed ipaserver-install.log from an ipa-server-install run.
$ rpm -qa '*ipa*' freeipa-python-2.2.0-1.fc17.x86_64 python-iniparse-0.4-4.fc17.noarch freeipa-server-2.2.0-1.fc17.x86_64 freeipa-admintools-2.2.0-1.fc17.x86_64 device-mapper-multipath-libs-0.4.9-26.fc17.x86_64 freeipa-client-2.2.0-1.fc17.x86_64 device-mapper-multipath-0.4.9-26.fc17.x86_64 freeipa-server-selinux-2.2.0-1.fc17.x86_64 libipa_hbac-1.8.4-14.fc17.x86_64 libipa_hbac-python-1.8.4-14.fc17.x86_64 Upstream ticket: https://fedorahosted.org/freeipa/ticket/3059 Fixed upstream. master: 7ce6c4a2d3920f502b9f02e841a651bd0819915b ipa-3-0: deb4c4afb80208ffe8d8cef44165668bd61ecd26 |
Description of problem: ipa-server-install uses different names for the same service for configuration start/finish messages in progress output and logs. This is confusing and makes it harder to look for corresponding start or finish messages. Example output quote: Configuring directory server for the CA: Estimated time 30 seconds [1/3]: creating directory server user [2/3]: creating directory server instance [3/3]: restarting directory server done configuring pkids. Example log quote: 2012-09-07T09:04:58Z DEBUG Configuring directory server for the CA: Estimated time 30 seconds ... 2012-09-07T09:07:11Z DEBUG done configuring pkids. Compare the first and the last lines of both. How reproducible: always. Steps to Reproduce: run ipa-server-install. Actual results: Configuring directory server for the CA: Estimated time 30 seconds [1/3]: creating directory server user [2/3]: creating directory server instance [3/3]: restarting directory server done configuring pkids. Expected results: Configuring pkids: Estimated time 30 seconds [1/3]: creating directory server user [2/3]: creating directory server instance [3/3]: restarting directory server done configuring pkids. Or: Configuring directory server for the CA: Estimated time 30 seconds [1/3]: creating directory server user [2/3]: creating directory server instance [3/3]: restarting directory server done configuring directory server for the CA. Or maybe: Configuring pkids (directory server for the CA): Estimated time 30 seconds [1/3]: creating directory server user [2/3]: creating directory server instance [3/3]: restarting directory server done configuring pkids (directory server for the CA). Additional info: One way to fix this would be to add a "service_description" field to the "Service" class, remove "message" argument of the "start_creation" member function and format start messages there instead, in addition to finish messages, using service_name and/or service_description fields.