Re: [packer] Error getting SSH address: IP lookup failed

[Benny Chan]

Thanks Rickard. 

I am suspect that my situation is the iso cannot be boot correctly and the 
installation even not started... 

On Monday, April 15, 2019 at 6:47:21 PM UTC+8, Rickard von Essen wrote:
>
> I really recommend that you start with a known good packer template or at 
> least a known good Kickstart file.
>
> If you install a vm manually centos will write a Kickstart file in /root 
> for whatever settings you used. But best is to fork a well known project 
> like github.com/chef/bento and adapt their packer templates to your needs 
> in small steps. 
>
> On Mon, Apr 15, 2019, 12:30 Benny Chan > 
> wrote:
>
>> Thanks. and I did it but same error message. When I VNC into the VM and I 
>> can see the error message as attached. I tried to added "ksdevice=eth0" or 
>> "ksdevice=0" as boot_command but no luck... 
>>
>>
>>
>> On Monday, April 15, 2019 at 4:08:15 PM UTC+8, Rickard von Essen wrote:
>>>
>>> Yes
>>>
>>> On Mon, Apr 15, 2019, 09:30 Benny Chan  wrote:
>>>
 Do you mean change the username and password ac "centos" (same as my 
 ks.cfg) in my "myenv_conf.json"? 

 On Monday, April 15, 2019 at 3:01:20 PM UTC+8, Rickard von Essen wrote:
>
> On CentOS, by default you can't connect as root on ssh. Try to use the 
> centos user configured in the ks.cfg. This should most likely allow you 
> to 
> connect. 
>
> On Mon, Apr 15, 2019, 08:06 Benny Chan  wrote:
>
>> Thanks Rickard. Attached the ks.cfg file 
>>
>> On Monday, April 15, 2019 at 1:10:34 PM UTC+8, Rickard von Essen 
>> wrote:
>>>
>>> According to your configuration there should be a file http/ks.cfg
>>>
>>>
>>> On Mon, Apr 15, 2019, 06:48 Benny Chan  wrote:
>>>
 Sorry I am totally new to Packer. May i know where can i find the 
 Kickstart file? 

 On Mon, Apr 15, 2019 at 12:34 PM Rickard von Essen <
 rickard...@gmail.com> wrote:

> And your Kickstart file how does it look like?
>
> On Mon, Apr 15, 2019, 03:14 Benny Chan  wrote:
>
>> Thanks Rickard. This is the command I run 
>>
>> /packer/packer build -var-file=myenv_conf.json 
>> vmware/local/centos_base.json
>>
>> All files are zipped. 
>>
>>
>>
>> On Saturday, April 13, 2019 at 3:07:11 PM UTC+8, Rickard von 
>> Essen wrote:
>>>
>>> Please provide your full Packer temple, Kickstart/preseed file 
>>> if applicable and a full log when running Packer with env var 
>>> PACKER_LOG=1.
>>>
>>> On Sat, Apr 13, 2019, 00:47 Benny Chan  wrote:
>>>
 hi All, 

 I encountered the situation about "Error getting SSH address". 
 The log message is listed below. 


 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP 
 information...
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress 
 found MAC address in VMX: 00:0c:29:64:ff:e1
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP 
 leases path: /etc/vmware/vmnet8/dhcpd/dhcpd.leases
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup 
 failed: None of the found device(s) [vmnet8] has a DHCP lease for 
 MAC 
 00:0c:29:64:ff:e1
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error 
 getting SSH address: IP lookup failed: None of the found device(s) 
 [vmnet8] 
 has a DHCP lease for MAC 00:0c:29:64:ff:e1
 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located 
 networkmapper configuration file using Workstation: 
 /etc/vmware/netmap.conf
 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP 
 discovered device matching nat: vmnet8

 Attached the vmx file for reference. 

 I followed a post online to vnc into the ip and I can reach the 
 VM but it is one a setup screen or something. I attached the 
 screen capture 
 for reference

 Any advice what steps to follow to make it works? 



 -- 
 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 Issues: https://github.com/mitchellh/packer/issues
 IRC: #packer-tool on Freenode
 --- 
 You received this message because you are subscribed to the 
 Google Groups "Packer" group.
 To uns

Re: [packer] Error getting SSH address: IP lookup failed

[Rickard von Essen]

I really recommend that you start with a known good packer template or at
least a known good Kickstart file.

If you install a vm manually centos will write a Kickstart file in /root
for whatever settings you used. But best is to fork a well known project
like github.com/chef/bento and adapt their packer templates to your needs
in small steps.

On Mon, Apr 15, 2019, 12:30 Benny Chan  wrote:

> Thanks. and I did it but same error message. When I VNC into the VM and I
> can see the error message as attached. I tried to added "ksdevice=eth0" or
> "ksdevice=0" as boot_command but no luck...
>
>
>
> On Monday, April 15, 2019 at 4:08:15 PM UTC+8, Rickard von Essen wrote:
>>
>> Yes
>>
>> On Mon, Apr 15, 2019, 09:30 Benny Chan  wrote:
>>
>>> Do you mean change the username and password ac "centos" (same as my
>>> ks.cfg) in my "myenv_conf.json"?
>>>
>>> On Monday, April 15, 2019 at 3:01:20 PM UTC+8, Rickard von Essen wrote:

 On CentOS, by default you can't connect as root on ssh. Try to use the
 centos user configured in the ks.cfg. This should most likely allow you to
 connect.

 On Mon, Apr 15, 2019, 08:06 Benny Chan  wrote:

> Thanks Rickard. Attached the ks.cfg file
>
> On Monday, April 15, 2019 at 1:10:34 PM UTC+8, Rickard von Essen wrote:
>>
>> According to your configuration there should be a file http/ks.cfg
>>
>>
>> On Mon, Apr 15, 2019, 06:48 Benny Chan  wrote:
>>
>>> Sorry I am totally new to Packer. May i know where can i find the
>>> Kickstart file?
>>>
>>> On Mon, Apr 15, 2019 at 12:34 PM Rickard von Essen <
>>> rickard...@gmail.com> wrote:
>>>
 And your Kickstart file how does it look like?

 On Mon, Apr 15, 2019, 03:14 Benny Chan  wrote:

> Thanks Rickard. This is the command I run
>
> /packer/packer build -var-file=myenv_conf.json
> vmware/local/centos_base.json
>
> All files are zipped.
>
>
>
> On Saturday, April 13, 2019 at 3:07:11 PM UTC+8, Rickard von Essen
> wrote:
>>
>> Please provide your full Packer temple, Kickstart/preseed file if
>> applicable and a full log when running Packer with env var 
>> PACKER_LOG=1.
>>
>> On Sat, Apr 13, 2019, 00:47 Benny Chan  wrote:
>>
>>> hi All,
>>>
>>> I encountered the situation about "Error getting SSH address".
>>> The log message is listed below.
>>>
>>>
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP
>>> information...
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress
>>> found MAC address in VMX: 00:0c:29:64:ff:e1
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP
>>> leases path: /etc/vmware/vmnet8/dhcpd/dhcpd.leases
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup
>>> failed: None of the found device(s) [vmnet8] has a DHCP lease for 
>>> MAC
>>> 00:0c:29:64:ff:e1
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error
>>> getting SSH address: IP lookup failed: None of the found device(s) 
>>> [vmnet8]
>>> has a DHCP lease for MAC 00:0c:29:64:ff:e1
>>> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located
>>> networkmapper configuration file using Workstation: 
>>> /etc/vmware/netmap.conf
>>> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP
>>> discovered device matching nat: vmnet8
>>>
>>> Attached the vmx file for reference.
>>>
>>> I followed a post online to vnc into the ip and I can reach the
>>> VM but it is one a setup screen or something. I attached the screen 
>>> capture
>>> for reference
>>>
>>> Any advice what steps to follow to make it works?
>>>
>>>
>>>
>>> --
>>> 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 Issues: https://github.com/mitchellh/packer/issues
>>> IRC: #packer-tool on Freenode
>>> ---
>>> You received this message because you are subscribed to the
>>> Google Groups "Packer" group.
>>> To unsubscribe from this group and stop receiving emails from
>>> it, send an email to packe...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/packer-tool/7ae69dc9-a942-470a-8c23-77d6c279e3bf%40googlegroups.com
>>> 

Re: [packer] Error getting SSH address: IP lookup failed

[Benny Chan]

Thanks. and I did it but same error message. When I VNC into the VM and I 
can see the error message as attached. I tried to added "ksdevice=eth0" or 
"ksdevice=0" as boot_command but no luck... 



On Monday, April 15, 2019 at 4:08:15 PM UTC+8, Rickard von Essen wrote:
>
> Yes
>
> On Mon, Apr 15, 2019, 09:30 Benny Chan > 
> wrote:
>
>> Do you mean change the username and password ac "centos" (same as my 
>> ks.cfg) in my "myenv_conf.json"? 
>>
>> On Monday, April 15, 2019 at 3:01:20 PM UTC+8, Rickard von Essen wrote:
>>>
>>> On CentOS, by default you can't connect as root on ssh. Try to use the 
>>> centos user configured in the ks.cfg. This should most likely allow you to 
>>> connect. 
>>>
>>> On Mon, Apr 15, 2019, 08:06 Benny Chan  wrote:
>>>
 Thanks Rickard. Attached the ks.cfg file 

 On Monday, April 15, 2019 at 1:10:34 PM UTC+8, Rickard von Essen wrote:
>
> According to your configuration there should be a file http/ks.cfg
>
>
> On Mon, Apr 15, 2019, 06:48 Benny Chan  wrote:
>
>> Sorry I am totally new to Packer. May i know where can i find the 
>> Kickstart file? 
>>
>> On Mon, Apr 15, 2019 at 12:34 PM Rickard von Essen <
>> rickard...@gmail.com> wrote:
>>
>>> And your Kickstart file how does it look like?
>>>
>>> On Mon, Apr 15, 2019, 03:14 Benny Chan  wrote:
>>>
 Thanks Rickard. This is the command I run 

 /packer/packer build -var-file=myenv_conf.json 
 vmware/local/centos_base.json

 All files are zipped. 



 On Saturday, April 13, 2019 at 3:07:11 PM UTC+8, Rickard von Essen 
 wrote:
>
> Please provide your full Packer temple, Kickstart/preseed file if 
> applicable and a full log when running Packer with env var 
> PACKER_LOG=1.
>
> On Sat, Apr 13, 2019, 00:47 Benny Chan  wrote:
>
>> hi All, 
>>
>> I encountered the situation about "Error getting SSH address". 
>> The log message is listed below. 
>>
>>
>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP 
>> information...
>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress 
>> found MAC address in VMX: 00:0c:29:64:ff:e1
>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP 
>> leases path: /etc/vmware/vmnet8/dhcpd/dhcpd.leases
>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup failed: 
>> None of the found device(s) [vmnet8] has a DHCP lease for MAC 
>> 00:0c:29:64:ff:e1
>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error 
>> getting SSH address: IP lookup failed: None of the found device(s) 
>> [vmnet8] 
>> has a DHCP lease for MAC 00:0c:29:64:ff:e1
>> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located 
>> networkmapper configuration file using Workstation: 
>> /etc/vmware/netmap.conf
>> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP 
>> discovered device matching nat: vmnet8
>>
>> Attached the vmx file for reference. 
>>
>> I followed a post online to vnc into the ip and I can reach the 
>> VM but it is one a setup screen or something. I attached the screen 
>> capture 
>> for reference
>>
>> Any advice what steps to follow to make it works? 
>>
>>
>>
>> -- 
>> 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 Issues: https://github.com/mitchellh/packer/issues
>> IRC: #packer-tool on Freenode
>> --- 
>> You received this message because you are subscribed to the 
>> Google Groups "Packer" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to packe...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/packer-tool/7ae69dc9-a942-470a-8c23-77d6c279e3bf%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
 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 Issues: https://github.com/mitchellh

Re: [packer] Error getting SSH address: IP lookup failed

[Rickard von Essen]

Yes

On Mon, Apr 15, 2019, 09:30 Benny Chan  wrote:

> Do you mean change the username and password ac "centos" (same as my
> ks.cfg) in my "myenv_conf.json"?
>
> On Monday, April 15, 2019 at 3:01:20 PM UTC+8, Rickard von Essen wrote:
>>
>> On CentOS, by default you can't connect as root on ssh. Try to use the
>> centos user configured in the ks.cfg. This should most likely allow you to
>> connect.
>>
>> On Mon, Apr 15, 2019, 08:06 Benny Chan  wrote:
>>
>>> Thanks Rickard. Attached the ks.cfg file
>>>
>>> On Monday, April 15, 2019 at 1:10:34 PM UTC+8, Rickard von Essen wrote:

 According to your configuration there should be a file http/ks.cfg


 On Mon, Apr 15, 2019, 06:48 Benny Chan  wrote:

> Sorry I am totally new to Packer. May i know where can i find the
> Kickstart file?
>
> On Mon, Apr 15, 2019 at 12:34 PM Rickard von Essen <
> rickard...@gmail.com> wrote:
>
>> And your Kickstart file how does it look like?
>>
>> On Mon, Apr 15, 2019, 03:14 Benny Chan  wrote:
>>
>>> Thanks Rickard. This is the command I run
>>>
>>> /packer/packer build -var-file=myenv_conf.json
>>> vmware/local/centos_base.json
>>>
>>> All files are zipped.
>>>
>>>
>>>
>>> On Saturday, April 13, 2019 at 3:07:11 PM UTC+8, Rickard von Essen
>>> wrote:

 Please provide your full Packer temple, Kickstart/preseed file if
 applicable and a full log when running Packer with env var 
 PACKER_LOG=1.

 On Sat, Apr 13, 2019, 00:47 Benny Chan  wrote:

> hi All,
>
> I encountered the situation about "Error getting SSH address". The
> log message is listed below.
>
>
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP
> information...
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress found
> MAC address in VMX: 00:0c:29:64:ff:e1
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP leases
> path: /etc/vmware/vmnet8/dhcpd/dhcpd.leases
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup failed:
> None of the found device(s) [vmnet8] has a DHCP lease for MAC
> 00:0c:29:64:ff:e1
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error
> getting SSH address: IP lookup failed: None of the found device(s) 
> [vmnet8]
> has a DHCP lease for MAC 00:0c:29:64:ff:e1
> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located
> networkmapper configuration file using Workstation: 
> /etc/vmware/netmap.conf
> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP discovered
> device matching nat: vmnet8
>
> Attached the vmx file for reference.
>
> I followed a post online to vnc into the ip and I can reach the VM
> but it is one a setup screen or something. I attached the screen 
> capture
> for reference
>
> Any advice what steps to follow to make it works?
>
>
>
> --
> 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 Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google
> Groups "Packer" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to packe...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/7ae69dc9-a942-470a-8c23-77d6c279e3bf%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> 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 Issues: https://github.com/mitchellh/packer/issues
>>> IRC: #packer-tool on Freenode
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Packer" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to packe...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/packer-tool/9c2d7e94-af62-4f9d-a8e5-8a6705501e0a%40googlegroups.c

Re: [packer] Error getting SSH address: IP lookup failed

[Benny Chan]

Do you mean change the username and password ac "centos" (same as my 
ks.cfg) in my "myenv_conf.json"? 

On Monday, April 15, 2019 at 3:01:20 PM UTC+8, Rickard von Essen wrote:
>
> On CentOS, by default you can't connect as root on ssh. Try to use the 
> centos user configured in the ks.cfg. This should most likely allow you to 
> connect. 
>
> On Mon, Apr 15, 2019, 08:06 Benny Chan > 
> wrote:
>
>> Thanks Rickard. Attached the ks.cfg file 
>>
>> On Monday, April 15, 2019 at 1:10:34 PM UTC+8, Rickard von Essen wrote:
>>>
>>> According to your configuration there should be a file http/ks.cfg
>>>
>>>
>>> On Mon, Apr 15, 2019, 06:48 Benny Chan  wrote:
>>>
 Sorry I am totally new to Packer. May i know where can i find the 
 Kickstart file? 

 On Mon, Apr 15, 2019 at 12:34 PM Rickard von Essen <
 rickard...@gmail.com> wrote:

> And your Kickstart file how does it look like?
>
> On Mon, Apr 15, 2019, 03:14 Benny Chan  wrote:
>
>> Thanks Rickard. This is the command I run 
>>
>> /packer/packer build -var-file=myenv_conf.json 
>> vmware/local/centos_base.json
>>
>> All files are zipped. 
>>
>>
>>
>> On Saturday, April 13, 2019 at 3:07:11 PM UTC+8, Rickard von Essen 
>> wrote:
>>>
>>> Please provide your full Packer temple, Kickstart/preseed file if 
>>> applicable and a full log when running Packer with env var PACKER_LOG=1.
>>>
>>> On Sat, Apr 13, 2019, 00:47 Benny Chan  wrote:
>>>
 hi All, 

 I encountered the situation about "Error getting SSH address". The 
 log message is listed below. 


 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP 
 information...
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress found 
 MAC address in VMX: 00:0c:29:64:ff:e1
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP leases 
 path: /etc/vmware/vmnet8/dhcpd/dhcpd.leases
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup failed: 
 None of the found device(s) [vmnet8] has a DHCP lease for MAC 
 00:0c:29:64:ff:e1
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error 
 getting SSH address: IP lookup failed: None of the found device(s) 
 [vmnet8] 
 has a DHCP lease for MAC 00:0c:29:64:ff:e1
 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located 
 networkmapper configuration file using Workstation: 
 /etc/vmware/netmap.conf
 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP discovered 
 device matching nat: vmnet8

 Attached the vmx file for reference. 

 I followed a post online to vnc into the ip and I can reach the VM 
 but it is one a setup screen or something. I attached the screen 
 capture 
 for reference

 Any advice what steps to follow to make it works? 



 -- 
 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 Issues: https://github.com/mitchellh/packer/issues
 IRC: #packer-tool on Freenode
 --- 
 You received this message because you are subscribed to the Google 
 Groups "Packer" group.
 To unsubscribe from this group and stop receiving emails from it, 
 send an email to packe...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/packer-tool/7ae69dc9-a942-470a-8c23-77d6c279e3bf%40googlegroups.com
  
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>> 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 Issues: https://github.com/mitchellh/packer/issues
>> IRC: #packer-tool on Freenode
>> --- 
>> You received this message because you are subscribed to the Google 
>> Groups "Packer" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to packe...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/packer-tool/9c2d7e94-af62-4f9d-a8e5-8a6705501e0a%40googlegroups.com
>>  
>> 

Re: [packer] Error getting SSH address: IP lookup failed

[Rickard von Essen]

On CentOS, by default you can't connect as root on ssh. Try to use the
centos user configured in the ks.cfg. This should most likely allow you to
connect.

On Mon, Apr 15, 2019, 08:06 Benny Chan  wrote:

> Thanks Rickard. Attached the ks.cfg file
>
> On Monday, April 15, 2019 at 1:10:34 PM UTC+8, Rickard von Essen wrote:
>>
>> According to your configuration there should be a file http/ks.cfg
>>
>>
>> On Mon, Apr 15, 2019, 06:48 Benny Chan  wrote:
>>
>>> Sorry I am totally new to Packer. May i know where can i find the
>>> Kickstart file?
>>>
>>> On Mon, Apr 15, 2019 at 12:34 PM Rickard von Essen 
>>> wrote:
>>>
 And your Kickstart file how does it look like?

 On Mon, Apr 15, 2019, 03:14 Benny Chan  wrote:

> Thanks Rickard. This is the command I run
>
> /packer/packer build -var-file=myenv_conf.json
> vmware/local/centos_base.json
>
> All files are zipped.
>
>
>
> On Saturday, April 13, 2019 at 3:07:11 PM UTC+8, Rickard von Essen
> wrote:
>>
>> Please provide your full Packer temple, Kickstart/preseed file if
>> applicable and a full log when running Packer with env var PACKER_LOG=1.
>>
>> On Sat, Apr 13, 2019, 00:47 Benny Chan  wrote:
>>
>>> hi All,
>>>
>>> I encountered the situation about "Error getting SSH address". The
>>> log message is listed below.
>>>
>>>
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP
>>> information...
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress found
>>> MAC address in VMX: 00:0c:29:64:ff:e1
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP leases
>>> path: /etc/vmware/vmnet8/dhcpd/dhcpd.leases
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup failed:
>>> None of the found device(s) [vmnet8] has a DHCP lease for MAC
>>> 00:0c:29:64:ff:e1
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error
>>> getting SSH address: IP lookup failed: None of the found device(s) 
>>> [vmnet8]
>>> has a DHCP lease for MAC 00:0c:29:64:ff:e1
>>> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located
>>> networkmapper configuration file using Workstation: 
>>> /etc/vmware/netmap.conf
>>> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP discovered
>>> device matching nat: vmnet8
>>>
>>> Attached the vmx file for reference.
>>>
>>> I followed a post online to vnc into the ip and I can reach the VM
>>> but it is one a setup screen or something. I attached the screen capture
>>> for reference
>>>
>>> Any advice what steps to follow to make it works?
>>>
>>>
>>>
>>> --
>>> 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 Issues: https://github.com/mitchellh/packer/issues
>>> IRC: #packer-tool on Freenode
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Packer" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to packe...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/packer-tool/7ae69dc9-a942-470a-8c23-77d6c279e3bf%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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 Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google
> Groups "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to packe...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/9c2d7e94-af62-4f9d-a8e5-8a6705501e0a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
 --
 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 Issues: https://github.com/

Re: [packer] Error getting SSH address: IP lookup failed

[Benny Chan]

Thanks Rickard. Attached the ks.cfg file 

On Monday, April 15, 2019 at 1:10:34 PM UTC+8, Rickard von Essen wrote:
>
> According to your configuration there should be a file http/ks.cfg
>
>
> On Mon, Apr 15, 2019, 06:48 Benny Chan > 
> wrote:
>
>> Sorry I am totally new to Packer. May i know where can i find the 
>> Kickstart file? 
>>
>> On Mon, Apr 15, 2019 at 12:34 PM Rickard von Essen > > wrote:
>>
>>> And your Kickstart file how does it look like?
>>>
>>> On Mon, Apr 15, 2019, 03:14 Benny Chan > 
>>> wrote:
>>>
 Thanks Rickard. This is the command I run 

 /packer/packer build -var-file=myenv_conf.json 
 vmware/local/centos_base.json

 All files are zipped. 



 On Saturday, April 13, 2019 at 3:07:11 PM UTC+8, Rickard von Essen 
 wrote:
>
> Please provide your full Packer temple, Kickstart/preseed file if 
> applicable and a full log when running Packer with env var PACKER_LOG=1.
>
> On Sat, Apr 13, 2019, 00:47 Benny Chan  wrote:
>
>> hi All, 
>>
>> I encountered the situation about "Error getting SSH address". The 
>> log message is listed below. 
>>
>>
>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP 
>> information...
>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress found 
>> MAC address in VMX: 00:0c:29:64:ff:e1
>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP leases 
>> path: /etc/vmware/vmnet8/dhcpd/dhcpd.leases
>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup failed: 
>> None of the found device(s) [vmnet8] has a DHCP lease for MAC 
>> 00:0c:29:64:ff:e1
>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error getting 
>> SSH address: IP lookup failed: None of the found device(s) [vmnet8] has 
>> a 
>> DHCP lease for MAC 00:0c:29:64:ff:e1
>> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located networkmapper 
>> configuration file using Workstation: /etc/vmware/netmap.conf
>> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP discovered 
>> device matching nat: vmnet8
>>
>> Attached the vmx file for reference. 
>>
>> I followed a post online to vnc into the ip and I can reach the VM 
>> but it is one a setup screen or something. I attached the screen capture 
>> for reference
>>
>> Any advice what steps to follow to make it works? 
>>
>>
>>
>> -- 
>> 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 Issues: https://github.com/mitchellh/packer/issues
>> IRC: #packer-tool on Freenode
>> --- 
>> You received this message because you are subscribed to the Google 
>> Groups "Packer" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to packe...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/packer-tool/7ae69dc9-a942-470a-8c23-77d6c279e3bf%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
 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 Issues: https://github.com/mitchellh/packer/issues
 IRC: #packer-tool on Freenode
 --- 
 You received this message because you are subscribed to the Google 
 Groups "Packer" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to packe...@googlegroups.com .
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/packer-tool/9c2d7e94-af62-4f9d-a8e5-8a6705501e0a%40googlegroups.com
  
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>>> 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 Issues: https://github.com/mitchellh/packer/issues
>>> IRC: #packer-tool on Freenode
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Packer" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email

Re: [packer] Error getting SSH address: IP lookup failed

[Rickard von Essen]

According to your configuration there should be a file http/ks.cfg


On Mon, Apr 15, 2019, 06:48 Benny Chan  wrote:

> Sorry I am totally new to Packer. May i know where can i find the
> Kickstart file?
>
> On Mon, Apr 15, 2019 at 12:34 PM Rickard von Essen <
> rickard.von.es...@gmail.com> wrote:
>
>> And your Kickstart file how does it look like?
>>
>> On Mon, Apr 15, 2019, 03:14 Benny Chan  wrote:
>>
>>> Thanks Rickard. This is the command I run
>>>
>>> /packer/packer build -var-file=myenv_conf.json
>>> vmware/local/centos_base.json
>>>
>>> All files are zipped.
>>>
>>>
>>>
>>> On Saturday, April 13, 2019 at 3:07:11 PM UTC+8, Rickard von Essen wrote:

 Please provide your full Packer temple, Kickstart/preseed file if
 applicable and a full log when running Packer with env var PACKER_LOG=1.

 On Sat, Apr 13, 2019, 00:47 Benny Chan  wrote:

> hi All,
>
> I encountered the situation about "Error getting SSH address". The log
> message is listed below.
>
>
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP
> information...
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress found MAC
> address in VMX: 00:0c:29:64:ff:e1
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP leases
> path: /etc/vmware/vmnet8/dhcpd/dhcpd.leases
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup failed: None
> of the found device(s) [vmnet8] has a DHCP lease for MAC 00:0c:29:64:ff:e1
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error getting
> SSH address: IP lookup failed: None of the found device(s) [vmnet8] has a
> DHCP lease for MAC 00:0c:29:64:ff:e1
> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located networkmapper
> configuration file using Workstation: /etc/vmware/netmap.conf
> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP discovered
> device matching nat: vmnet8
>
> Attached the vmx file for reference.
>
> I followed a post online to vnc into the ip and I can reach the VM but
> it is one a setup screen or something. I attached the screen capture for
> reference
>
> Any advice what steps to follow to make it works?
>
>
>
> --
> 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 Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google
> Groups "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to packe...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/7ae69dc9-a942-470a-8c23-77d6c279e3bf%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> 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 Issues: https://github.com/mitchellh/packer/issues
>>> IRC: #packer-tool on Freenode
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Packer" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to packer-tool+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/packer-tool/9c2d7e94-af62-4f9d-a8e5-8a6705501e0a%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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 Issues: https://github.com/mitchellh/packer/issues
>> IRC: #packer-tool on Freenode
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Packer" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to packer-tool+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/packer-tool/CALz9Rt82UkcsdpY_e2qLkqHjZDw-4weFNh4OoGCJoZs0ABQn9g%40mail.gmail.com
>> 

Re: [packer] Error getting SSH address: IP lookup failed

[Benny Chan]

Sorry I am totally new to Packer. May i know where can i find the Kickstart
file?

On Mon, Apr 15, 2019 at 12:34 PM Rickard von Essen <
rickard.von.es...@gmail.com> wrote:

> And your Kickstart file how does it look like?
>
> On Mon, Apr 15, 2019, 03:14 Benny Chan  wrote:
>
>> Thanks Rickard. This is the command I run
>>
>> /packer/packer build -var-file=myenv_conf.json
>> vmware/local/centos_base.json
>>
>> All files are zipped.
>>
>>
>>
>> On Saturday, April 13, 2019 at 3:07:11 PM UTC+8, Rickard von Essen wrote:
>>>
>>> Please provide your full Packer temple, Kickstart/preseed file if
>>> applicable and a full log when running Packer with env var PACKER_LOG=1.
>>>
>>> On Sat, Apr 13, 2019, 00:47 Benny Chan  wrote:
>>>
 hi All,

 I encountered the situation about "Error getting SSH address". The log
 message is listed below.


 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP
 information...
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress found MAC
 address in VMX: 00:0c:29:64:ff:e1
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP leases
 path: /etc/vmware/vmnet8/dhcpd/dhcpd.leases
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup failed: None
 of the found device(s) [vmnet8] has a DHCP lease for MAC 00:0c:29:64:ff:e1
 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error getting
 SSH address: IP lookup failed: None of the found device(s) [vmnet8] has a
 DHCP lease for MAC 00:0c:29:64:ff:e1
 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located networkmapper
 configuration file using Workstation: /etc/vmware/netmap.conf
 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP discovered
 device matching nat: vmnet8

 Attached the vmx file for reference.

 I followed a post online to vnc into the ip and I can reach the VM but
 it is one a setup screen or something. I attached the screen capture for
 reference

 Any advice what steps to follow to make it works?



 --
 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 Issues: https://github.com/mitchellh/packer/issues
 IRC: #packer-tool on Freenode
 ---
 You received this message because you are subscribed to the Google
 Groups "Packer" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to packe...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/packer-tool/7ae69dc9-a942-470a-8c23-77d6c279e3bf%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> --
>> 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 Issues: https://github.com/mitchellh/packer/issues
>> IRC: #packer-tool on Freenode
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Packer" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to packer-tool+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/packer-tool/9c2d7e94-af62-4f9d-a8e5-8a6705501e0a%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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 Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to packer-tool+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/CALz9Rt82UkcsdpY_e2qLkqHjZDw-4weFNh4OoGCJoZs0ABQn9g%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashic

Re: [packer] Error getting SSH address: IP lookup failed

[Rickard von Essen]

And your Kickstart file how does it look like?

On Mon, Apr 15, 2019, 03:14 Benny Chan  wrote:

> Thanks Rickard. This is the command I run
>
> /packer/packer build -var-file=myenv_conf.json
> vmware/local/centos_base.json
>
> All files are zipped.
>
>
>
> On Saturday, April 13, 2019 at 3:07:11 PM UTC+8, Rickard von Essen wrote:
>>
>> Please provide your full Packer temple, Kickstart/preseed file if
>> applicable and a full log when running Packer with env var PACKER_LOG=1.
>>
>> On Sat, Apr 13, 2019, 00:47 Benny Chan  wrote:
>>
>>> hi All,
>>>
>>> I encountered the situation about "Error getting SSH address". The log
>>> message is listed below.
>>>
>>>
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP
>>> information...
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress found MAC
>>> address in VMX: 00:0c:29:64:ff:e1
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP leases path:
>>> /etc/vmware/vmnet8/dhcpd/dhcpd.leases
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup failed: None
>>> of the found device(s) [vmnet8] has a DHCP lease for MAC 00:0c:29:64:ff:e1
>>> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error getting
>>> SSH address: IP lookup failed: None of the found device(s) [vmnet8] has a
>>> DHCP lease for MAC 00:0c:29:64:ff:e1
>>> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located networkmapper
>>> configuration file using Workstation: /etc/vmware/netmap.conf
>>> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP discovered
>>> device matching nat: vmnet8
>>>
>>> Attached the vmx file for reference.
>>>
>>> I followed a post online to vnc into the ip and I can reach the VM but
>>> it is one a setup screen or something. I attached the screen capture for
>>> reference
>>>
>>> Any advice what steps to follow to make it works?
>>>
>>>
>>>
>>> --
>>> 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 Issues: https://github.com/mitchellh/packer/issues
>>> IRC: #packer-tool on Freenode
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Packer" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to packe...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/packer-tool/7ae69dc9-a942-470a-8c23-77d6c279e3bf%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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 Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to packer-tool+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/9c2d7e94-af62-4f9d-a8e5-8a6705501e0a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/CALz9Rt82UkcsdpY_e2qLkqHjZDw-4weFNh4OoGCJoZs0ABQn9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [packer] Error getting SSH address: IP lookup failed

[Rickard von Essen]

Please provide your full Packer temple, Kickstart/preseed file if
applicable and a full log when running Packer with env var PACKER_LOG=1.

On Sat, Apr 13, 2019, 00:47 Benny Chan  wrote:

> hi All,
>
> I encountered the situation about "Error getting SSH address". The log
> message is listed below.
>
>
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP information...
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress found MAC
> address in VMX: 00:0c:29:64:ff:e1
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP leases path:
> /etc/vmware/vmnet8/dhcpd/dhcpd.leases
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup failed: None of
> the found device(s) [vmnet8] has a DHCP lease for MAC 00:0c:29:64:ff:e1
> 2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error getting SSH
> address: IP lookup failed: None of the found device(s) [vmnet8] has a DHCP
> lease for MAC 00:0c:29:64:ff:e1
> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located networkmapper
> configuration file using Workstation: /etc/vmware/netmap.conf
> 2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP discovered device
> matching nat: vmnet8
>
> Attached the vmx file for reference.
>
> I followed a post online to vnc into the ip and I can reach the VM but it
> is one a setup screen or something. I attached the screen capture for
> reference
>
> Any advice what steps to follow to make it works?
>
>
>
> --
> 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 Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to packer-tool+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/7ae69dc9-a942-470a-8c23-77d6c279e3bf%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/CALz9Rt9AJrhPGyc_%3DMyqp3sqJU95TdH1xfSa2_QDvPq8xTDctA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[packer] Error getting SSH address: IP lookup failed

[Benny Chan]

hi All, 

I encountered the situation about "Error getting SSH address". The log 
message is listed below. 


2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Lookup up IP information...
2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 GuestAddress found MAC 
address in VMX: 00:0c:29:64:ff:e1
2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 Trying DHCP leases path: 
/etc/vmware/vmnet8/dhcpd/dhcpd.leases
2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 IP lookup failed: None of 
the found device(s) [vmnet8] has a DHCP lease for MAC 00:0c:29:64:ff:e1
2019/04/11 17:43:01 packer: 2019/04/11 17:43:01 [DEBUG] Error getting SSH 
address: IP lookup failed: None of the found device(s) [vmnet8] has a DHCP 
lease for MAC 00:0c:29:64:ff:e1
2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 Located networkmapper 
configuration file using Workstation: /etc/vmware/netmap.conf
2019/04/11 17:43:06 packer: 2019/04/11 17:43:06 GuestIP discovered device 
matching nat: vmnet8

Attached the vmx file for reference. 

I followed a post online to vnc into the ip and I can reach the VM but it 
is one a setup screen or something. I attached the screen capture for 
reference

Any advice what steps to follow to make it works? 



-- 
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 Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/7ae69dc9-a942-470a-8c23-77d6c279e3bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
#!/usr/bin/vmware
.encoding = "UTF-8"
bios.bootorder = "hdd,cdrom"
checkpoint.vmstate = ""
cleanshutdown = "FALSE"
config.version = "8"
displayname = "pnda_template_base"
ehci.pcislotnumber = "-1"
ehci.present = "FALSE"
ethernet0.addresstype = "generated"
ethernet0.bsdname = "en0"
ethernet0.connectiontype = "bridged"
ethernet0.displayname = "Ethernet"
ethernet0.generatedaddressoffset = "0"
ethernet0.linkstatepropagation.enable = "FALSE"
ethernet0.networkname = "DPG-VLAN651"
ethernet0.pcislotnumber = "33"
ethernet0.present = "TRUE"
ethernet0.startconnected = "TRUE"
ethernet0.virtualdev = "e1000"
ethernet0.vnet = ""
ethernet0.wakeonpcktrcv = "FALSE"
extendedconfigfile = "pnda_template_base.vmxf"
floppy0.present = "FALSE"
guestos = "centos-64"
gui.fullscreenatpoweron = "FALSE"
gui.viewmodeatpoweron = "windowed"
hgfs.linkrootshare = "TRUE"
hgfs.maprootshare = "TRUE"
ide0:0.devicetype = "cdrom-image"
ide0:0.filename = "/root/pnda/packer/iso/CentOS-7-x86_64-Minimal-1810.iso"
ide0:0.present = "TRUE"
isolation.tools.hgfs.disable = "FALSE"
memsize = "4096"
mks.enable3d = "FALSE"
msg.autoanswer = "true"
numvcpus = "2"
nvme0.present = "FALSE"
nvram = "pnda_template_base.nvram"
parallel0.autodetect = "FALSE"
parallel0.bidirectional = ""
parallel0.filename = ""
parallel0.present = "FALSE"
parallel0.startconnected = "FALSE"
pcibridge0.pcislotnumber = "17"
pcibridge0.present = "TRUE"
pcibridge4.functions = "8"
pcibridge4.pcislotnumber = "21"
pcibridge4.present = "TRUE"
pcibridge4.virtualdev = "pcieRootPort"
pcibridge5.functions = "8"
pcibridge5.pcislotnumber = "22"
pcibridge5.present = "TRUE"
pcibridge5.virtualdev = "pcieRootPort"
pcibridge6.functions = "8"
pcibridge6.pcislotnumber = "23"
pcibridge6.present = "TRUE"
pcibridge6.virtualdev = "pcieRootPort"
pcibridge7.functions = "8"
pcibridge7.pcislotnumber = "24"
pcibridge7.present = "TRUE"
pcibridge7.virtualdev = "pcieRootPort"
powertype.poweroff = "soft"
powertype.poweron = "soft"
powertype.reset = "soft"
powertype.suspend = "soft"
proxyapps.publishtohost = "FALSE"
remotedisplay.vnc.enabled = "TRUE"
remotedisplay.vnc.ip = "127.0.0.1"
remotedisplay.vnc.port = "5947"
replay.filename = ""
replay.supported = "FALSE"
sata0.present = "FALSE"
scsi0.pcislotnumber = "16"
scsi0.present = "TRUE"
scsi0.virtualdev = "lsilogic"
scsi0:0.filename = "pnda_template_base.vmdk"
scsi0:0.present = "TRUE"
scsi0:0.redo = ""
serial0.autodetect = "FALSE"
serial0.filename = ""
serial0.filetype = ""
serial0.pipe.endpoint = ""
serial0.present = "FALSE"
serial0.startconnected = "FALSE"
serial0.trynorxloss = ""
serial0.yieldonmsrread = ""
sound.autodetect = "TRUE"
sound.filename = "-1"
sound.present = "FALSE"
sound.startconnected = "FALSE"
tools.synctime = "TRUE"
tools.upgrade.policy = "upgradeAtPowerCycle"
usb.pcislotnumber = "-1"
usb.present = "FALSE"
uuid.action = "create"
virtualhw.productcompatibility = "hosted"
virtualhw.version = "9"
vmci0.id = "1861462627"
vmci0.pcislotnumber = "35"
vmci0.present = "TRUE"
vmotion.checkpointfbsize = "33554432"
numa.autosize.vcpu.maxPerVirtualN

Re: [packer] Error getting SSH address

[Aaron Kulbe]

Thank you, Rickard. I'm not sure why, but this went to my Junk Mail folder. 
I ended up going back to the generic CentOS template I'd used at the 
beginning, and it worked. Then I used a diff util to compare it with my 
template, and I saw the missing colon. Once I put it in there, everything 
started working.

Thank you for your help, and my apologies for my obvious frustration coming 
through in the responses.

On Tuesday, April 17, 2018 at 12:26:06 PM UTC-7, Rickard von Essen wrote:
>
> Pulling my hair a bit on this before finding the error. The "boot_command" 
> is missing a colon after fd0. A correct line is:
>
> " text biosdevname=0 net.ifnames=0 
> ks=hd:fd0:/baseimage_130_74.cfg"
>
> See 
> https://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-kickstart2-startinginstall.html
>
> On 16 April 2018 at 23:10, Gabo Kete > 
> wrote:
>
>> Hi Aaron
>>
>> In order to rule out any possible issue with the DHCP server in VmWare or 
>> any lease issues, I'd suggest you build another VM where you 
>> install/configure another DHCP server or setup on an already running VM a  
>> DHCP server.. Once this server is up you can check the logs to see if your 
>> DHCP server just built is leasing any kind of IP address
>>
>> What does VMware server logs shows you in regards the dhcp lease time?
>>
>> On Tuesday, April 17, 2018 at 7:54:31 AM UTC+12, Aaron Kulbe wrote:
>>>
>>> I provided a copy of my kickstart file earlier in the thread. I can take 
>>> the kickstart file and pass it to the OS install manually and everything 
>>> works fine but when I attempt to do it with Packer nothing works.
>>>
>>> I'm not saying that it is not a configuration issue. I just need help 
>>> determining where I am getting this wrong.
>>>
>>> Get Outlook for iOS <https://aka.ms/o0ukef>
>>> --
>>> *From:* packe...@googlegroups.com  on behalf 
>>> of Rickard von Essen 
>>> *Sent:* Monday, April 16, 2018 10:27:02 AM
>>> *To:* packe...@googlegroups.com
>>> *Subject:* Re: [packer] Error getting SSH address 
>>>  
>>> You picture shows the problem. "Warning: can not boot. Starting 
>>> emergency shell" 
>>>
>>> This is most likely a problem with your ks file. Try building a known 
>>> good one such as 
>>> https://github.com/chef/bento/blob/master/centos/centos-7.4-x86_64.json 
>>> and compare what is different in their ks. If you don't find the cause but 
>>> theirs is working, us it and evolve it in small steps to what you need.
>>>
>>> On 16 April 2018 at 18:00, Aaron Kulbe  wrote:
>>>
>>>> Hi Rickard,
>>>>
>>>>  
>>>>
>>>> I’m not sure how this is supposed to be easy. I’m guessing I cannot 
>>>> attach screenshots to this group list post, but if it doesn’t work, you 
>>>> can 
>>>> see it at 
>>>> https://www.dropbox.com/s/w3o23riipmz3fpw/packer_issues.png?dl=0
>>>>
>>>>  
>>>>
>>>> The VM doesn’t getting a network, so I’m not sure how I can connect to 
>>>> it. On the left, is the packer run. On the right is tailing the debug log, 
>>>> and on top is the VNC connection to the host.
>>>>
>>>>  
>>>>
>>>>  
>>>>
>>>>  
>>>>
>>>> *From:* packe...@googlegroups.com [mailto:packe...@googlegroups.com] *On 
>>>> Behalf Of *Rickard von Essen
>>>> *Sent:* April 14, 2018 14:43
>>>> *To:* packe...@googlegroups.com
>>>>
>>>> *Subject:* Re: [packer] Error getting SSH address
>>>>
>>>>  
>>>>
>>>> This is usually quite easy to troubleshoot, use a playbook a something 
>>>> like this:
>>>>
>>>>  
>>>>
>>>> 1) Disable headless, or use VNC
>>>>
>>>> 2) Run the build, connect to the console. Check any error messages.
>>>>
>>>> 3) After reboot login as root and check what's the status of the 
>>>> network is it up, does it have an IP. Do the normal troubleshooting for 
>>>> networking.
>>>>
>>>> 4) Check if you can ssh from the host to the guest: ssh -l vagrant .
>>>>
>>>>  
>>>>
>>>> Interesting things to check where did it receive it's DHCP lease from? 
>>>> If it did get one. What's the mac for the NIC etc.
>

Re: [packer] Error getting SSH address

[Rickard von Essen]

Pulling my hair a bit on this before finding the error. The "boot_command"
is missing a colon after fd0. A correct line is:

" text biosdevname=0 net.ifnames=0
ks=hd:fd0:/baseimage_130_74.cfg"

See
https://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-kickstart2-startinginstall.html

On 16 April 2018 at 23:10, Gabo Kete  wrote:

> Hi Aaron
>
> In order to rule out any possible issue with the DHCP server in VmWare or
> any lease issues, I'd suggest you build another VM where you
> install/configure another DHCP server or setup on an already running VM a
> DHCP server.. Once this server is up you can check the logs to see if your
> DHCP server just built is leasing any kind of IP address
>
> What does VMware server logs shows you in regards the dhcp lease time?
>
> On Tuesday, April 17, 2018 at 7:54:31 AM UTC+12, Aaron Kulbe wrote:
>>
>> I provided a copy of my kickstart file earlier in the thread. I can take
>> the kickstart file and pass it to the OS install manually and everything
>> works fine but when I attempt to do it with Packer nothing works.
>>
>> I'm not saying that it is not a configuration issue. I just need help
>> determining where I am getting this wrong.
>>
>> Get Outlook for iOS <https://aka.ms/o0ukef>
>> --
>> *From:* packe...@googlegroups.com  on behalf
>> of Rickard von Essen 
>> *Sent:* Monday, April 16, 2018 10:27:02 AM
>> *To:* packe...@googlegroups.com
>> *Subject:* Re: [packer] Error getting SSH address
>>
>> You picture shows the problem. "Warning: can not boot. Starting emergency
>> shell"
>>
>> This is most likely a problem with your ks file. Try building a known
>> good one such as https://github.com/chef/bento/blob/master/centos/centos-
>> 7.4-x86_64.json and compare what is different in their ks. If you don't
>> find the cause but theirs is working, us it and evolve it in small steps to
>> what you need.
>>
>> On 16 April 2018 at 18:00, Aaron Kulbe  wrote:
>>
>>> Hi Rickard,
>>>
>>>
>>>
>>> I’m not sure how this is supposed to be easy. I’m guessing I cannot
>>> attach screenshots to this group list post, but if it doesn’t work, you can
>>> see it at https://www.dropbox.com/s/w3o23riipmz3fpw/packer_issues.png?
>>> dl=0
>>>
>>>
>>>
>>> The VM doesn’t getting a network, so I’m not sure how I can connect to
>>> it. On the left, is the packer run. On the right is tailing the debug log,
>>> and on top is the VNC connection to the host.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From:* packe...@googlegroups.com [mailto:packe...@googlegroups.com] *On
>>> Behalf Of *Rickard von Essen
>>> *Sent:* April 14, 2018 14:43
>>> *To:* packe...@googlegroups.com
>>>
>>> *Subject:* Re: [packer] Error getting SSH address
>>>
>>>
>>>
>>> This is usually quite easy to troubleshoot, use a playbook a something
>>> like this:
>>>
>>>
>>>
>>> 1) Disable headless, or use VNC
>>>
>>> 2) Run the build, connect to the console. Check any error messages.
>>>
>>> 3) After reboot login as root and check what's the status of the network
>>> is it up, does it have an IP. Do the normal troubleshooting for networking.
>>>
>>> 4) Check if you can ssh from the host to the guest: ssh -l vagrant .
>>>
>>>
>>>
>>> Interesting things to check where did it receive it's DHCP lease from?
>>> If it did get one. What's the mac for the NIC etc.
>>>
>>>
>>>
>>> On 14 April 2018 at 21:13, Aaron Kulbe  wrote:
>>>
>>> Does that apply if there is no external DHCP server? I’ll draw a text
>>> diagram, and hope it’ll render okay. Are you saying that the “builder VM”
>>> (as diagrammed below) is forwarding the DHCP request back upstream to the
>>> cluster, in hopes of getting an address there?
>>>
>>>
>>>
>>> [*target VM*] (whose final destination will be the cluster on the
>>> bottom)
>>>
>>> ^
>>>
>>> ^
>>>
>>> ^
>>>
>>> [*builder VM* where packer runs] (this VM has to have an IP statically
>>> configured, as all we have is vRA’s crappy IPAM, and no DHCP)
>>>
>>> ^
>>>
>>> ^
>>>
>>> ^
>>>
>>> [*vSphere cluster* w/vRealize Automation (vRA)]
>>

Re: [packer] Error getting SSH address

[Gabo Kete]

Hi Aaron

In order to rule out any possible issue with the DHCP server in VmWare or 
any lease issues, I'd suggest you build another VM where you 
install/configure another DHCP server or setup on an already running VM a  
DHCP server.. Once this server is up you can check the logs to see if your 
DHCP server just built is leasing any kind of IP address

What does VMware server logs shows you in regards the dhcp lease time?

On Tuesday, April 17, 2018 at 7:54:31 AM UTC+12, Aaron Kulbe wrote:
>
> I provided a copy of my kickstart file earlier in the thread. I can take 
> the kickstart file and pass it to the OS install manually and everything 
> works fine but when I attempt to do it with Packer nothing works.
>
> I'm not saying that it is not a configuration issue. I just need help 
> determining where I am getting this wrong.
>
> Get Outlook for iOS <https://aka.ms/o0ukef>
> --
> *From:* packe...@googlegroups.com   > on behalf of Rickard von Essen  >
> *Sent:* Monday, April 16, 2018 10:27:02 AM
> *To:* packe...@googlegroups.com 
> *Subject:* Re: [packer] Error getting SSH address 
>  
> You picture shows the problem. "Warning: can not boot. Starting emergency 
> shell" 
>
> This is most likely a problem with your ks file. Try building a known good 
> one such as 
> https://github.com/chef/bento/blob/master/centos/centos-7.4-x86_64.json 
> and compare what is different in their ks. If you don't find the cause but 
> theirs is working, us it and evolve it in small steps to what you need.
>
> On 16 April 2018 at 18:00, Aaron Kulbe  > wrote:
>
>> Hi Rickard,
>>
>>  
>>
>> I’m not sure how this is supposed to be easy. I’m guessing I cannot 
>> attach screenshots to this group list post, but if it doesn’t work, you can 
>> see it at 
>> https://www.dropbox.com/s/w3o23riipmz3fpw/packer_issues.png?dl=0
>>
>>  
>>
>> The VM doesn’t getting a network, so I’m not sure how I can connect to 
>> it. On the left, is the packer run. On the right is tailing the debug log, 
>> and on top is the VNC connection to the host.
>>
>>  
>>
>>  
>>
>>  
>>
>> *From:* packe...@googlegroups.com  [mailto:
>> packe...@googlegroups.com ] *On Behalf Of *Rickard von Essen
>> *Sent:* April 14, 2018 14:43
>> *To:* packe...@googlegroups.com 
>>
>> *Subject:* Re: [packer] Error getting SSH address
>>
>>  
>>
>> This is usually quite easy to troubleshoot, use a playbook a something 
>> like this:
>>
>>  
>>
>> 1) Disable headless, or use VNC
>>
>> 2) Run the build, connect to the console. Check any error messages.
>>
>> 3) After reboot login as root and check what's the status of the network 
>> is it up, does it have an IP. Do the normal troubleshooting for networking.
>>
>> 4) Check if you can ssh from the host to the guest: ssh -l vagrant .
>>
>>  
>>
>> Interesting things to check where did it receive it's DHCP lease from? If 
>> it did get one. What's the mac for the NIC etc.
>>
>>  
>>
>> On 14 April 2018 at 21:13, Aaron Kulbe > > wrote:
>>
>> Does that apply if there is no external DHCP server? I’ll draw a text 
>> diagram, and hope it’ll render okay. Are you saying that the “builder VM” 
>> (as diagrammed below) is forwarding the DHCP request back upstream to the 
>> cluster, in hopes of getting an address there?
>>
>>  
>>
>> [*target VM*] (whose final destination will be the cluster on the bottom)
>>
>> ^
>>
>> ^
>>
>> ^
>>
>> [*builder VM* where packer runs] (this VM has to have an IP statically 
>> configured, as all we have is vRA’s crappy IPAM, and no DHCP)
>>
>> ^
>>
>> ^
>>
>> ^
>>
>> [*vSphere cluster* w/vRealize Automation (vRA)]
>>
>>  
>>
>> *From: *'Nicholas Bayle' via Packer > >
>> *Reply-To: *"packe...@googlegroups.com " <
>> packe...@googlegroups.com >
>> *Date: *Saturday, April 14, 2018 at 11:58 AM
>> *To: *"packe...@googlegroups.com " <
>> packe...@googlegroups.com >
>> *Subject: *Re: [packer] Error getting SSH address
>>
>>  
>>
>> I had this issue. 
>>
>>  
>>
>> The problem occurs when the host VM has permission to "monitor all 
>> traffic" on the parent host. The DHCP request ends up going outside the 
>> VMware host (despite whatever your nat/hostonly settings are) to the parent 
>> VMware installation

Re: [packer] Error getting SSH address

[Aaron Kulbe]

I provided a copy of my kickstart file earlier in the thread. I can take the 
kickstart file and pass it to the OS install manually and everything works fine 
but when I attempt to do it with Packer nothing works.

I'm not saying that it is not a configuration issue. I just need help 
determining where I am getting this wrong.

Get Outlook for iOS<https://aka.ms/o0ukef>

From: packer-tool@googlegroups.com  on behalf of 
Rickard von Essen 
Sent: Monday, April 16, 2018 10:27:02 AM
To: packer-tool@googlegroups.com
Subject: Re: [packer] Error getting SSH address

You picture shows the problem. "Warning: can not boot. Starting emergency shell"

This is most likely a problem with your ks file. Try building a known good one 
such as https://github.com/chef/bento/blob/master/centos/centos-7.4-x86_64.json 
and compare what is different in their ks. If you don't find the cause but 
theirs is working, us it and evolve it in small steps to what you need.

On 16 April 2018 at 18:00, Aaron Kulbe 
mailto:aa...@longviewbits.com>> wrote:
Hi Rickard,

I’m not sure how this is supposed to be easy. I’m guessing I cannot attach 
screenshots to this group list post, but if it doesn’t work, you can see it at 
https://www.dropbox.com/s/w3o23riipmz3fpw/packer_issues.png?dl=0

The VM doesn’t getting a network, so I’m not sure how I can connect to it. On 
the left, is the packer run. On the right is tailing the debug log, and on top 
is the VNC connection to the host.



From: packer-tool@googlegroups.com<mailto:packer-tool@googlegroups.com> 
[mailto:packer-tool@googlegroups.com<mailto:packer-tool@googlegroups.com>] On 
Behalf Of Rickard von Essen
Sent: April 14, 2018 14:43
To: packer-tool@googlegroups.com<mailto:packer-tool@googlegroups.com>

Subject: Re: [packer] Error getting SSH address

This is usually quite easy to troubleshoot, use a playbook a something like 
this:

1) Disable headless, or use VNC
2) Run the build, connect to the console. Check any error messages.
3) After reboot login as root and check what's the status of the network is it 
up, does it have an IP. Do the normal troubleshooting for networking.
4) Check if you can ssh from the host to the guest: ssh -l vagrant .

Interesting things to check where did it receive it's DHCP lease from? If it 
did get one. What's the mac for the NIC etc.

On 14 April 2018 at 21:13, Aaron Kulbe 
mailto:aa...@longviewbits.com>> wrote:
Does that apply if there is no external DHCP server? I’ll draw a text diagram, 
and hope it’ll render okay. Are you saying that the “builder VM” (as diagrammed 
below) is forwarding the DHCP request back upstream to the cluster, in hopes of 
getting an address there?

[target VM] (whose final destination will be the cluster on the bottom)
^
^
^
[builder VM where packer runs] (this VM has to have an IP statically 
configured, as all we have is vRA’s crappy IPAM, and no DHCP)
^
^
^
[vSphere cluster w/vRealize Automation (vRA)]

From: 'Nicholas Bayle' via Packer 
mailto:packer-tool@googlegroups.com>>
Reply-To: "packer-tool@googlegroups.com<mailto:packer-tool@googlegroups.com>" 
mailto:packer-tool@googlegroups.com>>
Date: Saturday, April 14, 2018 at 11:58 AM
To: "packer-tool@googlegroups.com<mailto:packer-tool@googlegroups.com>" 
mailto:packer-tool@googlegroups.com>>
Subject: Re: [packer] Error getting SSH address

I had this issue.

The problem occurs when the host VM has permission to "monitor all traffic" on 
the parent host. The DHCP request ends up going outside the VMware host 
(despite whatever your nat/hostonly settings are) to the parent VMware 
installation or external DHCP server. You can verify this by looking at what 
subnet the VM is supposed to be on ( /etc/vmware/vmnet8/dhcpd/dhcpd.conf) and 
comparing it to the actual IP that the VM receives (VNC to the instance packer 
is building). If you go to your parent DHCP server and look at the leases, you 
will likely find your DHCP lease.

If you can figure out how to deny that traffic, it will get the correct DHCP 
server and the lease will end up in the correct file for packer.

It's all terribly confusing, so hopefully this makes sense.

Nick

On Sat, Apr 14, 2018 at 8:44 AM, Aaron Kulbe 
mailto:aa...@longviewbits.com>> wrote:
I have been using 1.2.2, but I also checked out the latest 1.2.3-dev code, and 
still get the same issue.

Here's my sanitized KS file.



#platform=x86, AMD64, or Intel EM64T
#version=DEVEL
# Install OS instead of upgrade
install
# Keyboard layouts
keyboard 'us'

# Root password
rootpw "$1$" --iscrypted

# System Services
services --enabled="chronyd"
services --enabled="sshd"

# Create default user
user --name=myuser --groups=myuser,wheel
user --name=vagrant --groups=vagrant,wheel --password=vagrant

# System timezone
timezone UTC --utc
# Sy

Re: [packer] Error getting SSH address

[Rickard von Essen]

You picture shows the problem. "Warning: can not boot. Starting emergency
shell"

This is most likely a problem with your ks file. Try building a known good
one such as
https://github.com/chef/bento/blob/master/centos/centos-7.4-x86_64.json and
compare what is different in their ks. If you don't find the cause but
theirs is working, us it and evolve it in small steps to what you need.

On 16 April 2018 at 18:00, Aaron Kulbe  wrote:

> Hi Rickard,
>
>
>
> I’m not sure how this is supposed to be easy. I’m guessing I cannot attach
> screenshots to this group list post, but if it doesn’t work, you can see it
> at https://www.dropbox.com/s/w3o23riipmz3fpw/packer_issues.png?dl=0
>
>
>
> The VM doesn’t getting a network, so I’m not sure how I can connect to it.
> On the left, is the packer run. On the right is tailing the debug log, and
> on top is the VNC connection to the host.
>
>
>
>
>
>
>
> *From:* packer-tool@googlegroups.com [mailto:packer-tool@googlegroups.com]
> *On Behalf Of *Rickard von Essen
> *Sent:* April 14, 2018 14:43
> *To:* packer-tool@googlegroups.com
>
> *Subject:* Re: [packer] Error getting SSH address
>
>
>
> This is usually quite easy to troubleshoot, use a playbook a something
> like this:
>
>
>
> 1) Disable headless, or use VNC
>
> 2) Run the build, connect to the console. Check any error messages.
>
> 3) After reboot login as root and check what's the status of the network
> is it up, does it have an IP. Do the normal troubleshooting for networking.
>
> 4) Check if you can ssh from the host to the guest: ssh -l vagrant .
>
>
>
> Interesting things to check where did it receive it's DHCP lease from? If
> it did get one. What's the mac for the NIC etc.
>
>
>
> On 14 April 2018 at 21:13, Aaron Kulbe  wrote:
>
> Does that apply if there is no external DHCP server? I’ll draw a text
> diagram, and hope it’ll render okay. Are you saying that the “builder VM”
> (as diagrammed below) is forwarding the DHCP request back upstream to the
> cluster, in hopes of getting an address there?
>
>
>
> [*target VM*] (whose final destination will be the cluster on the bottom)
>
> ^
>
> ^
>
> ^
>
> [*builder VM* where packer runs] (this VM has to have an IP statically
> configured, as all we have is vRA’s crappy IPAM, and no DHCP)
>
> ^
>
> ^
>
> ^
>
> [*vSphere cluster* w/vRealize Automation (vRA)]
>
>
>
> *From: *'Nicholas Bayle' via Packer 
> *Reply-To: *"packer-tool@googlegroups.com" 
> *Date: *Saturday, April 14, 2018 at 11:58 AM
> *To: *"packer-tool@googlegroups.com" 
> *Subject: *Re: [packer] Error getting SSH address
>
>
>
> I had this issue.
>
>
>
> The problem occurs when the host VM has permission to "monitor all
> traffic" on the parent host. The DHCP request ends up going outside the
> VMware host (despite whatever your nat/hostonly settings are) to the parent
> VMware installation or external DHCP server. You can verify this by looking
> at what subnet the VM is supposed to be on ( 
> /etc/vmware/vmnet8/dhcpd/dhcpd.conf)
> and comparing it to the actual IP that the VM receives (VNC to the instance
> packer is building). If you go to your parent DHCP server and look at the
> leases, you will likely find your DHCP lease.
>
>
>
> If you can figure out how to deny that traffic, it will get the correct
> DHCP server and the lease will end up in the correct file for packer.
>
>
>
> It's all terribly confusing, so hopefully this makes sense.
>
>
>
> Nick
>
>
>
> On Sat, Apr 14, 2018 at 8:44 AM, Aaron Kulbe 
> wrote:
>
> I have been using 1.2.2, but I also checked out the latest 1.2.3-dev code,
> and still get the same issue.
>
>
>
> Here's my sanitized KS file.
>
>
>
>
>
>
>
> #platform=x86, AMD64, or Intel EM64T
>
> #version=DEVEL
>
> # Install OS instead of upgrade
>
> install
>
> # Keyboard layouts
>
> keyboard 'us'
>
>
>
> # Root password
>
> rootpw "$1$" --iscrypted
>
>
>
> # System Services
>
> services --enabled="chronyd"
>
> services --enabled="sshd"
>
>
>
> # Create default user
>
> user --name=myuser --groups=myuser,wheel
>
> user --name=vagrant --groups=vagrant,wheel --password=vagrant
>
>
>
> # System timezone
>
> timezone UTC --utc
>
> # System language
>
> lang en_US.UTF-8
>
> # Firewall configuration
>
> firewall --disabled
>
> # System authorization information
>
> auth --enableshadow --enablemd5
>
>
>
> # Use 

Re: [packer] Error getting SSH address

[Rickard von Essen]

This is usually quite easy to troubleshoot, use a playbook a something like
this:

1) Disable headless, or use VNC
2) Run the build, connect to the console. Check any error messages.
3) After reboot login as root and check what's the status of the network is
it up, does it have an IP. Do the normal troubleshooting for networking.
4) Check if you can ssh from the host to the guest: ssh -l vagrant .

Interesting things to check where did it receive it's DHCP lease from? If
it did get one. What's the mac for the NIC etc.

On 14 April 2018 at 21:13, Aaron Kulbe  wrote:

> Does that apply if there is no external DHCP server? I’ll draw a text
> diagram, and hope it’ll render okay. Are you saying that the “builder VM”
> (as diagrammed below) is forwarding the DHCP request back upstream to the
> cluster, in hopes of getting an address there?
>
>
>
> [*target VM*] (whose final destination will be the cluster on the bottom)
>
> ^
>
> ^
>
> ^
>
> [*builder VM* where packer runs] (this VM has to have an IP statically
> configured, as all we have is vRA’s crappy IPAM, and no DHCP)
>
> ^
>
> ^
>
> ^
>
> [*vSphere cluster* w/vRealize Automation (vRA)]
>
>
>
> *From: *'Nicholas Bayle' via Packer 
> *Reply-To: *"packer-tool@googlegroups.com" 
> *Date: *Saturday, April 14, 2018 at 11:58 AM
> *To: *"packer-tool@googlegroups.com" 
> *Subject: *Re: [packer] Error getting SSH address
>
>
>
> I had this issue.
>
>
>
> The problem occurs when the host VM has permission to "monitor all
> traffic" on the parent host. The DHCP request ends up going outside the
> VMware host (despite whatever your nat/hostonly settings are) to the parent
> VMware installation or external DHCP server. You can verify this by looking
> at what subnet the VM is supposed to be on ( 
> /etc/vmware/vmnet8/dhcpd/dhcpd.conf)
> and comparing it to the actual IP that the VM receives (VNC to the instance
> packer is building). If you go to your parent DHCP server and look at the
> leases, you will likely find your DHCP lease.
>
>
>
> If you can figure out how to deny that traffic, it will get the correct
> DHCP server and the lease will end up in the correct file for packer.
>
>
>
> It's all terribly confusing, so hopefully this makes sense.
>
>
>
> Nick
>
>
>
> On Sat, Apr 14, 2018 at 8:44 AM, Aaron Kulbe 
> wrote:
>
> I have been using 1.2.2, but I also checked out the latest 1.2.3-dev code,
> and still get the same issue.
>
>
>
> Here's my sanitized KS file.
>
>
>
>
>
>
>
> #platform=x86, AMD64, or Intel EM64T
>
> #version=DEVEL
>
> # Install OS instead of upgrade
>
> install
>
> # Keyboard layouts
>
> keyboard 'us'
>
>
>
> # Root password
>
> rootpw "$1$" --iscrypted
>
>
>
> # System Services
>
> services --enabled="chronyd"
>
> services --enabled="sshd"
>
>
>
> # Create default user
>
> user --name=myuser --groups=myuser,wheel
>
> user --name=vagrant --groups=vagrant,wheel --password=vagrant
>
>
>
> # System timezone
>
> timezone UTC --utc
>
> # System language
>
> lang en_US.UTF-8
>
> # Firewall configuration
>
> firewall --disabled
>
> # System authorization information
>
> auth --enableshadow --enablemd5
>
>
>
> # Use CDROM installation media
>
> cdrom
>
>
>
> # Use text mode install
>
> text
>
>
>
> # SELinux configuration
>
> selinux --permissive
>
>
>
> # Do not configure the X Window System
>
> skipx
>
>
>
> # Network information
>
> network --bootproto=dhcp --device=eth0
>
> network --hostname=localhost.localdomain
>
>
>
> # Reboot after installation
>
> reboot
>
>
>
> # System bootloader configuration
>
> bootloader --location=mbr
>
>
>
> # Disk partitioning information
>
> zerombr
>
> clearpart --all --drives=sda
>
> part /boot --fstype ext4 --size=500
>
> part pv.00 --size=16000 --ondisk=sda
>
> volgroup vg00 pv.00
>
> logvol / --vgname=vg00 --fstype=xfs --size=12288 --name=lv_root
>
> #logvol /home --vgname=vg00 --fstype=xfs --size=2048 --name=lv_home
>
> #logvol /var/log --vgname=vg00 --fstype=xfs --size=2048 --name=lv_varlog
>
>
>
> %packages
>
> # Minimal RHEL install
>
> @core
>
> # Further minimize unneeded packages
>
> -alsa-lib
>
> -mariadb-libs
>
> -parted
>
> -aic94xx-firmware
>
> -iwl*
>
> -plymouth
>
> -firewalld
>
> # Add packages we actually need
>
> chrony
>
> 

Re: [packer] Error getting SSH address

[Aaron Kulbe]

Does that apply if there is no external DHCP server? I’ll draw a text diagram, 
and hope it’ll render okay. Are you saying that the “builder VM” (as diagrammed 
below) is forwarding the DHCP request back upstream to the cluster, in hopes of 
getting an address there?

[target VM] (whose final destination will be the cluster on the bottom)
^
^
^
[builder VM where packer runs] (this VM has to have an IP statically 
configured, as all we have is vRA’s crappy IPAM, and no DHCP)
^
^
^
[vSphere cluster w/vRealize Automation (vRA)]

From: 'Nicholas Bayle' via Packer 
Reply-To: "packer-tool@googlegroups.com" 
Date: Saturday, April 14, 2018 at 11:58 AM
To: "packer-tool@googlegroups.com" 
Subject: Re: [packer] Error getting SSH address

I had this issue.

The problem occurs when the host VM has permission to "monitor all traffic" on 
the parent host. The DHCP request ends up going outside the VMware host 
(despite whatever your nat/hostonly settings are) to the parent VMware 
installation or external DHCP server. You can verify this by looking at what 
subnet the VM is supposed to be on ( /etc/vmware/vmnet8/dhcpd/dhcpd.conf) and 
comparing it to the actual IP that the VM receives (VNC to the instance packer 
is building). If you go to your parent DHCP server and look at the leases, you 
will likely find your DHCP lease.


If you can figure out how to deny that traffic, it will get the correct DHCP 
server and the lease will end up in the correct file for packer.


It's all terribly confusing, so hopefully this makes sense.

Nick

On Sat, Apr 14, 2018 at 8:44 AM, Aaron Kulbe 
mailto:aa...@longviewbits.com>> wrote:
I have been using 1.2.2, but I also checked out the latest 1.2.3-dev code, and 
still get the same issue.

Here's my sanitized KS file.



#platform=x86, AMD64, or Intel EM64T
#version=DEVEL
# Install OS instead of upgrade
install
# Keyboard layouts
keyboard 'us'

# Root password
rootpw "$1$" --iscrypted

# System Services
services --enabled="chronyd"
services --enabled="sshd"

# Create default user
user --name=myuser --groups=myuser,wheel
user --name=vagrant --groups=vagrant,wheel --password=vagrant

# System timezone
timezone UTC --utc
# System language
lang en_US.UTF-8
# Firewall configuration
firewall --disabled
# System authorization information
auth --enableshadow --enablemd5

# Use CDROM installation media
cdrom

# Use text mode install
text

# SELinux configuration
selinux --permissive

# Do not configure the X Window System
skipx

# Network information
network --bootproto=dhcp --device=eth0
network --hostname=localhost.localdomain

# Reboot after installation
reboot

# System bootloader configuration
bootloader --location=mbr

# Disk partitioning information
zerombr
clearpart --all --drives=sda
part /boot --fstype ext4 --size=500
part pv.00 --size=16000 --ondisk=sda
volgroup vg00 pv.00
logvol / --vgname=vg00 --fstype=xfs --size=12288 --name=lv_root
#logvol /home --vgname=vg00 --fstype=xfs --size=2048 --name=lv_home
#logvol /var/log --vgname=vg00 --fstype=xfs --size=2048 --name=lv_varlog

%packages
# Minimal RHEL install
@core
# Further minimize unneeded packages
-alsa-lib
-mariadb-libs
-parted
-aic94xx-firmware
-iwl*
-plymouth
-firewalld
# Add packages we actually need
chrony
tmux
libyaml
ncurses-libs
setools-libs
open-vm-tools
vim-enhanced
yum-utils
net-tools
wget
bzip2
unzip
mtr
nmap-ncat
strace
tcpdump
selinux-policy-devel
libselinux-utils
sssd
realmd
policycoreutils-python
samba-common-tools
krb5-workstation
setools-console
make
openssh-clients
openssh-server
%end

%post --log=/root/ks-post.log
# Register with Red Hat
/usr/sbin/subscription-manager register --org= 
--activationkey=
# Unpinning for now.
/usr/sbin/subscription-manager release --set=7.2

# add extra repos
/usr/sbin/subscription-manager repos --enable rhel-7-server-optional-rpms
/usr/sbin/subscription-manager repos --enable rhel-7-server-rh-common-rpms

# add EPEL and packages on EPEL
wget http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
rpm -ivh epel-release-latest-7.noarch.rpm
yum check-update
yum -y install facter katello-agent mailx yum-utils
yum -y erase mariadb-libs postfix ivtv-firmware emacs-filesystem fxload

# set time
ln -s /usr/share/zoneinfo/UTC /etc/localtime

# Set up regular users & keys
mkdir -p /home/myuser/.ssh/
chmod 700 /home/myuser/.ssh
curl -k http:///myco_CD_rsa.pub -o 
/home/myuser/.ssh/authorized_keys
curl -k http:///myco_CD_DEV_rsa.pub >> 
/home/myuser/.ssh/authorized_keys
chown -R myuser:myuser /home/myuser/.ssh/
chmod 600 /home/myuser/.ssh/authorized_keys
echo "myuser ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers.d/myuser
echo "Defaults:myuser !requiretty" >> /etc/sudoers.d/myuser
chown root:root /etc/sudoers.d/myuser
chmod 440 /etc/sudoers.d/myuser

mkdir -p /home/vagrant/.ssh/
chmod 700 /home/vagrant/.ssh
curl -k http:///myco_CD_rsa.pub -o 
/home/vag

Re: [packer] Error getting SSH address

['Nicholas Bayle' via Packer]

I had this issue.

The problem occurs when the host VM has permission to "monitor all traffic"
on the parent host. The DHCP request ends up going outside the VMware host
(despite whatever your nat/hostonly settings are) to the parent VMware
installation or external DHCP server. You can verify this by looking at
what subnet the VM is supposed to be on ( /etc/vmware/vmnet8/dhcpd/dhcpd.conf)
and comparing it to the actual IP that the VM receives (VNC to the instance
packer is building). If you go to your parent DHCP server and look at the
leases, you will likely find your DHCP lease.

If you can figure out how to deny that traffic, it will get the correct
DHCP server and the lease will end up in the correct file for packer.

It's all terribly confusing, so hopefully this makes sense.

Nick

On Sat, Apr 14, 2018 at 8:44 AM, Aaron Kulbe  wrote:

> I have been using 1.2.2, but I also checked out the latest 1.2.3-dev code,
> and still get the same issue.
>
> Here's my sanitized KS file.
>
>
>
> #platform=x86, AMD64, or Intel EM64T
> #version=DEVEL
> # Install OS instead of upgrade
> install
> # Keyboard layouts
> keyboard 'us'
>
> # Root password
> rootpw "$1$" --iscrypted
>
> # System Services
> services --enabled="chronyd"
> services --enabled="sshd"
>
> # Create default user
> user --name=myuser --groups=myuser,wheel
> user --name=vagrant --groups=vagrant,wheel --password=vagrant
>
> # System timezone
> timezone UTC --utc
> # System language
> lang en_US.UTF-8
> # Firewall configuration
> firewall --disabled
> # System authorization information
> auth --enableshadow --enablemd5
>
> # Use CDROM installation media
> cdrom
>
> # Use text mode install
> text
>
> # SELinux configuration
> selinux --permissive
>
> # Do not configure the X Window System
> skipx
>
> # Network information
> network --bootproto=dhcp --device=eth0
> network --hostname=localhost.localdomain
>
> # Reboot after installation
> reboot
>
> # System bootloader configuration
> bootloader --location=mbr
>
> # Disk partitioning information
> zerombr
> clearpart --all --drives=sda
> part /boot --fstype ext4 --size=500
> part pv.00 --size=16000 --ondisk=sda
> volgroup vg00 pv.00
> logvol / --vgname=vg00 --fstype=xfs --size=12288 --name=lv_root
> #logvol /home --vgname=vg00 --fstype=xfs --size=2048 --name=lv_home
> #logvol /var/log --vgname=vg00 --fstype=xfs --size=2048 --name=lv_varlog
>
> %packages
> # Minimal RHEL install
> @core
> # Further minimize unneeded packages
> -alsa-lib
> -mariadb-libs
> -parted
> -aic94xx-firmware
> -iwl*
> -plymouth
> -firewalld
> # Add packages we actually need
> chrony
> tmux
> libyaml
> ncurses-libs
> setools-libs
> open-vm-tools
> vim-enhanced
> yum-utils
> net-tools
> wget
> bzip2
> unzip
> mtr
> nmap-ncat
> strace
> tcpdump
> selinux-policy-devel
> libselinux-utils
> sssd
> realmd
> policycoreutils-python
> samba-common-tools
> krb5-workstation
> setools-console
> make
> openssh-clients
> openssh-server
> %end
>
> %post --log=/root/ks-post.log
> # Register with Red Hat
> /usr/sbin/subscription-manager register --org=
> --activationkey=
> # Unpinning for now.
> /usr/sbin/subscription-manager release --set=7.2
>
> # add extra repos
> /usr/sbin/subscription-manager repos --enable rhel-7-server-optional-rpms
> /usr/sbin/subscription-manager repos --enable rhel-7-server-rh-common-rpms
>
> # add EPEL and packages on EPEL
> wget http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
> rpm -ivh epel-release-latest-7.noarch.rpm
> yum check-update
> yum -y install facter katello-agent mailx yum-utils
> yum -y erase mariadb-libs postfix ivtv-firmware emacs-filesystem fxload
>
> # set time
> ln -s /usr/share/zoneinfo/UTC /etc/localtime
>
> # Set up regular users & keys
> mkdir -p /home/myuser/.ssh/
> chmod 700 /home/myuser/.ssh
> curl -k http:///myco_CD_rsa.pub -o
> /home/myuser/.ssh/authorized_keys
> curl -k http:///myco_CD_DEV_rsa.pub >>
> /home/myuser/.ssh/authorized_keys
> chown -R myuser:myuser /home/myuser/.ssh/
> chmod 600 /home/myuser/.ssh/authorized_keys
> echo "myuser ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers.d/myuser
> echo "Defaults:myuser !requiretty" >> /etc/sudoers.d/myuser
> chown root:root /etc/sudoers.d/myuser
> chmod 440 /etc/sudoers.d/myuser
>
> mkdir -p /home/vagrant/.ssh/
> chmod 700 /home/vagrant/.ssh
> curl -k http:///myco_CD_rsa.pub -o
> /home/vagrant/.ssh/authorized_keys
> chown -R vagrant:vagrant /home/vagrant/.ssh/
> chmod 600 /home/vagrant/.ssh/authorized_keys
> echo "vagrant ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers.d/vagrant
> echo "Defaults:vagrant !requiretty" >> /etc/sudoers.d/vagrant
> chown root:root /etc/sudoers.d/vagrant
> chmod 440 /etc/sudoers.d/vagrant
>
> # Set up Manifest generation
> echo "export BASE_IMAGE_VERSION=1.3.0" > /etc/profile.d/baseimage.sh
> chmod +x /etc/profile.d/baseimage.sh
>
> curl -k http:///generate_manifest.sh -o
> /home/myuser/generate_manifest.sh
> chmod +x /home/myuser/generate_manifest.sh
>
> # update everything
> yum -y update
>
> %end
>
>
> On S

Re: [packer] Error getting SSH address

[Aaron Kulbe]

I have been using 1.2.2, but I also checked out the latest 1.2.3-dev code, 
and still get the same issue. 

Here's my sanitized KS file.



#platform=x86, AMD64, or Intel EM64T
#version=DEVEL
# Install OS instead of upgrade
install
# Keyboard layouts
keyboard 'us'

# Root password
rootpw "$1$" --iscrypted

# System Services
services --enabled="chronyd"
services --enabled="sshd"

# Create default user
user --name=myuser --groups=myuser,wheel
user --name=vagrant --groups=vagrant,wheel --password=vagrant

# System timezone
timezone UTC --utc
# System language
lang en_US.UTF-8
# Firewall configuration
firewall --disabled
# System authorization information
auth --enableshadow --enablemd5

# Use CDROM installation media
cdrom

# Use text mode install
text

# SELinux configuration
selinux --permissive

# Do not configure the X Window System
skipx

# Network information
network --bootproto=dhcp --device=eth0
network --hostname=localhost.localdomain

# Reboot after installation
reboot

# System bootloader configuration
bootloader --location=mbr

# Disk partitioning information
zerombr
clearpart --all --drives=sda
part /boot --fstype ext4 --size=500
part pv.00 --size=16000 --ondisk=sda
volgroup vg00 pv.00
logvol / --vgname=vg00 --fstype=xfs --size=12288 --name=lv_root
#logvol /home --vgname=vg00 --fstype=xfs --size=2048 --name=lv_home
#logvol /var/log --vgname=vg00 --fstype=xfs --size=2048 --name=lv_varlog

%packages
# Minimal RHEL install
@core
# Further minimize unneeded packages
-alsa-lib
-mariadb-libs
-parted
-aic94xx-firmware
-iwl*
-plymouth
-firewalld
# Add packages we actually need
chrony
tmux
libyaml
ncurses-libs
setools-libs
open-vm-tools
vim-enhanced
yum-utils
net-tools
wget
bzip2
unzip
mtr
nmap-ncat
strace
tcpdump
selinux-policy-devel
libselinux-utils
sssd
realmd
policycoreutils-python
samba-common-tools
krb5-workstation
setools-console
make
openssh-clients
openssh-server
%end

%post --log=/root/ks-post.log
# Register with Red Hat
/usr/sbin/subscription-manager register --org= 
--activationkey=
# Unpinning for now.
/usr/sbin/subscription-manager release --set=7.2

# add extra repos
/usr/sbin/subscription-manager repos --enable rhel-7-server-optional-rpms
/usr/sbin/subscription-manager repos --enable rhel-7-server-rh-common-rpms

# add EPEL and packages on EPEL
wget http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
rpm -ivh epel-release-latest-7.noarch.rpm
yum check-update
yum -y install facter katello-agent mailx yum-utils
yum -y erase mariadb-libs postfix ivtv-firmware emacs-filesystem fxload

# set time
ln -s /usr/share/zoneinfo/UTC /etc/localtime

# Set up regular users & keys
mkdir -p /home/myuser/.ssh/
chmod 700 /home/myuser/.ssh
curl -k http:///myco_CD_rsa.pub -o 
/home/myuser/.ssh/authorized_keys
curl -k http:///myco_CD_DEV_rsa.pub >> 
/home/myuser/.ssh/authorized_keys
chown -R myuser:myuser /home/myuser/.ssh/
chmod 600 /home/myuser/.ssh/authorized_keys
echo "myuser ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers.d/myuser
echo "Defaults:myuser !requiretty" >> /etc/sudoers.d/myuser
chown root:root /etc/sudoers.d/myuser
chmod 440 /etc/sudoers.d/myuser

mkdir -p /home/vagrant/.ssh/
chmod 700 /home/vagrant/.ssh
curl -k http:///myco_CD_rsa.pub -o 
/home/vagrant/.ssh/authorized_keys
chown -R vagrant:vagrant /home/vagrant/.ssh/
chmod 600 /home/vagrant/.ssh/authorized_keys
echo "vagrant ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers.d/vagrant
echo "Defaults:vagrant !requiretty" >> /etc/sudoers.d/vagrant
chown root:root /etc/sudoers.d/vagrant
chmod 440 /etc/sudoers.d/vagrant

# Set up Manifest generation
echo "export BASE_IMAGE_VERSION=1.3.0" > /etc/profile.d/baseimage.sh
chmod +x /etc/profile.d/baseimage.sh

curl -k http:///generate_manifest.sh -o 
/home/myuser/generate_manifest.sh
chmod +x /home/myuser/generate_manifest.sh

# update everything
yum -y update

%end


On Saturday, April 14, 2018 at 4:06:49 AM UTC-7, Rickard von Essen wrote:
>
> (Change management)... There have been some fixes around this is 1.2.1 and 
> 1.2.2 be sure to test it with 1.2.2. 
>
> If that doesn't solve it provide your KS file so we can comment on it.
>
> On 14 April 2018 at 04:41, Aaron Kulbe  > wrote:
>
>> The management won't let us run packer builds on vSphere yet. So we're 
>> stuck standing up a VM with nested virt enabled on it.
>>
>> When I attempt to do a build, I get this in the log:
>>
>> 2018/04/14 01:01:03 packer: 2018/04/14 01:01:03 [DEBUG] Error getting SSH 
>> address: IP lookup failed: None of the found device(s) [vmnet8] has a DHCP 
>> lease for MAC 00:0c:29:81:91:5d
>> 2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 Located networkmapper 
>> configuration file using Workstation: /etc/vmware/netmap.conf
>> 2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 GuestIP discovered device 
>> matching nat: vmnet8
>> 2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 Lookup up IP 
>> information...
>> 2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 GuestAddress found MAC 
>> address in VMX: 00:0c:29:81:91:5d
>> 2018/04

Re: [packer] Error getting SSH address

[Rickard von Essen]

(Change management)... There have been some fixes around this is 1.2.1 and
1.2.2 be sure to test it with 1.2.2.

If that doesn't solve it provide your KS file so we can comment on it.

On 14 April 2018 at 04:41, Aaron Kulbe  wrote:

> The management won't let us run packer builds on vSphere yet. So we're
> stuck standing up a VM with nested virt enabled on it.
>
> When I attempt to do a build, I get this in the log:
>
> 2018/04/14 01:01:03 packer: 2018/04/14 01:01:03 [DEBUG] Error getting SSH
> address: IP lookup failed: None of the found device(s) [vmnet8] has a DHCP
> lease for MAC 00:0c:29:81:91:5d
> 2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 Located networkmapper
> configuration file using Workstation: /etc/vmware/netmap.conf
> 2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 GuestIP discovered device
> matching nat: vmnet8
> 2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 Lookup up IP information...
> 2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 GuestAddress found MAC
> address in VMX: 00:0c:29:81:91:5d
> 2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 Trying DHCP leases path:
> /etc/vmware/vmnet8/dhcpd/dhcpd.leases
> 2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 IP lookup failed: None of
> the found device(s) [vmnet8] has a DHCP lease for MAC 00:0c:29:81:91:5d
>
> (it repeats continuously)
>
> Here is my template:
>
> ➜  build_here cat rhel72.json
> {
>   "builders": [
> {
>   "type": "vmware-iso",
>   "boot_command": [
> " text biosdevname=0 net.ifnames=0
> ks=hd:fd0/baseimage_130_72.cfg"
>   ],
>   "boot_wait": "15s",
>   "disk_size": "20480",
>   "guest_os_type": "rhel7-64",
>   "headless": true,
>   "iso_urls": [
> "rhel-server-7.2-x86_64-dvd.iso"
>   ],
>   "floppy_files": [ "http/baseimage_130_72.cfg" ],
>   "iso_checksum_type": "sha256",
>   "iso_checksum": "03f3a0291634335f6995534d829bd2
> 1ffaa0d04dfeb1b2fb81052d64a4d5",
>   "ssh_username": "vagrant",
>   "ssh_password": "vagrant",
>   "ssh_port": 22,
>   "ssh_wait_timeout": "2s",
>   "shutdown_command": "echo 'vagrant'|sudo -S /sbin/halt -h -p",
>   "tools_upload_flavor": "linux",
>   "vm_name": "packer-rhel-72-x86_64",
>   "vnc_port_min": "5902",
>   "vnc_port_max": "5902",
>   "vnc_disable_password": true,
>   "network": "nat",
>   "vmx_data": {
> "cpuid.coresPerSocket": "1",
> "memsize": "1024",
> "numvcpus": "1"
>   }
> }
>   ],
>   "post-processors": [
> {
>   "output": "builds/{{.Provider}}-rhel72.box",
>   "type": "vagrant",
>   "keep_input_artifact": true
> },
> {
>   "type": "ovftool",
>   "only": [
> "vmware-iso"
>   ],
>   "format": "ova"
> }
>   ]
> }
>
> --
> 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 Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to packer-tool+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/packer-tool/75afbb96-e1cb-4879-962f-6d2b30c32f30%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/CALz9Rt-i3H8iX%3Dupjjcd7mBH6Vz_UTCZiuRU9OyqrfNBahUnuw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[packer] Error getting SSH address

[Aaron Kulbe]

The management won't let us run packer builds on vSphere yet. So we're 
stuck standing up a VM with nested virt enabled on it.

When I attempt to do a build, I get this in the log:

2018/04/14 01:01:03 packer: 2018/04/14 01:01:03 [DEBUG] Error getting SSH 
address: IP lookup failed: None of the found device(s) [vmnet8] has a DHCP 
lease for MAC 00:0c:29:81:91:5d
2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 Located networkmapper 
configuration file using Workstation: /etc/vmware/netmap.conf
2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 GuestIP discovered device 
matching nat: vmnet8
2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 Lookup up IP information...
2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 GuestAddress found MAC 
address in VMX: 00:0c:29:81:91:5d
2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 Trying DHCP leases path: 
/etc/vmware/vmnet8/dhcpd/dhcpd.leases
2018/04/14 01:01:08 packer: 2018/04/14 01:01:08 IP lookup failed: None of 
the found device(s) [vmnet8] has a DHCP lease for MAC 00:0c:29:81:91:5d

(it repeats continuously)

Here is my template:

➜  build_here cat rhel72.json
{
  "builders": [
{
  "type": "vmware-iso",
  "boot_command": [
" text biosdevname=0 net.ifnames=0 
ks=hd:fd0/baseimage_130_72.cfg"
  ],
  "boot_wait": "15s",
  "disk_size": "20480",
  "guest_os_type": "rhel7-64",
  "headless": true,
  "iso_urls": [
"rhel-server-7.2-x86_64-dvd.iso"
  ],
  "floppy_files": [ "http/baseimage_130_72.cfg" ],
  "iso_checksum_type": "sha256",
  "iso_checksum": 
"03f3a0291634335f6995534d829bd21ffaa0d04dfeb1b2fb81052d64a4d5",
  "ssh_username": "vagrant",
  "ssh_password": "vagrant",
  "ssh_port": 22,
  "ssh_wait_timeout": "2s",
  "shutdown_command": "echo 'vagrant'|sudo -S /sbin/halt -h -p",
  "tools_upload_flavor": "linux",
  "vm_name": "packer-rhel-72-x86_64",
  "vnc_port_min": "5902",
  "vnc_port_max": "5902",
  "vnc_disable_password": true,
  "network": "nat",
  "vmx_data": {
"cpuid.coresPerSocket": "1",
"memsize": "1024",
"numvcpus": "1"
  }
}
  ],
  "post-processors": [
{
  "output": "builds/{{.Provider}}-rhel72.box",
  "type": "vagrant",
  "keep_input_artifact": true
},
{
  "type": "ovftool",
  "only": [
"vmware-iso"
  ],
  "format": "ova"
}
  ]
}

-- 
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 Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/75afbb96-e1cb-4879-962f-6d2b30c32f30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.