|
| 1 | +--- |
| 2 | +prelude: > |
| 3 | + The 15.0.1 Ocata release contains fixes for several high severity, high |
| 4 | + impact bugs. If you have not yet upgraded to 15.0.0, it is recommended to |
| 5 | + upgrade directly to 15.0.1. |
| 6 | +issues: |
| 7 | + - | |
| 8 | + There is a known regression in Ocata reported in `bug 1671648`_ where |
| 9 | + server build failures on a compute node are not retried on another compute |
| 10 | + node. The fix for this bug is being worked and will be provided shortly in |
| 11 | + a 15.0.2 release. |
| 12 | +
|
| 13 | + .. _bug 1671648: https://launchpad.net/bugs/1671648 |
| 14 | +critical: |
| 15 | + - | |
| 16 | + `Bug 1670627`_ is fixed. This bug led to potential over-quota errors after |
| 17 | + several failed server build attempts, resulting in quota usage to reach the |
| 18 | + limit even though the servers were deleted. |
| 19 | +
|
| 20 | + Unfortunately the ``nova-manage project quota_usage_refresh`` command will |
| 21 | + not reset the usages to fix this problem once encountered. |
| 22 | +
|
| 23 | + If the project should not have any outstanding resource usage, then one |
| 24 | + possible workaround is to delete the existing quota usage for the project:: |
| 25 | +
|
| 26 | + ``nova quota-delete --tenant <tenant_id>`` |
| 27 | +
|
| 28 | + That will cleanup the ``project_user_quotas``, ``quota_usages`` and |
| 29 | + ``reservations`` tables for the given project in the ``nova`` database and |
| 30 | + reset the quota limits for the project back to the defaults defined in |
| 31 | + nova.conf. |
| 32 | +
|
| 33 | + .. _Bug 1670627: https://launchpad.net/bugs/1670627 |
| 34 | +fixes: |
| 35 | + - | |
| 36 | + `Bug 1665263`_ is fixed. This was a regression where |
| 37 | + ``instance.delete.start`` and ``instance.delete.end`` notifications were |
| 38 | + not emitted when deleting an instance in ``ERROR`` state due to a failed |
| 39 | + build. |
| 40 | +
|
| 41 | + .. _Bug 1665263: https://launchpad.net/bugs/1665263 |
0 commit comments