** Also affects: nova/queens Importance: Undecided Status: New ** Also affects: nova/ocata Importance: Undecided Status: New
** Also affects: nova/pike Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1770726 Title: RequestedVRamTooHigh failures during server create will get needlessly rescheduled Status in OpenStack Compute (nova): In Progress Status in OpenStack Compute (nova) ocata series: New Status in OpenStack Compute (nova) pike series: New Status in OpenStack Compute (nova) queens series: New Bug description: RequestedVRamTooHigh can be raised during server create from the libvirt driver if the flavor's max video ram is less than the hw_video_ram specified in the image, and because the compute manager isn't handling that specific exception, it will result in a RescheduledException to another compute host, but this is never going to work on another compute host so we should just handle it and abort the build, since it's user-error. Long-term, we should be validating this in the REST API instead of on the compute although not all virt drivers support the image property and flavor extra spec - currently only the libvirt driver does but there is also a patch to add support for it with the vmware driver: https://review.openstack.org/#/c/564193/ https://github.com/openstack/nova/blob/bfcbfdf9169765219320abfa3e09ecda8ff1a80c/nova/virt/libvirt/driver.py#L4608 https://github.com/openstack/nova/blob/bfcbfdf9169765219320abfa3e09ecda8ff1a80c/nova/compute/manager.py#L2095 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1770726/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp