Bug 2141708 - Readiness probe of ocs-osd-controller-manager pod fails with statuscode: 503
Summary: Readiness probe of ocs-osd-controller-manager pod fails with statuscode: 503
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-managed-service
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Leela Venkaiah Gangavarapu
QA Contact: Filip Balák
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-10 15:12 UTC by Filip Balák
Modified: 2023-08-09 17:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-14 15:29:22 UTC
Embargoed:

Attachments (Terms of Use)

Description Filip Balák 2022-11-10 15:12:47 UTC 
Description of problem:
Pod ocs-osd-controller-manager fails to reach ready state during provider deployment. In events are following messages:

Generated from kubelet on ip-10-0-170-75.ec2.internal
7 times in the last 2 hours
Readiness probe failed: HTTP probe failed with statuscode: 503

Generated from kubelet on ip-10-0-170-75.ec2.internal
1017 times in the last 2 hours
Readiness probe error: HTTP probe failed with statuscode: 503 body: 

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

How reproducible:
1/1

Steps to Reproduce:
1.Install odf ms deployer with dev addon:
rosa create service --type ocs-provider-dev --name <name> --machine-cidr 10.0.0.0/16 --size 4 --onboarding-validation-key <key> --subnet-ids <subnets> --region us-east-1

Actual results:
Installation of the addon fails with message `'ocs-osd-deployer' : 'InstallCheckFailed'`

Expected results:
Installation passes

Additional info:
Comment 3 Leela Venkaiah Gangavarapu 2022-11-28 06:10:45 UTC 
- I don't think this is seen anymore, pls update otherwise.
Comment 7 Filip Balák 2023-02-06 10:20:05 UTC 
This no longer happens with deployer 2.0.10 --> VERIFIED
Comment 8 Ritesh Chikatwar 2023-03-14 15:29:22 UTC 
Closing this bug as fixed in v2.0.10 and tested by QE.
Note You need to log in before you can comment on or make changes to this bug.