Bug 1439289

Summary: The validator controller-token.yaml is called "Unnamed" in the GUI
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: openstack-tripleo-validationsAssignee: Florian Fuchs <flfuchs>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: medium Docs Contact:
Priority: low    
Version: 11.0 (Ocata)CC: akrivoka, beth.white, flfuchs, gchamoul, jjoyce, jschluet, opavlenk, slinaber, tvignaud
Target Milestone: betaKeywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-validations-7.4.2-0.20171016115241.c2c9bf2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 21:22:29 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 Udi Kalifon 2017-04-05 15:29:49 UTC
Description of problem:
In puddle 2017-04-04, one of the validators in the GUI is titled "Unnamed". I tried to look inside controller-token.yaml but couldn't see why it got this name... It is sipposed to be titled "Verify that keystone admin token is disabled."


Version-Release number of selected component (if applicable):
openstack-tripleo-validations-5.4.0-6.el7ost.noarch
openstack-tripleo-ui-3.1.0-6.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Look in the GUI, see the validators and their names

Comment 2 Gaƫl Chamoulaud 2017-10-03 14:57:19 UTC
This patch was merged in openstack/tripleo-validations (MASTER) and I proposed the backport into stable/pike [1].

[1] - https://review.openstack.org/#/c/509195/

Comment 7 errata-xmlrpc 2017-12-13 21:22:29 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:3462