So we have flavor created with properties:- properties | capabilities:boot_option='local', capabilities:profile='control', resources:CUSTOM_BAREMETAL='1', resources:DISK_GB='0', resources:MEMORY_MB='0', resources:VCPU='0' which is correct, jroll confirmed it.
Also suggested: for driver=filter_scheduler(which is used in undercloud) there is no need to use CoreFilter, RamFilter and DiskFilter. These filters are required atleast with caching_scheduler.
I tried without these filters and overcloud deployment completed.
The possible reason it's seen in tripleo jobs and not seen in ironic devstack jobs after https://review.openstack.org/#/c/565841 is that these filters are not enabled there. As a quick check it can be tested with ironic jobs by enabling these filters.
So we have flavor created with properties:- properties | capabilities: boot_option= 'local' , capabilities: profile= 'control' , resources: CUSTOM_ BAREMETAL= '1', resources: DISK_GB= '0', resources: MEMORY_ MB='0', resources:VCPU='0' which is correct, jroll confirmed it.
As matt said in https:/ /bugs.launchpad .net/tripleo/ +bug/1787910/ comments/ 15, there can be a regression bug in nova with ironic driver.
Also suggested: for driver= filter_ scheduler( which is used in undercloud) there is no need to use CoreFilter, RamFilter and DiskFilter. These filters are required atleast with caching_scheduler.
I tried without these filters and overcloud deployment completed.
The possible reason it's seen in tripleo jobs and not seen in ironic devstack jobs after https:/ /review. openstack. org/#/c/ 565841 is that these filters are not enabled there. As a quick check it can be tested with ironic jobs by enabling these filters.