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

want sdcadm delete #108

Open
jbarfield opened this issue Oct 13, 2023 · 0 comments
Open

want sdcadm delete #108

jbarfield opened this issue Oct 13, 2023 · 0 comments

Comments

@jbarfield
Copy link

jbarfield commented Oct 13, 2023

When creating additional services like papi, workflow, portolan, etc, sdcadm create workflow -s <UUID> is used to create an instance. If you create a 2nd and third instance, then migrate to new secondary headnodes, create a 4th and 5th instanecs, then decommission the old compute nodes, the instances remain orphaned in sapi. If by chance you subsequently run sdcadm experimental fix-core-resolvers the command fails with non-existent instances. You then must manually delete the instances from sapi with sdc-sapi /instances/<MISSING_VM_UUID> -X DELETE in order to get rid of the non-existent instance to get the resolvers to properly fix. sdcadm delete workflow1 and sdcadm delete workflow2 ideally should remove the instances from sapi in their entirety so that sdc is not left with orphaned core instances. Alternatively an sdcadm clean command could also be an ideal command to remove all orphaned instances from sapi as well.

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

1 participant