Bug 1662282 - Status of instance should not be Ready while pod of application didn't launch up
Summary: Status of instance should not be Ready while pod of application didn't launch up
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.1.0
Assignee: Jesus M. Rodriguez
QA Contact: Zhang Cheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-27 10:02 UTC by Zhang Cheng
Modified: 2019-04-11 02:24 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-10 19:52:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Jesus M. Rodriguez 2019-03-29 20:09:20 UTC 
Same underlying issue from BZ 1692637.

*** This bug has been marked as a duplicate of bug 1692637 ***
Comment 3 Jesus M. Rodriguez 2019-04-09 18:14:33 UTC 
Originally we thought this was a duplicate of 1692637. After re-reading the bugzilla, I believe it is indeed a different problem. Investigating to see if this is a broker issue or an APB issue.
Comment 4 Jesus M. Rodriguez 2019-04-10 19:52:25 UTC 
After further investigation, this is not really a bug. I've seen the issue where the pod is in ContainerCreating and the state is Provisioning. Then still in ContainerCreating then the state is marked as Ready, but when I requery the pod, it is now Ready. There has always been a slight disconnect between APBs and Service Catalog serviceinstance which required a refactoring which we won't be doing, as most of the issues were fixed by using an Operator instead of an APB.
Comment 5 Zhang Cheng 2019-04-11 02:24:33 UTC 
Jesus, That is OKay for me. Thanks for your clarification.
Note You need to log in before you can comment on or make changes to this bug.