** Description changed:
## Issue
openstack allocation candidate list works for os placement api version range
1.10 to to 1.17 but no version later than this.
## Expected result
allocation candidate should work from 1.10 up to 1.9 which is the current os
placement api version.
+
+
Note: Unsure if this is a bug or expected result. Posting for
consideration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851952
Title:
Openstack allocation candidate is functional for incorrect
** Description changed:
## Issue
- openstack allocation candidate list works for os placement api version range
1.10 to to 1.7 but no version later than this.
+ openstack allocation candidate list works for os placement api version range
1.10 to to 1.17 but no version later than this.
##
Public bug reported:
## Issue
openstack allocation candidate list works for os placement api version range
1.10 to to 1.7 but no version later than this.
## Expected result
allocation candidate should work from 1.10 up to 1.9 which is the current os
placement api version.
** Affects:
Public bug reported:
Using OS CLI 4.0.0, I am unable to set a flavors description with a flavors
name.
It works as expected with flavor ID.
Command:
openstack flavor set ${flavor_name} --description "sample description"
Result:
Flavor ${flavor_name} could not be found. (HTTP 404)
Expected
usage: openstack flavor set [-h] [--no-property] [--property ]
[--project ]
[--description ]
[--project-domain ]
Set flavor properties
positional arguments:
Flavor to
I think I have encountered exactly the same issue as you Nico. We have very
similar setups.
Upgrading the kernel did not help.
Only thing that helped was setting openstack to use qemu instead of kvm in L2
VMs with the performance cost associated with doing that :(
--
You received this bug
