Created attachment 1778289 [details] example Created attachment 1778289 [details] example Created attachment 1778289 [details] example Description of problem: I booted node with insufficient resources for OCS and OCP. The issue is that host status is Pending input instead of Insufficient. See attached example. note that issue resolved when clicking back and then next Version-Release number of selected component (if applicable): Staging 1.5.17 Steps to Reproduce: 1. boot node with insufficient resources 2. select Master role Actual results: host is Pending input Expected results: host is Insufficient
Created attachment 1778290 [details] example cont
The host status is retrieved from the backend, moving to the assisted-service.
jdzon it is going to be fixed with https://github.com/openshift/assisted-service/pull/1555 right?
@jdzon it is going to be fixed with https://github.com/openshift/assisted-service/pull/1555 right?
It is hard to tell; it doesn't look like it would fix it; https://github.com/openshift/assisted-service/pull/1555 will just introduce additional condition for Known->Insufficient host state transition.
Is this issue related to BZ #1954069 or is it something different?
I was able to reproduce the problem at staging and integration and I didn't see it at my environment built from the latest assisted-service. It's possible that it has been fixed by some change not deployed to the environments yet. @Lital: Could you, please, check if you are able to reproduce the problem at http://10.46.41.58:6008?
Sure, trying
Yes, it reproduces (http://10.46.41.58:6008/clusters/d2baaa40-d2ee-400d-90ca-7b5bd586e397). See attached example Steps: I have booted 3 masters, 2 workers, once they are Ready (Host Discovery stage), i marked OCS check-box. I guess this Pending-input is due to missing cidr set up?
Created attachment 1782362 [details] reproduce example
I was able to reproduce the problem on my cluster by creating it manually. Earlier, when the cluster was configured by assisted-test-infra it didn't show similar behavior. @Lital - the Pending Input status is caused, like you suggested, by missing machine CIDR configuration: cluster.validation_info: { "network": [ ... { "id": "machine-cidr-defined", "status": "failure", "message": "The Machine Network CIDR is undefined; setting the Machine Network CIDR initiates the VIPs DHCP lease allocation." }, ... ] } Can you, please, confirm that host in this case should be in the Insufficient state?
Right, when manually running it, then your unable to change network settings, because we are having insufficient hosts. When using test-infra, we update network settings using api. So on Host Discovery page, if host is insufficient then i expect host status to be Insufficient
The bug is caused by the UI logic [1] which identifies host status based on validations. We need to expand this to align with backend host status calculation logic. Moving to assisted-ui. [1] https://github.com/openshift-assisted/assisted-ui-lib/blob/d1f7733c3cc2323836eaae5a82ff0edf3a4e7747/src/components/clusterWizard/wizardTransition.ts#L223
This bug doesn't reproduce anymore, nor locally neither in staging. Following the discussion with Lital, we agreed to close this bug.