Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1251950

Summary: Rebase on newer mongodb
Product: Red Hat Satellite Reporter: Stephen Benjamin <stbenjam>
Component: PackagingAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bbuckingham, bkearney, cwelton, ehelms, greartes, stbenjam
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-16 20:38:24 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 Stephen Benjamin 2015-08-10 11:56:23 UTC
There's a disconnect between the mongo versions used upstream and down.

In the beginning, EPEL 7 included its own systemd service unit with this configuration:

  PIDFile=/var/run/mongodb/mongodb.pid

In August of last year, mongo added a service unit of their own to the repository, as part of https://jira.mongodb.org/browse/SERVER-7285.  With this value:

  PIDFile=/var/run/mongodb/mongod.pid (mongod vs mongodb)

This broke everyone who upgraded as /etc/mongodb.conf still referred to the old location.

Through some installer and puppet module changes we accommodated the change, but now run into the issue where upstream using the new location, and downstream using the old location, are causing problems for us (see: https://bugzilla.redhat.com/show_bug.cgi?id=1248663).

It'd be good if for Satellite 6.2 we can move to the same upstream version of mongo, if possible.  Or at the very least include the newer service unit.

Comment 4 Bryan Kearney 2016-08-04 20:18:02 UTC
Moving 6.2 bugs out to sat-backlog.