Merge ~smoser/cloud-init:bug/1701325-no-dmi-data-in-container into cloud-init:master
| Status: | Merged |
|---|---|
| Merged at revision: | 4d9f24f5c385cb7fa21d87a097ccd9a297613a75 |
| Proposed branch: | ~smoser/cloud-init:bug/1701325-no-dmi-data-in-container |
| Merge into: | cloud-init:master |
| Diff against target: |
65 lines (+30/-0) 2 files modified
cloudinit/util.py (+7/-0) tests/unittests/test_util.py (+23/-0) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Server Team CI bot | continuous-integration | Approve on 2017-06-29 | |
| Joshua Powers (community) | Approve on 2017-06-29 | ||
| Ryan Harper | 2017-06-29 | Approve on 2017-06-29 | |
|
Review via email:
|
|||
Commit Message
read_dmi_data: always return None when inside a container.
This fixes stacktrace and warning message that would be printed
to the log if running inside a container and read_dmi_data tried
to access a key that was not present.
In a container, the /sys/class/dmi/id data is not relevant to the
but to the host. Additionally an unpriviledged container might see
strange behavior:
# cd /sys/class/dmi/id/
# id -u
0
# ls -l chassis_serial
-r-------- 1 nobody nogroup 4096 Jun 29 16:49 chassis_serial
# cat chassis_serial
cat: /sys/class/
The solution here is to just always return None when running in a
container.
LP: #1701325
FAILED: Continuous integration, rev:2a60190bbc4
https:/
Executed test runs:
SUCCESS: Checkout
FAILED: Unit & Style Tests
Click here to trigger a rebuild:
https:/
| Joshua Powers (powersj) wrote : | # |
+1 once this is fixed:
tests/unittests
Create artful container, upgraded to built version of deb, rebooted. Cleaned out /var/lib/cloud (kept seed) and /var/log/
PASSED: Continuous integration, rev:
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
SUCCESS: CentOS 6 & 7: Build & Test
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild:
https:/
PASSED: Continuous integration, rev:b308922a729
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
SUCCESS: CentOS 6 & 7: Build & Test
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild:
https:/
PASSED: Continuous integration, rev:5e35beb8838
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
SUCCESS: CentOS 6 & 7: Build & Test
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild:
https:/


This is a good fix.