Comment 3 for bug 1823213

I believe this issue will be solved when the following gets Merged: https://review.openstack.org/#/c/648511/

This feature also solves the following (which is the reported issue):
- sysinv puppet generation of platform_cpu_list did not have all threads
- worker_reserved.conf not generated on unlock, so that file which gets sourced by various things was not current in during early init
- sysinv puppet cpulist-to-ranges inline code was incorrect; so for certain hardware (with funky logical cpu enumeration patterns), the platform_cpu_list is wrong with commas stripped out