| -opendevstatus- NOTICE: There will be a brief outage of the Gerrit service on review.opendev.org starting at 15:00 UTC today as part of a routine project rename maintenance: http://lists.opendev.org/pipermail/service-announce/2021-July/000023.html | 14:10 | |
| airship-irc-bot | <vetbijaya> Hi Amir, I'm not sure if Airshipctl is compatible with OpenStack Stein. I'm currently working on an upgrade with OpenStack Victoria in Devstack. Possibly @ratnopam.chakrabarti can give you more context on this. Meanwhile you can follow this documentation: https://docs.airshipit.org/airshipctl/providers/cluster_api_openstack.html | 14:24 |
|---|---|---|
| -opendevstatus- NOTICE: There will be a brief outage of the Gerrit service on review.opendev.org in the next few minutes as part of a routine project rename maintenance: http://lists.opendev.org/pipermail/service-announce/2021-July/000023.html | 14:59 | |
| airship-irc-bot | <ratnopam.chakrabarti> Hi Amir, Airshipctl uses cluster-api-openstack provider underneath. Stein version is supported as per cluster api documentation. From the error above, it seems to be an issue with authentication. Could you please follow the instructions @vetbijaya provided and see if it helps? If not, please let us know and we'd be happy to assist. Thanks. | 15:58 |
| airship-irc-bot | <sidney.shiba> Hi team, is it possible to render the `clusterctl-init-target` phase? Would like to see if the cert-manager Deployment has tolerations set. I am having an issue deploying `cert-manager` pods on the target's control plane node (CAPZ). I have verified that control plane node is tainted (see below). `capz@capz-v050-vm:~/projects/airshipctl$ kubectl --kubeconfig ~/.airship/kubeconfig --context target-cluster get nodes -o yaml | | 20:23 |
| airship-irc-bot | grep taints -A2` `taints:` `- effect: NoSchedule` `key: node-role.kubernetes.io/master` The workaround was to *untaint* the control plane node to allow CAPI/CAPZ components to be initialized in the Target cluster's control plane node. | 20:23 |
| airship-irc-bot | <raliev> as far as I know, cert-manager deployment is a part of initinfra-networking phase... regarding rendering clusterctl-init phases - it's only possible to render providers, not cert-manager | 20:32 |
| airship-irc-bot | <raliev> it is possible, but you will observe only rendered providers: ```airshipctl phase render clusterctl-init-target -s executor``` | 21:32 |
| airship-irc-bot | <sidney.shiba> @raliev the "blind spot" for `clusterctl-init-target` is for the three `cert-manager` pods. I am almost positive for CAPZ that it is an issue about _*tolerations*_ for `cert-manager` because as soon as I _*untaint*_ the control plane node, it resumes the initialization. Am I missing something that might be obvious to you? | 22:05 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!