Bug 2124825

Summary: semanage fcontext leads to libsemanage.dbase_llist_query error
Product: Red Hat Enterprise Linux 8 Reporter: Welterlen Benoit <bwelterl>
Component: policycoreutilsAssignee: Vit Mojzis <vmojzis>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: low Docs Contact:
Priority: low    
Version: 8.6CC: dwalsh, lvrabec, mmalik, plautrba, vmojzis
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: policycoreutils-2.9-21.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-16 09:11:23 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:

Description Welterlen Benoit 2022-09-07 08:12:30 UTC 
Description of problem:

[root@rhel86 ~]#  semanage fcontext -D
[root@rhel86 ~]#  semanage fcontext -f f -m -t passwd_file_t /etc/security/opasswd
libsemanage.dbase_llist_query: could not query record value (No such file or directory).

A second time is working without issue:
[root@rhel86 ~]#  semanage fcontext -f f -m -t passwd_file_t /etc/security/opasswd
[root@rhel86 ~]# 

The context is changed anyway.

Version-Release number of selected component (if applicable):
RHEL 8.6
policycoreutils-python-utils-2.9-19.el8.noarch

How reproducible:
always

Steps to Reproduce:
1. semanage fcontext -D
2. semanage fcontext -f f -m -t passwd_file_t /etc/security/opasswd
3.

Actual results:
Error msg "libsemanage.dbase_llist_query: could not query record value (No such file or directory)."


Expected results:
No error message

Additional info:
Comment 11 errata-xmlrpc 2023-05-16 09:11:23 UTC 
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 (policycoreutils bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:3034