Bug 2188231
Summary: | [AWS]Many AVC failures seen with : denied { create } comm="rhc-worker-play" and comm="ansible-playboo". | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | libhe | ||||
Component: | rhc-worker-playbook | Assignee: | CSI Client Tools Bugs <csi-client-tools-bugs> | ||||
Status: | CLOSED MIGRATED | QA Contact: | CSI Client Tools Bugs <csi-client-tools-bugs> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 9.2 | CC: | cmarinea, linl, lvrabec, mmalik, ptoscano, redakkan, xiliang, ymao, zpytela | ||||
Target Milestone: | rc | Keywords: | MigratedToJIRA, Regression, Reopened | ||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2023-10-19 13:55:54 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
libhe
2023-04-20 07:52:04 UTC
Hello, What is the rhc package version? # rpm -q rhc # semodule -lfull | grep rhcd [ec2-user@ip-10-0-25-4 ~]$ rpm -q rhc rhc-0.2.2-1.el9.x86_64 [ec2-user@ip-10-0-25-4 ~]$ sudo semodule -lfull | grep rhcd 100 rhcd pp Are you aware of any SELinux or rhc related changes since the installation time? The rhcd_t domain should be permissive: rhel93# rpm -q rhc rhc-0.2.2-1.el9.x86_64 rhel93# rpm -q rhc --scripts postinstall scriptlet (using /bin/sh): if [ -x /usr/sbin/selinuxenabled ] && /usr/sbin/selinuxenabled; then /usr/sbin/semanage permissive --add rhcd_t || true fi postuninstall scriptlet (using /bin/sh): if [ $1 -eq 0 ]; then if [ -x /usr/sbin/selinuxenabled ] && /usr/sbin/selinuxenabled; then /usr/sbin/semanage permissive --delete rhcd_t || true fi fi rhel93# semodule -lfull | grep rhcd 400 permissive_rhcd_t cil 100 rhcd pp NO any change for SELinux or rhc related since the installation with the latest AWS AMI. Can you also run this? $ rpm -q rhc --scripts The only explanation which comes to my mind is that selinux was disabled when rhc was being installed. In that case, reinstallation should help: # dnf reinstall rhc (In reply to Zdenek Pytela from comment #5) > Can you also run this? > > $ rpm -q rhc --scripts > > The only explanation which comes to my mind is that selinux was disabled > when rhc was being installed. In that case, reinstallation should help: [ec2-user@ip-10-0-16-30 ~]$ rpm -q rhc --scripts postinstall scriptlet (using /bin/sh): if [ -x /usr/sbin/selinuxenabled ] && /usr/sbin/selinuxenabled; then /usr/sbin/semanage permissive --add rhcd_t || true fi postuninstall scriptlet (using /bin/sh): if [ $1 -eq 0 ]; then if [ -x /usr/sbin/selinuxenabled ] && /usr/sbin/selinuxenabled; then /usr/sbin/semanage permissive --delete rhcd_t || true fi fi > > # dnf reinstall rhc Yes, reinstallation works. BTW, with the build before 20230419, there is no such issue observed. Here is the result with build RHEL-9.2.0-20230418.20_x86_64 [ec2-user@ip-10-0-22-92 ~]$ sudo semodule -lfull | grep rhcd 100 rhcd pp [ec2-user@ip-10-0-22-92 ~]$ sudo ausearch -m AVC -ts today <no matches> [ec2-user@ip-10-0-22-92 ~]$ rpm -q rhc rhc-0.2.2-1.el9.x86_64 Switching the component, but I believe all issues like this have already been addressed. Thanks for confirming that this is no longer an issue. Please feel free to report new issue if you have issues again. Closing this for now. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |