Packer: boot_wait ignored in 1.2.3 for QEMU provider

[sfinlayson-bt]

After upgrading to 1.2.3, boot_wait (even the default) is ignored for QEMU provider--I only use the QEMU provider, so I am not sure if it is affecting the other providers as well. This is running on Ubuntu 16.04.4 LTS x86_64. Logs of 1.2.2 and 1.2.3 processing the same config: https://gist.github.com/sfinlayson-bt/44adaef2ff50804c7d8ed5b0a80c3ac4

[mwhooker]

Thanks, will take a look

[jen20]

@mwhooker I'm looking into this at the moment also.

[mwhooker]

@jen20 I'm guessing this was probably introduced in #6129

[jen20]

@mwhooker I think it might be simpler than that, I'm running a test now.

[jen20]

Well, it's not the simple fix I was hoping for. Doing further investigation now.

[jen20]

@mwhooker The issue is that RawBootWait is not being parsed correctly any more - it used to accept "2m" to mean "2 minutes", or "45s" to mean "45 seconds". config.BootConfig.BootWait is returning 0 regardless of input value in the QEMU builder at the moment, hence no delay.

[mwhooker]

@sfinlayson-bt Thanks again for the report. This will be fixed in the next release. In the meantime, I think you should be able to add a <wait20s> at the beginning of your boot command to get the same effect, though I don't know if the VNC server needs time to start.

[jen20]

That fixes it - didn't think of adding <wait20> though!

[hashibot[bot]]

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.