Description of problem: when BareMetalPlatform=false in HCO cr. HCO operator is not progressing. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Have the logs from the operator?
Created attachment 1631256 [details] Step 1. Create ns in UI
Created attachment 1631257 [details] Step2. ns created
Created attachment 1631258 [details] Step 3. In operatorHub, locate HCO, click Install, pick 2.1 version and ns
Created attachment 1631259 [details] Step 4. Subscription is created
Created attachment 1631260 [details] Step 5. Create HCO CR, remove extra quotes
Created attachment 1631261 [details] Step 6. HCO CR created
Created attachment 1631262 [details] Step 7. Wath pods starting to run in UI
Created attachment 1631263 [details] Step 8. Watch pods starting to run in CLI
Created attachment 1631264 [details] Step 9. All pods are up and running in CLI
Created attachment 1631265 [details] Step 10. All pods are running in UI
Created attachment 1631266 [details] Step 11. The last one....
Created attachment 1632154 [details] hco operator log when BareMetalPlatform: "false"
(In reply to Ryan Hallisey from comment #1) > Have the logs from the operator? See attached log hco_operator.log.gz
Ryan, removing the quotes/double-quotes from (BareMetalPlatform: 'false'), seems to solve the issue.. AFAIK, it's ok to quote string values in yaml. WDYT
I guess it's a boolean value, so the bug is in UI composing the cr. Irina, pls reopen the bug (with different focus?).
>> AFAIK, it's ok to quote string values in yaml. Yes, if one needs to * escape a special char * force a string value instead of the numeric one, or * with yes/no to enforce string class instead of true/false class and a couple of other cases. Otherwise, generally, they are not used. It's in YAML cookbook. As far as I understand JSON parse takes quoted "false" as a string value, instead of true/false class. Anyway, The release and installation docs contain the note about quotas: https://github.com/openshift/openshift-docs/pull/17773 The issue itself has been fixed, i.e. the corresponding PR has been merged, it will be in 2.1.1 release: https://github.com/openshift/openshift-docs/pull/17773
ops, the last link should be: https://github.com/kubevirt/hyperconverged-cluster-operator/pull/332
*** This bug has been marked as a duplicate of bug 1767167 ***