[Yahoo-eng-team] [Bug 1982040] Re: stable/xena unable to attach multi-attach volume via "openstack nova add volume"
Marking this bug Invalid, as it is resolved after providing microversion with the command. ** Changed in: nova Status: Incomplete => Invalid -- 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/1982040 Title: stable/xena unable to attach multi-attach volume via "openstack nova add volume" Status in OpenStack Compute (nova): Invalid Bug description: Dear all I have encountered an error with Openstack Heat but I think this is something that is also affecting (or even caused by) a possible issue with nova. Here my post for HEAT team https://storyboard.openstack.org/#!/story/2010157 I have installed stable/xena using openstack-ansible and I am operating several test vms in my ecosystem before to move to a production stage. Currently I am using Cinder integrated with Ceph (if you think it may be of any interest). Just to summarize a possible test procedure (for convenience I simply use CLI but with Horizon there is another workaround that I presented in the storyboard's post above): - create a multi-attach volume - create 2 instances that potentially want to share the volume - attach the volume to the first instance [it will work great!] - attache the volume to a second instance... you should receive the following error: openstack server add volume --device /dev/vdb Multiattach volumes are only supported starting with compute API version 2.60. (HTTP 400) (Request-ID: req-5a60e72a-b7e2-49d6-81b2-c15753e054a2) BUT If I use the following command on the second attach: nova volume-attach auto +---+--+ | Property | Value| +---+--+ | delete_on_termination | False| | device| /dev/vdb | | id| c292cdd5-7dc5-4714-bdb3-a309e8416232 | | serverId | 7b6a0651-f4cd-4018-a042-58f695ab73aa | | tag | -| | volumeId | c292cdd5-7dc5-4714-bdb3-a309e8416232 | +---+--+ it works properly! Is it expected because of some implementation task or is it a potential bug? Actually I am able to create and use multi-attach volumes but only by making manually the attachment with the commands reported above. Thanks for your kind attention and looking forward to hear by you. Best regards, Davide To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1982040/+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 1975891] [NEW] Add missing if condition
Public bug reported: The change [1] added src|dst_supports_numa_live_migration fields to LibvirtLiveMigrateData object, where if condition for dst_supports_numa_live_migration is missing in obj_make_compatible method [2]. This wasn't catched earlier because of typo in unit test [3]. [1] https://opendev.org/openstack/nova/commit/71fafa5b19de98cbd2fb7b8e4a086521c9786638 [2] https://opendev.org/openstack/nova/src/branch/master/nova/objects/migrate_data.py#L279-L283 [3] https://opendev.org/openstack/nova/src/branch/master/nova/tests/unit/objects/test_migrate_data.py#L98 ** Affects: nova Importance: Undecided Assignee: Rajesh Tailor (ratailor) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (ratailor) -- 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/1975891 Title: Add missing if condition Status in OpenStack Compute (nova): In Progress Bug description: The change [1] added src|dst_supports_numa_live_migration fields to LibvirtLiveMigrateData object, where if condition for dst_supports_numa_live_migration is missing in obj_make_compatible method [2]. This wasn't catched earlier because of typo in unit test [3]. [1] https://opendev.org/openstack/nova/commit/71fafa5b19de98cbd2fb7b8e4a086521c9786638 [2] https://opendev.org/openstack/nova/src/branch/master/nova/objects/migrate_data.py#L279-L283 [3] https://opendev.org/openstack/nova/src/branch/master/nova/tests/unit/objects/test_migrate_data.py#L98 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1975891/+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 1909745] Re: Compute API in nova / Default for all_tenants is actually false not true
** Changed in: nova Status: Confirmed => Fix Released -- 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/1909745 Title: Compute API in nova / Default for all_tenants is actually false not true Status in OpenStack Compute (nova): Fix Released Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: Doc states that in list servers the default value for all_tenants is true. At least for Train it is actually false. --- Release: on 2020-03-11 10:38:56 SHA: d3bf430fc9eabbb09cefd59717e89c6f70f2ac18 Source: https://opendev.org/openstack/nova/src/api-ref/source/index.rst URL: https://docs.openstack.org/api-ref/compute/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1909745/+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 1741000] [NEW] Can't force-delete instance with task_state not 'None'
Public bug reported:
Problem Description:
When user tries to force-delete instance which is not in task_state
'None', throws 500 error on console, as below:
ERROR (ClientException): Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
(HTTP 500) (Request-ID:
req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8)
Steps to reproduce:
1) Create instance.
$ nova boot --flavor --image
2) To change the instance task_state to anything other than 'None', I tried to
resize the instance.
$ nova resize
3) Try to force-delete instance, just after above step, so that instance task
state is anything in (resize_prep, resize_migrating, resize_migrated,
resize_finish), but not 'None'.
$ nova force-delete
4) User gets below error on console:
ERROR (ClientException): Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
(HTTP 500) (Request-ID:
req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8)
Actual result:
User gets 500 ClientException Error.
Expected result:
The instance should be deleted without any error.
traceback from nova-api logs:
DEBUG oslo_concurrency.lockutils [None req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8
demo demo] Lock "fbe6eec8-be64-4473-8434-1d795e7ca5fb" released by
"nova.context.get_or_set_cached_cell_and_set_connections" :: held 0.0
00s {{(pid=24369) inner
/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:285}}
ERROR nova.api.openstack.wsgi [None req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8
demo demo] Unexpected exception in API method: InstanceInvalidState: Instance
6abb021a-174e-4551-acc1-a96653a9bf83 in task_state resize_prep. Cannot
force_delete while the instance is in this state.
ERROR nova.api.openstack.wsgi Traceback (most recent call last):
ERROR nova.api.openstack.wsgi File
"/opt/stack/nova/nova/api/openstack/wsgi.py", line 803, in wrapped
ERROR nova.api.openstack.wsgi return f(*args, **kwargs)
ERROR nova.api.openstack.wsgi File
"/opt/stack/nova/nova/api/openstack/compute/deferred_delete.py", line 61, in
_force_delete
ERROR nova.api.openstack.wsgi self.compute_api.force_delete(context,
instance)
ERROR nova.api.openstack.wsgi File "/opt/stack/nova/nova/compute/api.py",
line 201, in inner
ERROR nova.api.openstack.wsgi return function(self, context, instance,
*args, **kwargs)
ERROR nova.api.openstack.wsgi File "/opt/stack/nova/nova/compute/api.py",
line 141, in inner
ERROR nova.api.openstack.wsgi method=f.__name__)
ERROR nova.api.openstack.wsgi InstanceInvalidState: Instance
6abb021a-174e-4551-acc1-a96653a9bf83 in task_state resize_prep. Cannot
force_delete while the instance is in this state.
ERROR nova.api.openstack.wsgi
INFO nova.api.openstack.wsgi [None req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8
demo demo] HTTP exception thrown: Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
DEBUG nova.api.openstack.wsgi [None req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8
demo demo] Returning 500 to user: Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
NOTE: If user tries delete api instead of force-delete api for instance
deletion, in that case instance is deleted and no error is thrown.
** Affects: nova
Importance: Undecided
Assignee: Rajesh Tailor (ratailor)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Rajesh Tailor (ratailor)
** Changed in: nova
Status: New => In Progress
--
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/1741000
Title:
Can't force-delete instance with task_state not 'None'
Status in OpenStack Compute (nova):
In Progress
Bug description:
Problem Description:
When user tries to force-delete instance which is not in task_state
'None', throws 500 error on console, as below:
ERROR (ClientException): Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
(HTTP 500) (Request-ID:
req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8)
Steps to reproduce:
1) Create instance.
$ nova boot --flavor --image
2) To change the instance task_state to anything other than 'None', I tried
to resize the instance.
$ nova resize
3) Try to force-delete instance, just after above step, so that instance task
state is anything in (resize_prep, resize_migrating, resize_migrated,
resize_finish), but not 'None'.
$ nova force-delete
4) User gets below error on console:
ERROR (ClientException): Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and att
[Yahoo-eng-team] [Bug 1720062] [NEW] Nova unit tests are failing
Public bug reported:
Following nova unit tests are failing, when running with testtools using
below command.
$ python -m testtools.run nova.tests.unit.test_wsgi
[1] nova.tests.unit.test_wsgi.TestWSGIServerWithSSL.test_two_servers
[2] nova.tests.unit.test_wsgi.TestWSGIServerWithSSL.test_ssl_server
[3] nova.tests.unit.test_wsgi.TestWSGIServerWithSSL.test_app_using_ipv6_and_ssl
Traceback is similar caused by the SSLError, CertificateError. It's
because hostname doesn't match one from cert, sample:
Captured traceback:
~~~
Traceback (most recent call last):
File "nova/tests/unit/test_wsgi.py", line 278, in test_two_servers
verify=os.path.join(SSL_CERT_DIR, 'ca.crt'), data='PING')
File "/usr/lib/python2.7/site-packages/requests/api.py", line 112, in post
return request('post', url, data=data, json=json, **kwargs)
File "/usr/lib/python2.7/site-packages/requests/api.py", line 58, in
request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 508,
in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 618,
in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python2.7/site-packages/requests/adapters.py", line 506,
in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='127.0.0.1',
port=38499): Max retries exceeded with url: / (Caused by
SSLError(CertificateError("hostname '127.0.0.1' doesn't match either of
'localhost', 'ip6-localhost'",),))
** Affects: nova
Importance: Undecided
Status: New
** Description changed:
- Following nova unit tests are failing, when running with below command.
+ Following nova unit tests are failing, when running with testtools using
+ below command.
$ python -m testtools.run nova.tests.unit.test_wsgi
[1] nova.tests.unit.test_wsgi.TestWSGIServerWithSSL.test_two_servers
[2] nova.tests.unit.test_wsgi.TestWSGIServerWithSSL.test_ssl_server
[3]
nova.tests.unit.test_wsgi.TestWSGIServerWithSSL.test_app_using_ipv6_and_ssl
Traceback is similar caused by the SSLError, CertificateError. It's
because hostname doesn't match one from cert, sample:
-
Captured traceback:
~~~
- Traceback (most recent call last):
- File "nova/tests/unit/test_wsgi.py", line 278, in test_two_servers
- verify=os.path.join(SSL_CERT_DIR, 'ca.crt'), data='PING')
- File "/usr/lib/python2.7/site-packages/requests/api.py", line 112, in
post
- return request('post', url, data=data, json=json, **kwargs)
- File "/usr/lib/python2.7/site-packages/requests/api.py", line 58, in
request
- return session.request(method=method, url=url, **kwargs)
- File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 508,
in request
- resp = self.send(prep, **send_kwargs)
- File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 618,
in send
- r = adapter.send(request, **kwargs)
- File "/usr/lib/python2.7/site-packages/requests/adapters.py", line 506,
in send
- raise SSLError(e, request=request)
- requests.exceptions.SSLError: HTTPSConnectionPool(host='127.0.0.1',
port=38499): Max retries exceeded with url: / (Caused by
SSLError(CertificateError("hostname '127.0.0.1' doesn't match either of
'localhost', 'ip6-localhost'",),))
+ Traceback (most recent call last):
+ File "nova/tests/unit/test_wsgi.py", line 278, in test_two_servers
+ verify=os.path.join(SSL_CERT_DIR, 'ca.crt'), data='PING')
+ File "/usr/lib/python2.7/site-packages/requests/api.py", line 112, in
post
+ return request('post', url, data=data, json=json, **kwargs)
+ File "/usr/lib/python2.7/site-packages/requests/api.py", line 58, in
request
+ return session.request(method=method, url=url, **kwargs)
+ File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 508,
in request
+ resp = self.send(prep, **send_kwargs)
+ File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 618,
in send
+ r = adapter.send(request, **kwargs)
+ File "/usr/lib/python2.7/site-packages/requests/adapters.py", line 506,
in send
+ raise SSLError(e, request=request)
+ requests.exceptions.SSLError: HTTPSConnectionPool(host='127.0.0.1',
port=38499): Max retries exceeded with url: / (Caused by
SSLError(CertificateError("hostname '127.0.0.1' doesn't match either of
'localhost', 'ip6-localhost'",),))
--
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/1720062
Title:
Nova unit tests are failing
Status in OpenStack Compute (nova):
New
Bug description:
Following nova unit tests are failing, when running with
[Yahoo-eng-team] [Bug 1709260] [NEW] Addition of host to host-aggregate should be case -sensitive
Public bug reported:
I have multinode devstack setup with 2 compute and a controller node.
The hostnames of the nodes are as follows:
controller: controller.example.com
compute0: compute0.example.com
compute1: compute1.example.com
Reproduction steps:
1) I have created a host-aggregate in availability zone "nova".
nova aggregate-create test_agg nova
2) Then I set metadata on that host-aggregate.
nova aggregate-set-metadata 1 ssd=true
3) Then I added compute hosts mentioned above to host-aggregate.
nova aggregate-add-host test_agg COMPUTE0.example.com
nova aggregate-add-host test_agg compute1.example.com
While adding compute0 to host-aggregate, if I provide hostname as
"COMPUTE0.example.com", instead of
throwing HostNotFound error, it is added to host-aggregate.
4) After that I have created a flavor.
nova flavor-create ssd.large 6 8192 80 4
5) Added metadata to flavor.
nova flavor-key ssd.large set ssd=true
Now when I try to create instance with above mentioned flavor, I can't
spawn it on compute0 host. As scheduler is filtering only compute1 with
AggregateInstanceExtraSpecsFilter filter.
Expected Result: while adding the case-sensitive host to host-aggregate,
nova-api should have thrown HostNotFound error.
** Affects: nova
Importance: Undecided
Assignee: Rajesh Tailor (ratailor)
Status: New
** Changed in: nova
Assignee: (unassigned) => Rajesh Tailor (ratailor)
--
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/1709260
Title:
Addition of host to host-aggregate should be case -sensitive
Status in OpenStack Compute (nova):
New
Bug description:
I have multinode devstack setup with 2 compute and a controller node.
The hostnames of the nodes are as follows:
controller: controller.example.com
compute0: compute0.example.com
compute1: compute1.example.com
Reproduction steps:
1) I have created a host-aggregate in availability zone "nova".
nova aggregate-create test_agg nova
2) Then I set metadata on that host-aggregate.
nova aggregate-set-metadata 1 ssd=true
3) Then I added compute hosts mentioned above to host-aggregate.
nova aggregate-add-host test_agg COMPUTE0.example.com
nova aggregate-add-host test_agg compute1.example.com
While adding compute0 to host-aggregate, if I provide hostname as
"COMPUTE0.example.com", instead of
throwing HostNotFound error, it is added to host-aggregate.
4) After that I have created a flavor.
nova flavor-create ssd.large 6 8192 80 4
5) Added metadata to flavor.
nova flavor-key ssd.large set ssd=true
Now when I try to create instance with above mentioned flavor, I can't
spawn it on compute0 host. As scheduler is filtering only compute1
with AggregateInstanceExtraSpecsFilter filter.
Expected Result: while adding the case-sensitive host to host-
aggregate, nova-api should have thrown HostNotFound error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1709260/+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 1512880] Re: Failed cold migration with SR-IOV
** Changed in: nova/newton
Status: In Progress => Fix Released
--
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/1512880
Title:
Failed cold migration with SR-IOV
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) newton series:
Fix Released
Bug description:
Cold migration of an instance that has an SR-IOV interface fails to
migrate because on migrated compute's nova is trying to use the PCI
device/address that has been allocated from the incoming compute.
Obviously this is failing since the PCI device is not present on the
migrated compute.
See the error "libvirtError: Device :83:10.6 not found: could not
access /sys/bus/pci/devices/:83:10.6/config: No such file or
directory" in the log in the attachment.
Nova should allocate a new PCI device based the hardware configuration
of the compute where the instance is being migrated and this PCI
device should be use to create the instance XML.
Nova version:
commit 2397d636ff6ea3767fe62ee681d609fce4fc98ca
Author: OpenStack Proposal Bot
Date: Tue Oct 27 06:30:34 2015 +
Imported Translations from Zanata
For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure
Change-Id: I38f537e37972e5ddae13d388021412d85f6be898
Devstack setup:
* One server configured with controller and compute functions
* Intel 10G port is configured with 8 VFs: $ echo 8 >
/sys/bus/pci/devices/\:85\:00.0/sriov_numvfs
* /etc/nova/nova.conf: pci_passthrough_whitelist =
{"address":"*:85:10.*","physical_network":"default"}
* One server configured with compute function only
* Intel 10G port is configured with 8 VFs: $ echo 8 >
/sys/bus/pci/devices/\:83\:00.0/sriov_numvfs
* /etc/nova/nova.conf: pci_passthrough_whitelist =
{"address":"*:83:10.*","physical_network":"default"}
* Note that it is important for this test that the PCI addresses for the
SR-IOV interfaces are different. We want to validate that new PCI devices are
claimed/allocated on the incoming compute.
Reproduce steps:
1) Boot an instance with an SR-IOV interface:
$ NETID=`neutron net-list | grep default | awk '{print $2}'`
$ neutron port-create $NETID --binding:vnic-type direct --name p-direct
$ PORTID=`neutron port-list | grep "p-direct" | awk '{print $2}'`
$ nova boot test --image=ubuntu --nic port-id=$PORTID --flavor=m1.small
2) Migrate the instance to the other compute:
$ nova migrate test
Expected result:
The instance is successfully migrated on the other server.
Actual result:
The instance failed to migrate. Instance is stuck in error. See log
in attachment for more information.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1512880/+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 1589821] [NEW] cleanup_incomplete_migrations periodic task regression with commit 099cf53925c0a0275325339f21932273ee9ce2bc
Public bug reported: Patch [1] changes the instance filtering condition in periodic task "cleanup_incomplete_migrations" introduced in [2], in such a way that it generates new issue, [3] After change [1] lands, the condition changes filtering logic, so now all instances on current host are filtered, which is not expected. We should filter all instances which where instance uuid is filtered as per migration records. [1] https://review.openstack.org/#/c/256102/ [2] https://review.openstack.org/#/c/219299/ [2] https://bugs.launchpad.net/nova/+bug/1586309 ** Affects: nova Importance: Undecided Assignee: Rajesh Tailor (ratailor) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (ratailor) -- 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/1589821 Title: cleanup_incomplete_migrations periodic task regression with commit 099cf53925c0a0275325339f21932273ee9ce2bc Status in OpenStack Compute (nova): In Progress Bug description: Patch [1] changes the instance filtering condition in periodic task "cleanup_incomplete_migrations" introduced in [2], in such a way that it generates new issue, [3] After change [1] lands, the condition changes filtering logic, so now all instances on current host are filtered, which is not expected. We should filter all instances which where instance uuid is filtered as per migration records. [1] https://review.openstack.org/#/c/256102/ [2] https://review.openstack.org/#/c/219299/ [2] https://bugs.launchpad.net/nova/+bug/1586309 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1589821/+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 1578486] Re: Not able to launch instance in liberty version
*** This bug is a duplicate of bug 1536501 *** https://bugs.launchpad.net/bugs/1536501 ** This bug has been marked a duplicate of bug 1536501 type 'exceptions.ValueError'> (HTTP 500) -- 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/1578486 Title: Not able to launch instance in liberty version Status in OpenStack Compute (nova): New Bug description: Description: == I am not able to launch a instance in newly created openstack liberty version. Steps to reproduce: While I am creating the instance I am getting an error mentioned below Error: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req- dc754939-d6fd-4138-8c6c-19eb80de57f0) Expected Result = Instance should be launched proeprly. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1578486/+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 1557482] Re: nova hypervisor-list will generate exception
** Changed in: nova Status: Incomplete => Invalid -- 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/1557482 Title: nova hypervisor-list will generate exception Status in OpenStack Compute (nova): Invalid Bug description: Version: Liberty. OS: controller & compute node are ubuntu 14.04 server, follow the doc to install. After installed Using "nova host-list" will get the result correctly +--+-+--+ | host_name| service | zone | +--+-+--+ | controller | cert| internal | | controller | scheduler | internal | | controller | consoleauth | internal | | controller | conductor | internal | | compute-node-164 | compute | nova | +--+-+--+ but if use "nova hypervisor-list" ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-0649f773-8b50-4b84-a670-d8c290f77439) From the dashboard, in the System -> hypervisor panel, I can not find the hypervisor. when navigate to this page, an error will display get not the hypervisor informatin. The compute node is displayed on "Compute Host" tab, not not in the Hypervisor tab. version_instgalled: ii nova-api 2:12.0.1-0ubuntu1~cloud0 all OpenStack Compute - API frontend ii nova-cert2:12.0.1-0ubuntu1~cloud0 all OpenStack Compute - certificate management ii nova-common 2:12.0.1-0ubuntu1~cloud0 all OpenStack Compute - common files ii nova-conductor 2:12.0.1-0ubuntu1~cloud0 all OpenStack Compute - conductor service ii nova-consoleauth 2:12.0.1-0ubuntu1~cloud0 all OpenStack Compute - Console Authenticator ii nova-novncproxy 2:12.0.1-0ubuntu1~cloud0 all OpenStack Compute - NoVNC proxy ii nova-scheduler 2:12.0.1-0ubuntu1~cloud0 all OpenStack Compute - virtual machine scheduler ii python-nova 2:12.0.1-0ubuntu1~cloud0 all OpenStack Compute Python libraries ii python-novaclient2:2.30.1-1~cloud0 all client library for OpenStack Compute API nova-api.log below cut here -- 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions [req-7ddb9e1f-b74a-4df0-ade6-2b364a66ac36 c7922dbbc15b4e5e9ba93acba512e746 cfd6638eca634eb68060e6090ea105b1 - - -] Unexpected exception in API method 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/openstack/extensions.py", line 478, in wrapped 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/openstack/compute/hypervisors.py", line 101, in detail 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions for hyp in compute_nodes]) 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 3504, in service_get_by_compute_host 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions return objects.Service.get_by_compute_host(context, host_name) 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 171, in wrapper 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions result = fn(cls, context, *args, **kwargs) 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/objects/service.py", line 222, in get_by_compute_host 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions db_service = db.service_get_by_compute_host(context, host) 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/db/api.py", line 139, in service_get_by_compute_host 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions use_slave=use_slave) 2016-03-05 00:16:02.073 2798 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 500, in service_get_by_compute_host 2016-03-05 00:16:0
[Yahoo-eng-team] [Bug 1433435] Re: Change http_keepalive default value from Ture to False
** Changed in: glance Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1433435 Title: Change http_keepalive default value from Ture to False Status in Glance: Invalid Bug description: In order to close the client socket connection explicitly after the response is sent and read successfully by the client, you simply have to set keepalive to False when you create a wsgi server. Right now it is set to True for backward compatibility. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1433435/+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 1494653] [NEW] Remove unnecessary 'context' parameter from quotas reserve method call
e 270, in iterencode
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] return _iterencode(o, 0)
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] ValueError: Circular reference detected
[1] https://review.openstack.org/#/c/164268/
[2] https://review.openstack.org/#/c/160499/
** Affects: nova
Importance: Undecided
Assignee: Rajesh Tailor (rajesh-tailor)
Status: New
** Changed in: nova
Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor)
** Summary changed:
- Remove 'context' parameter from quotas reserve method call
+ Remove unnecessary 'context' parameter from quotas reserve method call
--
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/1494653
Title:
Remove unnecessary 'context' parameter from quotas reserve method call
Status in OpenStack Compute (nova):
New
Bug description:
In patch [1] 'context' parameter was removed from quota-related remotable
method signatures.
In patch [2] use of 'context' parameter was removed from quota-related
remotable method calls.
Still there are some occurrances where 'context' parameter is passed
to quotas.reserve method which is leading to erorr "ValueError:
Circular reference detected".
2015-09-08 00:36:34.133 ERROR nova.compute.manager
[req-3222b8a4-0542-48cf-a2e1-c92e5fd91e5e None None] [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] Failed to complete a deletion
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] Traceback (most recent call last):
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] File
"/opt/stack/nova/nova/compute/manager.py", line 952, in _init_instance
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] self._complete_partial_deletion(context,
instance)
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] File
"/opt/stack/nova/nova/compute/manager.py", line 879, in _complete_partial_d
eletion
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] bdms =
objects.BlockDeviceMappingList.get_by_instance_uuid(
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] File
"/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", lin
e 197, in wrapper
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] ctxt, self, fn.__name__, args, kwargs)
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] File
"/opt/stack/nova/nova/conductor/rpcapi.py", line 246, in object_action
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] objmethod=objmethod, args=args,
kwargs=kwargs)
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] File
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/client.py", line
158, in call
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] retry=self.retry)
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] File
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/transport.py", line 90,
in _send
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] timeout=timeout, retry=retry)
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] File
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py",
line 431, in send
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] retry=retry)
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] File
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py",
line 399, in _send
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] msg = rpc_common.serialize_msg(msg)
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] File
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/common.py",
line 286, in serialize_msg
2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
00c7a9ae-bff1-461f-ab95-0e8f15327536] _MESSAGE_KEY: jsonutils.dumps(raw_msg)}
2015-09-08 00:36:34.133 TRACE nova.compu
[Yahoo-eng-team] [Bug 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong
** Also affects: keystone Importance: Undecided Status: New ** Changed in: keystone Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) ** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- 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/1259292 Title: Some tests use assertEqual(observed, expected) , the argument order is wrong Status in Ceilometer: Invalid Status in Cinder: Fix Released Status in Glance: New Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): In Progress Status in Keystone: New Status in Manila: In Progress Status in neutron: New Status in OpenStack Compute (nova): In Progress Status in python-ceilometerclient: In Progress Status in python-cinderclient: Fix Released Status in Sahara: Fix Released Bug description: The test cases will produce a confusing error message if the tests ever fail, so this is worth fixing. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1259292/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong
** Also affects: glance 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/1259292 Title: Some tests use assertEqual(observed, expected) , the argument order is wrong Status in Ceilometer: Invalid Status in Cinder: Fix Released Status in Glance: New Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): In Progress Status in Manila: In Progress Status in OpenStack Compute (nova): In Progress Status in python-ceilometerclient: In Progress Status in python-cinderclient: Fix Released Status in Sahara: Fix Released Bug description: The test cases will produce a confusing error message if the tests ever fail, so this is worth fixing. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1259292/+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 1493694] [NEW] On compute restart, quotas are not updated when instance vm_state is 'DELETED' but instance is not destroyed in db
l/lib/python2.7/dist-packages/oslo_serialization/jsonutils.py", line 185, in dumps 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] return json.dumps(obj, default=default, **kwargs) 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] File "/usr/lib/python2.7/json/__init__.py", line 250, in dumps 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] sort_keys=sort_keys, **kw).encode(obj) 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] File "/usr/lib/python2.7/json/encoder.py", line 207, in encode 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] chunks = self.iterencode(o, _one_shot=True) 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] File "/usr/lib/python2.7/json/encoder.py", line 270, in iterencode 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] return _iterencode(o, 0) 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] ValueError: Circular reference detected ** Affects: nova Importance: Undecided Assignee: Rajesh Tailor (rajesh-tailor) Status: New ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- 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/1493694 Title: On compute restart, quotas are not updated when instance vm_state is 'DELETED' but instance is not destroyed in db Status in OpenStack Compute (nova): New Bug description: This is a timing issue and can occur if instance delete call reaches to _delete_instance method in nova/compute/manager.py module and nova- compute crashes after setting instance vm_state to 'DELETED' but before destroying the instance in db. Now on restarting nova-compute service, _init_instance method call checks whether instance vm_state is 'DELETED' or not, if yes, then it tries to call _complete_partial_deletion method and destroys instance in db then raises "ValueError: Circular reference detected" and quota was not updated for that instance which is not as expected. Steps to reproduce: 1) Put a break point in nova/compute/manager.py module in _delete_instance method, just after updating instance vm_state to 'DELETED' but before destroying instance in db. 2) Create instance and wait until instance vm_state become 'ACTIVE'. $ nova boot --image --flavor 3) Send request to delete instance. $ nova delete 4) When delete request reaches to break point in nova-compute, make sure instance vm_state is marked as 'DELETED' and stop the nova-compute service. 5) Restart nova-compute service and in _init_instance method call below error (ValueError: Circular reference detected) will be raised and instance will be marked as deleted in db but quota for that instance will never be updated. 2015-09-08 00:36:34.133 ERROR nova.compute.manager [req-3222b8a4-0542-48cf-a2e1-c92e5fd91e5e None None] [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] Failed to complete a deletion 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] Traceback (most recent call last): 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] File "/opt/stack/nova/nova/compute/manager.py", line 952, in _init_instance 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] self._complete_partial_deletion(context, instance) 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] File "/opt/stack/nova/nova/compute/manager.py", line 879, in _complete_partial_d eletion 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] bdms = objects.BlockDeviceMappingList.get_by_instance_uuid( 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] File "/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", lin e 197, in wrapper 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] ctxt, self, fn.__name__, args, kwargs) 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance: 00c7a9ae-bff1-461f-ab95-0e8f15327536] File "/opt/stack/nova/nova/conductor/rpcapi.py", line 246, in object_action 2015-09-08 00:36:34.133 TRACE nova.compute.manager [instance:
[Yahoo-eng-team] [Bug 1459958] Re: Error messages returned to the user are not consistent across all apis
** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- 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/1459958 Title: Error messages returned to the user are not consistent across all apis Status in Cinder: Fix Released Status in OpenStack Compute (nova): New Bug description: Error messages returned to the user are not consistent across all apis in case of all exceptions derived from NotFound exception, e.g., VolumeNotFound, SnapshotNotFound etc. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1459958/+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 1482585] Re: Fix duplicate-key pylint issue
** Also affects: oslo.log Importance: Undecided Status: New ** Changed in: oslo.log Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1482585 Title: Fix duplicate-key pylint issue Status in Keystone: Fix Committed Status in oslo.log: In Progress Bug description: steps to list duplicate-key pylint issue: (1) Run below command: pylint --rcfile=.pylintrc -f parseable cinder/ | grep '\[W0109' To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1482585/+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 1482625] [NEW] Fix unreachable code in test_v3 module
Public bug reported: assertIsInstance method is unreachable in assertValidISO8601ExtendedFormatDateTime method in test_v3 module. ** Affects: keystone Importance: Undecided Assignee: Rajesh Tailor (rajesh-tailor) Status: In Progress ** Changed in: keystone Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1482625 Title: Fix unreachable code in test_v3 module Status in Keystone: In Progress Bug description: assertIsInstance method is unreachable in assertValidISO8601ExtendedFormatDateTime method in test_v3 module. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1482625/+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 1482585] [NEW] Fix duplicate-key pylint issue
Public bug reported: steps to list duplicate-key pylint issue: (1) Run below command: pylint --rcfile=.pylintrc -f parseable cinder/ | grep '\[W0109' ** Affects: keystone Importance: Undecided Assignee: Rajesh Tailor (rajesh-tailor) Status: In Progress ** Changed in: keystone Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1482585 Title: Fix duplicate-key pylint issue Status in Keystone: In Progress Bug description: steps to list duplicate-key pylint issue: (1) Run below command: pylint --rcfile=.pylintrc -f parseable cinder/ | grep '\[W0109' To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1482585/+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 1470420] [NEW] Set migration status to 'error' instead of 'failed' during live-migration
Public bug reported: In resize, confirm-resize and revert-resize operation, migration status is marked as 'error' in case of failure for respective operation. Migration object support is added in live-migration operation, which mark migration status to 'failed' if live-migration operation fails in-between. To make live-migration consistent with resize, confirm-resize and revert-resize operation, it needs to mark migration status to 'error' instead of 'failed' in case of failure. ** 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/1470420 Title: Set migration status to 'error' instead of 'failed' during live- migration Status in OpenStack Compute (Nova): New Bug description: In resize, confirm-resize and revert-resize operation, migration status is marked as 'error' in case of failure for respective operation. Migration object support is added in live-migration operation, which mark migration status to 'failed' if live-migration operation fails in-between. To make live-migration consistent with resize, confirm-resize and revert-resize operation, it needs to mark migration status to 'error' instead of 'failed' in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470420/+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 1465659] [NEW] Use utils.validate_integer for int validation
Public bug reported:
Instead of checking for int type and min value separately,
utils.validate_integer method can be used.
for eg.:
try:
rotation = int(rotation)
except ValueError:
msg = _("createBackup attribute 'rotation' must be an integer")
raise exc.HTTPBadRequest(explanation=msg)
if rotation < 0:
msg = _("createBackup attribute 'rotation' must be greater "
"than or equal to zero")
raise exc.HTTPBadRequest(explanation=msg)
can be replaced with
try:
rotation = utils.validate_integer(rotation, "rotation", min_value=0)
except exception.InvalidInput as e:
raise webob.exc.HTTPBadRequest(explanation=e.format_message())
** Affects: nova
Importance: Undecided
Assignee: Rajesh Tailor (rajesh-tailor)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor)
** Changed in: nova
Status: New => In Progress
--
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/1465659
Title:
Use utils.validate_integer for int validation
Status in OpenStack Compute (Nova):
In Progress
Bug description:
Instead of checking for int type and min value separately,
utils.validate_integer method can be used.
for eg.:
try:
rotation = int(rotation)
except ValueError:
msg = _("createBackup attribute 'rotation' must be an integer")
raise exc.HTTPBadRequest(explanation=msg)
if rotation < 0:
msg = _("createBackup attribute 'rotation' must be greater "
"than or equal to zero")
raise exc.HTTPBadRequest(explanation=msg)
can be replaced with
try:
rotation = utils.validate_integer(rotation, "rotation", min_value=0)
except exception.InvalidInput as e:
raise webob.exc.HTTPBadRequest(explanation=e.format_message())
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1465659/+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 1462992] Re: Fix all Bad indentation pylint issues
** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) ** Changed in: nova Status: New => In Progress -- 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/1462992 Title: Fix all Bad indentation pylint issues Status in Cinder: In Progress Status in OpenStack Compute (Nova): In Progress Bug description: Look for W0311 pylint issues. steps to list W0311 pylint issues: (1) Run below command: pylint --rcfile=.pylintrc -f parseable -i yes cinder/ | grep '\[W0311' To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1462992/+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 1463696] Re: Agent object save method doesn't raise ValueError
** Project changed: cinder => nova -- 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/1463696 Title: Agent object save method doesn't raise ValueError Status in OpenStack Compute (Nova): New Bug description: ValueError exception is unnecessarily caught while saving agent object in nova/api/openstack/compute/contrib/agent.py module. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1463696/+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 1461931] Re: __init__ method should not return any value explicitly
** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) ** Changed in: nova Status: New => In Progress -- 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/1461931 Title: __init__ method should not return any value explicitly Status in Cinder: Fix Committed Status in OpenStack Compute (Nova): In Progress Bug description: As per python documentation [1], __init__ method should not return any value explicitly, doing so will raise TypeError. [1] https://docs.python.org/2/reference/datamodel.html#object.__init__ To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1461931/+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 1444300] [NEW] nova-compute service doesn't restart if resize operation fails
e 445, in inner 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup return f(*args, **kwargs) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/compute/resource_tracker.py", line 445, in _update_available_resource 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup self._update_usage_from_migrations(context, resources, migrations) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/compute/resource_tracker.py", line 708, in _update_usage_from_migrations 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup instance = migration.instance 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/objects/migration.py", line 80, in instance 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup return objects.Instance.get_by_uuid(self._context, self.instance_uuid) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/objects/base.py", line 161, in wrapper 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup args, kwargs) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/conductor/rpcapi.py", line 325, in object_class_action 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup objver=objver, args=args, kwargs=kwargs) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/client.py", line 156, in call 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup retry=self.retry) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/transport.py", line 90, in _send 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup timeout=timeout, retry=retry) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 350, in send 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup retry=retry) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 341, in _send 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup raise result 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup InstanceNotFound_Remote: Instance 1f24201e-4eac-4dc4-9532-8fb863949a09 could not be found. 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup Traceback (most recent call last): 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/conductor/manager.py", line 423, in _object_dispatch 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup return getattr(target, method)(*args, **kwargs) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/objects/base.py", line 163, in wrapper 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup result = fn(cls, context, *args, **kwargs) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/objects/instance.py", line 564, in get_by_uuid 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup use_slave=use_slave) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/db/api.py", line 651, in instance_get_by_uuid 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup columns_to_join, use_slave=use_slave) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 233, in wrapper 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup return f(*args, **kwargs) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 1744, in instance_get_by_uuid 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup columns_to_join=columns_to_join, use_slave=use_slave) 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup 2015-04-14 23:31:31.256 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 1756, in _instance_get_by_uuid 2015-04-14 23:31:31.256 TRACE nova.open
[Yahoo-eng-team] [Bug 1398349] [NEW] nova service-update fails for services on non-child (top) cell
Public bug reported: Nova service-update fails for services on non-child (top) cell. How to reproduce: 1) List available services using below command. $ nova --os-username admin service-list Output: ++--+-+--+-+---++-+ | Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason | ++--+-+--+-+---++-+ | region!child@1 | nova-conductor | region!child@ubuntu | internal | enabled | up | 2014-08-18T06:17:36.00 | - | | region!child@3 | nova-cells | region!child@ubuntu | internal | enabled | up | 2014-08-18T06:17:29.00 | - | | region!child@4 | nova-scheduler | region!child@ubuntu | internal | enabled | up | 2014-08-18T06:17:30.00 | - | | region!child@5 | nova-compute | region!child@ubuntu | nova | enabled | up | 2014-08-18T06:17:31.00 | - | | region@1 | nova-cells | region@ubuntu | internal | enabled | up | 2014-08-18T06:17:29.00 | - | | region@2 | nova-cert | region@ubuntu | internal | enabled | down | 2014-08-18T06:08:28.00 | - | | region@3 | nova-consoleauth | region@ubuntu | internal | enabled | up | 2014-08-18T06:17:37.00 | - | ++--+-+--+-+---++-+ 2) disable one of the services on top cell (e.g. nova-cert) $ nova --os-username admin service-disable 'region@ubuntu' nova-cert The above command gives the following error: a) On user console: ERROR (ClientException): The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-529f926f-fbda-4748-afb7-dfe8c7cc7877) b) In nova-api logs, it shows following error message: 2014-12-01 00:50:08.459 TRACE nova.api.openstack Traceback (most recent call last): 2014-12-01 00:50:08.459 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 134, in _dispatch_and_reply 2014-12-01 00:50:08.459 TRACE nova.api.openstack incoming.message)) 2014-12-01 00:50:08.459 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 177, in _dispatch 2014-12-01 00:50:08.459 TRACE nova.api.openstack return self._do_dispatch(endpoint, method, ctxt, args) 2014-12-01 00:50:08.459 TRACE nova.api.openstack 2014-12-01 00:50:08.459 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 123, in _do_dispatch 2014-12-01 00:50:08.459 TRACE nova.api.openstack result = getattr(endpoint, method)(ctxt, **new_args) 2014-12-01 00:50:08.459 TRACE nova.api.openstack 2014-12-01 00:50:08.459 TRACE nova.api.openstack File "/opt/stack/nova/nova/cells/manager.py", line 296, in service_update 2014-12-01 00:50:08.459 TRACE nova.api.openstack service = response.value_or_raise() 2014-12-01 00:50:08.459 TRACE nova.api.openstack File "/opt/stack/nova/nova/cells/messaging.py", line 407, in process 2014-12-01 00:50:08.459 TRACE nova.api.openstack next_hop = self._get_next_hop() 2014-12-01 00:50:08.459 TRACE nova.api.openstack File "/opt/stack/nova/nova/cells/messaging.py", line 362, in _get_next_hop 2014-12-01 00:50:08.459 TRACE nova.api.openstack dest_hops = target_cell.count(_PATH_CELL_SEP) 2014-12-01 00:50:08.459 TRACE nova.api.openstack 2014-12-01 00:50:08.459 TRACE nova.api.openstack AttributeError: 'NoneType' object has no attribute 'count' ** Affects: nova Importance: Undecided Assignee: Rajesh Tailor (rajesh-tailor) Status: New ** Tags: ntt ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- 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/1398349 Title: nova service-update fails for services on non-child (top) cell Status in OpenStack Compute (Nova): New Bug description: Nova service-update fails for services on non-child (top) cell. How to reproduce: 1) List available services using below command. $ nova --os-username admin service-list Output: ++--+-+--+-+---++-+ | Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason | ++--+-+--+-+---++-+ | region!child@1 | nova-conductor | region!child@ubuntu | internal | enabled | up | 2014-08-18T06:17:36.00 | - | | region!child@3 | nova-cells | region!child@ubuntu | in
[Yahoo-eng-team] [Bug 1381425] [NEW] nova cells, force-delete VM throws error even if VM gets deleted
4-10-15 01:59:36.742 TRACE nova.cells.messaging File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1749, in _attach 2014-10-15 01:59:36.742 TRACE nova.cells.messaging state.session_id, self.hash_key)) 2014-10-15 01:59:36.742 TRACE nova.cells.messaging InvalidRequestError: Object '' is already attached to session '75' (this is '79') Note: This issue occurs intermitently. ** Affects: nova Importance: Undecided Assignee: Rajesh Tailor (rajesh-tailor) Status: New ** Tags: ntt ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- 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/1381425 Title: nova cells, force-delete VM throws error even if VM gets deleted Status in OpenStack Compute (Nova): New Bug description: In nova cells environment, when try to force-delete an instance which is in 'active' state, the instance gets deleted successfully, but in nova-cells service in compute cell (n-cell-child), it throws the following error: InvalidRequestError: Object '' is already attached to session '75' (this is '79') Reproduction steps: 1) Create instance. 2) Wait until instance becomes 'active'. 3) Try to force-delete the instance. $ nova force-delete Found this error in nova-cells service in compute cell (n-cell-child service): 2014-10-15 01:59:36.742 ERROR nova.cells.messaging [req-7c1615ad-491d-4af8-88d7-ff83563ef429 admin admin] Error processing message locally: Object '' is already attached to session '75' (this is '79') 2014-10-15 01:59:36.742 TRACE nova.cells.messaging Traceback (most recent call last): 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/opt/stack/nova/nova/cells/messaging.py", line 199, in _process_locally 2014-10-15 01:59:36.742 TRACE nova.cells.messaging resp_value = self.msg_runner._process_message_locally(self) 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/opt/stack/nova/nova/cells/messaging.py", line 1293, in _process_message_locally 2014-10-15 01:59:36.742 TRACE nova.cells.messaging return fn(message, **message.method_kwargs) 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/opt/stack/nova/nova/cells/messaging.py", line 698, in run_compute_api_method 2014-10-15 01:59:36.742 TRACE nova.cells.messaging return fn(message.ctxt, *args, **method_info['method_kwargs']) 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/opt/stack/nova/nova/compute/api.py", line 219, in wrapped 2014-10-15 01:59:36.742 TRACE nova.cells.messaging return func(self, context, target, *args, **kwargs) 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/opt/stack/nova/nova/compute/api.py", line 209, in inner 2014-10-15 01:59:36.742 TRACE nova.cells.messaging return function(self, context, instance, *args, **kwargs) 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/opt/stack/nova/nova/compute/api.py", line 190, in inner 2014-10-15 01:59:36.742 TRACE nova.cells.messaging return f(self, context, instance, *args, **kw) 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/opt/stack/nova/nova/compute/api.py", line 1836, in force_delete 2014-10-15 01:59:36.742 TRACE nova.cells.messaging self._delete_instance(context, instance) 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/opt/stack/nova/nova/compute/api.py", line 1790, in _delete_instance2014-10-15 01:59:36.742 TRACE nova.cells.messaging task_state=task_states.DELETING) 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/opt/stack/nova/nova/compute/api.py", line 1622, in _delete 2014-10-15 01:59:36.742 TRACE nova.cells.messaging quotas.rollback() 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/usr/local/lib/python2.7/dist-packages/oslo/utils/excutils.py", line 82, in __exit__ 2014-10-15 01:59:36.742 TRACE nova.cells.messaging six.reraise(self.type_, self.value, self.tb) 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/opt/stack/nova/nova/compute/api.py", line 1550, in _delete 2014-10-15 01:59:36.742 TRACE nova.cells.messaging instance.save() 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/opt/stack/nova/nova/db/sqlalchemy/models.py", line 52, in save 2014-10-15 01:59:36.742 TRACE nova.cells.messaging super(NovaBase, self).save(session=session) 2014-10-15 01:59:36.742 TRACE nova.cells.messaging File "/usr/local/lib/python2.7/dist-packages/oslo/db/sqlalchemy/models.py", line 47, in save 2014-10-15 01:59:36.742 TRACE nova.cells.messaging session.ad
[Yahoo-eng-team] [Bug 1378683] [NEW] nova-cell, cannot delete VM once deleting VM with failure in nova-compute
Public bug reported: Not able to delete the VM once the VM deletion failed in nova compute. Steps to reproduce: 1. create VM 2. wait until VM becomes available 3. Stop nova-cell child process 4. delete VM nova delete 5. stop neutron service 6. start child nova-cell process 7. start neutron service 8. delete VM again VM is not deleted and will be listed in the nova list output. $ nova list +--+--+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+--+++-+--+ | 9d7c9fb2-010f-4de6-975a-1a2de825155b | vm09 | ERROR | - | Running | private=10.0.0.2 | +--+--+++-+--+ Following log messages is logged in n-child-cell screen: 2014-10-07 04:36:57.159 INFO nova.compute.api [req-11c20157-23ac-4892-9fdf-3e60201a9bb4 admin admin] [instance: 77aabf6c-7b33-4c49-8061-eb9805214085] Instance is already in deleting state, ignoring this request Note: VM never gets deleted. ** Affects: nova Importance: Undecided Assignee: Rajesh Tailor (rajesh-tailor) Status: New ** Tags: ntt ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- 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/1378683 Title: nova-cell, cannot delete VM once deleting VM with failure in nova- compute Status in OpenStack Compute (Nova): New Bug description: Not able to delete the VM once the VM deletion failed in nova compute. Steps to reproduce: 1. create VM 2. wait until VM becomes available 3. Stop nova-cell child process 4. delete VM nova delete 5. stop neutron service 6. start child nova-cell process 7. start neutron service 8. delete VM again VM is not deleted and will be listed in the nova list output. $ nova list +--+--+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+--+++-+--+ | 9d7c9fb2-010f-4de6-975a-1a2de825155b | vm09 | ERROR | - | Running | private=10.0.0.2 | +--+--+++-+--+ Following log messages is logged in n-child-cell screen: 2014-10-07 04:36:57.159 INFO nova.compute.api [req-11c20157-23ac-4892-9fdf-3e60201a9bb4 admin admin] [instance: 77aabf6c-7b33-4c49-8061-eb9805214085] Instance is already in deleting state, ignoring this request Note: VM never gets deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1378683/+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 1361186] [NEW] nova service-delete fails for services on non-child (top) cell
-+-+---++-+ | region!child@1 | nova-conductor | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:14:46.00 | - | | region!child@2 | nova-compute | region!child@ubuntu | nova | enabled | down | 2014-08-18T06:13:15.00 | - | | region!child@3 | nova-cells | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:14:49.00 | - | | region!child@4 | nova-scheduler | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:14:50.00 | - | | region@1 | nova-cells | region@ubuntu | internal | enabled | up| 2014-08-18T06:14:49.00 | - | | region@2 | nova-cert| region@ubuntu | internal | enabled | down | 2014-08-18T06:08:28.00 | - | | region@3 | nova-consoleauth | region@ubuntu | internal | enabled | up| 2014-08-18T06:14:47.00 | - | ++--+-+--+-+---++-+ Delete child cell service: $ nova --os-username admin service-delete 'region!child@2' $ nova --os-username admin service-list ++--+-+--+-+---++-+ | Id | Binary | Host| Zone | Status | State | Updated_at | Disabled Reason | ++--+-+--+-+---++-+ | region!child@1 | nova-conductor | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:15:46.00 | - | | region!child@3 | nova-cells | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:15:39.00 | - | | region!child@4 | nova-scheduler | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:15:40.00 | - | | region@1 | nova-cells | region@ubuntu | internal | enabled | up| 2014-08-18T06:15:39.00 | - | | region@2 | nova-cert| region@ubuntu | internal | enabled | down | 2014-08-18T06:08:28.00 | - | | region@3 | nova-consoleauth | region@ubuntu | internal | enabled | up| 2014-08-18T06:15:47.00 | - | ++--+-+--+-+---+--------+---------+ ** Affects: nova Importance: Undecided Assignee: Rajesh Tailor (rajesh-tailor) Status: New ** Tags: ntt ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- 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/1361186 Title: nova service-delete fails for services on non-child (top) cell Status in OpenStack Compute (Nova): New Bug description: Nova service-delete fails for services on non-child (top) cell. How to reproduce: $ nova --os-username admin service-list ++--+-+--+-+---++-+ | Id | Binary | Host| Zone | Status | State | Updated_at | Disabled Reason | ++--+-+--+-+---++-+ | region!child@1 | nova-conductor | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:06:56.00 | - | | region!child@2 | nova-compute | region!child@ubuntu | nova | enabled | up| 2014-08-18T06:06:55.00 | - | | region!child@3 | nova-cells | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:06:59.00 | - | | region!child@4 | nova-scheduler | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:06:50.00 | - | | region@1 | nova-cells | region@ubuntu | internal | enabled | up| 2014-08-18T06:06:59.00 | - | | region@2 | nova-cert| region@ubuntu | internal | enabled | up| 2014-08-18T06:06:58.00 | - | | region@3 | nova-consoleauth | region@ubuntu | internal | enabled | up| 2014-08-18T06:06:57.00 | - | ++--+-+--+-+---++-+ Stop
[Yahoo-eng-team] [Bug 1361180] [NEW] nova service disable/enable returns 500 on cell environment
ll__ 2014-08-18 15:18:23.934 TRACE nova.api.openstack content_type, body, accept) 2014-08-18 15:18:23.934 TRACE nova.api.openstack File "/opt/stack/nova/nova/api/openstack/wsgi.py", line 983, in _process_stack 2014-08-18 15:18:23.934 TRACE nova.api.openstack action_result = self.dispatch(meth, request, action_args) 2014-08-18 15:18:23.934 TRACE nova.api.openstack File "/opt/stack/nova/nova/api/openstack/wsgi.py", line 1070, in dispatch 2014-08-18 15:18:23.934 TRACE nova.api.openstack return method(req=request, **action_args) 2014-08-18 15:18:23.934 TRACE nova.api.openstack File "/opt/stack/nova/nova/api/openstack/compute/contrib/services.py", line 206, in update 2014-08-18 15:18:23.934 TRACE nova.api.openstack self.host_api.service_update(context, host, binary, status_detail) 2014-08-18 15:18:23.934 TRACE nova.api.openstack File "/opt/stack/nova/nova/compute/cells_api.py", line 579, in service_update 2014-08-18 15:18:23.934 TRACE nova.api.openstack db_service) 2014-08-18 15:18:23.934 TRACE nova.api.openstack File "/opt/stack/nova/nova/objects/service.py", line 67, in _from_db_object 2014-08-18 15:18:23.934 TRACE nova.api.openstack service[key] = db_service[key] 2014-08-18 15:18:23.934 TRACE nova.api.openstack File "/opt/stack/nova/nova/objects/base.py", line 398, in __setitem__ 2014-08-18 15:18:23.934 TRACE nova.api.openstack setattr(self, name, value) 2014-08-18 15:18:23.934 TRACE nova.api.openstack File "/opt/stack/nova/nova/objects/base.py", line 70, in setter 2014-08-18 15:18:23.934 TRACE nova.api.openstack field.coerce(self, name, value)) 2014-08-18 15:18:23.934 TRACE nova.api.openstack File "/opt/stack/nova/nova/objects/fields.py", line 166, in coerce 2014-08-18 15:18:23.934 TRACE nova.api.openstack return self._type.coerce(obj, attr, value) 2014-08-18 15:18:23.934 TRACE nova.api.openstack File "/opt/stack/nova/nova/objects/fields.py", line 231, in coerce 2014-08-18 15:18:23.934 TRACE nova.api.openstack return int(value) 2014-08-18 15:18:23.934 TRACE nova.api.openstack ValueError: invalid literal for int() with base 10: 'region!child@5' ** Affects: nova Importance: Undecided Assignee: Rajesh Tailor (rajesh-tailor) Status: New ** Tags: ntt ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- 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/1361180 Title: nova service disable/enable returns 500 on cell environment Status in OpenStack Compute (Nova): New Bug description: nova service disable/enable returns 500 on cell environment. Actual enable/disable looks processed correctly. It also throws following error in nova-api service: ValueError: invalid literal for int() with base 10: 'region!child@5' How to reproduce: $ nova --os-username admin service-list Output: ++--+-+--+-+---++-+ | Id | Binary | Host| Zone | Status | State | Updated_at | Disabled Reason | ++--+-+--+-+---++-+ | region!child@1 | nova-conductor | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:17:36.00 | - | | region!child@3 | nova-cells | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:17:29.00 | - | | region!child@4 | nova-scheduler | region!child@ubuntu | internal | enabled | up| 2014-08-18T06:17:30.00 | - | | region!child@5 | nova-compute | region!child@ubuntu | nova | enabled | up| 2014-08-18T06:17:31.00 | - | | region@1 | nova-cells | region@ubuntu | internal | enabled | up| 2014-08-18T06:17:29.00 | - | | region@2 | nova-cert| region@ubuntu | internal | enabled | down | 2014-08-18T06:08:28.00 | - | | region@3 | nova-consoleauth | region@ubuntu | internal | enabled | up| 2014-08-18T06:17:37.00 | - | ++--+-+--+-+---++-+ $ nova --os-username admin service-disable 'region!child@ubuntu' nova- compute The above command gives the following error: ERROR (ClientException): Unknown Error (HTTP 500) $ nova --os-username admin service-list Output: ++--+-+--+--+---++--
[Yahoo-eng-team] [Bug 1334651] [NEW] Nova api service outputs error messages when SIGHUP signal is sent
Public bug reported: When SIGHUP signal is send to nova-api service, it stops all the nova- api processes and while restarting the nova-api processes, it throws AttributeError: 'WSGIService' object has no attribute 'reset'. 2014-06-24 15:52:55.185 CRITICAL nova [-] AttributeError: 'WSGIService' object has no attribute 'reset' 2014-06-24 15:52:55.185 TRACE nova Traceback (most recent call last): 2014-06-24 15:52:55.185 TRACE nova File "/usr/local/bin/nova-api", line 10, in 2014-06-24 15:52:55.185 TRACE nova sys.exit(main()) 2014-06-24 15:52:55.185 TRACE nova File "/opt/stack/nova/nova/cmd/api.py", line 56, in main 2014-06-24 15:52:55.185 TRACE nova launcher.launch_service(server, workers=server.workers or 1) 2014-06-24 15:52:55.185 TRACE nova File "/opt/stack/nova/nova/openstack/common/service.py", line 340, in launch_service 2014-06-24 15:52:55.185 TRACE nova self._start_child(wrap) 2014-06-24 15:52:55.185 TRACE nova File "/opt/stack/nova/nova/openstack/common/service.py", line 324, in _start_child 2014-06-24 15:52:55.185 TRACE nova launcher.restart() 2014-06-24 15:52:55.185 TRACE nova File "/opt/stack/nova/nova/openstack/common/service.py", line 145, in restart 2014-06-24 15:52:55.185 TRACE nova self.services.restart() 2014-06-24 15:52:55.185 TRACE nova File "/opt/stack/nova/nova/openstack/common/service.py", line 478, in restart 2014-06-24 15:52:55.185 TRACE nova restart_service.reset() 2014-06-24 15:52:55.185 TRACE nova AttributeError: 'WSGIService' object has no attribute 'reset' 2014-06-24 15:52:55.185 TRACE nova Steps to reproduce: 1. Run nova-api service as daemon. 2. Send SIGHUP signal to nova-api service kill -1 ** Affects: nova Importance: Undecided Assignee: Rajesh Tailor (rajesh-tailor) Status: New ** Tags: ntt ** Changed in: nova Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor) -- 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/1334651 Title: Nova api service outputs error messages when SIGHUP signal is sent Status in OpenStack Compute (Nova): New Bug description: When SIGHUP signal is send to nova-api service, it stops all the nova- api processes and while restarting the nova-api processes, it throws AttributeError: 'WSGIService' object has no attribute 'reset'. 2014-06-24 15:52:55.185 CRITICAL nova [-] AttributeError: 'WSGIService' object has no attribute 'reset' 2014-06-24 15:52:55.185 TRACE nova Traceback (most recent call last): 2014-06-24 15:52:55.185 TRACE nova File "/usr/local/bin/nova-api", line 10, in 2014-06-24 15:52:55.185 TRACE nova sys.exit(main()) 2014-06-24 15:52:55.185 TRACE nova File "/opt/stack/nova/nova/cmd/api.py", line 56, in main 2014-06-24 15:52:55.185 TRACE nova launcher.launch_service(server, workers=server.workers or 1) 2014-06-24 15:52:55.185 TRACE nova File "/opt/stack/nova/nova/openstack/common/service.py", line 340, in launch_service 2014-06-24 15:52:55.185 TRACE nova self._start_child(wrap) 2014-06-24 15:52:55.185 TRACE nova File "/opt/stack/nova/nova/openstack/common/service.py", line 324, in _start_child 2014-06-24 15:52:55.185 TRACE nova launcher.restart() 2014-06-24 15:52:55.185 TRACE nova File "/opt/stack/nova/nova/openstack/common/service.py", line 145, in restart 2014-06-24 15:52:55.185 TRACE nova self.services.restart() 2014-06-24 15:52:55.185 TRACE nova File "/opt/stack/nova/nova/openstack/common/service.py", line 478, in restart 2014-06-24 15:52:55.185 TRACE nova restart_service.reset() 2014-06-24 15:52:55.185 TRACE nova AttributeError: 'WSGIService' object has no attribute 'reset' 2014-06-24 15:52:55.185 TRACE nova Steps to reproduce: 1. Run nova-api service as daemon. 2. Send SIGHUP signal to nova-api service kill -1 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1334651/+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 1334647] [NEW] Nova api service doesn't handle SIGHUP signal properly
Public bug reported: When SIGHUP signal is send to nova-api service, it doesn't complete processing of all pending requests before terminating all the processes. Steps to reproduce: 1. Run nova-api service as a daemon. 2. Send SIGHUP signal to nova-api service. kill -1 After getting SIGHUP signal all the processes of nova-api stops instantly, without completing existing request, which might cause failure. Ideally after getting the SIGHUP signal nova-api process should stop getting new requests and wait for existing requests to complete before terminating all the processes and restarting all nova-api processes. ** Affects: nova Importance: Undecided Assignee: Rajesh Tailor (rajesh-tailor) Status: New ** Tags: ntt -- 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/1334647 Title: Nova api service doesn't handle SIGHUP signal properly Status in OpenStack Compute (Nova): New Bug description: When SIGHUP signal is send to nova-api service, it doesn't complete processing of all pending requests before terminating all the processes. Steps to reproduce: 1. Run nova-api service as a daemon. 2. Send SIGHUP signal to nova-api service. kill -1 After getting SIGHUP signal all the processes of nova-api stops instantly, without completing existing request, which might cause failure. Ideally after getting the SIGHUP signal nova-api process should stop getting new requests and wait for existing requests to complete before terminating all the processes and restarting all nova-api processes. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1334647/+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
