Bug 1439289 - The validator controller-token.yaml is called "Unnamed" in the GUI
Summary: The validator controller-token.yaml is called "Unnamed" in the GUI
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-validations
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
Target Milestone: beta
: 12.0 (Pike)
Assignee: Florian Fuchs
QA Contact: nlevinki
Depends On:
TreeView+ depends on / blocked
Reported: 2017-04-05 15:29 UTC by Udi Kalifon
Modified: 2018-02-05 19:07 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-validations-7.4.2-0.20171016115241.c2c9bf2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 21:22:29 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1714962 0 None None None 2017-09-04 13:56:58 UTC
OpenStack gerrit 500555 0 None None None 2017-09-04 13:57:35 UTC
OpenStack gerrit 509195 0 None None None 2017-10-03 14:57:19 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

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):

How reproducible:

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.


Note You need to log in before you can comment on or make changes to this bug.