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

Deleting a serviceinstance from OpenShift resulting in an indefinite loading screen #184

Open
david-martin opened this issue Oct 26, 2018 · 4 comments
Labels
bug Something isn't working - code or design

Comments

@david-martin
Copy link
Member

Steps to reproduce:

  • Login to the webapp
  • Wait for the loading screen to finish i.e. all services are available for the user
  • Go to OpenShift in a new tab, keeping the webapp open in original tab
  • Open the users project for walkthroughs i.e. <userid>-walkthrough-projects
  • Delete 1 of the Provisioned Services e.g. 3Scale
  • Notice the webapp in the original tab has switched to a loading screen
  • The loading screen never finishes

From my understanding (explanation from @aidenkeating), this happens because there is a watch on serviceinstances in the users walkthrough project.
When an expected serviceinstance doesn't exist yet for that user, the loading screen is shown.
There is logic in 'componentDidMount' that provisions any missing services.
However, as the component has already mounted in this case, it never gets called again.

@david-martin david-martin added the bug Something isn't working - code or design label Oct 26, 2018
@catrobson
Copy link

@david-martin @aidenkeating - is this still valid? Did we add some polling so this gets picked up?

@david-martin
Copy link
Member Author

I don't think this is valid anymore.
@aidenkeating I think the behavior if you delete a serviceinstance would be for the webapp to auto-create it again?

@aidenkeating
Copy link
Contributor

@catrobson @david-martin I tried this out from master and this issue is there

@tiffanynolan
Copy link
Collaborator

Checking in on this again to see if it's still an issue. If yes, then we should probably move it to Jira for better visibility and triaging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working - code or design
Projects
None yet
Development

No branches or pull requests

4 participants