There's little sense in allowing a user to create flavors that do not match existing hardware. As we create profiles after discovery, it should be easy to have kind of openstack flavor autocreate that will go through Ironic nodes and create flavors.
os-cloud-config has very close4 functionality, maybe we should use/extend it: https://github.com/openstack/os-cloud-config/blob/master/os_cloud_config/flavors.py#L29-L48
+1, openstack flavor autocreate sounds like a good fit to me.
It looks like we should extend the functionality in os-cloud-config and then use it from the unified client work. We do this with node registration already for example.
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.