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 1381326 - dirsrv-snmp.service is provided by 389-ds-base instead of 389-ds-base-snmp
Summary: dirsrv-snmp.service is provided by 389-ds-base instead of 389-ds-base-snmp
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: mreynolds
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-03 17:27 UTC by Viktor Ashirov
Modified: 2020-09-13 21:12 UTC (History)
3 users (show)

Fixed In Version: 389-ds-base-1.3.6.1-7.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 21:10:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1242 0 None None None 2020-09-13 21:12:43 UTC
Red Hat Product Errata RHBA-2017:2086 0 normal SHIPPED_LIVE 389-ds-base bug fix and enhancement update 2017-08-01 18:37:38 UTC

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


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