hashicorp/packer

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

Open

#6,119 建立於 2018年4月8日

在 GitHub 查看
 (0 留言) (0 反應) (1 負責人)Go (13,697 star) (3,228 fork)batch import
bugbuilder/lxccommunity-supported-pluginhelp wantedremote-plugin/lxc

描述

  • 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.

貢獻者指南

技術棧
goshell
領域
devopsinfrastructure
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
basic understanding of Gofamiliarity with Packer buildsknowledge of LXC filesystem
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
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.