Bug 987079
| Summary: | setup-ds.pl takes very long time | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Martin Kosek <mkosek> | ||||||||
| Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Sankar Ramalingam <sramling> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 7.0 | CC: | mkosek, nkinder | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-07-23 06:57:57 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: |
|
||||||||||
|
Description
Martin Kosek
2013-07-22 16:28:47 UTC
Created attachment 776971 [details]
Strace of setup-ds.pl
Created attachment 776972 [details]
IPA server install log
Ah, I see the setup-ds.pl finished after all, it just took very long time (8 minutes in my case) - lowering severity. Can you run setup-ds.pl with the -ddd option to get debugging output? It looks like it is having trouble with semanage. Created attachment 776973 [details]
Successful, but very long run of setup-ds.pl
I'm pretty sure that this is related to semanage being broken by the recent build of policycoreutils-python (see bug 980143). Specifically, semanage in policycoreutils-2.1.14-66.el7 thinks that the options used by setup-ds.pl are incorrect. What version of policycoreutils-python are you using? Does 'semanage port -l' work properly, or does it complain about illegal usage? (In reply to Nathan Kinder from comment #7) > I'm pretty sure that this is related to semanage being broken by the recent > build of policycoreutils-python (see bug 980143). Specifically, semanage in > policycoreutils-2.1.14-66.el7 thinks that the options used by setup-ds.pl > are incorrect. > > What version of policycoreutils-python are you using? Does 'semanage port > -l' work properly, or does it complain about illegal usage? In the strace output it looks as though semanage is complaining, so yes, it looks like this is the problem. (In reply to Nathan Kinder from comment #7) > I'm pretty sure that this is related to semanage being broken by the recent > build of policycoreutils-python (see bug 980143). Specifically, semanage in > policycoreutils-2.1.14-66.el7 thinks that the options used by setup-ds.pl > are incorrect. > > What version of policycoreutils-python are you using? Does 'semanage port > -l' work properly, or does it complain about illegal usage? I used policycoreutils-2.1.14-66.el7.x86_64, 'semanage port -l' indeed reported illegal use: # semanage port -l list option can not be used with --range When I updated to policycoreutils-2.1.14-67.el7.x86_64, problem with setup-ds.pl went away. Thanks for help Nathan and Rich! Closing this bug. |