Description of problem: Multiple issues related to DPDK derive parameters 1) Getting stack already exists issue in the environment where overcloud with same name is already deployed. get_network_config action is failing and error message is stack already exists if overcloud is deployed already. 2) get_network_config action is not providing the validation message when not able to determine the network config for any role. 3) ODL DPDK condition is missing to check whether DPDK features is enabled or not in ODL to support the derive parameters. 4) Empty messages are not filtered for the roles which are success. Derive parameters failure message format needs to be changed to display only failures messages. Version-Release number of selected component (if applicable): OSP12 How reproducible: Steps to Reproduce: Actual results: Expected results: Additional info:
Below patches are merged in upstream and back-ported to stable/pike. https://review.openstack.org/#/c/489168/ https://review.openstack.org/#/c/486425/ Below patches are in progress to merge in upstream. https://review.openstack.org/#/c/488362/ https://review.openstack.org/#/c/481524/
All the patches are merged in upstream. https://review.openstack.org/#/c/488362/ https://review.openstack.org/#/c/481524/ Above patches are backported to stable/pike but merging is in progress. https://review.openstack.org/#/c/527877/ https://review.openstack.org/#/c/527112/
Below backported patches are merged in stable/pike: https://review.openstack.org/#/c/527112/ https://review.openstack.org/#/c/511410/ https://review.openstack.org/#/c/500888/
Below backported patch is also merged in stable/pike: https://review.openstack.org/#/c/527877/
ODL is TechPreview for Pike Please move it to Queens z release
Closing this BZ will Reopen for Queens [ODL is TP in Pike]
(In reply to Jaganathan Palanisamy from comment #0) > Description of problem: > Multiple issues related to DPDK derive parameters > 1) Getting stack already exists issue in the environment where overcloud > with same name is already deployed. get_network_config action is failing and > error message is stack already exists if overcloud is deployed already. Jagan, Please advise how to Verify? is unit test is enough? > 2) get_network_config action is not providing the validation message when > not able to determine the network config for any role. Jagan, Please advise how to Verify? is unit test is enough? > 3) ODL DPDK condition is missing to check whether DPDK features is enabled > or not in ODL to support the derive parameters. Should move to 13 since ODL is TP Queens > 4) Empty messages are not filtered for the roles which are success. Derive > parameters failure message format needs to be changed to display only > failures messages. Jagan, Please advise how to Verify? is unit test is enough? > > Version-Release number of selected component (if applicable): > OSP12 > > How reproducible: > > > Steps to Reproduce: > > > Actual results: > > > Expected results: > > > Additional info:
(In reply to Yariv from comment #22) > (In reply to Jaganathan Palanisamy from comment #0) > > Description of problem: > > Multiple issues related to DPDK derive parameters > > 1) Getting stack already exists issue in the environment where overcloud > > with same name is already deployed. get_network_config action is failing and > > error message is stack already exists if overcloud is deployed already. > > Jagan, Please advise how to Verify? is unit test is enough? Yariv, Need to check whether derives the parameters once overcloud deployment is done. > > > 2) get_network_config action is not providing the validation message when > > not able to determine the network config for any role. > > Jagan, Please advise how to Verify? is unit test is enough? Validation message 'Unable to determine network config for role' will be displayed if network config is not provided for any role. > > > 3) ODL DPDK condition is missing to check whether DPDK features is enabled > > or not in ODL to support the derive parameters. > > Should move to 13 since ODL is TP Queens > > > 4) Empty messages are not filtered for the roles which are success. Derive > > parameters failure message format needs to be changed to display only > > failures messages. > > Jagan, Please advise how to Verify? is unit test is enough? Failure message format can be verified by providing invalid value for custom plan env workflow input 'num_phy_cores_per_numa_node_for_pmd' or 'huge_page_allocation_percentage'. > > > > > > Version-Release number of selected component (if applicable): > > OSP12 > > > > How reproducible: > > > > > > Steps to Reproduce: > > > > > > Actual results: > > > > > > Expected results: > > > > > > Additional info:
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/RHSA-2018:2331