DescriptionShailesh Chhabdiya
2022-09-11 10:51:32 UTC
Description of problem:
Creating multiple VM via horizon leads to failure with error `Failed to allocate the network(s), not rescheduling`
Error: Failed to perform requested operation on instance "yess-vm-6", the instance has an error status: Please try again later [Error: Build of instance 45dc7fee-22ab-432f-b05b-4c4e7598e7ed aborted: Failed to allocate the network(s), not rescheduling.].
Error: Failed to perform requested operation on instance "yess-vm-5", the instance has an error status: Please try again later [Error: Build of instance 17c777ef-c938-4e28-b5ed-0d556185f891 aborted: Failed to allocate the network(s), not rescheduling.].
Version-Release number of selected component (if applicable):
RHOSP16.1.8
How reproducible:
Always
Steps to Reproduce:
1. Launch 10 VMs via horizon
2. Wait for few minutes
3. issue gets reproduced
Actual results:
VM creation fails
Expected results:
VM creations should be successful
Additional info:
Comment 1Shailesh Chhabdiya
2022-09-11 10:54:16 UTC
Hello Team,
Here are the details about issue
- Created VM via CLI 2-3 times everything went well
- Than tried creating 5 VMs from Horizon at a single time out of which 3 were Active and 2 failed with network ERROR
Error: Failed to perform requested operation on instance "yess-vm-6", the instance has an error status: Please try again later [Error: Build of instance 45dc7fee-22ab-432f-b05b-4c4e7598e7ed aborted: Failed to allocate the network(s), not rescheduling.].
Error: Failed to perform requested operation on instance "yess-vm-5", the instance has an error status: Please try again later [Error: Build of instance 17c777ef-c938-4e28-b5ed-0d556185f891 aborted: Failed to allocate the network(s), not rescheduling.].
- Than we tried combination nova configs in nova.conf of controller
~~~
[DEFAULT]/vif_plugging_timeout=900
[neutron]/timeout=30
~~~
~~~
[DEFAULT]/vif_plugging_timeout=300
[neutron]/timeout=60
~~~
- Than we created 10 VMs out of which 5 were Active and 5 in ERROR with same `neutron error`
- The reason behind why always compute-7 is selected it has weight in +ve value whereas for rest its in -ve
- The issues seems to be call/request timeout between nova and neutron
Description of problem: Creating multiple VM via horizon leads to failure with error `Failed to allocate the network(s), not rescheduling` Error: Failed to perform requested operation on instance "yess-vm-6", the instance has an error status: Please try again later [Error: Build of instance 45dc7fee-22ab-432f-b05b-4c4e7598e7ed aborted: Failed to allocate the network(s), not rescheduling.]. Error: Failed to perform requested operation on instance "yess-vm-5", the instance has an error status: Please try again later [Error: Build of instance 17c777ef-c938-4e28-b5ed-0d556185f891 aborted: Failed to allocate the network(s), not rescheduling.]. Version-Release number of selected component (if applicable): RHOSP16.1.8 How reproducible: Always Steps to Reproduce: 1. Launch 10 VMs via horizon 2. Wait for few minutes 3. issue gets reproduced Actual results: VM creation fails Expected results: VM creations should be successful Additional info: