Activity log for bug #1957939

Date Who What changed Old value New value Message
2022-01-14 16:55:23 Will Szumski bug added bug
2022-01-14 17:00:56 Will Szumski attachment added 1: nova compute logs from server where the the instance was resized to https://bugs.launchpad.net/nova/+bug/1957939/+attachment/5554359/+files/nova-log-1.txt
2022-01-14 17:01:16 Will Szumski attachment added 2: nova compute logs from server where the the instance was resized to https://bugs.launchpad.net/nova/+bug/1957939/+attachment/5554360/+files/nova-log-2.txt
2022-01-14 17:01:40 Will Szumski description Description =========== When attempting to revert a resize operation the instance will be get wedged in the VERIFY_RESIZE state. Steps to reproduce ================== - Boot instance - Resize instance to larger flavor - Wait for status VERIFY_RESIZE - Run openstack server resize revert <server> - Instance moves to status REVERT_RESIZE - Wait some time - Instance moves back to VERIFY_RESIZE There then doesn't seem to be a way to recover the server via the CLI once you hit this condition: (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize confirm 9ba8ad66-d16b-4023-adb9-d5898c73b6db Instance has not been resized. (HTTP 400) (Request-ID: req-53d1e915-ea31-40ee-a9de-126d3089e944) (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize --revert 9ba8ad66-d16b-4023-adb9-d5898c73b6db Both of these operations fail. Environment =========== 1. Exact version of OpenStack you are running. See the following list for all releases: http://docs.openstack.org/releases/ Kolla-ansible deployed wallaby on centos8-stream. This is a source build using the version: `23.1.1.dev6` 2. Which hypervisor did you use? libvirt with KVM (libvirt: 7.9.0) 2. Which storage type did you use? Ceph Octopus 3. Which networking type did you use? Neutron with openvswitch Description =========== When attempting to revert a resize operation the instance will be get wedged in the VERIFY_RESIZE state. Steps to reproduce ================== - Boot instance - Resize instance to larger flavor - Wait for status VERIFY_RESIZE - Run openstack server resize revert <server> - Instance moves to status REVERT_RESIZE - Wait some time - Instance moves back to VERIFY_RESIZE There then doesn't seem to be a way to recover the server via the CLI once you hit this condition: (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize confirm 9ba8ad66-d16b-4023-adb9-d5898c73b6db Instance has not been resized. (HTTP 400) (Request-ID: req-53d1e915-ea31-40ee-a9de-126d3089e944) (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize --revert 9ba8ad66-d16b-4023-adb9-d5898c73b6db Both of these operations fail. Environment =========== 1. Exact version of OpenStack you are running. See the following   list for all releases: http://docs.openstack.org/releases/    Kolla-ansible deployed wallaby on centos8-stream. This is a source build using the version:   `23.1.1.dev6` 2. Which hypervisor did you use?    libvirt with KVM (libvirt: 7.9.0) 2. Which storage type did you use?    Ceph Octopus 3. Which networking type did you use?    Neutron with openvswitch
2022-01-14 17:02:06 Pablo bug added subscriber Pablo
2022-01-14 17:06:04 Will Szumski description Description =========== When attempting to revert a resize operation the instance will be get wedged in the VERIFY_RESIZE state. Steps to reproduce ================== - Boot instance - Resize instance to larger flavor - Wait for status VERIFY_RESIZE - Run openstack server resize revert <server> - Instance moves to status REVERT_RESIZE - Wait some time - Instance moves back to VERIFY_RESIZE There then doesn't seem to be a way to recover the server via the CLI once you hit this condition: (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize confirm 9ba8ad66-d16b-4023-adb9-d5898c73b6db Instance has not been resized. (HTTP 400) (Request-ID: req-53d1e915-ea31-40ee-a9de-126d3089e944) (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize --revert 9ba8ad66-d16b-4023-adb9-d5898c73b6db Both of these operations fail. Environment =========== 1. Exact version of OpenStack you are running. See the following   list for all releases: http://docs.openstack.org/releases/    Kolla-ansible deployed wallaby on centos8-stream. This is a source build using the version:   `23.1.1.dev6` 2. Which hypervisor did you use?    libvirt with KVM (libvirt: 7.9.0) 2. Which storage type did you use?    Ceph Octopus 3. Which networking type did you use?    Neutron with openvswitch Description =========== When attempting to revert a resize operation, the instance will be get wedged in the VERIFY_RESIZE state. Steps to reproduce ================== - Boot instance - Resize instance to larger flavor - Wait for status VERIFY_RESIZE - Run openstack server resize revert <server> - Instance moves to status REVERT_RESIZE - Wait some time - Instance moves back to VERIFY_RESIZE There then doesn't seem to be a way to recover the server via the CLI once you hit this condition: (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize confirm 9ba8ad66-d16b-4023-adb9-d5898c73b6db Instance has not been resized. (HTTP 400) (Request-ID: req-53d1e915-ea31-40ee-a9de-126d3089e944) (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize --revert 9ba8ad66-d16b-4023-adb9-d5898c73b6db Both of these operations fail. Environment =========== 1. Exact version of OpenStack you are running. See the following   list for all releases: http://docs.openstack.org/releases/    Kolla-ansible deployed wallaby on centos8-stream. This is a source build using the version:   `23.1.1.dev6` 2. Which hypervisor did you use?    libvirt with KVM (libvirt: 7.9.0) 2. Which storage type did you use?    Ceph Octopus 3. Which networking type did you use?    Neutron with openvswitch
2022-01-14 17:22:59 Will Szumski description Description =========== When attempting to revert a resize operation, the instance will be get wedged in the VERIFY_RESIZE state. Steps to reproduce ================== - Boot instance - Resize instance to larger flavor - Wait for status VERIFY_RESIZE - Run openstack server resize revert <server> - Instance moves to status REVERT_RESIZE - Wait some time - Instance moves back to VERIFY_RESIZE There then doesn't seem to be a way to recover the server via the CLI once you hit this condition: (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize confirm 9ba8ad66-d16b-4023-adb9-d5898c73b6db Instance has not been resized. (HTTP 400) (Request-ID: req-53d1e915-ea31-40ee-a9de-126d3089e944) (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize --revert 9ba8ad66-d16b-4023-adb9-d5898c73b6db Both of these operations fail. Environment =========== 1. Exact version of OpenStack you are running. See the following   list for all releases: http://docs.openstack.org/releases/    Kolla-ansible deployed wallaby on centos8-stream. This is a source build using the version:   `23.1.1.dev6` 2. Which hypervisor did you use?    libvirt with KVM (libvirt: 7.9.0) 2. Which storage type did you use?    Ceph Octopus 3. Which networking type did you use?    Neutron with openvswitch Description =========== When attempting to revert a resize operation, the instance will be get wedged in the VERIFY_RESIZE state. Steps to reproduce ================== - Boot instance - Resize instance to larger flavor - Wait for status VERIFY_RESIZE - Run openstack server resize revert <server> - Instance moves to status REVERT_RESIZE - Wait some time - Instance moves back to VERIFY_RESIZE There then doesn't seem to be a way to recover the server via the CLI once you hit this condition: (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize confirm 9ba8ad66-d16b-4023-adb9-d5898c73b6db Instance has not been resized. (HTTP 400) (Request-ID: req-53d1e915-ea31-40ee-a9de-126d3089e944) (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize --revert 9ba8ad66-d16b-4023-adb9-d5898c73b6db Both of these operations fail. Environment =========== 1. Exact version of OpenStack you are running. See the following   list for all releases: http://docs.openstack.org/releases/    Kolla-ansible deployed wallaby on centos8-stream. This is a source build using the following version of nova: `23.1.1.dev6`, installed via pip. 2. Which hypervisor did you use?    libvirt with KVM (libvirt: 7.9.0) 2. Which storage type did you use?    Ceph Octopus 3. Which networking type did you use?    Neutron with openvswitch
2022-01-14 17:23:30 Will Szumski description Description =========== When attempting to revert a resize operation, the instance will be get wedged in the VERIFY_RESIZE state. Steps to reproduce ================== - Boot instance - Resize instance to larger flavor - Wait for status VERIFY_RESIZE - Run openstack server resize revert <server> - Instance moves to status REVERT_RESIZE - Wait some time - Instance moves back to VERIFY_RESIZE There then doesn't seem to be a way to recover the server via the CLI once you hit this condition: (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize confirm 9ba8ad66-d16b-4023-adb9-d5898c73b6db Instance has not been resized. (HTTP 400) (Request-ID: req-53d1e915-ea31-40ee-a9de-126d3089e944) (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize --revert 9ba8ad66-d16b-4023-adb9-d5898c73b6db Both of these operations fail. Environment =========== 1. Exact version of OpenStack you are running. See the following   list for all releases: http://docs.openstack.org/releases/    Kolla-ansible deployed wallaby on centos8-stream. This is a source build using the following version of nova: `23.1.1.dev6`, installed via pip. 2. Which hypervisor did you use?    libvirt with KVM (libvirt: 7.9.0) 2. Which storage type did you use?    Ceph Octopus 3. Which networking type did you use?    Neutron with openvswitch Description =========== When attempting to revert a resize operation, the instance will be get wedged in the VERIFY_RESIZE state. Steps to reproduce ================== - Boot instance - Resize instance to larger flavor - Wait for status VERIFY_RESIZE - Run openstack server resize revert <server> - Instance moves to status REVERT_RESIZE - Wait some time - Instance moves back to VERIFY_RESIZE There then doesn't seem to be a way to recover the server via the CLI once you hit this condition: (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize confirm 9ba8ad66-d16b-4023-adb9-d5898c73b6db Instance has not been resized. (HTTP 400) (Request-ID: req-53d1e915-ea31-40ee-a9de-126d3089e944) (rally) stackhpc@cerebro:~/shakespeare$ openstack server resize --revert 9ba8ad66-d16b-4023-adb9-d5898c73b6db Both of these operations fail. Environment =========== 1. Exact version of OpenStack you are running. See the following   list for all releases: http://docs.openstack.org/releases/    Kolla-ansible deployed wallaby on centos8-stream. This is a source    build using the following version of nova: `23.1.1.dev6`, installed via    pip. 2. Which hypervisor did you use?    libvirt with KVM (libvirt: 7.9.0) 2. Which storage type did you use?    Ceph Octopus 3. Which networking type did you use?    Neutron with openvswitch
2022-01-18 14:16:48 Sylvain Bauza nova: status New Incomplete
2022-01-18 14:16:55 Sylvain Bauza tags resize
2022-01-21 15:58:27 Pablo bug watch added https://bugzilla.redhat.com/show_bug.cgi?id=1678681
2022-01-21 16:47:37 Pablo nova: status Incomplete New
2022-08-16 09:34:54 Balazs Gibizer nova: status New Incomplete
2022-08-16 09:35:01 Balazs Gibizer tags resize neutron resize
2022-11-21 17:45:27 Maximilian Stinsky nova: status Incomplete New
2023-03-27 21:36:06 melanie witt nominated for series nova/wallaby
2023-03-27 21:36:06 melanie witt bug task added nova/wallaby
2023-03-27 21:36:18 melanie witt nova/wallaby: status New Fix Committed
2023-03-27 21:37:02 melanie witt nova: status New Fix Released