Bug 1419930

Summary: automation id is visible on create plan button
Product: Red Hat OpenStack Reporter: Ola Pavlenko <opavlenk>
Component: openstack-tripleo-uiAssignee: Honza Pokorny <hpokorny>
Status: CLOSED ERRATA QA Contact: Ola Pavlenko <opavlenk>
Severity: low Docs Contact:
Priority: unspecified    
Version: 11.0 (Ocata)CC: apannu, jjoyce, jpichon, jschluet, slinaber, tvignaud
Target Milestone: rc   
Target Release: 11.0 (Ocata)   
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-05-17 19:57:20 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:
Attachments:
Description Flags
create plan button none

Description Ola Pavlenko 2017-02-07 12:27:32 UTC
Created attachment 1248389 [details]
create plan button

Description of problem:

Create plan button should not have automation id visible for a user 

Version-Release number of selected component (if applicable):
openstack-tripleo-ui-2.0.1-0.20170126144317.f3bd97e.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1.Navigate to https://<Undercloud host>/plans/list
2.Take a look on Create plan button
3.

Actual results:
automation id is visible on create plan button

Expected results:
Create plan button should not have automation id visible for a user 


Additional info:
see attached screenshot

Comment 2 Julie Pichon 2017-02-09 11:11:28 UTC
A fix for this merged upstream on Jan 31st. It doesn't look like the fix made it into the last puddle but hopefully it will be in the next one.

Comment 3 Ola Pavlenko 2017-03-01 12:27:22 UTC
Merged upstream

Comment 5 Ola Pavlenko 2017-03-15 17:26:54 UTC
Verified openstack-tripleo-ui-3.1.0-2.el7ost.noarch

Comment 6 errata-xmlrpc 2017-05-17 19:57:20 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