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

Ensure that CaaS that failed to start are removed after the sovity Portal timeout #202

Closed
kamilczaja opened this issue May 6, 2024 · 1 comment
Labels
area/backend kind/enhancement New feature or request

Comments

@kamilczaja
Copy link
Collaborator

Enhancement

Description

Connectors that are still PROVISIONING after 15 minutes are automatically removed in the sovity Portal. Since status update requests will fail after that happens, there is no more hope that the connector will start and should be removed from AP.

@kamilczaja kamilczaja added kind/enhancement New feature or request area/backend labels May 6, 2024
@kamilczaja
Copy link
Collaborator Author

Contrary to my initial analysis, status requests to the CaaS portal do not fail when the connector is removed there. The reported status is NOT_FOUND which is a valid status in the AP. Since this does not cause any issues and even prevents the connector from disappearing in thin air, I'm opting for leaving it as is and requiring the user to manually remove the faulty connector.

Closed as not planned.

@kamilczaja kamilczaja closed this as not planned Won't fix, can't repro, duplicate, stale Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backend kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant