Bug 1229795

Summary:	Post-install validation doesn't exist in the CLI
Product:	Red Hat OpenStack	Reporter:	Imre Farkas <ifarkas>
Component:	python-rdomanager-oscplugin	Assignee:	Imre Farkas <ifarkas>
Status:	CLOSED ERRATA	QA Contact:	Ola Pavlenko <opavlenk>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	Director	CC:	athomas, calfonso, dnavale, jslagle, mburns, oblaut, rhel-osp-director-maint, ukalifon
Target Milestone:	ga	Keywords:	Triaged
Target Release:	Director
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-rdomanager-oscplugin-0.0.6-2.el7ost	Doc Type:	Bug Fix
Doc Text:	The post-install validation was not implemented in the unified CLI, it was implemented only in the deprecated OpenStack Deployment (tripleO) scripts. As a result, the command was missing from python-rdomanager-oscplugin. With this update, the post-install validation is implemented and the 'openstack overcloud validate' command is now present in the CLI.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:53:00 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:
Embargoed:

Description Imre Farkas 2015-06-09 15:54:39 UTC

Description of problem:
Post-install validation doesn't exist in the CLI, it's only in instack scripts.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Mike Burns 2015-06-09 16:02:04 UTC

https://review.gerrithub.io/#/c/235079/

Comment 6 Mike Burns 2015-06-12 13:04:13 UTC

Patch merged upstream: https://github.com/rdo-management/python-rdomanager-oscplugin/commit/d67e483c1384c958352232e2e0c67b894e2296af

Comment 8 Udi Kalifon 2015-06-29 16:08:55 UTC

Tempest is included by default with the director now. Verified.

Comment 10 errata-xmlrpc 2015-08-05 13:53:00 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1549