Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue during upgrade from 0.16.2 to 0.16.3 : capi-provider #414

Closed
matthieu-robin opened this issue Oct 9, 2024 · 3 comments · Fixed by #415
Closed

Issue during upgrade from 0.16.2 to 0.16.3 : capi-provider #414

matthieu-robin opened this issue Oct 9, 2024 · 3 comments · Fixed by #415

Comments

@matthieu-robin
Copy link

Got an issue related to the capi-provider during the upgrade.
Hope it helps:

Helm rollback to previous release cozy-cluster-api/capi-providers.v9 with chart [email protected] failed: cannot patch "kubeadm" with kind BootstrapProvider: Internal error occurred: failed calling webhook "vbootstrapprovider.kb.io": failed to call webhook: Post "https://capi-operator-webhook-service.cozy-cluster-api.svc:443/mutate-operator-cluster-x-k8s-io-v1alpha2-bootstrapprovider?timeout=10s": context deadline exceeded && cannot patch "kamaji" with kind ControlPlaneProvider: Internal error occurred: failed calling webhook "vcontrolplaneprovider.kb.io": failed to call webhook: Post "https://capi-operator-webhook-service.cozy-cluster-api.svc:443/mutate-operator-cluster-x-k8s-io-v1alpha2-controlplaneprovider?timeout=10s": context deadline exceeded && cannot patch "cluster-api" with kind CoreProvider: Internal error occurred: failed calling webhook "vcoreprovider.kb.io": failed to call webhook: Post "https://capi-operator-webhook-service.cozy-cluster-api.svc:443/mutate-operator-cluster-x-k8s-io-v1alpha2-coreprovider?timeout=10s": context deadline exceeded && cannot patch "kubevirt" with kind InfrastructureProvider: Internal error occurred: failed calling webhook "vinfrastructureprovider.kb.io": failed to call webhook: Post "https://capi-operator-webhook-service.cozy-cluster-api.svc:443/mutate-operator-cluster-x-k8s-io-v1alpha2-infrastructureprovider?timeout=10s": context deadline exceeded
@kvaps
Copy link
Member

kvaps commented Oct 9, 2024

Thank you for report, could you please check the state of pods in cozy-cluster-api namespace:

kubectl get pod -o cozy-cluster-api

@matthieu-robin
Copy link
Author

After investigation, I found that I lost one linstor node ( OFFLINE), I rebooted the node, and after reboot, ther issue was gone.
let me know if you need logs... I think we can close the issue.

@kvaps kvaps mentioned this issue Oct 9, 2024
Merged
@kvaps
Copy link
Member

kvaps commented Oct 9, 2024 •
edited
Loading

All right, just found that fix for cluster api didn't work, I'm going to prepare a new release with #415

@kvaps kvaps closed this as completed in #415 Oct 9, 2024
@kvaps kvaps closed this as completed in 3842191 Oct 9, 2024
chumkaska pushed a commit to chumkaska/cozystack that referenced this issue Oct 15, 2024
@kvaps @agaenix
Fix cluster-api operator resources (aenix-io#415)
ff7d275 
same as aenix-io#400, second try 

fixes aenix-io#414

Signed-off-by: Andrei Kvapil <[email protected]>

Signed-off-by: Andrei Kvapil <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix cluster-api operator resources aenix-io/cozystack
2 participants
@kvaps @matthieu-robin