Upgrades, puppet fails because it cannot start supervisor inside of container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Matthew Mosesohn |
Bug Description
1. install 5.0
2. run upgrade to 5.1
It happens 3 runs out of 10
Actual result:
It fails with errors
2014-08-26 16:20:27 INFO 31163 (health_checker) Checkers which are still fail ['integration_
Or
2014-08-26 16:20:27 INFO 31163 (health_checker) Checkers which are still fail ['ostf']
Here a logs from containers
http://
Error: Could not start Service[
Error: Could not start Service[
Here is debugging information http://
The reason is there is lock file /var/run/
When I added removing of pid file in the beginning of start.sh script, I got another error:
Error: Another program is already listening on a port that one of our HTTP servers is configured to use. Shut this program down first before starting supervisord.
http://
It looks like there is supervisor which was started by puppet, and then start.sh tries to start another supervisor and fails.
Expected result:
upgrade succeed
*5.1*
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "5.1"
api: "1.0"
build_number: "478"
build_id: "2014-08-
astute_sha: "bc60b7d027ab24
fuellib_sha: "ca5aa450ea3da7
ostf_sha: "907f25f8fad39b
nailgun_sha: "44876ddae29823
fuelmain_sha: "74ad3dd68020aa
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Matthew Mosesohn (raytrac3r) |
Fix proposed to branch: master /review. openstack. org/117250
Review: https:/