containers cannot replace /etc/hostname causing service failures on startup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Alex Schultz |
Bug Description
If /etc/hostname is grabbed during the container configuration process, the container startup will fail with something like:
INFO:__
INFO:__
ERROR:_
Traceback (most recent call last):
File "/usr/local/
execute_
File "/usr/local/
copy_
File "/usr/local/
config_
File "/usr/local/
self.
File "/usr/local/
os.
File "/usr/local/
self.
File "/usr/local/
self.
File "/usr/local/
os.remove(path)
OSError: [Errno 16] Device or resource busy: '/etc/hostname'
This stems from the fact that /etc/hostname is a special file in docker (and podman) which cannot be removed. The content can be replaced but it cannot be removed.
Changed in tripleo: | |
importance: | Medium → High |
Fix proposed to branch: master /review. opendev. org/738490
Review: https:/