Bug 1724898

Summary: [OSP13] Backport role-specific parameter validation message for CLI
Product: Red Hat OpenStack Reporter: Saravanan KR <skramaja>
Component: python-tripleoclientAssignee: Saravanan KR <skramaja>
Status: CLOSED ERRATA QA Contact: Sasha Smolyak <ssmolyak>
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: cfontain, hbrock, jslagle, mburns, yrachman
Target Milestone: z10Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-tripleoclient-9.3.1-6.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1783156 (view as bug list) Environment:
Last Closed: 2020-03-10 11:18:32 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:
Bug Depends On:    
Bug Blocks: 1783156    

Description Saravanan KR 2019-06-28 03:52:02 UTC
A warning message has been added to CLI deploy command, if a parameter is used for deployment is provided as role-specific, but not implemented as role-specific. It is available in OSP14, but not in OSP13. As the patches has no dependency, it would be more helpful to backport it to OSP13 as it is long life.

tripleo-common - https://review.opendev.org/#/c/545257/
tripleo-client - https://review.opendev.org/#/c/545260/

Comment 2 Yariv 2020-03-03 10:27:01 UTC
Verified
(undercloud) [stack@undercloud-0 ~]$ rpm -qa | grep python-tripleoclient
python-tripleoclient-9.3.1-7.el7ost.noarch

cat core_puddle_version 
2020-02-20.4


Added the following parameters

  ComputeOvsDpdkSriovParameters:
    TestParam: "TestValue"

Got the following output in openstack overcloud deploy :
  WARNING: Following parameter(s) are not supported as role-specific inputs.
    TestParam

Comment 4 errata-xmlrpc 2020-03-10 11:18:32 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/RHBA-2020:0760