search

hashicorp / packer

Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
http://www.packer.io
Other
15.1k stars 3.33k forks source link

disable_stop_instance doesnt wait and stops the instance after 10 minutes #11740

Closed yossisp1972 closed 2 years ago

yossisp1972 commented 2 years ago

Hello,

I am trying to prevent an instance from stopping after the provisioner runs. But still even when setting disable_stop_instance=true for this source the instance still stops after 10 minutes or so and I get "Error waiting for instance to stop: ResourceNotReady: exceeded wait attempts" and it stops. I would expect packer to not try stopping the instance at all until i will stop it myself with code or manually. Thanks,

nywilken commented 2 years ago

Hello @yossisp1972 the timeout is actually the expected behavior. The disable_stop_instance argument is meant to prevent the Amazon builder from stopping the instance via the API because the shutdown process will be handled via a provisioner or configuration management step. There is a default timeout for all steps that will cancel the build if no action is taken, which is what you are running into here.

Could you share a little more detail on what you are trying to do?

If you you are looking to run some manual processes that you are not able to codify in Packer or requires some manual execution on the host. You way want to look into the the breakpoint provisioner, which allows you to pause the build and wait for the the user to manually continue the build.

nywilken commented 2 years ago

Hi there, I'm going to close this issue since there has been no activity on it. If you are still running into issues and suspect that it is a bug in Packer or the Amazon builder please open a new bug type issue.

github-actions[bot] commented 2 years ago

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.