Le déploiement du contrôle plan est bloqué avec ceci
oc get openstackcontrolplane.core.openstack.org/openstack-control-plane NAME STATUS MESSAGEopenstack-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-operators2024-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 keystoneoc logs keystone-operator-controller-manager-75d9b8dc6b-pg8tx -n openstack-operators | grep -v INFO2024-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 visiblementoc get svc keystone-internalNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEkeystone-internal LoadBalancer 172.30.116.131 <pending> 5000:32682/TCP 23m
On vérifie le loadbalanceroc get pod -n metallb-systemNo resources found in metallb-system namespace.
Il n'est pas installé, il faut donc installé l'operateur et créé un metalLB
Comments