Bug 1393378

Summary: OPS Tools | Availability Monitoring | OS Checks | Existing oschecks are required pre-configured openstack services in order to work correctly. They don't work from "scratch" on a fresh openstack deployment.
Product: Red Hat OpenStack Reporter: Leonid Natapov <lnatapov>
Component: sensuAssignee: Martin Magr <mmagr>
Status: CLOSED WONTFIX QA Contact: Leonid Natapov <lnatapov>
Severity: high Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: lars, mrunge, oblaut
Target Milestone: ---Keywords: Documentation, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-11 17:13:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Leonid Natapov 2016-11-09 12:36:01 UTC 
Description of problem:

Existing oschecks are required pre-existing openstack configuration in order to work correctly. 

Oschecks don't work "from scratch" on a fresh openstack deployment.

----------------------------------------------------------------------------
This means that some of oschecks will report failures on a fresh openstack deployment.
----------------------------------------------------------------------------

In order to make those checks to work the following should be configured on a fresh openstack deployment:

1.flavor  named “m1.tiny”
2.external network named “public”
3.Image named “cirrus”
4.IPv4 subnet for creating floating IP
5.The cinder volume check uses an outdated api and results in the WARRNING message.



oschecks should work on fresh openstack deployment without additional configuration.
Comment 1 Martin Magr 2017-10-11 17:13:06 UTC 
oschecks are being replaced by healthchecks, so this bug is irrelevant now.
Comment 2 Lars Kellogg-Stedman 2017-10-11 17:17:45 UTC 
In OSP10, while we ship the oschecks package we don't actually make use of it on the overcloud.  The fix for this bug is to provide appropriate documentation so that deployers can make use of this package if they so choose.

In OSP 12 and later, service checks will be provided by the container healthcheck mechanism.