Seems my initial mistake affected to rdb-provisionner as well. Noticed that apiServer set the wrong IP in /etc/kubernetes/kubeadm.yaml file. Is there a way I can fix this certificate issue? Warning Failed 15h (x4 over 15h) kubelet, controller-0 Failed to pull image "registry.local:9001/ quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11": rpc error: code = Unknown desc = failed to pull and unpack image "registry.local:9001/ quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11": failed to resolve reference "registry.local:9001/ quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11": failed to authorize: failed to fetch oauth token: Post https://192.168.172.106:9002/token/: x509: *certificate is valid for 192.168.204.1, 172.168.172.106, not 192.168.172.106* https://paste.opendev.org/show/810179/ On Fri, Oct 22, 2021 at 5:59 PM open infra <openinfradn@gmail.com> wrote:

Hi,

During the bootstrap, I miss configured OAM IP. I noticed that network config is incorrect after unlocking the controller (AIO Simplex). I managed to updated OAM IP using system oam-modify, but it did not reflect on the network interface. I know that the puppet is managing NIC config, though I managed to fix the IP address of the host. Where is the source, that puppet use to update the host IP when the host reboot?

Regards, Danishka