M/N upgrades - Start mongod before calling ceilometer-dbsync
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Michele Baldessari |
Bug Description
Currently we in major_upgrade_
We also get this during the db-sync if mongod is down:
root 4387 0.4 0.5 315644 41812 ? Ss Sep23 1:52 /usr/bin/python /usr/bin/
root 6810 0.0 0.1 195516 9912 ? S 06:03 0:00 \_ /usr/bin/python /usr/bin/
root 6823 0.0 0.0 115248 1568 ? S 06:03 0:00 \_ /bin/bash /usr/local/
root 14714 0.0 0.1 227008 14876 ? S 06:03 0:00 \_ python /usr/libexec/
root 14719 0.0 0.0 149708 6184 ? S 06:03 0:00 \_ python /var/lib/
root 14720 0.0 0.0 115380 1676 ? S 06:03 0:00 \_ /bin/bash /var/lib/
root 19205 1.1 0.6 627596 51988 ? Sl 06:05 0:14 \_ /usr/bin/python2 /usr/bin/
And we can see the process constantly trying to talk to a mongo server:
[pid 19205] connect(4, {sa_family=AF_INET, sin_port=
[pid 19257] poll([{fd=4, events=POLLOUT}], 1, 20000) = 1 ([{fd=4, revents=
[pid 19205] getsockopt(4, SOL_SOCKET, SO_ERROR, [111], [4]) = 0
[pid 19205] close(4) = 0
summary: |
- M/N upgrades - Stop the services to be moved to systemd directly in the - migration function + M/N upgrades - Start mongod before calling ceilometer-dbsync |
Fix proposed to branch: master /review. openstack. org/375979
Review: https:/