Thanks for the response. I have stopped and started the nova-compute service. The re-starting of nova-compute service is shown in the log (I am not sure why the stopping of nova-compute service is not shown; probably I should use "raw").
stack@devstack01:~/devstack$ systemctl start [email protected] ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to start '[email protected]'. Authenticating as: stack,,, (stack) Password: ==== AUTHENTICATION COMPLETE === BR/Perry ** Changed in: nova Status: Invalid => Incomplete -- 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/1714247 Title: Cleaning up deleted instances leaks resources Status in OpenStack Compute (nova): Incomplete Bug description: When the '_cleanup_running_deleted_instances' nova-compute manager periodic task cleans up an instance that still exists on the host although being deleted from the DB, the according network info is not properly retrieved. For this reason, vif ports will not be cleaned up. In this situation there may also be stale volume connections. Those will be leaked as well as os-brick attempts to flush those inaccessible devices, which will fail. As per a recent os-brick change, a 'force' flag must be set in order to ignore flush errors. Log: http://paste.openstack.org/raw/620048/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1714247/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
