Bug 2074001 - NFV vars are missing from deploy_steps_tasks.yaml
Summary: NFV vars are missing from deploy_steps_tasks.yaml
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Alpha
: ---
Assignee: Saravanan KR
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-11 10:14 UTC by Ella Shulman
Modified: 2022-06-16 10:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-16 10:34:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
templates used for deployment (7.52 KB, application/gzip)
2022-04-11 10:14 UTC, Ella Shulman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NFV-2492 0 None None None 2022-04-19 09:03:53 UTC
Red Hat Issue Tracker OSP-14617 0 None Closed Rados don't start after OS reinstallation 2022-06-13 08:10:57 UTC

Description Ella Shulman 2022-04-11 10:14:45 UTC
Created attachment 1871752 [details]
templates used for deployment

Description of problem:
when deploying with NFV an error is raised which indicates tripleo_ovs_dpdk_pmd_core_list is missing although it exists in the templates.

Version-Release number of selected component (if applicable):
osp 17.0
rhel 9

How reproducible:
100%

Steps to Reproduce:
1.run overcloud deploy with NFV features enabled
2.
3.

Actual results:
2022-04-11 09:45:21.497276 | 5254007f-1c52-b9a3-dcb6-000000000c70 |      FATAL | Check valid input for tripleo_ovs_dpdk_pmd_core_list | computeovsdpdksriov-0 | error={"changed": false, "msg": "List of PMD cores cannot be empty - tripleo_ovs_dpdk_pmd_core_list"}                
2022-04-11 09:45:21.499332 | 5254007f-1c52-b9a3-dcb6-000000000c70 |     TIMING | tripleo_ovs_dpdk : Check valid input for tripleo_ovs_dpdk_pmd_core_list | computeovsdpdksriov-0 | 0:00:28.704901 | 0.07s                                                                                
2022-04-11 09:45:21.519718 | 5254007f-1c52-b9a3-dcb6-000000000cac |      FATAL | Check valid input for tripleo_ovs_dpdk_pmd_core_list | computeovsdpdksriov-1 | error={"changed": false, "msg": "List of PMD cores cannot be empty - tripleo_ovs_dpdk_pmd_core_list"}                    
2022-04-11 09:45:21.520405 | 5254007f-1c52-b9a3-dcb6-000000000cac |     TIMING | tripleo_ovs_dpdk : Check valid input for tripleo_ovs_dpdk_pmd_core_list | computeovsdpdksriov-1 | 0:00:28.726002 | 0.03s  

Expected results:
working deployment

Additional info:
when manually setting this var in deploy_steps_tasks.yaml it works

Comment 1 Haresh Khandelwal 2022-04-13 08:01:34 UTC

*** This bug has been marked as a duplicate of bug 2041429 ***

Comment 4 Saravanan KR 2022-04-19 11:47:27 UTC
the problem is one parameter under parameter_defaults can be present only once. which means ComputeOvsDpdkSriovParameters can be in only one file, if it is in multiple files, it will override the older ones. and that is what happens, dpdk-config is added first and then sriov-config, so the dpdk configs are removed. After changing the templates, this dpdk config is available in the deployment. closing it as not a bug.


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