Bug 2132006

Summary:	Deployment of Managed Service cluster with size 20 fails
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Filip Balák <fbalak>
Component:	odf-managed-service	Assignee:	Leela Venkaiah Gangavarapu <lgangava>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jilju Joy <jijoy>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	aeyal, ebenahar, lgangava, ocs-bugs, odf-bz-bot, rchikatw
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.0.11-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-23 06:53:56 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 Filip Balák 2022-10-04 12:56:30 UTC

Description of problem:
Cluster with dev addon that contains changes in topology related to ODFMS-55 can not finish ODF addon installation. Intallation is turned after a while from Installing to Failed state with description: 'ocs-osd-deployer' : 'InstallCheckFailed'

Version-Release number of selected component (if applicable):
ocs-osd-deployer.v2.0.8

How reproducible:
1/1

Steps to Reproduce:
1. Install provider:
rosa create service --type ocs-provider-dev --name fbalak-pr --machine-cidr 10.0.0.0/16 --size 20 --onboarding-validation-key <key> --subnet-ids <subnet-ids> --region us-east-1
2. Wait until installation finishes.

Actual results:
Installation of the odf addon fails with description: 'ocs-osd-deployer' : 'InstallCheckFailed'

Expected results:
Installation succeeds.

Additional info:
The cluster was deployed with dev addon that contains changes to epic ODFMS-55.

Comment 2 Leela Venkaiah Gangavarapu 2022-10-10 11:15:11 UTC

hi,

- from the must-gather I can see the reason for the installation failure is due to unscheduled monitors
- however, at a previous time around (11:38 from events) I can see all monitors were scheduled and running fine
- by 13:40, all monitors were killed and when they were coming up again they went into unscheduled state and the installation stuck
- if possible, when you repeat the operation and this issue is hit, pls let me have access to the cluster
- I believe the nodes were getting upgraded during this time, however this doesn't explain why monitors failed to schedule in a later time

Thanks,
Leela.

Comment 3 Leela Venkaiah Gangavarapu 2022-10-27 13:38:29 UTC

- Still awaiting a confirmation whether this is hit or not

Comment 4 Jilju Joy 2022-11-24 05:01:11 UTC

Deployment of provider cluster with size 20 was tested with dev addon which contains the changes in topology related to ODFMS-55. Deployment was successful.
Adding must-gather logs for reference - http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/jijoy-n22-pr/jijoy-n22-pr_20221122T075048/logs/testcases_1669119379/

Comment 8 Ritesh Chikatwar 2023-01-23 08:49:22 UTC

As per Comment4 Closing the bug as it's fixed in 2.0.11-1 and verified by QA.