Instance Groups — Troubleshooting
Cannot Create a New Instance When the Group Uses Soft Anti Affinity
Symptom: Creating a new Instance fails when that Instance is assigned to an Instance Group with the Soft Anti Affinity policy.
Cause: The physical host server where the group is running no longer has sufficient resources (CPU, RAM) to host the new Instance. With Soft Anti Affinity, the system requires all Instances to reside on the same host server — if that server is full, there is no fallback.
Resolution:
- Delete Instances in the group that are no longer needed to free resources on that host server.
- Or switch to the Soft Affinity policy if you can accept that Instances may run on different servers — create a new group with the Soft Affinity policy and reassign the Instances.
The Instance I Want to Add Does Not Appear in the Selection List
Symptom: When creating a group or performing Attach, some Instances do not appear in the list.
Cause: That Instance already belongs to another Instance Group. Each Instance can only belong to one group at a time.
Resolution:
- Go to the Instance's current group.
- Edit the group to remove the Instance (Edit instance group → deselect the Instance → Save).
- Then add the Instance to the desired group.
Cannot Edit the Affinity Policy of a Group
Symptom: There is no option to change the Policy when editing a group.
Cause: The Affinity policy is a fixed attribute assigned at group creation time — the system does not allow changes after the group exists.
Resolution:
- Delete the current group (the Instances are not deleted).
- Create a new group with the desired policy.
- Reassign the Instances to the new group.
The Group Displays Fewer Instances Than Expected
Symptom: The Instances column in the list shows a count that does not match after adding Instances to the group.
Cause: The displayed data has not been refreshed.
Resolution: Press F5 or refresh the page to reload the list. If it is still incorrect, click the group name in the Instances column to see the accurate list.
Instances Still Exist After Deleting the Group
Symptom: After deleting an Instance Group, the Instances that previously belonged to the group still appear in the Instances list.
Cause: This is the expected behavior — deleting a group only removes the Affinity policy, not the Instances. The Instances continue to operate normally; they are simply no longer bound by the hardware placement policy.
Resolution: If you want to delete the Instances, go to Instances and delete each Instance individually.