Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2040438

Summary:	ODF4.10 UI deployment, AWS_RHEL and VMWare_RHEL, Worker nodes do not appear in the "select nodes" list
Product:	OpenShift Container Platform	Reporter:	Oded <oviner>
Component:	Machine Config Operator	Assignee:	ravig <rgudimet>
Machine Config Operator sub component:	Machine Config Operator	QA Contact:	Rio Liu <rioliu>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	urgent
Priority:	unspecified	CC:	amagrawa, aos-bugs, dahorak, hnallurv, jerzhang, mkrejci, nberry, nthomas, rgudimet, sagrawal, skumari, ypersky
Version:	4.10	Keywords:	Automation, Reopened
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-23 14:36:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Oded 2022-01-13 17:13:40 UTC

Description of problem:
The worker nodes do not appear in the "select nodes" list

Version-Release number of selected component (if applicable):
OCP Version:4.10.0-0.nightly-2022-01-11-065245
ODF Version:4.10.0-79
platform: 'aws'
deployment_type: 'upi'
worker_replicas: 3
master_replicas: 3
rhel_worker_ami: 'ami-073251e3a0e36cebb' # RHEL7.7 as of now
rhel_worker_instance_type: 'm5.4xlarge'

https://github.com/red-hat-storage/ocs-ci/blob/master/conf/deployment/aws/upi_3az_rhel7_3m_3w.yaml

How reproducible:


Steps to Reproduce:
1.Install ODF4.10.0 Opertor via UI
2.Create storage System via UI
3.On "Capacity and nodes" page-> The worker nodes do not appear in the "select nodes" list

http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-011au3r33-d/j-011au3r33-d_20220113T124836/logs/screenshots_ui_1642078431/test_deployment/2022-01-13T13-57-06.381123.png

Must-Gather OCS+OCP:
http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-011au3r33-d/j-011au3r33-d_20220113T124836/logs/failed_testcase_ocs_logs_1642078431/deployment_ocs_logs/

job:
https://ocs4-jenkins-csb-odf-qe.apps.ocp-c1.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/2906/

Actual results:


Expected results:


Additional info:
This issue does not reconstructed in AWS_RHCOS,

http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/jnk-pr5282-b2147/jnk-pr5282-b2147_20220111T231800/logs/screenshots_ui_1641943328/test_deployment/2022-01-11T23-58-54.001025.png

Comment 5 Yu Qi Zhang 2022-01-19 18:54:42 UTC

May be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2035005. Assigning to ravi.

Comment 6 Afreen 2022-02-22 05:46:43 UTC

*** Bug 2056695 has been marked as a duplicate of this bug. ***

Comment 9 ravig 2022-05-02 19:10:34 UTC

https://bugzilla.redhat.com/show_bug.cgi?id=2076308 is in verified state. If 4.10.x with the fix from https://github.com/openshift/machine-config-operator/pull/3091 doesn't solve the problem mentioned at https://bugzilla.redhat.com/show_bug.cgi?id=2040438#c4, then perhaps the issue is elsewhere. I am wondering about the workflow of ODF. Does a pod need to be deployed during upgrade? If yes does it need to land onto non-upgraded node or upgraded node.

Comment 10 Sinny Kumari 2022-05-04 08:05:28 UTC

Hello Aman, Neha and Oded,

Since severity of the bug is marked as urgent, can you please check if latest 4.10 nightly fixes the issue like mentioned in comments#9?

Thanks

Comment 11 Sinny Kumari 2022-05-04 16:49:20 UTC

We think that this issue should get fixed by bug https://bugzilla.redhat.com/show_bug.cgi?id=2076308 . If this is not the case, we will re-look into the issue and reevaluate blocker flag.

Comment 14 Red Hat Bugzilla 2023-09-15 01:51:01 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days