Bug 2149967
| Summary: | SELinux labeling for dirsrv files seen during ipa install/uninstall should be moved to DEBUG. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Sudhir Menon <sumenon> |
| Component: | 389-ds-base | Assignee: | mreynolds |
| Status: | MODIFIED --- | QA Contact: | LDAP QA Team <idm-ds-qe-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.8 | CC: | abokovoy, frenaud, idm-ds-dev-bugs, mreynolds, rcritten, tscherf, vashirov |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | 8.9 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-1.4-820230816162424-17499975 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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: | |||
|
Description
Sudhir Menon
2022-12-01 13:32:15 UTC
Any reason why it should be under 'debug'? It is generated by the 389-ds code as a part of other operations. We have no control of the level here. If we'd move the whole output that 389-ds generates to DEBUG, it will apply to every single line, not just these ones. I think it is either an invalid request or it should be moved to 389-ds. Yes, seems like a side-effect of a change in 389-ds. Re-assigning component to see if there is a way to suppress this output. The root cause is here: https://github.com/389ds/389-ds-base/blob/389-ds-base-1.4.3/src/lib389/lib389/utils.py#L283-L312 log.info(f"Setting label {label} in seLinux file context {path}.") Note that in the main branch, the message is logged with debug level instead of info level: https://github.com/389ds/389-ds-base/blob/main/src/lib389/lib389/utils.py#L288-L317 log.debug(f"Setting label {label} in SELinux file context {path}.") This was fixed as part of https://github.com/389ds/389-ds-base/pull/5525, perhaps a separate backport just for log messages should be done. Mark, I'm still seeing this in 389-ds-base-1.4.3.36-1.module+el8.9.0+19111+92b42fe2.x86_64:
# grep -i log.info /usr/lib/python3.6/site-packages/lib389/utils.py | grep -i selinux
log.info('selinux is disabled, will not relabel ports or files.' )
log.info(f"Removing seLinux file context {path} with label {local[path]}.")
log.info(f"Setting label {label} in seLinux file context {path}.")
|