-
Notifications
You must be signed in to change notification settings - Fork 393
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
build-qemu-ubuntu-2204 stuck in "Waiting for SSH to become available..." #1076
Comments
Could you try running the build with |
@wwentland Thanks for your response.
|
Thank you! Right, this is to be expected if it is a headless box. You could try connecting via VNC or reproduce the issue locally. You would have to adjust the address to which vnc binds to Does it hang every time, or are there some builds that work and others that hang? How often have you tried? |
I can also confirm this. We are building our images in on a headless machine within a CI-CD pipeline. It happens every time for us. Will try to investigate according to your suggestions. |
The problem is resolved for us at least. CI-CD now works again. Regarding the reason: I honestly cannot tell you. Seems that it was just a hick-up. |
That's great to hear @tibeer. I only ever ran into a stuck build once, but it failed much earlier in the process (error while entering the boot command). I'm not seeing anything obvious in the output you pasted and it might have just been taking a long time installing the base system. This could very well be due to problems in the build environment (e.g. network issues) that only present themselves intermittedly, but aren't directly caused by a misconfiguration of the build process. |
same issue here :( @tibeer If you can try to remember what solved your problem it would be <3 |
ok .. So I just read the documentation ;-S https://developer.hashicorp.com/packer/plugins/builders/qemu
It seems that some kind of template is missing , And it must be a common mistake. |
having the same issue :( hoping someone would found what's missing :( |
@xinity I'm also hitting this atm, locally on my computer, the build was eventually completed:
yikes! But I don't know what build times to expect either, did you ever wait to see if it was completed? If made the following changes to cut off ~10min: diff --git a/images/capi/packer/qemu/qemu-ubuntu-2204.json b/images/capi/packer/qemu/qemu-ubuntu-2204.json
index 65efe6be0..1f620abc6 100644
--- a/images/capi/packer/qemu/qemu-ubuntu-2204.json
+++ b/images/capi/packer/qemu/qemu-ubuntu-2204.json
@@ -3,9 +3,9 @@
"build_name": "ubuntu-2204",
"distro_name": "ubuntu",
"guest_os_type": "ubuntu-64",
- "iso_checksum": "10f19c5b2b8d6db711582e0e27f5116296c34fe4b313ba45f9b201a5007056cb",
+ "iso_checksum": "5e38b55d57d94ff029719342357325ed3bda38fa80054f9330dc789cd2d43931",
"iso_checksum_type": "sha256",
- "iso_url": "https://old-releases.ubuntu.com/releases/jammy/ubuntu-22.04.1-live-server-amd64.iso",
+ "iso_url": "https://releases.ubuntu.com/jammy/ubuntu-22.04.2-live-server-amd64.iso",
"os_display_name": "Ubuntu 22.04",
"shutdown_command": "shutdown -P now",
"unmount_iso": "true" Not directly solving any issues here but using a newer Ubuntu 22.04 base iso so that the package upgrade steps take less time. The original Ubuntu iso used is around a year old now, with quite a bit of delta in terms of missing package upgrades. |
will try that out today and let you know 🤞 |
Came across this issue as well. After 22min i cancelled the first run as it seemed to have stucked on After that I made the changes recommended by @mikejoh which seems to have "solved it". I speculate that because the default image is rather old, the package upgrade step takes too long, and depending on the environment might even pass the ssh timeout set by packer, or the patience of the user (like me who killed the first run after 22min assuming it was stuck). So using the newer image made the package upgrade faster and after ~10min i get into the config phase. Not sure what an appropriate fix would be for this. Bump the packer ssh timeout, document it and "periodically" update the base images to newer? |
@nikParasyr 👍🏻 As a side note to this, I'm not sure if the Ubuntu 22.04 image actually works and boots correctly. I'm evaluating CAPI + CAPO at the moment, I've only managed to build the image but not tested it! |
@mikejoh I ran into some issues well that i couldnt troubleshoot. People in the capo slack channel pointed out to me that the are running ubuntu 22.04 images but they are built with https://image-builder.sigs.k8s.io/capi/providers/openstack-remote.html and not the qemu-builder. the openstack-remote provider worked for me as well. I've opened a ticket (#1137) with my findings for the qemu built. I hope this helps |
Maybe it's time to stop using ubuntu legacy live iso image for newest releases ? I observed that it's seems to be the main cause of all these problems. So (on my side) I'm currently replacing ubuntu image & script used by image-builder, using this server cloudimg and everything works like a charm. |
I think this indeed is an issue stemming from the fact that we have a very big apt upgrade that happens. |
Hi @BarthV, any chance you can share the config you're using to build from the cloudimg? Thx! |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
For 22.04, I had similar issue with provider "vsphere" with command: It turns out, the VM IP changes due to reboot (I workaround it by forcing VM IP back with netplan apply). |
Just a warning, for those who are using the latest image, there has been some changes that break things. vexxhost/magnum-cluster-api#378 So you would end up with non functional images. |
Hey @abrahamhwj , have you found any workaround for this? For me proxmox build is stuck in same place. If i check the terminal, i see that new VM is stuck on language selection screen. |
@BarthV could you share more details please what exactly needs to be updated so that cloudimg would work? |
OK, it took me a while, but it seems i have figured it out. So in my case i was building proxmox template, and got
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Hi,
I installed the image builder based on this doc.
Then to building an image for Openstack I use this doc.
But with this command
make build-qemu-ubuntu-2204
it stucks in the ssh step.My operating system is ubuntu 22.04
This is the log of the command:
/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]
The text was updated successfully, but these errors were encountered: