Bug 1702695

Summary: fresh install of mod_auth_mellon shows rpm verification warnings
Product: Red Hat Enterprise Linux 8 Reporter: Scott Poore <spoore>
Component: mod_auth_mellonAssignee: Jakub Hrozek <jhrozek>
Status: CLOSED ERRATA QA Contact: Scott Poore <spoore>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0   
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mod_auth_mellon-0.14.0-5.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 21:09:17 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 Scott Poore 2019-04-24 13:49:44 UTC 
Description of problem:

Immediately after install, I see rpm verification warnings.

[root@sp1 ~]# rpm -V mod_auth_mellon
.....UG..    /run/mod_auth_mellon


Version-Release number of selected component (if applicable):
mod_auth_mellon-0.14.0-3.el8.x86_64


How reproducible:
always

Steps to Reproduce:
1. dnf -y install mod_auth_mellon
2. rpm -V mod_auth_mellon

Actual results:
[root@sp1 ~]# rpm -V mod_auth_mellon
.....UG..    /run/mod_auth_mellon


Expected results:
No warnings/errors/messages

Additional info:
Comment 1 Jakub Hrozek 2019-04-25 07:00:18 UTC 
The fix was pushed to dist-git, we're going to build the package once the gating is done..
Comment 3 Scott Poore 2019-06-11 18:15:26 UTC 
Verified.

Version ::

mod_auth_mellon-0.14.0-8.el8.x86_64

Results ::

[root@rhel8-0 ~]# rpm -q mod_auth_mellon
package mod_auth_mellon is not installed

[root@rhel8-0 ~]# dnf -y install mod_auth_mellon > dnf_install.log 2>&1

[root@rhel8-0 ~]# rpm -q mod_auth_mellon
mod_auth_mellon-0.14.0-8.el8.x86_64

[root@rhel8-0 ~]# rpm -V mod_auth_mellon
[root@rhel8-0 ~]#
Comment 5 errata-xmlrpc 2019-11-05 21:09:17 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/RHSA-2019:3421