Public bug reported:
Steps to reproduce
==================
Set network throttle properties of a flavor to something large, such as 40Gbps
(specified in KiB per second):
quota:vif_inbound_average='4882813', quota:vif_outbound_average='4882813'
Launch an instance.
Easy to reproduce. Lowering the quota values to something smaller
(15Gbps or less is what I have tested so far), works fine, so I'm
guessing we're running into a 32-bit number issue (too large of throttle
to store in a 32-bit number), or a signed number issue (negative number
is being generated by setting the throttle too high and wrapping around.
Might be a limitation in LibVirt.
Expected result
===============
Successful instance launch.
Actual result
=============
Server status is ERROR. Fault information indicates:
build of instance XXXXX aborted. Volume attachment YYYYY could not be found.
where XXXXX and YYYYY are UUIDs.
Environment
===========
stable/rocky deployed with Kolla-Ansible 7.0.0.0rc2 with latest Kolla
and Kolla-Ansible built from source.
All machines are running CentOS with the latest elrepo kernel (as of
today): 4.18.12-1.el7.elrepo.x86_64
Hypervisor is KVM.
Storage is Ceph on SSDs.
Network is Neutron DVR (with OpenVSwitch).
Regarding version of nova - I'm not sure how to get this from the
containers since rpm lists nothing from inside any of the Kolla Nova
containers.
** Affects: nova
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/1796410
Title:
Large network throttle values cause instance launch failure
Status in OpenStack Compute (nova):
New
Bug description:
Steps to reproduce
==================
Set network throttle properties of a flavor to something large, such as
40Gbps (specified in KiB per second):
quota:vif_inbound_average='4882813', quota:vif_outbound_average='4882813'
Launch an instance.
Easy to reproduce. Lowering the quota values to something smaller
(15Gbps or less is what I have tested so far), works fine, so I'm
guessing we're running into a 32-bit number issue (too large of
throttle to store in a 32-bit number), or a signed number issue
(negative number is being generated by setting the throttle too high
and wrapping around.
Might be a limitation in LibVirt.
Expected result
===============
Successful instance launch.
Actual result
=============
Server status is ERROR. Fault information indicates:
build of instance XXXXX aborted. Volume attachment YYYYY could not be found.
where XXXXX and YYYYY are UUIDs.
Environment
===========
stable/rocky deployed with Kolla-Ansible 7.0.0.0rc2 with latest Kolla
and Kolla-Ansible built from source.
All machines are running CentOS with the latest elrepo kernel (as of
today): 4.18.12-1.el7.elrepo.x86_64
Hypervisor is KVM.
Storage is Ceph on SSDs.
Network is Neutron DVR (with OpenVSwitch).
Regarding version of nova - I'm not sure how to get this from the
containers since rpm lists nothing from inside any of the Kolla Nova
containers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1796410/+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
