Hi,
I tried to reproduce the bug in openstack mitaka version following the steps as mentioned.
Below is my observation:
By changing "nova flavor-key bm-flavor set cpu_arch=x86_64" to
"nova flavor-key bm-flavor set capabilities:cpu_info:arch=x86_64" we are not getting any error and the host is qualified.
In dashboard ,
we can set the same in dashboard as cpu_arch to x86 in flavors metadata->compute host capabilities-> architecture->x86_64 .
Hi, cpu_info: arch=x86_ 64" we are not getting any error and the host is qualified.
I tried to reproduce the bug in openstack mitaka version following the steps as mentioned.
Below is my observation:
By changing "nova flavor-key bm-flavor set cpu_arch=x86_64" to
"nova flavor-key bm-flavor set capabilities:
In dashboard , >x86_64 .
we can set the same in dashboard as cpu_arch to x86 in flavors metadata->compute host capabilities-> architecture-