packer-build | Packer Automated VM Image and Vagrant Box Builds

It hangs because you're doing the wrong thing. You do not want to run the OpenVAS service when provisioning an image, you only want to install it.

The service should only be run when a machine using the image is started. In this case, you probably want to use systemd to start the service. I haven't installed the package myself, but I've checked online and it looks like it installs the requisite systemd configuration for you automatically, but it is probably best to check further by creating an instance of your image and seeing if the server is running. Based on your configuration above, I'd guess that those flags are the defaults anyway and so are probably not necessary. If they're not and you're really attached to them, then there is probably somewhere you can put a configuration file that'll be noticed by the system at startup, and failing that your provisioning script can use sed to put them in the systemd configuration files.

Solution: don't run OpenVAS during provisioning.

It turns out I was using the wrong security_group for my Packer builder. It works on my machine, but Jenkins slaves use a different security group. Once I set it to that SG, it worked.

That is weird - the two issues should not be connected. Even weirder is the fact that it works, when checking out the code twice. You have an actions.yml in your packer-build folder?

Nevertheless, possible workaround: Use the actions/upload Action to persist your file.

Like this: