Detailed bug description: When I try to migrate instance with macvtap port 5 time, it has error state
Steps to reproduce:
Deploy env with 1 controller, 2 computes with SR-IOV feature and 1 compute without SR-IOV.
1. Create net, subnet neutron net-create net01 neutron subnet-create --name net01__subnet net01 10.1.1.0/24 2. Create router, set gatawey and interface to net01 neutron router-create router_01 neutron router-gateway-set router_01 admin_floating_net neutron router-interface-add router_01 net01__subnet 3. Create macvtap port and boot vm NET_ID_1=`neutron net-list | awk '/net01/ {print $2}'` neutron port-create $NET_ID_1 --binding:vnic-type macvtap --device_owner nova-compute --name sriov_1 port_id_s1=`neutron port-list | awk '/sriov_1/ {print $2}'` NODE_1=node-2.domain.tld nova boot vm1 --flavor m1.small --image ubuntu_14.04 --availability-zone nova:$NODE_1 --nic port-id=$port_id_s1 --key-name cloudkey 4. Check active state: nova list 5. Migrate vm1 (migrate, wait some time, confirm resizing) nova migrate vm1 6. Check status 7. Repeat 5 and 6 for 5 times Expected results: instance has status ACTIVE
Actual result: The instance has status ERROR Error message: https://paste.mirantis.net/show/2370/
Description of the environment: iso 482
cat /etc/fuel_build_id: 482 cat /etc/fuel_build_number: 482 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-release-9.0.0-1.mos6349.noarch fuel-misc-9.0.0-1.mos8458.noarch python-packetary-9.0.0-1.mos140.noarch fuel-bootstrap-cli-9.0.0-1.mos285.noarch fuel-migrate-9.0.0-1.mos8458.noarch rubygem-astute-9.0.0-1.mos750.noarch fuel-mirror-9.0.0-1.mos140.noarch shotgun-9.0.0-1.mos90.noarch fuel-openstack-metadata-9.0.0-1.mos8742.noarch fuel-notify-9.0.0-1.mos8458.noarch nailgun-mcagents-9.0.0-1.mos750.noarch python-fuelclient-9.0.0-1.mos325.noarch fuel-9.0.0-1.mos6349.noarch fuel-utils-9.0.0-1.mos8458.noarch fuel-setup-9.0.0-1.mos6349.noarch fuel-provisioning-scripts-9.0.0-1.mos8742.noarch fuel-library9.0-9.0.0-1.mos8458.noarch network-checker-9.0.0-1.mos74.x86_64 fuel-agent-9.0.0-1.mos285.noarch fuel-ui-9.0.0-1.mos2717.noarch fuel-ostf-9.0.0-1.mos936.noarch fuelmenu-9.0.0-1.mos274.noarch fuel-nailgun-9.0.0-1.mos8742.noarch
Additional information: It reproduced only on 5th-time migration. My list of nodes during migration looks like: node_4 -> node_5 node_5 -> node_4 node_4 -> node_5 node_5 -> node_4 node_4 -> node_5 - error
Link on snapshot: https://drive.google.com/uc?export=download&id=0B05EZCZN-hilWHJQLV8xUGlGWk0
Detailed bug description:
When I try to migrate instance with macvtap port 5 time, it has error state
Steps to reproduce:
Deploy env with 1 controller, 2 computes with SR-IOV feature and 1 compute without SR-IOV.
1. Create net, subnet interface- add router_01 net01__subnet node-2. domain. tld
neutron net-create net01
neutron subnet-create --name net01__subnet net01 10.1.1.0/24
2. Create router, set gatawey and interface to net01
neutron router-create router_01
neutron router-gateway-set router_01 admin_floating_net
neutron router-
3. Create macvtap port and boot vm
NET_ID_1=`neutron net-list | awk '/net01/ {print $2}'`
neutron port-create $NET_ID_1 --binding:vnic-type macvtap --device_owner nova-compute --name sriov_1
port_id_s1=`neutron port-list | awk '/sriov_1/ {print $2}'`
NODE_1=
nova boot vm1 --flavor m1.small --image ubuntu_14.04 --availability-zone nova:$NODE_1 --nic port-id=$port_id_s1 --key-name cloudkey
4. Check active state:
nova list
5. Migrate vm1 (migrate, wait some time, confirm resizing)
nova migrate vm1
6. Check status
7. Repeat 5 and 6 for 5 times
Expected results:
instance has status ACTIVE
Actual result: /paste. mirantis. net/show/ 2370/
The instance has status ERROR
Error message: https:/
Description of the environment:
iso 482
cat /etc/fuel_build_id: build_number: openstack_ version: network- checker| nailgun| packetary| shotgun' : 9.0.0-1. mos6349. noarch 9.0.0-1. mos8458. noarch packetary- 9.0.0-1. mos140. noarch -cli-9. 0.0-1.mos285. noarch 9.0.0-1. mos8458. noarch astute- 9.0.0-1. mos750. noarch 9.0.0-1. mos140. noarch 9.0.0-1. mos90.noarch -metadata- 9.0.0-1. mos8742. noarch 9.0.0-1. mos8458. noarch mcagents- 9.0.0-1. mos750. noarch fuelclient- 9.0.0-1. mos325. noarch 0.0-1.mos6349. noarch 9.0.0-1. mos8458. noarch 9.0.0-1. mos6349. noarch ing-scripts- 9.0.0-1. mos8742. noarch 0-9.0.0- 1.mos8458. noarch checker- 9.0.0-1. mos74.x86_ 64 9.0.0-1. mos285. noarch 9.0.0-1. mos2717. noarch 9.0.0-1. mos936. noarch 9.0.0-1. mos274. noarch 9.0.0-1. mos8742. noarch
482
cat /etc/fuel_
482
cat /etc/fuel_release:
9.0
cat /etc/fuel_
mitaka-9.0
rpm -qa | egrep 'fuel|astute|
fuel-release-
fuel-misc-
python-
fuel-bootstrap
fuel-migrate-
rubygem-
fuel-mirror-
shotgun-
fuel-openstack
fuel-notify-
nailgun-
python-
fuel-9.
fuel-utils-
fuel-setup-
fuel-provision
fuel-library9.
network-
fuel-agent-
fuel-ui-
fuel-ostf-
fuelmenu-
fuel-nailgun-
Additional information:
It reproduced only on 5th-time migration. My list of nodes during migration looks like:
node_4 -> node_5
node_5 -> node_4
node_4 -> node_5
node_5 -> node_4
node_4 -> node_5 - error
Link on snapshot: /drive. google. com/uc? export= download& id=0B05EZCZN- hilWHJQLV8xUGlG Wk0
https:/