Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A arch-boxes
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch Linux
  • arch-boxes
  • Issues
  • #94
Closed
Open
Created Feb 26, 2020 by Sven-Hendrik Haase@svenstaroContributor

[Bug] Build timeout

Created by: juadde

Describe the bug Build does not finish anymore with latest changes.

To Reproduce Steps to reproduce the behavior:

  1. Fetch latest master branch
  2. run packer build -only=virtualbox-iso local.json or packer build cloud.json
  3. Wait for ssh_timeout to end (> 2h)
  4. Build does not finish

Expected behavior Build should finish successfully.

Screenshots & Logs VM does not restart, even if "systemctl reboot" is sent to the machine. The VMs is stuck here: Build

Packer finishes with the following error:

Build 'virtualbox-iso' errored: Timeout waiting for SSH. ==> Some builds didn't complete successfully and had errors: --> virtualbox-iso: Timeout waiting for SSH. ==> Builds finished but no artifacts were created.

Host Software (please complete the following information):

  • OS: Windows / Linux
  • Distribution: 10 Pro / Archlinux
  • Vagrant Version: 2.2.7
  • Packer: 1.5.4
  • Hypervisor: Virtualbox
  • Hypervisor Version: 6.1.4
  • Image Version: Current master branch
  • Output of uname -a: N/A
  • Vagrant Plugins: vagrant-reload (0.0.1, global), vagrant-timezone (1.3.0, global), vagrant-vbguest (0.20.0, global), vagrant-windows-update (0.0.7, global), vagrant_reboot_linux (1.0.0, global)

Additional context Build is successful on those machines before the changes for the cloud scripts (Rebuilding the arch-box from an older commit is working properly). I will investigate to get the exact commit where the build begin to fail and report here: ea7869f1 is working properly.

Please let me know if anybody have a clue on what is happening.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking