Addition of host to host-aggregate should be case -sensitive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Rajesh Tailor | ||
Pike |
Fix Committed
|
Low
|
Rajesh Tailor | ||
Queens |
Fix Committed
|
Low
|
Rajesh Tailor |
Bug Description
I have multinode devstack setup with 2 compute and a controller node.
The hostnames of the nodes are as follows:
controller: controller.
compute0: compute0.
compute1: compute1.
Reproduction steps:
1) I have created a host-aggregate in availability zone "nova".
nova aggregate-create test_agg nova
2) Then I set metadata on that host-aggregate.
nova aggregate-
3) Then I added compute hosts mentioned above to host-aggregate.
nova aggregate-add-host test_agg COMPUTE0.
nova aggregate-add-host test_agg compute1.
While adding compute0 to host-aggregate, if I provide hostname as "COMPUTE0.
throwing HostNotFound error, it is added to host-aggregate.
4) After that I have created a flavor.
nova flavor-create ssd.large 6 8192 80 4
5) Added metadata to flavor.
nova flavor-key ssd.large set ssd=true
Now when I try to create instance with above mentioned flavor, I can't spawn it on compute0 host. As scheduler is filtering only compute1 with AggregateInstan
Expected Result: while adding the case-sensitive host to host-aggregate, nova-api should have thrown HostNotFound error.
Note: when I add the correct hostname "compute0.
Changed in nova: | |
assignee: | nobody → Rajesh Tailor (ratailor) |
description: | updated |
For clarity on the bug report, could you please provide the nova-sceduler log that shows the filter missing that host because the name is different ?
TBC, all FQDNs are case-sensitive, so we should probably indeed return a 404 when you're trying to add a host with the wrong case. The only point I wonder is whether it would require a new API microversion since we were previously accepting that from a REST perpective (my guts tend to say yes to that :( )