[SRU] ConfigDrive datasource fails when metadata files is null
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Unassigned |
Bug Description
SRU Justification
[IMPACT] On Ubuntu 12.04, cloud-init fails to provision when ConfigDrive data has a null value for "files". Instances are DOA.
[FIX] Cloud-init should check if "files" is a valid value.
[REGRESSION POTENTIAL] This change is low-risk as it is error-hardening.
[TEST CASES 1] :
1. Build new images from proposed
2. Boot image on Cloud with files as null
3. Boot image on Cloud with files populated
4. Check to make sure that cloud-init provisioned with out errors
[TEST CASE 2]:
1. Build existing Ubuntu image on ConfigDrive provisioned cloud
2. Check for any errors in the logs
3. Upgrade cloud-init
4. Reboot and check for errors in logs
5. Create a new instance from existing instance
6. Check for errors in the log.
[FROM ORIGINAL REPORT]
Sep 4 18:46:28 utl-precise-
Sep 4 18:46:28 utl-precise-
Sep 4 18:46:28 utl-precise-
root@utl-
meta_data.json:
{
"domain": "foobar.com",
"files": [
[]
],
"hostname": "utl-precise-
"meta": {
"dsmode": "net"
},
"name": "utl-precise-
"network_
},
"public_keys": {
"177313": "<REDACTED FOR READABILITY>"
},
"uuid": "9ba148b1-
}
Related branches
summary: |
- ConfigDrive datasource fails when metadata files is null + [SRU] ConfigDrive datasource fails when metadata files is null |
description: | updated |
Changed in cloud-init (Ubuntu Precise): | |
importance: | Undecided → Medium |
tags: |
added: verification-done removed: verification-needed |
This bug only affects Ubuntu 12.04.