Description of problem: when performing dry-run, Create swift logging symlink task fails Version-Release number of selected component (if applicable): 2018-10-25.3 puddle How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: TASK [Create swift logging symlink] ******************************************** skipping: [compute-1] skipping: [compute-0] fatal: [controller-2]: FAILED! => {"changed": false, "msg": "src file does not exist, use \"force=yes\" if you really want to create the link: /var/log/swift", "path": "/var/log/containers/swift", "src": "/var/log/swift", "state": "absent"} fatal: [controller-1]: FAILED! => {"changed": false, "msg": "src file does not exist, use \"force=yes\" if you really want to create the link: /var/log/swift", "path": "/var/log/containers/swift", "src": "/var/log/swift", "state": "absent"} fatal: [controller-0]: FAILED! => {"changed": false, "msg": "src file does not exist, use \"force=yes\" if you really want to create the link: /var/log/swift", "path": "/var/log/containers/swift", "src": "/var/log/swift", "state": "absent"} NO MORE HOSTS LEFT ************************************************************* to retry, use: --limit @/home/stack/config-download/deploy_steps_playbook.retry PLAY RECAP ********************************************************************* compute-0 : ok=83 changed=29 unreachable=0 failed=0 compute-1 : ok=83 changed=29 unreachable=0 failed=0 controller-0 : ok=154 changed=88 unreachable=0 failed=1 controller-1 : ok=154 changed=88 unreachable=0 failed=1 controller-2 : ok=154 changed=88 unreachable=0 failed=1 undercloud : ok=2 changed=0 unreachable=0 failed=0 Expected results: Dry run completes with no errors Additional info:
Verified on puddle 2018-11-13.1, successfully passed failing task with beta puddle.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045