-
Notifications
You must be signed in to change notification settings - Fork 17
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
fix(windows/fast-launch): the fast-launch step fail in packer on the main branch #1769
base: main
Are you sure you want to change the base?
fix(windows/fast-launch): the fast-launch step fail in packer on the main branch #1769
Conversation
here are the log for
took 24mn for the AMI to become ready I was propose within the AWS console UI to enable fast-launch, I did try and it worked. |
as planned the build with
|
no EC2Launch in
|
WIP
as per jenkins-infra/helpdesk#4565
lets disable this fast-launch feature for now and activate the publish for this PR only : green - #1769 (comment)
now lets revert to fast-launch enable with activate the publish for this PR only : red - #1769 (comment)
lets try to repair the sysprep by changing the delimiter : - https://infra.ci.jenkins.io/job/infra-tools/job/packer-images/job/PR-1769/4/pipeline-console/?selected-node=150 - red
check the installation of ec2launch and if not installed, lets install the latest version with https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2launch-download.html
==================================
the fast-launch option need the sysprep to work, last green build on main shows that sysprep was working:
whereas it's not anymore: