Importing opscode-centos-6.4 fails with virtualbox error

[stevendanna]

The Chef provided opscode-centos-6.4 box no longer imports cleanly into virtual box:

sdanna@thrace ~/src/cookbooks/logrotate (master) > kitchen test centos
-----> Starting Kitchen (v1.2.1)
-----> Cleaning up any prior instances of <default-centos-64>
-----> Destroying <default-centos-64>...
       Finished destroying <default-centos-64> (0m0.00s).
-----> Testing <default-centos-64>
-----> Creating <default-centos-64>...
       Bringing machine 'default' up with 'virtualbox' provider...
       ==> default: Box 'opscode-centos-6.4' could not be found. Attempting to find and install...
           default: Box Provider: virtualbox
           default: Box Version: >= 0
       ==> default: Adding box 'opscode-centos-6.4' (v0) for provider: virtualbox
           default: Downloading: https://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_centos-6.4_chef-provisionerless.box
       ==> default: Successfully added box 'opscode-centos-6.4' (v0) for 'virtualbox'!
       ==> default: Importing base box 'opscode-centos-6.4'...
Progress: 90%>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Failed to complete #create action: [Expected process to exit with [0], but received '1'
---- Begin output of vagrant up --no-provision --provider=virtualbox ----
STDOUT: Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'opscode-centos-6.4' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Adding box 'opscode-centos-6.4' (v0) for provider: virtualbox
    default: Downloading: https://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_centos-6.4_chef-provisionerless.box
==> default: Successfully added box 'opscode-centos-6.4' (v0) for 'virtualbox'!
==> default: Importing base box 'opscode-centos-6.4'...
Progress: 90%
STDERR: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/Users/sdanna/.vagrant.d/boxes/opscode-centos-6.4/0/virtualbox/box.ovf", "--vsys", "0", "--vmname", "packer-virtualbox_1410420405175_19550", "--vsys", "0", "--unit", "8", "--disk", "/Users/sdanna/Virtua
lBox VMs/packer-virtualbox_1410420405175_19550/packer-virtualbox-disk1.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/sdanna/.vagrant.d/boxes/opscode-centos-6.4/0/virtualbox/box.ovf...
OK.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Appliance import failed
VBoxManage: error: <vbox:Machine> element in OVF contains a medium attachment for the disk image 6bd4390b-bd73-42a2-9526-0e34a8be8779 but the OVF describes no such image
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Appliance, interface IAppliance
VBoxManage: error: Context: "int handleImportAppliance(HandlerArg*)" at line 781 of file VBoxManageAppliance.cpp
---- End output of vagrant up --no-provision --provider=virtualbox ----
Ran vagrant up --no-provision --provider=virtualbox returned 1]
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

[juliandunn]

So generally the policy with Bento is that I maintain only the latest patchlevels of the OSes (in this case, CentOS 6.5) and older releases are unsupported. I'm sure this issue was probably a Packer bug at some point.