Bug 1797112 - rook-ceph-mon-a-canary pod doesn't come up: default-scheduler pod has unbound immediate PersistentVolumeClaims (repeated 3 times)
Summary: rook-ceph-mon-a-canary pod doesn't come up: default-scheduler pod has unbo...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: rook
Version: 4.3
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Travis Nielsen
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-31 22:28 UTC by Petr Balogh
Modified: 2020-02-04 15:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-04 15:46:08 UTC
Embargoed:

Attachments (Terms of Use)

Comment 1 Sébastien Han 2020-02-03 09:13:04 UTC 
Please stop using the "installation" component.
Comment 2 Petr Balogh 2020-02-03 13:35:31 UTC 
This happening during installation of OCS and blocking whole deployment hence I used the installation component when I found it in the list of the components. Sorry for confusing.

Is there somewhere list of the components and for such issues we should use it?

For what purpose is installation component @leseb?
Comment 3 Sébastien Han 2020-02-03 14:10:09 UTC 
Hi Petr,

It's hard to tell what the purpose of that component is but recently we all agreed it was confusing, so we should stop using it.
Bug related to installation should either go on Rook or ocs-operator.
Comment 4 Travis Nielsen 2020-02-04 15:17:57 UTC 
@Petr, we aren't able to repro this. Have you seen it again? Sounds like QE is unblocked now since Seb re-synced on Monday.
Comment 5 Petr Balogh 2020-02-04 15:28:24 UTC 
With the latest build we haven't seen this issue again.
Comment 6 Sébastien Han 2020-02-04 15:46:08 UTC 
Thanks Petr, closing then.
Note You need to log in before you can comment on or make changes to this bug.