)]}'
{"deployment/swift/swift-storage-container-puppet.yaml":[{"author":{"_account_id":14985,"name":"Alex Schultz","email":"aschultz@next-development.com","username":"mwhahaha"},"change_message_id":"8b383c6d997aca0813e06f46ec218b9840a2ea0e","unresolved":false,"context_lines":[{"line_number":330,"context_line":"            environment:"},{"line_number":331,"context_line":"              # NOTE: this should force this container to re-run on each"},{"line_number":332,"context_line":"              # update (scale-out, etc.)"},{"line_number":333,"context_line":"              TRIPLEO_DEPLOY_IDENTIFIER: {get_param: DeployIdentifier}"},{"line_number":334,"context_line":"        step_4:"},{"line_number":335,"context_line":"          map_merge:"},{"line_number":336,"context_line":"            - if:"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"bf51134e_611fe55a","line":333,"updated":"2020-06-23 18:03:04.000000000","message":"This seems like a different bug because docker_config should always be run I think","commit_id":"9b8a75739174d3e0682ced2ca3afff6b73216d2b"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"68146dd7e9849eaa15e70b7517fe6d8d3e2ec0a7","unresolved":false,"context_lines":[{"line_number":330,"context_line":"            environment:"},{"line_number":331,"context_line":"              # NOTE: this should force this container to re-run on each"},{"line_number":332,"context_line":"              # update (scale-out, etc.)"},{"line_number":333,"context_line":"              TRIPLEO_DEPLOY_IDENTIFIER: {get_param: DeployIdentifier}"},{"line_number":334,"context_line":"        step_4:"},{"line_number":335,"context_line":"          map_merge:"},{"line_number":336,"context_line":"            - if:"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"bf51134e_dbddaedd","line":333,"in_reply_to":"bf51134e_611fe55a","updated":"2020-06-29 15:36:56.000000000","message":"I\u0027ve checked the current gate job results, but it seems like the issue was fixed in master already.\n https://2c3c0b1787659ea3b842-1eceb8a6fb7f917522f65bda64a8589f.ssl.cf1.rackcdn.com/737391/5/check/tripleo-ci-centos-8-scenario002-standalone/a5fe331/logs/undercloud/var/lib/tripleo-config/container-startup-config/step_3/swift_rsync_fix.json\n\nOn the other hand, in my stable/queens and stable/train deployment, definition of  swift_rsync_fix container doesn\u0027t include TRIPLEO_DEPLOY_IDENTIFIER.\n\nBecause of this definition swift_rsync_fix container is not invoked unless TRIPLEO_CONFIG_HASH is changed or container definitions are changed (bind mount, container images and so on)\nThis means that the container is not invoked during scale out, etc.\n\nI\u0027ll investigate what caused this change.","commit_id":"9b8a75739174d3e0682ced2ca3afff6b73216d2b"}]}