Currently, DBaaS Operator simply copies the status of the corresponding provider connection and inventory CRs (which are updated by the provider operators) as the status of the DBaaSConnection and DBaaSInventory CRs. As a result, users won't know the processing issues of these CRs if such issues happen in the DBaaS Operator itself.

This task is to enhance the reconciliation logic so that the operator sets the appropriate status for the DBaaSConnection and DBaaSInventory CRs. Typical cases include:

1) There is no tenant configured for the DBaaSInventory CR in the namespace

2) There is no valid provider found for the DBaaSInventory CR

3) The inventory for the DBaaSConnection CR does not exist

4) The provider of the inventory for the DBaaSConnection CR is not valid

 5) The inventory for the DBaaSConnection CR is not ready, ie, service discovery has not been completed successfully