-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.12.0
-
None
-
None
-
CLOUD Sprint 226
-
1
-
False
-
-
N/A
Description of problem:
When an error happens continuously, such as a failure to create a machine because of an invalid provider spec, the operator sits and does not report up to the end user that an issue is occurring. There are logs that reveal the errors but these do not show on the CPMS status.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create an Azure cluster with a CPMS 2. Ensure the subnet field and vnet fields are set in the providerSpec 3. Activate the CPMS, it should be healthy and running ok 4. Drop the vnet field from the providerSpec, observer errors in logs
Actual results:
Errors are logged but nothing shows on CPMS -o yaml
Expected results:
The error should be shown on the CPMS object if it happens continuously
Additional info: