The fix above introduces a new bug, which has been backported. We now accept return values of 0, 1 or 2 from command modules that call 'dmidecode'. However we then unconditionally look at the stdout key in the result object. When the dmidecode binary is missing the result dictionary from the command module doesn't contain a stdout key (resulting in something like):
---
fatal: [overcloud-novacomputeppc64le-1]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'\n\nThe error appears to have been in '/var/lib/mistral/overcloud/ceph-ansible/nodes_uuid_playbook.yml': line 14, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n failed_when: machine_uuid.rc not in [0, 1, 2]\n - name: generate host vars from nodes data\n ^ here\n"}
---
The fix above introduces a new bug, which has been backported. We now accept return values of 0, 1 or 2 from command modules that call 'dmidecode'. However we then unconditionally look at the stdout key in the result object. When the dmidecode binary is missing the result dictionary from the command module doesn't contain a stdout key (resulting in something like):
--- novacomputeppc6 4le-1]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'\n\nThe error appears to have been in '/var/lib/ mistral/ overcloud/ ceph-ansible/ nodes_uuid_ playbook. yml': line 14, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n failed_when: machine_uuid.rc not in [0, 1, 2]\n - name: generate host vars from nodes data\n ^ here\n"}
fatal: [overcloud-
---