mongodb starts before network on VM and standalone

Bug #1691912 reported by Luca Cervigni
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
MOS Linux

Bug Description

Hello

In a deployment with 3 mongodb on separate VMs, the mongodb server service in systemd does not wait for network.target for starting up. This makes mongodb.service failing when the server restart, and when started by hand (after the network is restarted) works.

Workaround:

add the line:
After=network.target

in /lib/systemd/system/mongodb.service under the section [Unit]

Impact: mongodb fails to start if server restarted.
Reproducibility: on VMs, mongodb standalone node.

Changed in fuel:
assignee: nobody → MOS Linux (mos-linux)
milestone: none → 12.0
importance: Undecided → Medium
Revision history for this message
Michael Polenchuk (mpolenchuk) wrote :

Marked as invalid as we've stock/original mongodb package from ubuntu.

Changed in fuel:
status: New → Invalid
Revision history for this message
Ivan Suzdal (isuzdal) wrote :

We use upstream mongodb so it's better to file this bug here: https://launchpad.net/mongodb

Revision history for this message
Luca Cervigni (cervigni) wrote :

Ivan,
It seems that is not the right place to report mongodb bugs. Any idea where is the correct official channel? the only thing that pops up in google is a jira website I do not have access to.

Revision history for this message
Michael Polenchuk (mpolenchuk) wrote :

Luca, please have a look on above #2 comment from Ivan.

Revision history for this message
Luca Cervigni (cervigni) wrote :

Thanks, I was probably sleeping.

Reported here: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1693122

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.