Hello Matt, or anyone else affected, Accepted nova into queens-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.
Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:queens-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-queens-needed to verification-queens-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-queens-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/queens Status: Won't Fix => Fix Committed ** Tags added: verification-queens-needed -- 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/1852610 Title: [SRU] API allows source compute service/node deletion while instances are pending a resize confirm/revert Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive queens series: Fix Committed Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) queens series: Fix Committed Status in OpenStack Compute (nova) rocky series: Fix Committed Status in OpenStack Compute (nova) stein series: Fix Committed Status in OpenStack Compute (nova) train series: Fix Committed Status in nova package in Ubuntu: Invalid Status in nova source package in Bionic: Fix Released Bug description: [Impact] * API will allow deleting a source compute service which has migration-based allocations for the source node resource provider and pending instance resizes involving the source node. * Backporting the fix will improve application resilience in this case. [Test Case] 1. create a server on host1 2. resize or cold migrate it to a dest host2 3. delete the compute service for host1 At this point the resource provider for host1 is orphaned. 4. try to confirm/revert the resize of the server which will fail because the compute node for host1 is gone and this results in the server going to ERROR status [Where problems could occur] * This change introduces an exception condition in the API and prevents the erroneous deletion of compute services which would result in orphaned state. * As such we should expect to see altered behavior from the API as detailed in api-ref/source/os-services.inc * If problems were to occur they would manifest in behavior that is different from both the original behavior of the API and the new behavior. --- Original Description --- This is split off from bug 1829479 which is about deleting a compute service which had servers evacuated from it which will orphan resource providers in placement. A similar scenario is true where the API will allow deleting a source compute service which has migration-based allocations for the source node resource provider and pending instance resizes involving the source node. A simple scenario is: 1. create a server on host1 2. resize or cold migrate it to a dest host2 3. delete the compute service for host1 At this point the resource provider for host1 is orphaned. 4. try to confirm/revert the resize of the server which will fail because the compute node for host1 is gone and this results in the server going to ERROR status Based on the discussion in this mailing list thread: http://lists.openstack.org/pipermail/openstack- discuss/2019-November/010843.html We should probably have the DELETE /os-services/{service_id} API block trying to delete a service that has pending migrations. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1852610/+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
