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.
DescriptionMichal Trunecka
2013-08-20 12:56:00 UTC
Description of problem:
When trying to permanently change nonexisting boolean, following error message is shown:
"Failed to change boolean xyz: Success"
But it happens only once after some other correct permanent boolean change:
###### correct permanent change
# setsebool -P ftp_home_dir 1
###### Trying to change non-existing boolean, bad error only once:
# setsebool -P xyz=1
Failed to change boolean xyz: Success
# setsebool -P xyz=1
Failed to change boolean xyz: No such file or directory
# setsebool -P xyz=1
Failed to change boolean xyz: No such file or directory
###### correct permanent change
# setsebool -P ftp_home_dir 0
###### Trying to change non-existing boolean:
# setsebool -P xyz=1
Failed to change boolean xyz: Success
# setsebool -P xyz=1
Failed to change boolean xyz: No such file or directory
Version-Release number of selected component (if applicable):
policycoreutils-2.0.83-19.32.el6.x86_64
We could change to have
#setsebool -P aa=1
Could not change boolean aa
#echo $?
255
#setsebool -P ftp_home_dir 0
#echo $?
0
#setsebool -P aa=1
Could not change boolean aa
#echo $?
255
So we won't see the issue which Michal described.
It looks it also happens on Fedora.
sh-4.2# setsebool -P aa=1
Failed to change boolean aa: No such file or directory
sh-4.2# setsebool -P ftp_home_dir 0
sh-4.2# setsebool -P aa=1
Failed to change boolean aa: Success
Need to try to do more debugging.
Comment 5RHEL Program Management
2013-09-05 10:10:33 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
(In reply to Miroslav Grepl from comment #12)
> # rpm -q policycoreutils
> policycoreutils-2.0.83-19.35.el6.x86_64
>
> # setsebool -P aa=1
> Boolean aa is not defined
>
> # getsebool ftp_home_dir
> ftp_home_dir --> off
> # setsebool -P ftp_home_dir 1
> # getsebool ftp_home_dir
> ftp_home_dir --> on
For QA.
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.
http://rhn.redhat.com/errata/RHBA-2013-1608.html
Description of problem: When trying to permanently change nonexisting boolean, following error message is shown: "Failed to change boolean xyz: Success" But it happens only once after some other correct permanent boolean change: ###### correct permanent change # setsebool -P ftp_home_dir 1 ###### Trying to change non-existing boolean, bad error only once: # setsebool -P xyz=1 Failed to change boolean xyz: Success # setsebool -P xyz=1 Failed to change boolean xyz: No such file or directory # setsebool -P xyz=1 Failed to change boolean xyz: No such file or directory ###### correct permanent change # setsebool -P ftp_home_dir 0 ###### Trying to change non-existing boolean: # setsebool -P xyz=1 Failed to change boolean xyz: Success # setsebool -P xyz=1 Failed to change boolean xyz: No such file or directory Version-Release number of selected component (if applicable): policycoreutils-2.0.83-19.32.el6.x86_64