[Starlingx-discuss] Does anybody know why controller stuck in the status "degraded"

Poncea, Ovidiu Ovidiu.Poncea at windriver.com
Wed May 15 09:37:17 UTC 2019

Check "fm alarm-list"

From: Fang, Liang A [liang.a.fang at intel.com]
Sent: Wednesday, May 15, 2019 12:14 PM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] Does anybody know why controller stuck in the status "degraded"


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”
[cid:image001.png at 01D50B40.EE7E6150]
[wrsroot at controller-0 ~(keystone_admin)]$ kubectl get pod --namespace=openstack | grep cinder
The connection to the server was refused - did you specify the right host or port? is the floating IP, right?

Anybody knows the root cause? Thanks.

My env is 2+2
2Controller: 4 cpu + 24G
2Worker: 4 cpu + 16G

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190515/4d6ee641/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 18735 bytes
Desc: image001.png
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190515/4d6ee641/attachment-0001.png>

More information about the Starlingx-discuss mailing list