On 12/10/19 8:22 AM, Eric Lafontaine wrote:
> I'm trying to understand how this bug is considered fixed by the
> following commit; https://git.launchpad.net/cloud-
> init/commit/?id=067516d7
>
> We have resolved the issue by just not base64 decoding;
> - if 'random_seed' in metadata:
> - random_seed = metadata['random_seed']
> - try:
> - metadata['random_seed'] = base64.b64decode(random_seed)
> - except (ValueError, TypeError) as e:
> - raise BrokenMetadata("Badly formatted metadata"
> - " random_seed entry: %s" % e)
>
> Could somebody help me with some information about why we try to get the
> random_seed and interpret it?
We had discussions at the last summit about not persisting the
random_seed to cache, which would avoid this problem. But I am not
certain we reached an actionable conclusion. Then again the topic
becomes somewhat academic at this point as Python 2 support will be
dropped at the end of this year with the release of 19.4
On 12/10/19 8:22 AM, Eric Lafontaine wrote: /git.launchpad. net/cloud- ?id=067516d7 'random_ seed'] 'random_ seed'] = base64. b64decode( random_ seed) "Badly formatted metadata"
> I'm trying to understand how this bug is considered fixed by the
> following commit; https:/
> init/commit/
>
> We have resolved the issue by just not base64 decoding;
> - if 'random_seed' in metadata:
> - random_seed = metadata[
> - try:
> - metadata[
> - except (ValueError, TypeError) as e:
> - raise BrokenMetadata(
> - " random_seed entry: %s" % e)
>
> Could somebody help me with some information about why we try to get the
> random_seed and interpret it?
We had discussions at the last summit about not persisting the
random_seed to cache, which would avoid this problem. But I am not
certain we reached an actionable conclusion. Then again the topic
becomes somewhat academic at this point as Python 2 support will be
dropped at the end of this year with the release of 19.4