Expected running services not running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
New
|
Undecided
|
Unassigned |
Bug Description
Failure from url:
http://
2014-07-18 20:02:13.874 | Couldn't find log for s-proxy at /opt/stack/
2014-07-18 20:02:13.874 | tempest does not look like a valid service, skipping log check
2014-07-18 20:02:13.874 | Expected running services not running: ,s-proxy
2014-07-18 20:02:13.878 | + die 330 'Failure in check-sanity'
2014-07-18 20:02:13.878 | + local exitcode=1
2014-07-18 20:02:13.878 | [Call Trace]
2014-07-18 20:02:13.878 | ./grenade.
2014-07-18 20:02:13.881 | [ERROR] ./grenade.sh:330 Failure in check-sanity
2014-07-18 20:02:13.881 | Exit code: 1
2014-07-18 20:02:13.881 |
logstash query shows at least 3 other instances of this failure in the past week
"Expected running services not running: ,s-proxy"
Found another: logs.openstack. org/78/ 106778/ 12/check/ check-grenade- dsvm/bf28a42/ logs/grenade. sh.txt. gz
http://
2014-07-18 20:32:35.086 | Expected running services not running: ,n-obj sh:330: die
2014-07-18 20:32:35.087 | + die 330 'Failure in check-sanity'
2014-07-18 20:32:35.087 | + local exitcode=1
2014-07-18 20:32:35.087 | [Call Trace]
2014-07-18 20:32:35.087 | ./grenade.
2014-07-18 20:32:35.090 | [ERROR] ./grenade.sh:330 Failure in check-sanity
2014-07-18 20:32:35.090 | Exit code: 1
Looks like a lot more hits for query: "Expected running services not running:"
266 hits in last 48 hours