cc_seed_random: unexpectedly appends cloud's random_seed to specified seed data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Dan Watkins |
Bug Description
The test_seed_
#cloud-config
random_seed:
data: 'MYUb34023nD:
encoding: raw
file: /root/seed
and asserts that that is the exact content of /root/seed. If we're using a datasource which sets random_seed in its metadata (i.e. Azure and OpenStack, at least), this test fails: cc_seed_random will _append_ the cloud's random_seed to the given data before writing it out.
To be clear, the bug here is that this is unexpected: we do not document this behaviour. I can't think of a compelling case for not behaving in this way: more entropy is good, and we have write_files if users really do want to write out exact content to a path.
The TestSeedRandomD
Changed in cloud-init: | |
status: | New → Triaged |
importance: | Undecided → Medium |
summary: |
cc_seed_random: unexpectedly appends cloud's random_seed to specified - seed + seed data |
description: | updated |
I've just opened a PR for this: https:/ /github. com/canonical/ cloud-init/ pull/771