You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
Community Note
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
The text was updated successfully, but these errors were encountered: