8f5fbd83de
As of now, if hostname is set as "compute0.example.com" (in lower case)
and user tries to add this host to host-aggregate but by-mistake types
"COMPUTE0.example.com" (in capital case), then instead of throwing
HostNotFound error, that host is successfully added to host-aggregate
as "COMPUTE0.example.com". And after that if instance creation request
with flavor matching metadata as host-aggregate metadata comes, this
host is not filtered by scheduler, since there is no host with hostname
COMPUTE0.example.com, as added in host-aggregate.
Fixed the issue by lowercasing all hostnames in host_aggregate_map
dictionary.
Change-Id: Iee4b9bbf412adfdc6fdc62ea3429fb960d6ac2a2
Closes-Bug: 1709260
(cherry picked from commit
|
||
---|---|---|
.. | ||
client | ||
filters | ||
weights | ||
__init__.py | ||
caching_scheduler.py | ||
chance.py | ||
driver.py | ||
filter_scheduler.py | ||
host_manager.py | ||
ironic_host_manager.py | ||
manager.py | ||
rpcapi.py | ||
utils.py |