Comment 0 for bug 1911227
Revision history for this message
| Dan Watkins (oddbloke) wrote cc_seed_random: unexpectedly appends cloud's random_seed to specified seed | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
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.