[Yahoo-eng-team] [Bug 1868889] [NEW] instance turned to "error" state after reboot compute node
Public bug reported: Description === The instance turned to "error" state after reboot compute node. And I tried the "nova reset-state --active" command, the instance turned into active state. But, when I login the compute node and use "virsh list" command, there are no instance on the compute node.Then, I ran the "openstack server stop" and "openstack server start" command.After that, the server recovered. Steps to reproduce == 1. Create a instance 2. Confirm the compute node the instance running on 3. Reboot the compute node === After the execution of the steps above, what should have happened if the issue wasn't present? the server shoud migrated to other compute nodes or should recover automatically after the conpute node reboot. Actual result = the server turned into "error" state Environment === 1. Exact version of OpenStack you are running. See the following list for all releases: http://docs.openstack.org/releases/ 18.2.3 2. Which hypervisor did you use? Libvirt + KVM 2. Which storage type did you use? Ceph 3. Which networking type did you use? Neutron with OpenVSwitch ** Affects: nova Importance: Undecided Status: New -- 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/1868889 Title: instance turned to "error" state after reboot compute node Status in OpenStack Compute (nova): New Bug description: Description === The instance turned to "error" state after reboot compute node. And I tried the "nova reset-state --active" command, the instance turned into active state. But, when I login the compute node and use "virsh list" command, there are no instance on the compute node.Then, I ran the "openstack server stop" and "openstack server start" command.After that, the server recovered. Steps to reproduce == 1. Create a instance 2. Confirm the compute node the instance running on 3. Reboot the compute node === After the execution of the steps above, what should have happened if the issue wasn't present? the server shoud migrated to other compute nodes or should recover automatically after the conpute node reboot. Actual result = the server turned into "error" state Environment === 1. Exact version of OpenStack you are running. See the following list for all releases: http://docs.openstack.org/releases/ 18.2.3 2. Which hypervisor did you use? Libvirt + KVM 2. Which storage type did you use? Ceph 3. Which networking type did you use? Neutron with OpenVSwitch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1868889/+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
[Yahoo-eng-team] [Bug 1868890] [NEW] instance turned to "error" state after reboot compute node
Public bug reported: Description === The instance turned to "error" state after reboot compute node. And I tried the "nova reset-state --active" command, the instance turned into active state. But, when I login the compute node and use "virsh list" command, there are no instance on the compute node.Then, I ran the "openstack server stop" and "openstack server start" command.After that, the server recovered. Steps to reproduce == 1. Create a instance 2. Confirm the compute node the instance running on 3. Reboot the compute node === After the execution of the steps above, what should have happened if the issue wasn't present? the server shoud migrated to other compute nodes or should recover automatically after the conpute node reboot. Actual result = the server turned into "error" state Environment === 1. Exact version of OpenStack you are running. See the following list for all releases: http://docs.openstack.org/releases/ 18.2.3 2. Which hypervisor did you use? Libvirt + KVM 2. Which storage type did you use? Ceph 3. Which networking type did you use? Neutron with OpenVSwitch ** Affects: nova Importance: Undecided Status: New -- 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/1868890 Title: instance turned to "error" state after reboot compute node Status in OpenStack Compute (nova): New Bug description: Description === The instance turned to "error" state after reboot compute node. And I tried the "nova reset-state --active" command, the instance turned into active state. But, when I login the compute node and use "virsh list" command, there are no instance on the compute node.Then, I ran the "openstack server stop" and "openstack server start" command.After that, the server recovered. Steps to reproduce == 1. Create a instance 2. Confirm the compute node the instance running on 3. Reboot the compute node === After the execution of the steps above, what should have happened if the issue wasn't present? the server shoud migrated to other compute nodes or should recover automatically after the conpute node reboot. Actual result = the server turned into "error" state Environment === 1. Exact version of OpenStack you are running. See the following list for all releases: http://docs.openstack.org/releases/ 18.2.3 2. Which hypervisor did you use? Libvirt + KVM 2. Which storage type did you use? Ceph 3. Which networking type did you use? Neutron with OpenVSwitch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1868890/+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
[Yahoo-eng-team] [Bug 1863755] [NEW] default vcpus_used and memory_mb_used for ironic baremetal node was not 0
Public bug reported: Description === When a baremetal node enrolled to ironic, nova whould create one hypervisor for the baremeatl node.By default the values of vcpus_used and memory_mb_used was not 0, even though no instance scheduled to this baremeatl nodes. Steps to reproduce == Enroll a baremeatl node and a hypervisor would be created automatically. Expected result === vcpus_used and memory_mb_used of the new hypervisor would be 0. Actual result = vcpus_used and memory_mb_used was not 0. Environment === 1. Exact version of OpenStack you are running. See the following 18.2.3 2. Which hypervisor did you use? ironic 11.1.3 2. Which storage type did you use? LVM 3. Which networking type did you use? Neutron ** Affects: nova Importance: Undecided Status: New -- 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/1863755 Title: default vcpus_used and memory_mb_used for ironic baremetal node was not 0 Status in OpenStack Compute (nova): New Bug description: Description === When a baremetal node enrolled to ironic, nova whould create one hypervisor for the baremeatl node.By default the values of vcpus_used and memory_mb_used was not 0, even though no instance scheduled to this baremeatl nodes. Steps to reproduce == Enroll a baremeatl node and a hypervisor would be created automatically. Expected result === vcpus_used and memory_mb_used of the new hypervisor would be 0. Actual result = vcpus_used and memory_mb_used was not 0. Environment === 1. Exact version of OpenStack you are running. See the following 18.2.3 2. Which hypervisor did you use? ironic 11.1.3 2. Which storage type did you use? LVM 3. Which networking type did you use? Neutron To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1863755/+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
[Yahoo-eng-team] [Bug 1860312] [NEW] compute service failed to delete
Public bug reported: Description === I deployed openstack with openstack-helm on kubernetes.When one of the nova-compute service(driver=ironic replica of the deployment is 1) breakdown.It may be scheduled to another node by kubernetes.When I try to delete the old compute service(status down), it failed. Steps to reproduce == Firstly, openstack was deployed in kubernetes cluster, and the replica of the nova-compute-ironic is 1. * I deleted the pod nova-compute-ironic-x * then wait for the new pod to start * then exec openstack compute service list, there will be two compute service for ironic, the status of the old one would be down. * then I try to delete the old compute service Expected result === the old compute service could be deleted successfully Actual result = failed to delete, and returned an http 500 Environment === 1. Exact version of OpenStack you are running. See the following 18.2.2, rocky 2. Which hypervisor did you use? Libvirt + KVM 2. Which storage type did you use? ceph 3. Which networking type did you use? Neutron with OpenVSwitch Logs & Configs == 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi [req-922cc601-9aa1-4c3d-ad9c-71f73a341c28 40e7b8c3d59943e08a52acd24fe30652 d13f1690c08d41ac854d720ea510a710 - default default] Unexpected exception in API method: ComputeHostNotFound: Compute host mgt-slave03 could not be found. 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi Traceback (most recent call last): 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi File "/var/lib/openstack/local/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 801, in wrapped 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi return f(*args, **kwargs) 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi File "/var/lib/openstack/local/lib/python2.7/site-packages/nova/api/openstack/compute/services.py", line 252, in delete 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi context, service.host) 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi File "/var/lib/openstack/local/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 184, in wrapper 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi result = fn(cls, context, *args, **kwargs) 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi File "/var/lib/openstack/local/lib/python2.7/site-packages/nova/objects/compute_node.py", line 443, in get_all_by_host 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi use_slave=use_slave) 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi File "/var/lib/openstack/local/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 213, in wrapper 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi return f(*args, **kwargs) 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi File "/var/lib/openstack/local/lib/python2.7/site-packages/nova/objects/compute_node.py", line 438, in _db_compute_node_get_all_by_host 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi return db.compute_node_get_all_by_host(context, host) 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi File "/var/lib/openstack/local/lib/python2.7/site-packages/nova/db/api.py", line 291, in compute_node_get_all_by_host 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi return IMPL.compute_node_get_all_by_host(context, host) 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi File "/var/lib/openstack/local/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 258, in wrapped 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi return f(context, *args, **kwargs) 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi File "/var/lib/openstack/local/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 659, in compute_node_get_all_by_host 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi raise exception.ComputeHostNotFound(host=host) 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi ComputeHostNotFound: Compute host mgt-slave03 could not be found. 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi [req-922cc601-9aa1-4c3d-ad9c-71f73a341c28 40e7b8c3d59943e08a52acd24fe30652 d13f1690c08d41ac854d720ea510a710 - default default] Unexpected exception in API method: ComputeHostNotFound: Compute host mgt-slave03 could not be found. 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi Traceback (most recent call last): 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi File "/var/lib/openstack/local/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 801, in wrapped 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi return f(*args, **kwargs) 2020-01-20 06:44:53.480 1 ERROR nova.api.openstack.wsgi File
