hashicorp/packer

Packer fails to perform cleanup if one of the files in a LXC container is immutable

Open

#6119 opened on Apr 8, 2018

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Go (13,697 stars) (3,228 forks)batch import
bugbuilder/lxccommunity-supported-pluginhelp wantedremote-plugin/lxc

Description

  • Packer version from packer version: 1.2.2
  • Host platform: Ubuntu 17.10

You can find a reproducible test case and the logs at: https://gist.github.com/thedrow/5858891db0e99eabfcd1dfd7ee80126f

Fortunately, the build still exists with 0 so I can perform the cleanup manually in CI.

Contributor guide

Tech stack
goshell
Domain
devopsinfrastructure
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic understanding of Gofamiliarity with Packer buildsknowledge of LXC filesystem
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Review the provided gist (https://gist.github.com/thedrow/5858891db0e99eabfcd1dfd7ee80126f) to understand the reproduction steps and logs. The issue occurs when an immutable file exists in the LXC container during cleanup. Look into Packer's LXC builder source code (likely in `builder/lxc/` directory) to identify where cleanup fails. The fix should handle the case where `chattr` or similar operations are needed to remove immutability before deletion. Check if there are any existing tests for cleanup in LXC builder and consider adding a test case for this scenario.