After further investigation, it seems the error seen on that environment was not a due to a t-h-t regression but to a misconfiguration. Quoting ysandeep:
"
I don't think we need that anymore.. In our case that was due to downstream nodepool customization. 99-tripleo.conf is correctly poppulated by tripleo ansible.
"
After further investigation, it seems the error seen on that environment was not a due to a t-h-t regression but to a misconfiguration. Quoting ysandeep:
"
I don't think we need that anymore.. In our case that was due to downstream nodepool customization. 99-tripleo.conf is correctly poppulated by tripleo ansible.
"
I'm closing the bug accordingly.