Check "fm alarm-list"
From: Fang, Liang A [liang.a.fang@intel.com]
Sent: Wednesday, May 15, 2019 12:14 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Does anybody know why controller stuck in the status "degraded"
Sent: Wednesday, May 15, 2019 12:14 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Does anybody know why controller stuck in the status "degraded"
Hi
I’m deploying an starlingx environment using the iso of 20190506, but after applied stx-openstack, the controller status always stuck in “degraded” or “online”
[wrsroot@controller-0 ~(keystone_admin)]$ kubectl get pod --namespace=openstack | grep cinder
The connection to the server 192.168.206.2:6443 was refused - did you specify the right host or port?
192.168.206.2 is the floating IP, right?
Anybody knows the root cause? Thanks.
My env is 2+2
2Controller: 4 cpu + 24G
2Worker: 4 cpu + 16G
Regards
Liang