Activity log for bug #1650209

Date Who What changed Old value New value Message
2016-12-15 10:36:11 Ekaterina Shutova bug added bug
2016-12-15 10:40:59 Roman Podoliaka mos: milestone 9.2
2016-12-15 10:41:04 Roman Podoliaka mos: assignee MOS Nova (mos-nova)
2016-12-15 10:41:06 Roman Podoliaka mos: importance Undecided Medium
2016-12-15 10:41:08 Roman Podoliaka mos: status New Confirmed
2016-12-15 11:10:59 Timofey Durakov summary Nova evacuate should be used twice when use cluster with Ceph Nova evacuate fails with ImageBusy exception on Ceph enabled envs
2016-12-15 11:12:11 Timofey Durakov description Detailed bug description: Using nova evacuate leads to changing instance state to ERROR after destroy compute where instance is located. To move instance to another compute nova evacuate should be used one more time. Details: https://paste.mirantis.net/show/2866/ Steps to reproduce: Use environment with ceph(controller + 2compute+ceph) 1. Create net01 2. Boot instances vm1 and vm2 in net01 on a single compute node 3. Shut off the compute node where instances are scheduled (with virsh destroy) 4. Evacuate instances vm1 and vm2: nova evacuate vm1 5. Check that vm1 is rescheduled onto another compute node and are in ACTIVE state Details: https://paste.mirantis.net/show/2868/ Expected results: Instance is in Active state and recheduled to another compute Actual result: Instance is in Error state Reproducibility: Always on that cluster Workaround: Use nova evacuate vm1 twice. After that instance move to another compute and ping is working. Impact: Description of the environment: 9.2 snapshot #6​32 cat /etc/fuel_build_id: 495 cat /etc/fuel_build_number: 495 cat /etc/fuel_release: 9.0 cat /etc/fuel_openstack_version: mitaka-9.0 rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun': fuel-nailgun-9.0.0-1.mos8915.noarch network-checker-9.0.0-1.mos77.x86_64 fuel-9.0.0-1.mos6359.noarch fuel-misc-9.0.0-1.mos8660.noarch fuel-mirror-9.0.0-1.mos158.noarch shotgun-9.0.0-1.mos90.noarch python-fuelclient-9.0.0-1.mos363.noarch fuelmenu-9.0.0-1.mos276.noarch fuel-library9.0-9.0.0-1.mos8660.noarch fuel-notify-9.0.0-1.mos8660.noarch fuel-setup-9.0.0-1.mos6359.noarch rubygem-astute-9.0.0-1.mos782.noarch fuel-release-9.0.0-1.mos6359.noarch fuel-provisioning-scripts-9.0.0-1.mos8915.noarch fuel-ostf-9.0.0-1.mos947.noarch fuel-bootstrap-cli-9.0.0-1.mos291.noarch fuel-ui-9.0.0-1.mos2848.noarch fuel-agent-9.0.0-1.mos291.noarch python-packetary-9.0.0-1.mos158.noarch nailgun-mcagents-9.0.0-1.mos782.noarch fuel-migrate-9.0.0-1.mos8660.noarch fuel-utils-9.0.0-1.mos8660.noarch fuel-openstack-metadata-9.0.0-1.mos8915.noarch Additional information: Log from compute: https://paste.mirantis.net/show/2867/ Detailed bug description:  Using nova evacuate leads to changing instance state to ERROR after destroy compute where instance is located. To move instance to another compute nova evacuate should be used one more time. Details: https://paste.mirantis.net/show/2866/ Steps to reproduce:  Use environment with ceph(controller + 2compute+ceph) 1. Create net01 2. Boot instances vm1 and vm2 in net01 on a single compute node 3. Shut off the compute node where instances are scheduled (with virsh destroy) 4. Evacuate instances vm1 and vm2:      nova evacuate vm1 5. Check that vm1 is rescheduled onto another compute node and are in ACTIVE state Details: https://paste.mirantis.net/show/2868/ Expected results:  Instance is in Active state and recheduled to another compute Actual result:  Instance is in Error state Reproducibility:  Always on that cluster Workaround:  Use nova evacuate vm1 twice. After that instance move to another compute and ping is working. Impact: Description of the environment: 9.2 snapshot #6​32 cat /etc/fuel_build_id:  495 cat /etc/fuel_build_number:  495 cat /etc/fuel_release:  9.0 cat /etc/fuel_openstack_version:  mitaka-9.0 rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':  fuel-nailgun-9.0.0-1.mos8915.noarch  network-checker-9.0.0-1.mos77.x86_64  fuel-9.0.0-1.mos6359.noarch  fuel-misc-9.0.0-1.mos8660.noarch  fuel-mirror-9.0.0-1.mos158.noarch  shotgun-9.0.0-1.mos90.noarch  python-fuelclient-9.0.0-1.mos363.noarch  fuelmenu-9.0.0-1.mos276.noarch  fuel-library9.0-9.0.0-1.mos8660.noarch  fuel-notify-9.0.0-1.mos8660.noarch  fuel-setup-9.0.0-1.mos6359.noarch  rubygem-astute-9.0.0-1.mos782.noarch  fuel-release-9.0.0-1.mos6359.noarch  fuel-provisioning-scripts-9.0.0-1.mos8915.noarch  fuel-ostf-9.0.0-1.mos947.noarch  fuel-bootstrap-cli-9.0.0-1.mos291.noarch  fuel-ui-9.0.0-1.mos2848.noarch  fuel-agent-9.0.0-1.mos291.noarch  python-packetary-9.0.0-1.mos158.noarch  nailgun-mcagents-9.0.0-1.mos782.noarch  fuel-migrate-9.0.0-1.mos8660.noarch  fuel-utils-9.0.0-1.mos8660.noarch  fuel-openstack-metadata-9.0.0-1.mos8915.noarch Additional information:  Log from compute: https://paste.mirantis.net/show/2867/
2017-02-07 14:11:52 Vitaly Sedelnik mos: milestone 9.2 9.x-updates