Folks,

I have made very good progress, now I can see CAPI started building workload cluster but when I noticed its stuck in CREATE_IN_PROGRESS for long time then I hope into workload master node and noticed following error spitting up in logs 

Look like some cinder-csi related error (I am using 1.27.x image to build cluster) 

38u-xpvv4-fkp9f kubelet[1815]: I1219 21:30:22.631478 1815 scope.go:115] "RemoveContainer" containerID="00c2df6cf4e1e4cac15d0d2698fbe19adedb7c5b49c7102c99e3b273ef57335b" Dec 19 21:30:22 kube-8f38u-xpvv4-fkp9f kubelet[1815]: E1219 21:30:22.632141 1815 pod_workers.go:1294] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"openstack-cloud-controller-manager\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=openstack-cloud-controller-manager pod=openstack-cloud-controller-manager-fhnhj_kube-system(7c1162c6-51d0-4207-b462-97e2536d302d)\"" pod="kube-system/openstack-cloud-controller-manager-fhnhj" podUID=7c1162c6-51d0-4207-b462-97e2536d302d Dec 19 21:30:26 kube-8f38u-xpvv4-fkp9f kubelet[1815]: I1219 21:30:26.631784 1815 scope.go:115] "RemoveContainer" containerID="7f60974870b0eb472549de51777ea6660db2592687eafa05f2dcbd6db25bdfb1" Dec 19 21:30:26 kube-8f38u-xpvv4-fkp9f kubelet[1815]: E1219 21:30:26.632424 1815 pod_workers.go:1294] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"cinder-csi-plugin\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=cinder-csi-plugin pod=csi-cinder-nodeplugin-9fjwp_kube-system(0b8f67de-fdf2-4996-aab4-5998da795434)\"" pod="kube-system/csi-cinder-nodeplugin-9fjwp" podUID=0b8f67de-fdf2-4996-aab4-5998da795434


root@kube-8f38u-xpvv4-fkp9f:/etc/kubernetes# kubectl get deployments -A
NAMESPACE     NAME                          READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   calico-kube-controllers       0/1     1            0           23m
kube-system   coredns                       0/2     2            0           23m
kube-system   csi-cinder-controllerplugin   0/1     1            0           23m

root@kube-8f38u-xpvv4-fkp9f:/etc/kubernetes# kubectl get nodes
NAME                                    STATUS   ROLES           AGE   VERSION
kube-8f38u-default-worker-zpg2j-9w5pk   Ready    <none>          22m   v1.27.4
kube-8f38u-default-worker-zpg2j-vp56f   Ready    <none>          22m   v1.27.4
kube-8f38u-xpvv4-fkp9f                  Ready    control-plane   24m   v1.27.4


What else should I check or look for? 


On Mon, Dec 18, 2023 at 7:39 PM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com> wrote:
Oh. 
Why I didn't see it before, some months ago, is very basic. It has changed, I am happy with this now. 

But It will be much better if we:
- separate topic: ask and answer, tutorial... 
- improve mail size limit. When I reply with many previous loops. I need approment from mods
- allow attach pictures (size limit).

I get what you are saying. Thank you for your explanation. 


Nguyen Huu Khoi


On Tue, Dec 19, 2023 at 5:57 AM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2023-12-19 04:31:33 +0700 (+0700), Nguyễn Hữu Khôi wrote:
[...]
> I think Openstack still need an OFFICIAL Forum.I talked about this
> some months ago. New users cannot search problems via email, a
> very hard approach.
[...]

https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/
does function as a real web forum now. It has list-specific and
site-wide keyword search indexing updated in real time, and you can
read and post to it from a browser without using any E-mail client
if you prefer that kind of interaction. It even has upvote/downvote
buttons for "liking" posts, read/unread tracking, favorites,
profiles... I'm sure it's not perfect, but it's where most of the
knowledgeable OpenStack people are reading and responding.

We could create a separate web-only forum where people aren't
allowed to treat it as a mailing list, and then anyone asking
questions there will get answers just from people who are paying
attention to that forum. We tried it in the past (three different
times in the past 13 years), but each time we ended up with a
useless forum full of questions nobody was answering. It was the
easiest place for newcomers to ask questions, however people with
experience in the software had no reason to actually pay attention
and answer anything in it. The end result was a much *worse* and far
more frustrating user experience, because a forum can have all the
fancy bells and whistles but if you never get any (or any useful)
answers then what's the point?
--
Jeremy Stanley