Re: [packer] Re: packer fails after upgrade to ESX 6.5

2017-03-20 Thread Steven Langlois
I changed the guest_os_type to "centos7-64" instead of "centos-64" and it is now working on both 0.12.3 and 0.10.2. On Monday, March 20, 2017 at 4:28:33 PM UTC-4, Steven Langlois wrote: > > Same issue with 0.12.3. > > >>> -- This mailing list is governed under the HashiCorp Community Guidelines

Re: [packer] Hyper-V Builder change boot order on reboot?

2017-03-20 Thread nick.hankins via Packer
That worked, thank you! On Monday, March 20, 2017 at 1:12:50 PM UTC-7, Alvaro Miranda Aguilera wrote: > > on real computers the default is like this. > > boot from hdd > boot from dvd > > in that way the 2nd time will boot from the hdd. > > What you can try is eject the dvd from the kickstart > >

Re: [packer] Re: packer 1.0.0-rc1 released

2017-03-20 Thread Dan Linder
I've added a comment - I can produce a minimal JSON file and steps to reproduce this in a lab if necessary. DanL On Mon, Mar 20, 2017 at 3:35 PM, Matthew Hooker wrote: > Thanks for the report, Dan. I don't think we have an issue about this. > Created one here: https://github.com/mitchellh/packe

[packer] Re: packer 1.0.0-rc1 released

2017-03-20 Thread Matthew Hooker
Thanks for the report, Dan. I don't think we have an issue about this. Created one here: https://github.com/mitchellh/packer/issues/4689 If you wanted to reply to that, it would help in case we need to ask questions when we look into it. On Monday, March 20, 2017 at 12:22:45 PM UTC-7, Dan Linde

Re: [packer] Re: packer fails after upgrade to ESX 6.5

2017-03-20 Thread Steven Langlois
Same issue with 0.12.3. This is my vmware.sh: #!/bin/sh -eux #case "$PACKER_BUILDER_TYPE" in #vmware-iso|vmware-vmx) #rpm -i /TMP/rpms/open-vm-tools-9.10.2-4.el7.x86_64.rpm; #mkdir /mnt/hgfs; # echo "platform specific vmware.sh executed"; #esac case "$PACKER_BUILDER_TYPE" in vmware-iso

Re: [packer] Hyper-V Builder change boot order on reboot?

2017-03-20 Thread Alvaro Miranda Aguilera
on real computers the default is like this. boot from hdd boot from dvd in that way the 2nd time will boot from the hdd. What you can try is eject the dvd from the kickstart replace reboot with: reboot --eject

Re: [packer] Re: packer fails after upgrade to ESX 6.5

2017-03-20 Thread Rickard von Essen
Upgrade packer to 0.12.3 and report back again. On Mar 20, 2017 6:38 PM, "Steven Langlois" wrote: > Sorry, should have mentioned that I am running packer 0.10.2. > > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.h

[packer] Re: packer 1.0.0-rc1 released

2017-03-20 Thread Dan Linder
I found a but that was also in 0.12.3 but has continued into -rc1. On Windows 10, building a RHEL 6 using the "ansible-local" provisioner like this: { "playbook_file": "ansible/main.yml", "role_paths": [ "./ansible/" ], "type": "ansible-local" }, The bui

[packer] Hyper-V Builder change boot order on reboot?

2017-03-20 Thread nick.hankins via Packer
Building CentOS box with hyperv as the builder, everything is working perfectly EXCEPT that when the VM reboots after installing from ISO, it boots right back into the ISO since that is listed first in the boot order. Is there a way to make sure it boots from the hard drive on the second boot

[packer] Re: packer fails after upgrade to ESX 6.5

2017-03-20 Thread Steven Langlois
Sorry, should have mentioned that I am running packer 0.10.2. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Is

[packer] packer fails after upgrade to ESX 6.5

2017-03-20 Thread Steven Langlois
We upgraded our ESX server from 5.5 to 6.5 over the weekend and now the packer script is failing without any changes to the script. It is complaining not being able to mount the VMware tools ISO and to check the guest_os_type. Packer is running on a VM on the ESX server but I also tried runnin

Re: [packer] The easiest way to build a windows version of Packer for testing

2017-03-20 Thread Patrick van der Velde
Woot! You're right. I have a build. Thanks heaps On Monday, 20 March 2017 22:46:41 UTC+13, Rickard von Essen wrote: > > Sorry that's expected behaviour, it actually work but our dev target tries > to copy the binary from pkg/linux_amd64 to $GOPATH/bin/ to put it on the > path, but it doesn

Re: [packer] The easiest way to build a windows version of Packer for testing

2017-03-20 Thread Rickard von Essen
Sorry that's expected behaviour, it actually work but our dev target tries to copy the binary from pkg/linux_amd64 to $GOPATH/bin/ to put it on the path, but it doesn't adheres to XC_ARCH and XC_OS. So you can just ignore that error. You should have the windows binary, pkg/windows_amd64/packer.exe

Re: [packer] The easiest way to build a windows version of Packer for testing

2017-03-20 Thread Patrick van der Velde
Ok that got me nearly there. If I cd to my packer directory cd e:\documents\Petrik\documents\software\go\src\github.com\mitchellh\packer and then call the following command line docker run -v %cd%:/go/src/github.com/mitchellh/packer -w /go/src/github.com/mitchellh/packer golang:1.8 ba

Re: [packer] The easiest way to build a windows version of Packer for testing

2017-03-20 Thread Rickard von Essen
We vendor our deps so you don't need your full go path tree, $GOPATH/src/ github.com/mitchellh/packer is enough. (Unless you want to modify deps) On 20 March 2017 at 10:13, Patrick van der Velde < petrikvanderve...@gmail.com> wrote: > So based on your command line I tried the following: > > Go to

Re: [packer] The easiest way to build a windows version of Packer for testing

2017-03-20 Thread Patrick van der Velde
So based on your command line I tried the following: Go to the GOPATH directory cd e:\documents\Petrik\documents\src\go Then run docker run -v %cd%:/usr/src/go -w /usr/src/go/src/github.com/mitchellh/packer golang:1.8 bash -c "GOPATH=/usr/src/go XC_ARCH=amd64 XC_OS=windows make dev" T

Re: [packer] The easiest way to build a windows version of Packer for testing

2017-03-20 Thread Rickard von Essen
I tested my docker command and it's not completely accurate. This works on my Mac: docker run -v $PWD:/go/src/github.com/mitchellh/packer -w /go/src/ github.com/mitchellh/packer golang:1.8 bash -c "XC_ARCH=amd64 XC_OS=windows make dev" It produces a windows binary in pkg/windows_amd64 I guess yo

Re: [packer] The easiest way to build a windows version of Packer for testing

2017-03-20 Thread Patrick van der Velde
Yeah I guess my environment is not correctly configured. I got docker for windows to work by the way but while it doesn't fail, it doesn't seem to produce a package either. On Monday, 20 March 2017 21:36:21 UTC+13, Rickard von Essen wrote: > > It should work to build on Windows, unfortunately I

Re: [packer] The easiest way to build a windows version of Packer for testing

2017-03-20 Thread Rickard von Essen
It should work to build on Windows, unfortunately I can't really help with that. We build each commit in appveyor and that is green so I expect there is something with you setup. On 20 March 2017 at 02:05, Patrick van der Velde < petrikvanderve...@gmail.com> wrote: > I was really hoping to avoid