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

Tenant Automator leaves idle service instances when error occured during subscription #95

Open
gekko68 opened this issue Jan 30, 2025 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@gekko68
Copy link

gekko68 commented Jan 30, 2025

Hi,
if during the provisioning of a new subscription an error occurs ( i.e. CF login not successful ) , some instance are not being shutdown. If u now enter the right information in the credential store and redo the subscription , the subscription is not successful again as there are two 'zombie' processes .

Image

if you end those manually, subcription works ...

The issue is in the error handling around : automator.js

Best, Mike

@alperdedeoglu
Copy link
Contributor

alperdedeoglu commented Jan 30, 2025

@gekko68, thank you very much for the effort. I completely understood the problem.
Rollback mechanism is not working as expected.

I would like to rework the automator.js in general. Will update here.

@alperdedeoglu alperdedeoglu self-assigned this Jan 30, 2025
@alperdedeoglu alperdedeoglu changed the title Subscription fails Tenant Automator leaves idle service instances when error occured during subscription Jan 30, 2025
@alperdedeoglu alperdedeoglu added the bug Something isn't working label Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants