Public bug reported: when a live-migration in process, the resource tracker in dest don't take it into account, which means resource in dest won't be occupied by the live-migration.
Steps to reproduce ================== 1. nova hypervisor-show HyperName 2. nova live-migration --block-migrate 15ef4dc6-0b6d-4ce0-8ffe-6e8d838639be HostName 3. nova hypervisor-show HyperName (when this live-migration(step 2) is still running, but after CONF.update_resources_interval seconds) Expected result =============== free_ram_mb_new == free_ram_mb_old - instance.flavor.memory_mb Actual result ============= free_ram_mb_new == free_ram_mb_old Environment =========== $rpm -qa | grep nova python-novaclient-2.30.1-1.el7.noarch openstack-nova-conductor-12.0.0-1.el7.centos.noarch python-nova-12.0.0-1.el7.centos.noarch openstack-nova-scheduler-12.0.0-1.el7.centos.noarch openstack-nova-novncproxy-12.0.0-1.el7.centos.noarch openstack-nova-api-12.0.0-1.el7.centos.noarch openstack-nova-common-12.0.0-1.el7.centos.noarch openstack-nova-cert-12.0.0-1.el7.centos.noarch openstack-nova-console-12.0.0-1.el7.centos.noarch ** Affects: nova Importance: Undecided Assignee: czy (rcmerci) Status: New ** Changed in: nova Assignee: (unassigned) => czy (rcmerci) -- 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/1697877 Title: make rt track live-migration Status in OpenStack Compute (nova): New Bug description: when a live-migration in process, the resource tracker in dest don't take it into account, which means resource in dest won't be occupied by the live-migration. Steps to reproduce ================== 1. nova hypervisor-show HyperName 2. nova live-migration --block-migrate 15ef4dc6-0b6d-4ce0-8ffe-6e8d838639be HostName 3. nova hypervisor-show HyperName (when this live-migration(step 2) is still running, but after CONF.update_resources_interval seconds) Expected result =============== free_ram_mb_new == free_ram_mb_old - instance.flavor.memory_mb Actual result ============= free_ram_mb_new == free_ram_mb_old Environment =========== $rpm -qa | grep nova python-novaclient-2.30.1-1.el7.noarch openstack-nova-conductor-12.0.0-1.el7.centos.noarch python-nova-12.0.0-1.el7.centos.noarch openstack-nova-scheduler-12.0.0-1.el7.centos.noarch openstack-nova-novncproxy-12.0.0-1.el7.centos.noarch openstack-nova-api-12.0.0-1.el7.centos.noarch openstack-nova-common-12.0.0-1.el7.centos.noarch openstack-nova-cert-12.0.0-1.el7.centos.noarch openstack-nova-console-12.0.0-1.el7.centos.noarch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1697877/+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