Fix for pci-irq-affinity-agent failing to start in AIO
Ensure that pci-irq-affinity-agent is launched on worker nodes.
This includes AIO and standard configs.
Root cause is in this agent start script, it can be started
only if node type is worker. But for AIO, the node type is controller.
Then pmon will restart it again and again and cause controller degrade
in the end.
Below test for AIO pass
1) Pci-irq-affinity-agent started normally before openstack apply.
After openstack apply, related openstack config applied to
agent config file as expected.
2) Verified agent started normally in non-openstack worker node for
both AIO and multi-node.
No degrade in controller node.
Reviewed: https:/ /review. opendev. org/659081 /git.openstack. org/cgit/ starlingx/ integ/commit/ ?id=ce0cc60346a 73372ca967f6311 f8a92a924641d7
Committed: https:/
Submitter: Zuul
Branch: master
commit ce0cc60346a7337 2ca967f6311f8a9 2a924641d7
Author: zhipengl <email address hidden>
Date: Wed May 15 07:22:42 2019 +0800
Fix for pci-irq- affinity- agent failing to start in AIO
Ensure that pci-irq- affinity- agent is launched on worker nodes.
This includes AIO and standard configs.
Root cause is in this agent start script, it can be started
only if node type is worker. But for AIO, the node type is controller.
Then pmon will restart it again and again and cause controller degrade
in the end.
Below test for AIO pass affinity- agent started normally before openstack apply.
1) Pci-irq-
After openstack apply, related openstack config applied to
agent config file as expected.
2) Verified agent started normally in non-openstack worker node for
both AIO and multi-node.
No degrade in controller node.
Change-Id: I73e9dff0358b7e d86bfaaadac834e 19fe227892f
Closes-Bug: #1828877
Signed-off-by: zhipengl <email address hidden>