Issue:
Jobs are intended to run in their closest region's instance/instance group. But they are running from other instances, as well.
Verifications:
- Instances in instance groups are enabled and not over capacity:
- AAP Controller login --> Admin (left menu twistie) --> Instance Groups (left menu) --> select/open instance group --> click Instances (tab)
--> confirm instances Enabled (under Actions column)
--> confirm CPU and RAM numbers are under limits (under Used Capacity column)
- Instance receptor service is healthy:
$ ssh myadminid@aapee2.mindwatering.net
$ sudo systemctl status receptor
< confirm Active:running status>
$ exit
- Instance Group Assignments are done in the Job Template (first priority), Inventory (second priority), and Organization (3rd/last priority). Verify that Job Template isn't overriding Inventory or Organization.
Note: If the Instance Group is not visible on the the Organization, Inventory, and Template, then the field isn't populated. Confirm by clicking the Edit button.
- AAP Controller login --> Access (left menu twistie) --> Organizations (left menu) --> select/open organization that is parent of template
--> confirm if Instance Groups field is populated
- AAP Controller login --> Resources (left menu twistie) --> Inventories (left menu) --> select/open inventory used by the template
--> confirm if Instance Groups field is populated
- AAP Controller login --> Resources (left menu twistie) --> Templates (left menu) --> select/open inventory used by the template
--> confirm if Instance Groups field is populated
--> confirm if Prompt on Launch is selected next to the field
Troubleshooting:
- If all three levels are empty, the controllers will just send to an available Instance group. Populate the Instance Group at the correct level.
- If the Prompt on Launch is set on the Template, but an instance group is not passed in the API call, then it will be like nothing was entered in the field. Make sure that the Instance Group is populated correctly.
In our case, someone had cleared the Prompt on Launch on the Template so jobs were not going where intended.
previous page
|