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.

Sign up for GitHub

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

Jump to bottom

[BUG] Worker records stuck in creating are never deleted on appliance #22644

Open

agrare opened this issue Aug 3, 2023 · 6 comments

Assignees

Labels

bug core/workers core stale

Member

agrare commented Aug 3, 2023

If a worker crashes early in startup it leaves a worker record in :status => "creating". This record is never cleaned up but counts as "starting" so new workers are not started.

The text was updated successfully, but these errors were encountered:

agrare added bug core/workers core labels

agrare self-assigned this

miq-bot added the stale label

Member

miq-bot commented Nov 6, 2023

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

agrare removed the stale label

Member Author

agrare commented Nov 6, 2023

agrare mentioned this issue

[WIP] Ensure workers and miq_worker rows match #22771

Open

miq-bot added the stale label

Member

miq-bot commented Feb 19, 2024

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

3 similar comments

Member

miq-bot commented May 20, 2024

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Member

miq-bot commented Aug 26, 2024

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Member

miq-bot commented Dec 9, 2024

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment