Comment 2 for bug 1868422

`helm ls -a` doesn't show any issue. There are a couple of weird issues I see after deploying controller-0. I followed this doc:

https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/dedicated_storage_install_kubernetes.html

all the way up to `system host-unlock controller-0`.

After controller-0 reboots:

- if i run `nslookup tiller-deploy.kube-system.svc.cluster.local` on controller-0, dns resolution fails every now and then because 8.8.8.8 is resolving it instead of `192.168.204.1`

- still running on controller-0, `ping tiller-deploy.kube-system.svc.cluster.local` fails all the time. i can cfm that the request is going out of the oam interface.