Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The status of a service that takes a long time to provision is not updated appropriately #53

Closed
vazirim opened this issue Sep 18, 2019 · 3 comments
Assignees

Comments

@vazirim
Copy link
Member

vazirim commented Sep 18, 2019

No description provided.

@vazirim vazirim self-assigned this Oct 8, 2019
@pdettori
Copy link
Member

pdettori commented Oct 8, 2019

Based on chat with @vazirim , seems like this applies to services that take a long time to provision, initially they are inactive (or failed in the case of db2), and it used to be that they would eventually become Online. But for some reason this is not happening (but the Binding works fine.

@pdettori
Copy link
Member

pdettori commented Oct 8, 2019

Example for a cloudant service showing 'inactive'

apiVersion: ibmcloud.ibm.com/v1alpha1
kind: Service
metadata:
   name: cloudanttest
spec:
   plan: lite
   serviceClass: cloudantnosqldb
---
apiVersion: ibmcloud.ibm.com/v1alpha1
kind: Binding
metadata:
   name: clbinding
spec:
   serviceName: cloudanttest

@vazirim vazirim changed the title db2 sample provisions correctly but status is failed The status of a service that takes a long time to provision is not updated appropriately Oct 8, 2019
@vazirim
Copy link
Member Author

vazirim commented Oct 9, 2019

Fixed in v0.1.2

@vazirim vazirim closed this as completed Oct 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants