Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1587957

Summary: DPDK: vswitchd failure logs with osp10 & ovs29 can be ignored at the start of deployment
Product: Red Hat OpenStack Reporter: Saravanan KR <skramaja>
Component: openstack-tripleo-heat-templatesAssignee: Saravanan KR <skramaja>
Status: CLOSED WONTFIX QA Contact: Amit Ugol <augol>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: dbecker, mburns, morazi, samccann
Target Milestone: asyncKeywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Release Note
Doc Text:
During the start of the deployment with ovs2.9, the OVS-DPDK is enabled using first-boot before applying the kernel arguments and rebooting. This will cause vswitchd service to fail initially, but later when the kernel arguments are applied and the node has been rebooted, vswtichd will run as expected with DPDK enabled. The failure messages at the initial stage before the reboot can be ignored.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-06 10:56:44 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:

Description Saravanan KR 2018-06-06 10:46:23 UTC 
From ovs2.7 onwards, vswitchd will be restarted when dpdk-init
flag is set to true. In the current version of the first-boot, we are
enabling dpdk before setting the kernel args and reboot. So, huge
pages will not be available. It will fail the vswitchd restart during
the dpdk-init.

But later when kernel args are applied and rebooted, it will all work
fine. And all the ovs configurations will be applied correctly. But
this causes atleast a few set of logs related to vswtichd failure
before the restart. Though this does not harm, we need to be aware of
this behavior as analyzing logs will create questions around it.