docs: Trying to terminate an instance during its creation might prevent the virtual function used by that instance from being reused afterwards
Bug #1404661 reported by
Gil Meir
This bug report is a duplicate of:
Bug #1404659: docs: Deleting multiple instances on a compute node simultaneously might cause the host losing network connectivity.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
New
|
Medium
|
Irina Povolotskaya | ||
5.1.x |
Fix Committed
|
Medium
|
Irina Povolotskaya | ||
6.0.x |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
* Trying to terminate an instance during its creation might prevent the virtual function used by that instance from being reused afterwards.
* This causes the total amount of available virtual functions to decline.
* To work around this restart the eswitchd service on the compute node by executing: service eswitchd restart.
* This was found in version 5.1.1 and will be added to the release notes.
Changed in fuel: | |
milestone: | none → 5.1.2 |
assignee: | nobody → Fuel Documentation Team (fuel-docs) |
status: | New → Confirmed |
importance: | Undecided → Medium |
summary: |
- Trying to terminate an instance during its creation might prevent the - virtual function used by that instance from being reused afterwards + docs: Trying to terminate an instance during its creation might prevent + the virtual function used by that instance from being reused afterwards |
tags: | added: docs |
Changed in fuel: | |
milestone: | 5.1.2 → 6.1 |
status: | Confirmed → New |
To post a comment you must log in.
I believe, I've covered that within https:/ /review. openstack. org/#/c/ 143810/