Description of problem: With latest minor update, decimal numbers in heat templates are rewritten to exponent notation in hieradata if they end with "0". Puppet output: \u001b[mNotice: /Stage[main]/Cinder::Backup::Nfs/Cinder_config[DEFAULT/backup_file_size]/value: value changed '100000000' to '1e+08'\u001b[0m \u001b[mNotice: /Stage[main]/Cinder::Backup::Nfs/Cinder_config[DEFAULT/backup_sha_block_size_bytes]/value: value changed '2000000' to '2e+06'\u001b[0m templates file has this : environments/6a-environment.yaml: cinder::backup::nfs::backup_file_size: 100000000 environments/6a-environment.yaml: cinder::backup::nfs::backup_sha_block_size_bytes: 100000000 hieradata has this: cinder::backup::nfs::backup_file_size: 1e+08 cinder::backup::nfs::backup_sha_block_size_bytes: 2e+06 Adding 1 to the values like this: environments/6a-environment.yaml: cinder::backup::nfs::backup_file_size: 100000001 environments/6a-environment.yaml: cinder::backup::nfs::backup_sha_block_size_bytes: 2000001 hieradata now has this: controller_extraconfig.yaml:cinder::backup::nfs::backup_file_size: 100000001 controller_extraconfig.yaml:cinder::backup::nfs::backup_sha_block_size_bytes: 2000001 openstack-cinder-backup will probably start by now. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Since it's the hieradata getting written out in a different format, I think it's related to how heat is handling the yaml.
The following settings solvs the problem too: environments/6a-environment.yaml: cinder::backup::nfs::backup_file_size: "100000000" environments/6a-environment.yaml: cinder::backup::nfs::backup_sha_block_size_bytes: "2000000"
Can we get some more details from the environment? What was the starting version, and the target version? Was it a 7.4 to 7.5 upgrade?