ClusterStackRelease is ready even when OpenStackClusterStackRelease is not

Start by tracing how ClusterStackRelease evaluates the providerClusterStackRelease status, then compare that behavior with the OpenStackClusterStackRelease and OpenStackNodeImageRelease statuses shown in the kubectl output. Confirm the intended handling when the provider release is not ready, including ClusterClass lifecycle, and add or update coverage for the reported sequence.

/kind question

Question

I created clusterstack:

apiVersion: clusterstack.x-k8s.io/v1alpha1
kind: ClusterStack
metadata:
  name: clusterstack
  namespace: cluster
spec:
  provider: openstack
  name: ferrol
  kubernetesVersion: "1.27"
  channel: stable
  autoSubscribe: false
  providerRef:
    apiVersion: infrastructure.clusterstack.x-k8s.io/v1alpha1
    kind: OpenStackClusterStackReleaseTemplate
    name: cspotemplate
  versions:
  - v4

And every created resource has status ready true.

Then, for OpenStack, I deactivated one image so object OpenStackNodeImageRelease is ready false(because the image is not active and cannot be used):

$ k get osnir openstack-ferrol-1-27-ubuntu-capi-image-v1.27.8-v2 -n cluster
NAME                                                 READY   AGE   REASON                    MESSAGE
openstack-ferrol-1-27-ubuntu-capi-image-v1.27.8-v2   false   83m   IssueWithOpenStackImage   image status deactivated is unexpected

CSPO correctly set status also on OpenStackClusterStackRelease object:

$ k get oscsr openstack-ferrol-1-27-v4 -n cluster
NAME                       READY   AGE   REASON           MESSAGE
openstack-ferrol-1-27-v4   false   83m   ProcessOngoing   OpenStackNodeImageReleases not ready yet

Also, there is a nice message from CSO on ClusterStackRelase object:

$ k get clusterstackrelease openstack-ferrol-1-27-v4 -n cluster
NAME                       K8S VERSION   READY   AGE   REASON           MESSAGE
openstack-ferrol-1-27-v4   v1.27.8       true    84m   ProcessOngoing   providerClusterStackRelease not ready yet

But I expected also the READY status to be false here and the deletion of ClusterClass if it is not used.

$ k get clusterclass openstack-ferrol-1-27-v4 -n cluster 
NAME                       AGE
openstack-ferrol-1-27-v4   85m

So my question is: Is it meant to be?