Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: While running a test which updates cluster.conf to add and remove nodes, I ran into the following error when running `cman_tool version -r.` Unable to update relaxng schema: /usr/sbin/ccs_update_schema: line 375: /var/lib/cluster/rng_update.lock: Permission denied cman_tool: Not reloading, generic error running ccs_config_validate I believe this was caused by the following AVC: type=SYSCALL msg=audit(1313704814.087:406): arch=c000003e syscall=2 success=no exit=-13 a0=28715f0 a1=241 a2=1b6 a3=fffffffffffffff0 items=0 ppid=8051 pid=8053 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="ccs_update_sche" exe="/bin/bash" subj=system_u:system_r:corosync_t:s0 key=(null) type=AVC msg=audit(1313704823.999:407): avc: denied { write } for pid=8402 comm="ccs_update_sche" name="cluster" dev=dm-0 ino=1442475 scontext=system_u:system_r:corosync_t:s0 tcontext=system_u:object_r:cluster_var_lib_t:s0 tclass=dir It looks like some of the new binaries need to be labelled correctly. [root@buzz-01 ~]# ls -Z `rpm -ql cman | grep bin` -rwxr-xr-x. root root system_u:object_r:bin_t:s0 /usr/sbin/ccs_config_dump -rwxr-xr-x. root root system_u:object_r:bin_t:s0 /usr/sbin/ccs_config_validate lrwxrwxrwx. root root system_u:object_r:bin_t:s0 /usr/sbin/ccs_test -> ccs_tool -rwxr-xr-x. root root system_u:object_r:corosync_exec_t:s0 /usr/sbin/ccs_tool -rwxr-xr-x. root root system_u:object_r:bin_t:s0 /usr/sbin/ccs_update_schema -rwxr-xr-x. root root system_u:object_r:bin_t:s0 /usr/sbin/cman_notify -rwxr-xr-x. root root system_u:object_r:bin_t:s0 /usr/sbin/cmannotifyd -rwxr-xr-x. root root system_u:object_r:corosync_exec_t:s0 /usr/sbin/cman_tool -rwxr-xr-x. root root system_u:object_r:dlm_controld_exec_t:s0 /usr/sbin/dlm_controld -rwxr-xr-x. root root system_u:object_r:bin_t:s0 /usr/sbin/dlm_tool -rwxr-xr-x. root root system_u:object_r:fenced_exec_t:s0 /usr/sbin/fenced -rwxr-xr-x. root root system_u:object_r:fenced_exec_t:s0 /usr/sbin/fence_node -rwxr-xr-x. root root system_u:object_r:fenced_exec_t:s0 /usr/sbin/fence_tool -rwxr-xr-x. root root system_u:object_r:bin_t:s0 /usr/sbin/gfs_control -rwxr-xr-x. root root system_u:object_r:gfs_controld_exec_t:s0 /usr/sbin/gfs_controld -rwxr-xr-x. root root system_u:object_r:groupd_exec_t:s0 /usr/sbin/groupd -rwxr-xr-x. root root system_u:object_r:bin_t:s0 /usr/sbin/group_tool -rwxr-xr-x. root root system_u:object_r:bin_t:s0 /usr/sbin/mkqdisk -rwxr-xr-x. root root system_u:object_r:qdiskd_exec_t:s0 /usr/sbin/qdiskd Version-Release number of selected component (if applicable): cman-3.0.12.1-10.el6.x86_64 selinux-policy-3.7.19-107.el6.noarch How reproducible: Easily Steps to Reproduce: 1. update cluster.conf 2. run cman_tool version -r Actual results: See above Expected results: cluster.conf should be updated around the cluster without causing selinux AVCs. Additional info: