Menu

1 / 2

[BUG]: when reinstalling a cluster without deleting the old kubeconfig, the old kubeconfig can lead to issues

GitHub Public Timeline Feed·artificial-intelligence·14 days ago
#9fHDJCo7
Reading 0:00
15s threshold

Type

Role

Ansible Version

No response

Bug Description

TASK [redhat_consulting_services.openshift.cluster_installation_check: Wait for cluster bootstrap to complete]
[ERROR]: Task failed: Module failed: The command existed with a non-zero return code.
Origin: /usr/share/ansible/collections/ansible_collectio9ns/redhat_consulting_services/openshift/roles/cluster_installation_check/tasks/main.yml:3:3

[...]
Get https://api.example.com[...] tls: failed to verify certificate[...]

When inspecting the kubeconfig (which was leftover from the previous installation), it was discovered that it was incomplete, it was missing:

- cluster:
    certificate-authority-data: [...]

section

I would propose to fix this, by making sure the file is empty (delete it), before regenrating it, as I can not imagine a usecase where you need to preserve an old KUBECONFIG when (re)installing.

Steps to Reproduce

No response

Expected Behavior

No response

Actual Behavior

No response