The situation in the post thread you list in this new thread was in fact resolved.
However, it was not due to anything that you might have control over. It turns out the person responsible for the install.py playbook had made some alterations that completely sent the install process off the rails.
He did eventually dig in and find the issue in his edits and fix them. However, one thing that remained after his fix was the requirement to install some extra packages before running the install.py script.
See THIS LINK for a little more details on what he recommended.
Hope this helps. If not you might try reaching out to him directly to see if he can shed any light on your new recurrence of the same error. @codingCoffee was very helpful when we worked together on resolving it the last time.
Ahh… one last thing. His work was hampered at the time by his exclusive use of the --develop switch with the install.py… It was not until he looked at it from our perspective (–production) that the errors in his edits were located. He did promise to pay closer attention to the difference for future edits. His experience in this may be helpful to your current errors.
Hope this helps…
BKM