要約

All elastic agents that are started using a specific custom Windows AMI remain in a pending state.

環境

Bamboo using Elastic Agents with custom Windows AMIs

診断

After starting a new elastic agent, you can see on the  > Overview > Instances menu that the agent status remains pending even after a long time and if you access the EC2 instance, you don't see the agent service running on task manager.

原因

This might indicate that for some reason the Task Scheduler is not being able to start the agent service along with the EC2 instance.

ソリューション

The solution will depend on what's preventing the C:\opt\bamboo-elastic-agent\bin\bamboo-elastic-agent.bat executable to get executed by the Task Scheduler. You can access the EC2 instance and go to Start > Windows Administrative Tools > Task Scheduler, select the ElasticBambooAgent task then click on the "history" tab to get more details about the error.

Known problem 1 - A Wrong password is being used by the ElasticBambooAgent task

If you change the password for the OS user account created while going through the steps from Creating a custom elastic image guide after adding the task to the Task Scheduler. In this scenario, the scheduled task added while creating the AMI will still be using the old password and you'll see the following message at the Task Scheduler history log:

Additional Data: Error Value: 2147943726

If that's the case all you need to do is:

1. Go to properties of task
2. Under the General tab, click on "Change User or Group..."
3. Enter the username in the field "Enter the object name to select" and hit save
4. This will ask for Authentication, provide your credentials
5. Create a new AMI