Bug 1381326

Summary: dirsrv-snmp.service is provided by 389-ds-base instead of 389-ds-base-snmp
Product: Red Hat Enterprise Linux 7 Reporter: Viktor Ashirov <vashirov>
Component: 389-ds-baseAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: mreynolds, nkinder, rmeggins
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.6.1-7.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 21:10:21 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 Viktor Ashirov 2016-10-03 17:27:48 UTC 
Description of problem:
After package split, dirsrv-snmp.service is provided by 389-ds-base instead of 389-ds-base-snmp:

# rpm -qf /usr/lib/systemd/system/dirsrv-snmp.service
389-ds-base-1.3.5.10-11.el7.x86_64

Version-Release number of selected component (if applicable):
389-ds-base-1.3.5.10-11.el7.x86_64
Comment 1 Noriko Hosoi 2016-10-03 17:34:37 UTC 
You are right, Viktor...  This is wrong...
$ rpm -ql 389-ds-base | egrep dirsrv-snmp
/usr/lib/systemd/system/dirsrv-snmp.service
Comment 3 Viktor Ashirov 2017-04-06 11:07:53 UTC 
Build tested:
389-ds-base-1.3.6.1-6.el7.x86_64

# rpm -qf /usr/lib/systemd/system/dirsrv-snmp.service
389-ds-base-1.3.6.1-6.el7.x86_64

# rpm -ql 389-ds-base | grep dirsrv-snmp
/usr/lib/systemd/system/dirsrv-snmp.service

Looks like RHEL spec file doesn't contain the required change that is present in upstream. Marking as ASSIGNED.
Comment 5 Viktor Ashirov 2017-04-24 13:45:01 UTC 
Build tested:
389-ds-base-1.3.6.1-9.el7.x86_64


# rpm -qf /usr/lib/systemd/system/dirsrv-snmp.service
389-ds-base-snmp-1.3.6.1-9.el7.x86_64

Marking as VERIFIED.
Comment 6 errata-xmlrpc 2017-08-01 21:10:21 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-2017:2086