AIO-SX: coredns pod stuck in pending

[Brent Rowsell]

Brief Description
-----------------
coredns pod stuck in pending state on an AIO-SX. There are two replicas when there should only be 1 on this config

kubectl describe ReplicaSet -n kube-system coredns-5c4849b47c
Name: coredns-5c4849b47c
Namespace: kube-system
Selector: k8s-app=kube-dns,pod-template-hash=5c4849b47c
Labels: k8s-app=kube-dns
                pod-template-hash=5c4849b47c
Annotations: deployment.kubernetes.io/desired-replicas: 2
                deployment.kubernetes.io/max-replicas: 3
                deployment.kubernetes.io/revision: 1
Controlled By: Deployment/coredns
Replicas: 2 current / 2 desired
Pods Status: 1 Running / 1 Waiting / 0 Succeeded / 0 Failed

Severity
--------
Major

Steps to Reproduce
------------------
Deploy an AIO-SX

Expected Behavior
------------------
See above

Actual Behavior
----------------
See above

Reproducibility
---------------
100%

System Configuration
--------------------
AIO-SX

Branch/Pull Time/Commit
-----------------------
BUILD_DATE="2019-06-03 18:36:49 -0400"

Last Pass
---------
Don't know

Timestamp/Logs
--------------
See above

Test Activity
-------------
Other

[Lin Shuicheng (shuicheng)]

I fixed the issue before. Let me check it again with latest code.

[Brent Rowsell (brent-rowsell)]

Issues exists in a load built "2019-06-12 20:20:07"

[Lin Shuicheng (shuicheng)]

It should be due to ansible switch. The fix is implemented in puppet only. I am adding the fix for ansible now.

[Lin Shuicheng (shuicheng)]

The issue has been fixed by below patch.
https://review.opendev.org/664764
"
Additionally, commit ab595415aa02e1010a710c4d4b9170f1c7a04ab2
to address LP https://bugs.launchpad.net/bugs/1822880 - Two coredns
pods in one node system - is also ported to the playbook in this
commit.
"