-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
?
-
?
-
?
-
?
-
None
-
-
-
Moderate
OpenStackDataPlaneNodeSet does not report SetupReady status in short output, see below:
[root@jumphost 06_data_plane]# oc get -f 06_openstackdataplanenodeset.yaml -o yaml | grep SetupReady -C5
type: ServiceAccountReady
- lastTransitionTime: "2024-09-09T13:39:17Z"
message: Setup complete
reason: Ready
status: "True"
type: SetupReady
configHash: nf4hd8hc6h99h89hc7h5d5hd7h684h5d6h5d6hddh64h574h67bh549h68bh57ch5f6h6fhfh699h587h59bh5fdh96h68bh5dchdfh577h567h577q
ctlplaneSearchDomain: ctlplane.example.com
dnsClusterAddresses:
- 172.30.145.88
observedGeneration: 1
[root@jumphost 06_data_plane]# oc wait openstackdataplanenodeset openstack-data-plane --for condition=SetupReady --timeout=10m
openstackdataplanenodeset.dataplane.openstack.org/openstack-data-plane condition met
[root@jumphost 06_data_plane]# oc get -f 06_openstackdataplanenodeset.yaml
NAME STATUS MESSAGE
openstack-data-plane False Deployment not started
So when a user just checks the short output, it looks like nothing happened. Make sure to report SetupReady in the short output as well so that admins get a clear signal that they can continue with the installation (other than having to do -o yaml or the wait command)
