The same issue got hit into Downstream Testing, So bit of investigation done in https://review.opendev.org/#/c/736468/ and it's found that it do not happens when using single playbook multinode.yml instead of using all playbooks. This differs in having multiple ansible-playbook call vs single ansible-playbook call, The root cause is not clear why it happens with multiple playbooks, but using single playbook should clear the issue, will propose the patch by removing DNM.
The same issue got hit into Downstream Testing, So bit of investigation done in https:/ /review. opendev. org/#/c/ 736468/ and it's found that it do not happens when using single playbook multinode.yml instead of using all playbooks. This differs in having multiple ansible-playbook call vs single ansible-playbook call, The root cause is not clear why it happens with multiple playbooks, but using single playbook should clear the issue, will propose the patch by removing DNM.