Bug 1302382
| Summary: | running remove-ds-admin.pl multiple times will make it so you cannot install DS | |||
|---|---|---|---|---|
| Product: | Red Hat Directory Server | Reporter: | Eugene Keck <ekeck> | |
| Component: | Install/Uninstall | Assignee: | Noriko Hosoi <nhosoi> | |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> | |
| Severity: | medium | Docs Contact: | Aneta Šteflová Petrová <apetrova> | |
| Priority: | medium | |||
| Version: | 10.0 | CC: | msauton, nhosoi, pbokoc, spichugi | |
| Target Milestone: | DS10.1 | |||
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | 389-admin-1.1.44-1.el7dsrv | Doc Type: | Bug Fix | |
| Doc Text: |
setup-ds-admin.pl no longer fails after running remove-ds-admin.pl due to missing configuration files
Previously, executing the remove-ds-admin.pl script removed files in the Administration Server's configuration directory if no backup was available for them. Consequently, if the user executed the setup-ds-admin.pl script after running remove-ds-admin.pl, setup-ds-admin.pl failed. The problem occurred in the following situations:
* when remove-ds-admin.pl was executed repeatedly
* when remove-ds-admin.pl was executed without executing the setup-ds-admin.pl first
Instead of removing the files, remove-ds-admin.pl now overrides them from backup if a backup is available. As a result, the script no longer removes files that do not have a backup, and setup-ds-admin.pl no longer fails in this situation.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1334480 (view as bug list) | Environment: | ||
| Last Closed: | 2016-11-07 15:39:36 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1334480 | |||
|
Description
Eugene Keck
2016-01-27 16:41:29 UTC
as a workaround, re-installing 389-admin will add back the missing config files when no backup exists note I forgot to post/save last week..: Viktor Ashirov pointed me to those known references (thanks): bz 1229445 - [DOC -- known issue] remove-ds-admin.pl removes files in the rpm https://bugzilla.redhat.com/show_bug.cgi?id=1229445 and http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Directory_Server/10/html/Release_Notes/Release_Notes-Bugs_Addressed-Known_Issues.html " If the remove-ds-admin.pl script is executed without an installed Admin server, it removes configuration files that were installed from the RPM package. As a consequence, subsequently run setup-ds-admin.pl script terminates without creating the configuration file backups. To work around this problem, run the yum reinstall 389-admin command to recover the missing files. " with this workaround, GSS is trying to close the sf case number 01572443 Build tested: 389-admin-1.1.44-1.el7dsrv.x86_64 Steps to verify: 1. Install an instance with setup-ds-admin.pl 2. remove-ds-admin.pl -f -d -a -y 3. remove-ds-admin.pl -f -d -a -y 4. Install an install second time with setup-ds-admin.pl: Result output: ... The admin server was successfully started. Admin server was successfully created, configured, and started. Exiting . . . Marking as verified. Your new relnote looks good. Thanks, Aneta! Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2665.html |