Skip to content
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 crashed while building EKS Anywhere node image for cloudstack #13104

Closed
rugboo opened this issue Jul 9, 2024 · 2 comments
Closed

Packer crashed while building EKS Anywhere node image for cloudstack #13104

rugboo opened this issue Jul 9, 2024 · 2 comments
Labels

Comments

@rugboo
Copy link

rugboo commented Jul 9, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Overview of the Issue

I'm running image-builder on Ubuntu 22.04 server EC2 metal instance.
As I can understand fro the attached log the connection to qemu vm closes unexpectedly which causes the flow failure.

Reproduction Steps

Running the image build by the instruction here

Packer version

Packer v1.11.1

Operating system and Environment details

Using Cloud9 environment with EC2 instance of type m5.metal and OS Ubuntu server 22.04.
The OS image ISO - Red Hat Enterprise Linux 8.9 Binary DVD
Purpose: to use created image to instantiate CloudStack 4.19 VMs as EKS Anywhere nodes.

Log Fragments and crash.log files

crash.log

@rugboo rugboo added the bug label Jul 9, 2024
@rugboo rugboo closed this as completed Jul 11, 2024
@rugboo
Copy link
Author

rugboo commented Jul 11, 2024

The issue was the incorrect qemu-system-x86_64 executable I used. Once I fixed this the image-builder completed the flow successfully.

Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant