Description
When filing a bug, please include the following headings if possible. Any example text in this template can be deleted.
Overview of the Issue
I'm seeing the same issue as #5113, namely that Packer is hanging at the command line when issuing any Packer command.
By looking at #5113 I notice that I do have a packer binary in my path even before adding the Hashicorp repo to my systems. Some investigation suggests that this alternative binary (/usr/sbin/packer) is provided by the cracklib-dicts package on Red Hat family systems.
Once I install Packer from the official Hashicorp repos (or simply by downloading the binary), it hangs whenever I try and issue any commands, as described.
Interestingly, the default $PATH on both Fedora and RHEL sets the order of precedence such that once Hashicorp Packer is installed (into /usr/bin/packer), that binary takes precedence over the one from cracklib (in /usr/sbin/packer) so I'm a little unsure why the commands are hanging. If anything, I'd expect installing Hashicorp Packer to break Cracklib Packer and not the other way around.
Reproduction Steps
Install Packer on a default Workstation install of either RHEL 8 or Fedora 34.
Packer version
Well packer version hangs at the command line, but:
╰─ rpm -q packer
packer-1.7.2-1.x86_64
Simplified Packer Buildfile
Any
(Can reproduce the problem without a buildfile even being present)
Operating system and Environment details
RHEL 8 / Fedora 34 confirmed
x86_64
Latest packer from official Hashicorp repositories
Fairly default Workstation install for both (which appear to pull in cracklib-dicts as a requirement for password enforcement)
Log Fragments and crash.log files
As with #5113, setting PACKER_LOG=1 does not produce any logs.