-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
packer build -only=vmware-iso -var-file=ubuntu2004.json ubuntu.json - stuck #196
Comments
When I looked at this last, packer hadn't yet been upgraded to work with VMware Workstation 16/VMware Fusion 12. Apparently the way the desktop products handle ip addresses has changed significantly. I ended up downgrading to VMware Workstation 15 to get my packer builds to work as I didn't have time to look at it more thoroughly. Might still be an issue.
There was an open issue I was looking at around this - lemme see if I can pull it up. hashicorp/packer#10009 <hashicorp/packer#10009>
Ah yes, netmap.conf isn't generate in VMware Workstation 16, which packer was using to determin ip addresses.
This was back in October when I looked it at, so the status might have changed, but the issue is still open.
… On Dec 30, 2020, at 3:13 PM, Kon Papazis ***@***.***> wrote:
packer build -only=vmware-iso -var-file=ubuntu2004.json ubuntu.json
gets stuck at :
mware-iso: Waiting for SSH to become available... (in terminal)
finish: subiquity/Refresh: SUCCESS: completed (in vmware workstation 16.1.0)
any ideas?
thanks
<https://user-images.githubusercontent.com/5752483/103385928-a73a1300-4b50-11eb-937e-0200d01b32ae.PNG>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#196>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC7FMAZDMIJKCB5VQIKSZPDSXOXX3ANCNFSM4VOZ5DNA>.
|
Hi boxcutter-robot thanks for your feedback. |
Other than that without trying the template, looks like rasa merged a change to the subiquity installer recently. You might want to try reverting that commit to see if that helps. It looks like the ubuntu 20.04 support is new and I don't think anyone has tried it with VMware. You might have to play with it a bit to sort out the exact issue. In another source tree I was able to use the old preseed files with ubuntu 20.04 just fine with VMware Workstation without modification. I'm not sure about these new subiquity replacements as I've never used those before myself.
I don't have time ATM to try it myself and troubleshoot, so that's the best I can do eyeballing it. Sorry.
… On Jan 2, 2021, at 9:35 PM, Kon Papazis ***@***.***> wrote:
When I looked at this last, packer hadn't yet been upgraded to work with VMware Workstation 16/VMware Fusion 12. Apparently the way the desktop products handle ip addresses has changed significantly. I ended up downgrading to VMware Workstation 15 to get my packer builds to work as I didn't have time to look at it more thoroughly. Might still be an issue. There was an open issue I was looking at around this - lemme see if I can pull it up. hashicorp/packer#10009 <hashicorp/packer#10009> <hashicorp/packer#10009 <hashicorp/packer#10009>> Ah yes, netmap.conf isn't generate in VMware Workstation 16, which packer was using to determin ip addresses. This was back in October when I looked it at, so the status might have changed, but the issue is still open.
… <x-msg://1/#>
On Dec 30, 2020, at 3:13 PM, Kon Papazis @.***> wrote: packer build -only=vmware-iso -var-file=ubuntu2004.json ubuntu.json gets stuck at : mware-iso: Waiting for SSH to become available... (in terminal) finish: subiquity/Refresh: SUCCESS: completed (in vmware workstation 16.1.0) any ideas? thanks https://user-images.githubusercontent.com/5752483/103385928-a73a1300-4b50-11eb-937e-0200d01b32ae.PNG <https://user-images.githubusercontent.com/5752483/103385928-a73a1300-4b50-11eb-937e-0200d01b32ae.PNG> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#196 <#196>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC7FMAZDMIJKCB5VQIKSZPDSXOXX3ANCNFSM4VOZ5DNA <https://github.com/notifications/unsubscribe-auth/AC7FMAZDMIJKCB5VQIKSZPDSXOXX3ANCNFSM4VOZ5DNA>.
Hi boxcutter-robot
thanks for your feedback.
however, i have installed vmware workstation 15.5.6 and it still gets stuck at same phase: Waiting for SSH to become available.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#196 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC7FMA7C5EY3PN6MNJH22FDSX763DANCNFSM4VOZ5DNA>.
|
I made the changes to use the subiquity installer. Indeed it is pretty new so there was much trial and error to get it working correctly and I only have virtualbox to test with. From your screenshot it looks like the subiquity installer at least started and was running. The number one problem that most people are having with subiquity and packer is the fact that it starts its own ssh server during the install. Packer relies on the ssh server becoming available after the install is finished. The currently recommended way to handle this is with the |
I installed a trial of VMWare Worksatation 16.1.0 and managed to get it to complete the install but then packer still hung waiting for ssh. It looks like a problem with the network configuration. The part that is causing the issue for you is the network configuration in the user-data file. It looks like the default adapter name for virtualbox differs from vmware. Try removing the network configuration section from the user-data file and see if you get further. After I removed that part it completed the subiquity installer and rebooted the vm. I can ssh into the vm myself, but it keeps coming up with a different dhcp address than what packer is waiting for. I can't quite figure out this part. |
packer build -only=vmware-iso -var-file=ubuntu2004.json ubuntu.json
gets stuck at :
mware-iso: Waiting for SSH to become available... (in terminal)
finish: subiquity/Refresh: SUCCESS: completed (in vmware workstation 16.1.0)
any ideas?
thanks
The text was updated successfully, but these errors were encountered: