Déploiement de RHOSO 18 bloqué en in progress

By cyril, 22 November, 2024

Le déploiement du contrôle plan est bloqué avec ceci

oc get openstackcontrolplane.core.openstack.org/openstack-control-plane 
NAME                      STATUS   MESSAGE
openstack-control-plane   False    OpenStackControlPlane PlacementAPI in progress

Alors on regarde l'opérateur du service 

oc logs placement-operator-controller-manager-5c548c5579-sqprw -n openstack-operators
2024-11-22T13:07:51.943Z        ERROR   Reconciler error        {"controller": "placementapi", "controllerGroup": "placement.openstack.org", "controllerKind": "PlacementAPI", "PlacementAPI": {"name":"placement","namespace":"openstack"}, "namespace": "openstack", "name": "placement", "reconcileID": "73b4b805-4004-4785-90b3-ebc9da939211", "error": "internal endpoint not found"}

Donc on vérifie l'opérateur keystone
oc logs keystone-operator-controller-manager-75d9b8dc6b-pg8tx -n openstack-operators | grep -v INFO
2024-11-22T12:57:25Z    ERROR   Reconciler error        {"controller": "keystoneapi", "controllerGroup": "keystone.openstack.org", "controllerKind": "KeystoneAPI", "KeystoneAPI": {"name":"keystone","namespace":"openstack"}, "namespace": 
"openstack", "name": "keystone", "reconcileID": "b6c2bbab-7d30-4d78-aa47-30955b510838", "error": "keystone-internal LoadBalancer IP still pending"}

Problème de service visiblement
oc get svc keystone-internal
NAME                TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
keystone-internal   LoadBalancer   172.30.116.131   <pending>     5000:32682/TCP   23m

On vérifie le loadbalancer
oc get pod -n metallb-system
No resources found in metallb-system namespace.
 

Il n'est pas installé, il faut donc installé l'operateur et créé un metalLB

https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/networking/load-balancing-with-metallb?extIdCarryOver=true&sc_cid=7015Y0000048JF5QAM#metallb-operator-install

 

Comments