-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
CloudBees Jenkins Enterprise 2.32.3.2-rolling,
Amazon EC2 plugin 1.36
When Jenkins creates a new EC2 agent, it logins in through ssh and runs slave.jar before cloud-init has finished running the commands in User Data. This can cause builds to fail if they try to perform actions that require setup done by cloud-init. Jenkins should wait until cloud-init is finished before allowing the agent to be used for a build.
- duplicates
-
JENKINS-43064 ec2computerlauncher needs instance status as well as state
-
- Open
-