Bug 857344 - Old existing mongodb is stopped after STAGE is upgraded
Old existing mongodb is stopped after STAGE is upgraded
Product: OpenShift Origin
Classification: Red Hat
Component: Containers (Show other bugs)
Unspecified Unspecified
medium Severity high
: ---
: ---
Assigned To: Rob Millner
libra bugs
Depends On:
  Show dependency treegraph
Reported: 2012-09-14 03:33 EDT by Jianwei Hou
Modified: 2015-05-14 18:59 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-09-17 17:29:55 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
mongodb.log (3.97 KB, text/x-log)
2012-09-14 03:33 EDT, Jianwei Hou
no flags Details

  None (edit)
Description Jianwei Hou 2012-09-14 03:33:36 EDT
Created attachment 612748 [details]

Description of problem:
After an upgrade on STG, the embedded mongodb cartridge is stopped.

Version-Release number of selected component (if applicable):
on STG

How reproducible:

Steps to Reproduce:
1. On STG, create app and embed mongodb, app and mongodb are both running
2. After STG has been upgraded, check apps and mongodb.

Actual results:
App is running, but mongodb is stopped.
[hjw@hjwlaptop ruby19]$ rhc app cartridge status -a ruby19s -c mongodb-2.0
Password: ******

MongoDB is stopped

Here are some information in log file, full log is attached:
Thu Sep 13 07:51:00 [PeriodicTask::Runner] task: DBConnectionPool-cleaner took: 4ms
Thu Sep 13 10:51:16 got kill or ctrl c or hup signal 15 (Terminated), will terminate after current cmd ends
Thu Sep 13 10:51:16 [interruptThread] now exiting
Thu Sep 13 10:51:16 dbexit:
Thu Sep 13 10:51:16 [interruptThread] shutdown: going to close listening sockets...
Thu Sep 13 10:51:16 [interruptThread] closing listening socket: 9
Thu Sep 13 10:51:16 [interruptThread] shutdown: going to flush diaglog...
Thu Sep 13 10:51:16 [interruptThread] shutdown: going to close sockets...
Thu Sep 13 10:51:16 [interruptThread] shutdown: waiting for fs preallocator...
Thu Sep 13 10:51:16 [interruptThread] shutdown: closing all files...

Expected results:
mongodb should be running.

Additional info:
I have one non-scaling perl app and a scaling ruby-1.9 app, they are both embedded with mongodb, which stopped for both of them.
Have to start mongodb from CLI to get it get back to work
Comment 1 Rob Millner 2012-09-14 15:26:20 EDT
Upgrading the mongodb kills all instances of mongodb running in gears.  Adding a restart to the migration script brings it back up.

Li commit 5f87da6.
Comment 2 Rob Millner 2012-09-14 15:35:19 EDT
Master pull request:

Stage pull request:
Comment 3 Rob Millner 2012-09-14 15:36:16 EDT
Reset severity high based on this will wipe out all instances of mongodb on all gears in prod when we upgrade.
Comment 4 Rob Millner 2012-09-14 19:08:46 EDT
Merged into the stage and master branches.
Comment 5 Adam Miller 2012-09-14 19:36:02 EDT
Rob's patch is a part of devenv-stage_237 (ami-f58b3b9c)
Comment 6 Jianwei Hou 2012-09-17 02:01:39 EDT
Verified on STAGE

1. Create apps and embed mongodb before upgrade on STAGE
2. After STAGE has been upgraded check app and embedded mongodb

App and mongodb are both running.

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