Bug 1437103

Summary:	Validations always fail from the GUI, and their output is blank
Product:	Red Hat OpenStack	Reporter:	Udi Kalifon <ukalifon>
Component:	openstack-tripleo-validations	Assignee:	Florian Fuchs <flfuchs>
Status:	CLOSED ERRATA	QA Contact:	Ola Pavlenko <opavlenk>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	11.0 (Ocata)	CC:	apannu, dbecker, jjoyce, jrist, jschluet, slinaber, tvignaud
Target Milestone:	beta	Keywords:	Regression, Triaged
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-validations-5.4.0-7.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-17 20:15:51 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 Udi Kalifon 2017-03-29 13:16:49 UTC

Description of problem:
You can successfully run a validation from CLI with:
run-validation <path-to-validator> <path-to-ssh-key> <plan-name>

b.t.w. you can get the ssh key from:
mistral environment-get ssh_keys

But when you start the validations from the GUI they fail, and when you click on one to see the failure - the output in it is blank.


Version-Release number of selected component (if applicable):
openstack-tripleo-ui-3.1.0-4.el7ost.noarch (puddle 2017-03-24)


How reproducible:
100%


Steps to Reproduce:
1. Run a validator from the GUI

Comment 4 Florian Fuchs 2017-03-31 11:13:38 UTC

Upstream bug report and fix:

- https://bugs.launchpad.net/tripleo/+bug/1678029
- https://review.openstack.org/#/c/452147/

Comment 5 Florian Fuchs 2017-04-05 14:49:32 UTC

Fix has landed upstream: https://review.openstack.org/#/c/453183/

Comment 7 Ola Pavlenko 2017-04-09 07:47:53 UTC

Verified 
openstack-tripleo-ui-3.1.0-8.el7ost.noarch

Comment 8 errata-xmlrpc 2017-05-17 20:15:51 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-2017:1245