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.
Bug 1726209 - rpm -V fails with Group ownership differs
Summary: rpm -V fails with Group ownership differs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libstoragemgmt
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.2
Assignee: Tony Asleson
QA Contact: ChanghuiZhong
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-02 10:32 UTC by Jakub Krysl
Modified: 2021-09-06 15:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:46:14 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Correction for issue (204 bytes, patch)
2019-07-02 15:40 UTC, Tony Asleson
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-23850 0 None None None 2021-09-06 15:52:56 UTC
Red Hat Product Errata RHBA-2020:1805 0 None None None 2020-04-28 16:46:16 UTC

Description Jakub Krysl 2019-07-02 10:32:13 UTC
Description of problem:
# rpm -qa libstoragemgmt
libstoragemgmt-1.8.1-2.el8.x86_64

# rpm -V libstoragemgmt
......G..  g /run/lsm
......G..  g /run/lsm/ipc

# ll /run | grep lsm
drwxrwxr-x. 3 root libstoragemgmt 60 Jul  2 10:06 lsm

# ll /run/lsm | grep ipc
drwxrwxr-x. 2 root libstoragemgmt 40 Jul  2 10:06 ipc

Version-Release number of selected component (if applicable):
libstoragemgmt-1.8.1-2.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. rpm -V libstoragemgmt

Actual results:
......G..  g /run/lsm
......G..  g /run/lsm/ipc

Expected results:
no errors

Additional info:
TPS

Comment 1 Tony Asleson 2019-07-02 15:40:11 UTC
Created attachment 1586760 [details]
Correction for issue

Comment 3 ChanghuiZhong 2019-10-31 03:34:24 UTC
Hi,Tony Asleson 

Is there a fix patch to fix this bug now? i don't find fix version build message in errata.

Thanks
Changhui

Comment 4 Tony Asleson 2019-11-04 13:35:13 UTC
I have attached a build.

Comment 5 ChanghuiZhong 2019-11-05 05:17:50 UTC
Hi,all

This bug has fixed by libstoragemgmt-1.8.1-3.el8.

[root@hpe-dl320egen8-02 ~]# rpm -qa libstoragemgmt
libstoragemgmt-1.8.1-3.el8.x86_64
[root@hpe-dl320egen8-02 ~]# rpm -V libstoragemgmt
[root@hpe-dl320egen8-02 ~]# 
[root@hpe-dl320egen8-02 ~]# 

The consistent of rpm package is intergrity and there is no error with "rpm -V libstoragemgmt".

Move status to "VERIFIED"

Thanks

Comment 7 errata-xmlrpc 2020-04-28 16:46:14 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, 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-2020:1805


Note You need to log in before you can comment on or make changes to this bug.