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.
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.
- Still awaiting a confirmation whether this is hit or not
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/
As per Comment4 Closing the bug as it's fixed in 2.0.11-1 and verified by QA.