[Yahoo-eng-team] [Bug 1403379] [NEW] can not delete an instance with Chinese name
Public bug reported: can not delete an instance which display name is Chinese. [tagett@stack-01 devstack]$ nova --debug delete 测试 'ascii' codec can't encode characters in position 0-1: ordinal not in range(128) DEBUG (shell:908) Unable to delete the specified server(s). Traceback (most recent call last): File "/opt/stack/python-novaclient/novaclient/shell.py", line 905, in main OpenStackComputeShell().main(argv) File "/opt/stack/python-novaclient/novaclient/shell.py", line 832, in main args.func(self.cs, args) File "/opt/stack/python-novaclient/novaclient/v1_1/shell.py", line 1876, in do_delete _("Unable to delete the specified server(s).")) File "/opt/stack/python-novaclient/novaclient/utils.py", line 320, in do_action_on_many raise exceptions.CommandError(error_msg) ** Affects: python-novaclient Importance: Undecided Status: New ** Project changed: nova => python-novaclient -- 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/1403379 Title: can not delete an instance with Chinese name Status in Python client library for Nova: New Bug description: can not delete an instance which display name is Chinese. [tagett@stack-01 devstack]$ nova --debug delete 测试 'ascii' codec can't encode characters in position 0-1: ordinal not in range(128) DEBUG (shell:908) Unable to delete the specified server(s). Traceback (most recent call last): File "/opt/stack/python-novaclient/novaclient/shell.py", line 905, in main OpenStackComputeShell().main(argv) File "/opt/stack/python-novaclient/novaclient/shell.py", line 832, in main args.func(self.cs, args) File "/opt/stack/python-novaclient/novaclient/v1_1/shell.py", line 1876, in do_delete _("Unable to delete the specified server(s).")) File "/opt/stack/python-novaclient/novaclient/utils.py", line 320, in do_action_on_many raise exceptions.CommandError(error_msg) To manage notifications about this bug go to: https://bugs.launchpad.net/python-novaclient/+bug/1403379/+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 1404791] [NEW] can not delete an instance if the instance's rescue volume is not found
Public bug reported: can not delete an instance if the instance's rescue lvm can not be found. how to reproduce: 1. configure images_type lvm for libvirt dirver. [libvirt] images_type = lvm < images_volume_group = stack-volumes-lvmdriver-1 <-- lvm used 2. rescue the instance, will generate uuid.rescue lvm 3. unrescue the instance, the rescue lvm can not be deleted due to bug https://bugs.launchpad.net/nova/+bug/1385480 4. delete the uuid.rescue lvm manually. 5. delete the instance(failed and set to error state) below is the call trace of nova-compute driver. 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher self._cleanup_lvm(instance) 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 944, in _cleanup_lvm 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher lvm.remove_volumes(disks) 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/lvm.py", line 272, in remove_volumes 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher clear_volume(path) 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/lvm.py", line 250, in clear_volume 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher volume_size = get_volume_size(path) 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/lvm.py", line 66, in decorated_function 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher return function(path) 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/lvm.py", line 197, in get_volume_size 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher run_as_root=True) 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/utils.py", line 53, in execute 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher return utils.execute(*args, **kwargs) 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/utils.py", line 164, in execute 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher return processutils.execute(*cmd, **kwargs) 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher File "/usr/lib/python2.7/site-packages/oslo_concurrency/processutils.py", line 224, in execute 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher cmd=sanitized_cmd) 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher ProcessExecutionError: Unexpected error while running command. 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher Command: sudo nova-rootwrap /etc/nova/rootwrap.conf blockdev --getsize64 /dev/stack-volumes-lvmdriver-1/b09687ee-f525-4edc-aaf4-1272562d46fd_disk.rescue 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher Exit code: 1 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher Stdout: u'' 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher Stderr: u'blockdev: cannot open /dev/stack-volumes-lvmdriver-1/b09687ee-f525-4edc-aaf4-1272562d46fd_disk.rescue: No such file or directory\n' 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1404791 Title: can not delete an instance if the instance's rescue volume is not found Status in OpenStack Compute (Nova): New Bug description: can not delete an instance if the instance's rescue lvm can not be found. how to reproduce: 1. configure images_type lvm for libvirt dirver. [libvirt] images_type = lvm < images_volume_group = stack-volumes-lvmdriver-1 <-- lvm used 2. rescue the instance, will generate uuid.rescue lvm 3. unrescue the instance, the rescue lvm can not be deleted due to bug https://bugs.launchpad.net/nova/+bug/1385480 4. delete the uuid.rescue lvm manually. 5. delete the instance(failed and set to error state) below is the call trace of nova-compute driver. 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher self._cleanup_lvm(instance) 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 944, in _cleanup_lvm 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher lvm.remove_volumes(disks) 2014-12-22 13:18:29.691 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/lvm.py", line 272, in remove_volumes 2014-12-2
[Yahoo-eng-team] [Bug 1405069] [NEW] nova client list not working when pass sort parameter
Public bug reported: nova client send error request url to nova-api nova --debug list --all-tenants --deleted --sort name ... DEBUG (session:162) REQ: curl -i -X GET http://cloudcontroller:8774/v2/d7beb7f28e0b4f41901215000339361d/servers/detail?all_tenants=1&deleted=True&sort_dir=desc&sort_key=name -H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: {SHA1}6ba6e70be8c8367deec4e1696758b7dc4a1a891a" ... ClientException: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-c2a132da-05b0-4db3-84ee-1b8aeb7d0f61) ERROR (ClientException): The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-c2a132da-05b0-4db3-84ee-1b8aeb7d0f61) the url parameter should be passed as 'sort_keys' instead of 'sort_key' beside, nova-api/nova should handle this exception instead of raise an internal error(500) this to customer. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Affects: python-novaclient Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Also affects: python-novaclient Importance: Undecided Status: New ** Changed in: python-novaclient Assignee: (unassigned) => Eli Qiao (taget-9) ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1405069 Title: nova client list not working when pass sort parameter Status in OpenStack Compute (Nova): New Status in Python client library for Nova: New Bug description: nova client send error request url to nova-api nova --debug list --all-tenants --deleted --sort name ... DEBUG (session:162) REQ: curl -i -X GET http://cloudcontroller:8774/v2/d7beb7f28e0b4f41901215000339361d/servers/detail?all_tenants=1&deleted=True&sort_dir=desc&sort_key=name -H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: {SHA1}6ba6e70be8c8367deec4e1696758b7dc4a1a891a" ... ClientException: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-c2a132da-05b0-4db3-84ee-1b8aeb7d0f61) ERROR (ClientException): The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-c2a132da-05b0-4db3-84ee-1b8aeb7d0f61) the url parameter should be passed as 'sort_keys' instead of 'sort_key' beside, nova-api/nova should handle this exception instead of raise an internal error(500) this to customer. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1405069/+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 1405069] Re: nova client list not working when pass sort parameter
** Changed in: python-novaclient Status: New => 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/1405069 Title: nova client list not working when pass sort parameter Status in OpenStack Compute (Nova): New Status in Python client library for Nova: Invalid Bug description: nova client send error request url to nova-api nova --debug list --all-tenants --deleted --sort name ... DEBUG (session:162) REQ: curl -i -X GET http://cloudcontroller:8774/v2/d7beb7f28e0b4f41901215000339361d/servers/detail?all_tenants=1&deleted=True&sort_dir=desc&sort_key=name -H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: {SHA1}6ba6e70be8c8367deec4e1696758b7dc4a1a891a" ... ClientException: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-c2a132da-05b0-4db3-84ee-1b8aeb7d0f61) ERROR (ClientException): The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-c2a132da-05b0-4db3-84ee-1b8aeb7d0f61) the url parameter should be passed as 'sort_keys' instead of 'sort_key' beside, nova-api/nova should handle this exception instead of raise an internal error(500) this to customer. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1405069/+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 1405069] Re: nova client list not working when pass sort parameter
** Also affects: oslo.db Importance: Undecided Status: New ** Changed in: nova Status: New => Invalid ** Changed in: oslo.db Assignee: (unassigned) => Eli Qiao (taget-9) ** Changed in: oslo.db Status: New => Confirmed -- 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/1405069 Title: nova client list not working when pass sort parameter Status in OpenStack Compute (Nova): Invalid Status in Oslo Database library: Confirmed Status in Python client library for Nova: Invalid Bug description: nova client send error request url to nova-api nova --debug list --all-tenants --deleted --sort name ... DEBUG (session:162) REQ: curl -i -X GET http://cloudcontroller:8774/v2/d7beb7f28e0b4f41901215000339361d/servers/detail?all_tenants=1&deleted=True&sort_dir=desc&sort_key=name -H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: {SHA1}6ba6e70be8c8367deec4e1696758b7dc4a1a891a" ... ClientException: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-c2a132da-05b0-4db3-84ee-1b8aeb7d0f61) ERROR (ClientException): The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-c2a132da-05b0-4db3-84ee-1b8aeb7d0f61) the url parameter should be passed as 'sort_keys' instead of 'sort_key' beside, nova-api/nova should handle this exception instead of raise an internal error(500) this to customer. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1405069/+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 1409613] [NEW] nova evacuate allows to evacuate to a host which are not in same aggregate with origin host
Public bug reported: nova allows evacuate an instance to a host which doesn't have specify feature. how to reproduce : 1 create aggregate [tagett@stack-01 devstack]$ nova aggregate-details 2 ++--+---++--+ | Id | Name | Availability Zone | Hosts | Metadata | ++--+---++--+ | 2 | s| nova | 'stack-kvm110' | 'availability_zone=nova', 'ssd=true' 2 create flavor [tagett@stack-01 devstack]$ nova flavor-show 100 ++--+ | Property | Value| ++--+ | OS-FLV-DISABLED:disabled | False| | OS-FLV-EXT-DATA:ephemeral | 0| | disk | 10 | | extra_specs| {"ssd": "true", "availability_zone": "nova"} | | id | 100 | | name | stack110 | | os-flavor-access:is_public | True | | ram| 1024 | | rxtx_factor| 1.0 | | swap | | | vcpus | 2| ++--+ 3 create an instance with flavor 100 [tagett@stack-01 devstack]$ nova list +--+--+-++-++ | ID | Name | Status | Task State | Power State | Networks | +--+--+-++-++ | 428f0235-be54-462f-8916-f32965d42e63 | boot_from_volume | SHUTOFF | - | Shutdown| public=172.24.4.3 | | b48aa410-769e-4f10-bb9c-181250bb4441 | test | ACTIVE | 1 | Running | public=172.24.4.21 | 4 stop compute service on stack-kvm110 5 nova evacuate test to another host which don't in aggregate 2 ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1409613 Title: nova evacuate allows to evacuate to a host which are not in same aggregate with origin host Status in OpenStack Compute (Nova): New Bug description: nova allows evacuate an instance to a host which doesn't have specify feature. how to reproduce : 1 create aggregate [tagett@stack-01 devstack]$ nova aggregate-details 2 ++--+---++--+ | Id | Name | Availability Zone | Hosts | Metadata | ++--+---++--+ | 2 | s| nova | 'stack-kvm110' | 'availability_zone=nova', 'ssd=true' 2 create flavor [tagett@stack-01 devstack]$ nova flavor-show 100 ++--+ | Property | Value| ++--+ | OS-FLV-DISABLED:disabled | False| | OS-FLV-EXT-DATA:ephemeral | 0| | disk | 10 | | extra_specs| {"ssd": "true", "availability_zone": "nova"} | | id | 100 | | name | stack110 | | os-flavor-access:is_public | True | | ram| 1024 | | rxtx_factor| 1.0 | | swap | | | vcpus | 2|
[Yahoo-eng-team] [Bug 1427092] [NEW] preallocate_images can be arbitrary characters to enable preallocate feature
Public bug reported: Raw and Qcow2 image type support preallocate image. by enable this we need to set preallocate_images in config file. currently , we can set it to any character except 'none' to enable it. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: 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/1427092 Title: preallocate_images can be arbitrary characters to enable preallocate feature Status in OpenStack Compute (Nova): In Progress Bug description: Raw and Qcow2 image type support preallocate image. by enable this we need to set preallocate_images in config file. currently , we can set it to any character except 'none' to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1427092/+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 1428539] [NEW] nova instance actions don't have finish time
Public bug reported: taget@taget-ThinkStation-P300:~/devstack$ nova instance-action-list tt2 ++--+-++ | Action | Request_ID | Message | Start_Time | ++--+-++ | create | req-76bac38a-2b04-44cd-a2aa-1b169581c82a | - | 2015-03-05T06:50:06.00 | | stop | req-6431b956-d790-4f9e-95a7-a25b5e697910 | - | 2015-03-05T08:08:26.00 | | start | req-0da5a5d1-d9f7-4c97-b2cd-7a652c282597 | - | 2015-03-05T08:14:52.00 | ++--+-++ query from db , got the finish time is null. mysql> select * from instance_actions; +-+-++++--+--+--+--+-+-+-+-+ | created_at | updated_at | deleted_at | id | action | instance_uuid| request_id | user_id | project_id | start_time | finish_time | message | deleted | +-+-++++--+--+--+--+-+-+-+-+ | 2015-03-05 06:42:31 | 2015-03-05 06:42:42 | NULL | 1 | create | 8e126d7b-afbe-4d40-b924-57c3e1a64ca8 | req-7ae89424-c3c3-4d04-8f22-23cc96b1edbd | 4950987b531840e3b546d72476c3d3c2 | 15e4a8cf15da4271ba4e38b5c40e93cc | 2015-03-05 06:42:30 | 2015-03-05 06:42:42 | NULL| 0 | | 2015-03-05 06:50:07 | 2015-03-05 06:50:26 | NULL | 2 | create | a3f69c3c-f922-4418-8464-508d4740f447 | req-76bac38a-2b04-44cd-a2aa-1b169581c82a | 4950987b531840e3b546d72476c3d3c2 | 15e4a8cf15da4271ba4e38b5c40e93cc | 2015-03-05 06:50:06 | 2015-03-05 06:50:26 | NULL| 0 | | 2015-03-05 08:08:26 | 2015-03-05 08:08:40 | NULL | 3 | stop | a3f69c3c-f922-4418-8464-508d4740f447 | req-6431b956-d790-4f9e-95a7-a25b5e697910 | 4950987b531840e3b546d72476c3d3c2 | 15e4a8cf15da4271ba4e38b5c40e93cc | 2015-03-05 08:08:26 | 2015-03-05 08:08:40 | NULL| 0 | | 2015-03-05 08:14:52 | 2015-03-05 08:14:53 | NULL | 4 | start | a3f69c3c-f922-4418-8464-508d4740f447 | req-0da5a5d1-d9f7-4c97-b2cd-7a652c282597 | 4950987b531840e3b546d72476c3d3c2 | 15e4a8cf15da4271ba4e38b5c40e93cc | 2015-03-05 08:14:52 | 2015-03-05 08:14:53 | NULL| 0 | +-+-++++--+--+--+--+-+-+-+-+ the reason is that we save the start_time in compute api layer and for some async operations we don't have a chance to save the finish time. but instance_actions_events does, it saves the time by create a event (save it in __enter__ and __exit__), we can add the finish time when instance action event exit , just like what instance_action_event did. ** 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/1428539 Title: nova instance actions don't have finish time Status in OpenStack Compute (Nova): New Bug description: taget@taget-ThinkStation-P300:~/devstack$ nova instance-action-list tt2 ++--+-++ | Action | Request_ID | Message | Start_Time | ++--+-++ | create | req-76bac38a-2b04-44cd-a2aa-1b169581c82a | - | 2015-03-05T06:50:06.00 | | stop | req-6431b956-d790-4f9e-95a7-a25b5e697910 | - | 2015-03-05T08:08:26.00 | | start | req-0da5a5d1-d9f7-4c97-b2cd-7a652c282597 | - | 2015-03-05T08:14:52.00 | ++--+-++ query from db , got the finish time is null. mysql> select * from instance_actions; +-+-++++--+--+--+--+-+-+
[Yahoo-eng-team] [Bug 1408708] Re: The API returns a serial console connection without an activated nova-serialproxy
hi Markus, I don't think this is a bug, nova-compute will not know if nova-serialproxy service is running. let's take libvirt driver as an example, it start a local service on port 1 if you configure serial_console in nova-compute taget@taget-ThinkStation-P300:/opt/stack/nova$ netstat -an | grep 1 tcp0 0 127.0.0.1:1 0.0.0.0:* LISTEN and the libvirt driver will return a vm's serial_console information and nova-compute service will decorate this by a default url 'ws://127.0.0.1:6083/'. nova-compute has no way to know if a nova-serialproxy is running or not, it only return user as a valid url by default or the url you manually configured in nova conf. thanks Eli. ** Changed in: nova Status: New => 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/1408708 Title: The API returns a serial console connection without an activated nova- serialproxy Status in OpenStack Compute (Nova): Invalid Bug description: Problem description === The Nova REST API returns with server action ``os-getSerialConsole`` a connection info (a websocket URL) although the nova-serialproxy service is *not* activated. Steps to reproduce == * Configure in ``nova.conf`` [serial_console] enabled=true * restart nova compute service * boot an instance * query serial console connection (e.g. with CLI ``nova get-serial-console ``) Expected behavior = Get an exception with a reason that the ``nova-serialproxy`` is not activated. Observed behavior = Get a valid looking URL which doesn't lead to an actual connection because of the inactive nova-serialproxy. Additional data === * Nova code from master branch until commit 31bfc6415484054457c84924ac2d824e8ce2db93 (Mon Jan 5 11:49:56 2015 +) * A serial console client: https://github.com/larsks/novaconsole To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1408708/+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 1346108] [NEW] nova doesn't release network when network_info is not equal to 1
| | image| cirros-0.3.2-x86_64-uec (44c37b90-0ec3-460a-bdf2-bd8bb98c9fdf) | | key_name | 11 | | metadata | {} | | name | vm1 | | os-extended-volumes:volumes_attached | [] | | private network | 192.168.1.16, 192.168.1.17, 192.168.1.18, 192.168.1.19, 192.168.1.20, 192.168.1.21, 192.168.1.22, 192.168.1.23, 192.168.1.25 | | progress | 0 | | public network | 172.24.4.14, 172.24.4.15, 172.24.4.16, 172.24.4.17, 172.24.4.18, 172.24.4.19, 172.24.4.21 | | security_groups | default, default, default, default, default, default, default, default, default, default, default, default, default, default, default, default, default, default | | status | ACTIVE | | tenant_id| d7beb7f28e0b4f41901215000339361d | | updated | 2014-07-21T08:22:55Z | | user_id | fba8a67b69004320b2ace0b35aeebb18 | in guest side ,no new nic was added. we need to release network when allocate_port _for instace() return multiple networks. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1346108 Title: nova doesn't release network when network_info is not equal to 1 Status in OpenStack Compute (Nova): New Bug description: nova [tagett@stack-01 devstack]$ nova net-list +--+-+--+ | ID | Label | CIDR | +--+-+--+ | d838074c-632c-43cf-8aae-24e17a2d1828 | public | -| | cc16209f-a7b4-44f6-8c8f-27ea7b0cc9ff | private | -| | b745b2c6-db16-40ab-8ad7-af6da0e5e699 | private | -| +--+-+--+ [tagett@stack-01 devstack]$ nova --os-compute-api-version 2 interface-attach vm1 ERROR (ClientException): Failed to attach interface (HTTP 500) (Request-ID: req-a2da4531-0f22-46b2-94a9-ac9a7b0c350f) see from log 2014-07-21 17:06:16.543 ERROR nova.compute.manager [req- 375c0956-70f8-4d3a-b659-f48666787198 admin admin] allocate_port_for_instance returned 2 ports check nova show output [tagett@stack-01 devstack]$ nova --os-compute-api-version 2 show vm1 +--+--+ | Property | Value | +--+--+ | OS-DCF:diskConfig
[Yahoo-eng-team] [Bug 1341919] Re: Aggreate's update need validate for metadata
for v2: see from api code of aggregate-update , there is validation of updates keys. it only accept name of availability_zone, so we can not update metadata: for key in updates.keys(): if key not in ["name", "availability_zone"]: raise exc.HTTPBadRequest() for v3: there is schema to validation the api input, we can't update metadata neither. update = { 'type': 'object', 'properties': { 'type': 'object', 'aggregate': { 'type': 'object', 'properties': { 'name': parameter_types.name, 'availability_zone': parameter_types.name }, 'additionalProperties': False, 'anyOf': [ {'required': ['name']}, {'required': ['availability_zone']} ] }, }, 'required': ['aggregate'], 'additionalProperties': False, } ** Changed in: nova Status: Confirmed => 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/1341919 Title: Aggreate's update need validate for metadata Status in OpenStack Compute (Nova): Invalid Bug description: This patch https://review.openstack.org/#/c/79529/17 tightened the input validation of set_metadata action. But user also can use aggreate's update for metadata, but there isn't any input validation for metadata in update action. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1341919/+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 1349680] [NEW] nova v3 api raise an exceptions.NotImplementedError instead of error message
Public bug reported: nova v3 diagnostics api returns a NotImplementedError , but it is not caught by api. [tagett@stack-01 devstack]$ nova --os-compute-api-version 3 diagnostics f1 ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) libvirt driver doesn't implement get_instance_diagnostics, it raise an NotImplementedError ,but v3 api doesn't handle it . it returns http 500, but should be 501 ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: nova-api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Description changed: - nova v3 diagnostics api return an NotImplementedError , but it is not - catch by api. + nova v3 diagnostics api returns a NotImplementedError , but it is not + caught by api. [tagett@stack-01 devstack]$ nova --os-compute-api-version 3 diagnostics f1 ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) libvirt driver doesn't implement get_instance_diagnostics, it raise an NotImplementedError ,but v3 api doesn't handle it . it return http 500, it should be 501 ** Description changed: nova v3 diagnostics api returns a NotImplementedError , but it is not caught by api. [tagett@stack-01 devstack]$ nova --os-compute-api-version 3 diagnostics f1 ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) libvirt driver doesn't implement get_instance_diagnostics, it raise an NotImplementedError ,but v3 api doesn't handle it . - it return http 500, it should be 501 + it returns http 500, but should be 501 -- 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/1349680 Title: nova v3 api raise an exceptions.NotImplementedError instead of error message Status in OpenStack Compute (Nova): New Bug description: nova v3 diagnostics api returns a NotImplementedError , but it is not caught by api. [tagett@stack-01 devstack]$ nova --os-compute-api-version 3 diagnostics f1 ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) libvirt driver doesn't implement get_instance_diagnostics, it raise an NotImplementedError ,but v3 api doesn't handle it . it returns http 500, but should be 501 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1349680/+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 1350800] [NEW] nova v3 api boot failed, return error 500 instead of 404
Public bug reported: when boot an instance without specify the networking. nova-api v2 and v3 behavior difference: [tagett@stack-01 devstack]$ nova --os-compute-api-version 2 boot vm2 --flavor 1 --image 44c37b90-0ec3-460a-bdf2-bd8bb98c9fdf ERROR (BadRequest): Multiple possible networks found, use a Network ID to be more specific. (HTTP 400) (Request-ID: req-dbbf32e4-7eda-421c-8b3b-2ae697769077) [tagett@stack-01 devstack]$ nova --os-compute-api-version 3 boot vm2 --flavor 1 --image 44c37b90-0ec3-460a-bdf2-bd8bb98c9fdf ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) nova-api should report BadRequest with correct error message instead of 'Unexpected API Error' ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1350800 Title: nova v3 api boot failed, return error 500 instead of 404 Status in OpenStack Compute (Nova): New Bug description: when boot an instance without specify the networking. nova-api v2 and v3 behavior difference: [tagett@stack-01 devstack]$ nova --os-compute-api-version 2 boot vm2 --flavor 1 --image 44c37b90-0ec3-460a-bdf2-bd8bb98c9fdf ERROR (BadRequest): Multiple possible networks found, use a Network ID to be more specific. (HTTP 400) (Request-ID: req-dbbf32e4-7eda-421c-8b3b-2ae697769077) [tagett@stack-01 devstack]$ nova --os-compute-api-version 3 boot vm2 --flavor 1 --image 44c37b90-0ec3-460a-bdf2-bd8bb98c9fdf ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) nova-api should report BadRequest with correct error message instead of 'Unexpected API Error' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1350800/+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 1351124] [NEW] py26 Unit test failure: nova.tests.integrated.test_api_samples.AdminActionsSamplesXmlTest.test_post_unlock_server
Public bug reported: jenkins py26 unit test failed: 2014-07-31 12:12:40.050 | Traceback (most recent call last): 2014-07-31 12:12:40.050 | File "nova/tests/integrated/test_api_samples.py", line 103, in setUp 2014-07-31 12:12:40.050 | super(ApiSampleTestBaseV2, self).setUp() 2014-07-31 12:12:40.050 | File "nova/tests/integrated/integrated_helpers.py", line 67, in setUp 2014-07-31 12:12:40.050 | super(_IntegratedTestBase, self).setUp() 2014-07-31 12:12:40.050 | File "nova/tests/virt/baremetal/db/base.py", line 49, in setUp 2014-07-31 12:12:40.051 | sqlite_clean_db=None) 2014-07-31 12:12:40.200 | File "nova/test.py", line 98, in __init__ 2014-07-31 12:12:40.200 | if db_migrate.db_version() > db_migrate.db_initial_version(): 2014-07-31 12:12:40.200 | File "nova/virt/baremetal/db/migration.py", line 35, in db_version 2014-07-31 12:12:40.200 | return IMPL.db_version() 2014-07-31 12:12:40.200 | File "nova/utils.py", line 426, in __getattr__ 2014-07-31 12:12:40.201 | backend = self.__get_backend() 2014-07-31 12:12:40.201 | File "nova/utils.py", line 422, in __get_backend 2014-07-31 12:12:40.201 | self.__backend = __import__(name, None, None, fromlist) 2014-07-31 12:12:40.201 | ImportError: No module named migration 2014-07-31 12:12:40.201 | == 2014-07-31 12:12:40.201 | FAIL: nova.tests.integrated.test_api_samples.BareMetalNodesXmlTest.test_delete_node 2014-07-31 12:12:40.201 | tags: worker-3 2014-07-31 12:12:40.201 | -- 2014-07-31 12:12:40.201 | Empty attachments: 2014-07-31 12:12:40.201 | pythonlogging:'' 2014-07-31 12:12:40.201 | stderr 2014-07-31 12:12:40.202 | stdout 2014-07-31 12:12:40.202 | 2014-07-31 12:12:40.202 | Traceback (most recent call last): 2014-07-31 12:12:40.202 | File "nova/tests/integrated/test_api_samples.py", line 103, in setUp 2014-07-31 12:12:40.202 | super(ApiSampleTestBaseV2, self).setUp() 2014-07-31 12:12:40.202 | File "nova/tests/integrated/integrated_helpers.py", line 67, in setUp 2014-07-31 12:12:40.202 | super(_IntegratedTestBase, self).setUp() 2014-07-31 12:12:40.202 | File "nova/tests/virt/baremetal/db/base.py", line 49, in setUp 2014-07-31 12:12:40.202 | sqlite_clean_db=None) 2014-07-31 12:12:40.202 | File "nova/test.py", line 98, in __init__ 2014-07-31 12:12:40.202 | if db_migrate.db_version() > db_migrate.db_initial_version(): 2014-07-31 12:12:40.202 | File "nova/virt/baremetal/db/migration.py", line 35, in db_version 2014-07-31 12:12:40.203 | return IMPL.db_version() 2014-07-31 12:12:40.203 | File "nova/utils.py", line 426, in __getattr__ 2014-07-31 12:12:40.203 | backend = self.__get_backend() 2014-07-31 12:12:40.203 | File "nova/utils.py", line 422, in __get_backend 2014-07-31 12:12:40.203 | self.__backend = __import__(name, None, None, fromlist) 2014-07-31 12:12:40.203 | ImportError: No module named migration 2014-07-31 12:12:40.203 | == 2014-07-31 12:12:40.203 | FAIL: nova.tests.integrated.test_api_samples.BareMetalNodesXmlTest.test_show_node 2014-07-31 12:12:40.046 | Traceback (most recent call last): 2014-07-31 12:12:40.046 | File "nova/tests/integrated/test_api_samples.py", line 3818, in test_show_interfaces 2014-07-31 12:12:40.046 | instance_uuid = self._post_server() 2014-07-31 12:12:40.046 | File "nova/tests/integrated/test_api_samples.py", line 180, in _post_server 2014-07-31 12:12:40.046 | response = self._do_post('servers', 'server-post-req', subs) 2014-07-31 12:12:40.046 | File "nova/tests/integrated/api_samples_test_base.py", line 312, in _do_post 2014-07-31 12:12:40.046 | body = self._read_template(name) % subs 2014-07-31 12:12:40.046 | File "nova/tests/integrated/api_samples_test_base.py", line 101, in _read_template 2014-07-31 12:12:40.047 | with open(template) as inf: 2014-07-31 12:12:40.047 | IOError: [Errno 2] No such file or directory: '/home/jenkins/workspace/gate-nova-python26/CA/nova/tests/integrated/api_samples/os-attach-interfaces/server-post-req.xml.tpl' 2014-07-31 12:12:40.047 | == 2014-07-31 12:12:40.047 | FAIL: nova.tests.integrated.test_api_samples.BareMetalExtStatusJsonTest.test_create_node_with_address 2014-07-31 12:12:40.047 | tags: worker-3 below is the log : http://logs.openstack.org/21/110921/2/check/gate-nova-python26/2b0be77/console.html ** Affects: nova Importance: Undecided Status: New ** Tags: jenkins openstack-ci -- 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/1351124 Title: py26 Unit test failure: nova.tests.integrated.test_api_samples.AdminActionsSamplesXmlTest.test_post_unlock
[Yahoo-eng-team] [Bug 1357138] [NEW] nova unit test failed due to No reply on topic network
Public bug reported: 2014-08-14 11:56:07.215 | Traceback (most recent call last): 2014-08-14 11:56:07.215 | File "nova/tests/compute/test_compute.py", line 8848, in test_attach_interface 2014-08-14 11:56:07.215 | req_ip) 2014-08-14 11:56:07.215 | File "nova/compute/manager.py", line 408, in decorated_function 2014-08-14 11:56:07.215 | return function(self, context, *args, **kwargs) 2014-08-14 11:56:07.215 | File "nova/exception.py", line 88, in wrapped 2014-08-14 11:56:07.216 | payload) 2014-08-14 11:56:07.216 | File "nova/openstack/common/excutils.py", line 82, in __exit__ 2014-08-14 11:56:07.216 | six.reraise(self.type_, self.value, self.tb) 2014-08-14 11:56:07.216 | File "nova/exception.py", line 71, in wrapped 2014-08-14 11:56:07.216 | return f(self, context, *args, **kw) 2014-08-14 11:56:07.216 | File "nova/compute/manager.py", line 292, in decorated_function 2014-08-14 11:56:07.216 | pass 2014-08-14 11:56:07.216 | File "nova/openstack/common/excutils.py", line 82, in __exit__ 2014-08-14 11:56:07.216 | six.reraise(self.type_, self.value, self.tb) 2014-08-14 11:56:07.216 | File "nova/compute/manager.py", line 278, in decorated_function 2014-08-14 11:56:07.216 | return function(self, context, *args, **kwargs) 2014-08-14 11:56:07.216 | File "nova/compute/manager.py", line 320, in decorated_function 2014-08-14 11:56:07.217 | kwargs['instance'], e, sys.exc_info()) 2014-08-14 11:56:07.217 | File "nova/openstack/common/excutils.py", line 82, in __exit__ 2014-08-14 11:56:07.217 | six.reraise(self.type_, self.value, self.tb) 2014-08-14 11:56:07.217 | File "nova/compute/manager.py", line 308, in decorated_function 2014-08-14 11:56:07.217 | return function(self, context, *args, **kwargs) 2014-08-14 11:56:07.217 | File "nova/compute/manager.py", line 4537, in attach_interface 2014-08-14 11:56:07.217 | self.network_api.validate_networks(context, requested_networks, 1) 2014-08-14 11:56:07.217 | File "nova/network/api.py", line 44, in wrapped 2014-08-14 11:56:07.217 | return func(self, context, *args, **kwargs) 2014-08-14 11:56:07.217 | File "nova/network/api.py", line 370, in validate_networks 2014-08-14 11:56:07.217 | requested_networks) 2014-08-14 11:56:07.218 | File "nova/network/rpcapi.py", line 232, in validate_networks 2014-08-14 11:56:07.218 | return self.client.call(ctxt, 'validate_networks', networks=networks) 2014-08-14 11:56:07.218 | File "/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/oslo/messaging/rpc/client.py", line 389, in call 2014-08-14 11:56:07.218 | return self.prepare().call(ctxt, method, **kwargs) 2014-08-14 11:56:07.218 | File "/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/oslo/messaging/rpc/client.py", line 152, in call 2014-08-14 11:56:07.218 | retry=self.retry) 2014-08-14 11:56:07.218 | File "/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/oslo/messaging/transport.py", line 90, in _send 2014-08-14 11:56:07.218 | timeout=timeout, retry=retry) 2014-08-14 11:56:07.218 | File "/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/oslo/messaging/_drivers/impl_fake.py", line 194, in send 2014-08-14 11:56:07.218 | return self._send(target, ctxt, message, wait_for_reply, timeout) 2014-08-14 11:56:07.218 | File "/home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/oslo/messaging/_drivers/impl_fake.py", line 186, in _send 2014-08-14 11:56:07.219 | 'No reply on topic %s' % target.topic) 2014-08-14 11:56:07.219 | MessagingTimeout: No reply on topic network ** Affects: nova Importance: Undecided Status: New ** Tags: openstack-ci -- 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/1357138 Title: nova unit test failed due to No reply on topic network Status in OpenStack Compute (Nova): New Bug description: 2014-08-14 11:56:07.215 | Traceback (most recent call last): 2014-08-14 11:56:07.215 | File "nova/tests/compute/test_compute.py", line 8848, in test_attach_interface 2014-08-14 11:56:07.215 | req_ip) 2014-08-14 11:56:07.215 | File "nova/compute/manager.py", line 408, in decorated_function 2014-08-14 11:56:07.215 | return function(self, context, *args, **kwargs) 2014-08-14 11:56:07.215 | File "nova/exception.py", line 88, in wrapped 2014-08-14 11:56:07.216 | payload) 2014-08-14 11:56:07.216 | File "nova/openstack/common/excutils.py", line 82, in __exit__ 2014-08-14 11:56:07.216 | six.reraise(self.type_, self.value, self.tb) 2014-08-14 11:56:07.216 | File "nova/exception.py", line 71, in wrapped 2014-08-14 11:56:07.216 | return f(self, context, *args, **kw) 2014-08-14 11:56:07.
[Yahoo-eng-team] [Bug 1476490] [NEW] wrong expected code for os-resetState action
Public bug reported: os-resetState action have no 400(BadRequest Error) comes out, we need to remove it. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: In Progress ** Tags: api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1476490 Title: wrong expected code for os-resetState action Status in OpenStack Compute (nova): In Progress Bug description: os-resetState action have no 400(BadRequest Error) comes out, we need to remove it. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1476490/+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 1437154] Re: instance 's host was not updated after live-migration if source compute host crash
** Changed in: nova Status: Confirmed => Opinion -- 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/1437154 Title: instance 's host was not updated after live-migration if source compute host crash Status in OpenStack Compute (nova): Opinion Bug description: I do a live-migration from host1 to host2 live-migration successfully to but the instance's host is not set back to host2 yet before host1's nova-compute service crash(ctrl+c to stop it) nova list show that the instance is still active(actually , it is done the migration and I can see it host2 by virsh list) taget@liyong:~/devstack$ nova list +--+---+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+--+ | 1d114104-9a62-49ba-b209-6a42beff4133 | test1 | ACTIVE | - | NOSTATE | private_net=10.0.0.9 | show this instance, the instance's host is still host1(due to host1's compute crashed an no chance to set it yet). after that. do a reboot on this instance, failed due to the instance can not be found from host1 host(yes, it is) and nova set it to error status(but the instance is still running on host2) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1437154/+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 1478430] [NEW] nova failed to list old db instances
x27;progress': 0L, 'project_id': u'52a0ee83fb524376bd603547aea415a3', 'launched_at': datetime.datetime(2015, 7, 27, 3, 49, 29), 'scheduled_at': None, 'node': u'liyong', 'ephemeral_gb': 0L, 'access_ip_v6': None, 'access_ip_v4': None, 'kernel_id': u'712e417f- 16ec-42fb-b2cb-ef8c316d9903', 'key_name': None, 'user_data': None, 'host': u'liyong', 'root_gb': 1L, 'architecture': None, 'display_name': u'test2', 'system_metadata': [, , , , , , ], 'task_state': None, 'shutdown_terminate': False, 'cell_name': None, 'ephemeral_key_uuid': None, 'locked': False, 'name': 'instance-004c', 'created_at': datetime.datetime(2015, 7, 27, 3, 49, 18), 'locked_by': None, 'launch_index': 0L, 'metadata': [], 'memory_mb': 512L, 'vcpus': 1L, 'image_ref': u'93169d18-1bb2-45f7-861c-6735ef687db9', 'root_device_name': u'/dev/vda', 'auto_disk_config': False, 'os_type': None, 'config_drive': u''} ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1478430 Title: nova failed to list old db instances Status in OpenStack Compute (nova): New Bug description: I have a old version of nova, there is an instance running, when I upgrade to lastest upstream version of nova (commit 183cd88cb2f9781b53f71b6b161df401c286c9ff) after sync db, I get 500 error when I try to list the old instance. nova-api get follow error: 2015-07-27 12:00:11.397 TRACE nova.api.openstack sort_keys=sort_keys, sort_dirs=sort_dirs) 2015-07-27 12:00:11.397 TRACE nova.api.openstack File "/opt/stack/nova/nova/compute/api.py", line 2083, in _get_instances_by_filters 2015-07-27 12:00:11.397 TRACE nova.api.openstack expected_attrs=fields, sort_keys=sort_keys, sort_dirs=sort_dirs) 2015-07-27 12:00:11.397 TRACE nova.api.openstack File "/opt/stack/nova/nova/objects/base.py", line 71, in wrapper 2015-07-27 12:00:11.397 TRACE nova.api.openstack result = fn(cls, context, *args, **kwargs) 2015-07-27 12:00:11.397 TRACE nova.api.openstack File "/opt/stack/nova/nova/objects/instance.py", line 1221, in get_by_filters 2015-07-27 12:00:11.397 TRACE nova.api.openstack expected_attrs) 2015-07-27 12:00:11.397 TRACE nova.api.openstack File "/opt/stack/nova/nova/objects/instance.py", line 1146, in _make_instance_list 2015-07-27 12:00:11.397 TRACE nova.api.openstack expected_attrs=expected_attrs) 2015-07-27 12:00:11.397 TRACE nova.api.openstack File "/opt/stack/nova/nova/objects/instance.py", line 505, in _from_db_object 2015-07-27 12:00:11.397 TRACE nova.api.openstack if db_inst['info_cache'] is None: 2015-07-27 12:00:11.397 TRACE nova.api.openstack KeyError: 'info_cache' 2015-07-27 12:00:11.397 TRACE nova.api.openstack nova compute get follow error when restart: Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/eventlet/queue.py", line 117, in switch self.greenlet.switch(value) File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 214, in main result = function(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/oslo_service/service.py", line 623, in run_service service.start() File "/opt/stack/nova/nova/service.py", line 158, in start self.manager.init_host() File "/opt/stack/nova/nova/compute/manager.py", line 1261, in init_host context, self.host, expected_attrs=['info_cache']) File "/opt/stack/nova/nova/objects/base.py", line 69, in wrapper args, kwargs) File "/opt/stack/nova/nova/conductor/rpcapi.py", line 243, in object_class_action objver=objver, args=args, kwargs=kwargs) File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/client.py", line 158, in call retry=self.retry) File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/transport.py", line 90, in _send timeout=timeout, retry=retry) File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 431, in send retry=retry) File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 422, in _send raise result KeyErr
[Yahoo-eng-team] [Bug 1281295] Re: Live-migration nova fails with qemu and libvirt
This may most likely resolved by https://review.openstack.org/#/c/91722 Beside, I can not reproduce it with nfs storage on my local environment. Eli. ** Changed in: nova Status: Confirmed => Invalid ** Changed in: nova Status: Invalid => Incomplete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1281295 Title: Live-migration nova fails with qemu and libvirt Status in OpenStack Compute (nova): Incomplete Bug description: Hi, I posted two messages to ask.ubuntu about my problem without solution: https://ask.openstack.org/en/question/12033/live-migration-with-qemu-is-possible/ https://ask.openstack.org/en/question/12134/live-migration-with-qemu-is-really-possible/ and I reported the problem in #openstack. Until now, I can't find a solution. I'm using Openstack Havana in CentOS. I've installed 1 controller and 2 compute nodes, with NFS. Controller folder is shared by the compute nodes (folder /var/lib/nova/instances). All nodes are accessible among them without password. I can perform a migration in the dashboard. In the shell, I exaustivelly tried live migration without sucess. I'm setting /etc/nova/nova.conf and uncomment all live-migration options. I'm trying the following in the shell: # nova live-migration MY_UUID_VM_INSTANCE my_host_destine But silenty this command not works. Finally, my log of /var/log/nova-all.log: --- <0>Feb 17 20:19:43 node-4 ¿<179>nova-nova.openstack.common.rpc.amqp ERROR: Exception during message handling Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py", line 461, in _process_data **args) File "/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/dispatcher.py", line 172, in dispatch result = getattr(proxyobj, method)(ctxt, **kwargs) File "/usr/lib/python2.6/site-packages/nova/exception.py", line 90, in wrapped payload) File "/usr/lib/python2.6/site-packages/nova/exception.py", line 73, in wrapped return f(self, context, *args, **kw) File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 4016, in pre_live_migration migrate_data) File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 4162, in pre_live_migration self._create_images_and_backing(context, instance, instance_dir, UnboundLocalError: local variable 'instance_dir' referenced before assignment <0>Feb 17 20:20:16 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Auditing locally available compute resources <0>Feb 17 20:20:16 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free ram (MB): 1494 <0>Feb 17 20:20:16 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free disk (GB): 14 <0>Feb 17 20:20:16 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free VCPUS: 2 <0>Feb 17 20:20:16 node-4 ¿<182>nova-nova.compute.resource_tracker INFO: Compute_service record updated for node-4.domain.tld:node-4.domain.tld <0>Feb 17 20:21:15 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Auditing locally available compute resources <0>Feb 17 20:21:15 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free ram (MB): 1494 <0>Feb 17 20:21:15 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free disk (GB): 14 <0>Feb 17 20:21:15 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free VCPUS: 2 <0>Feb 17 20:21:15 node-4 ¿<182>nova-nova.compute.resource_tracker INFO: Compute_service record updated for node-4.domain.tld:node-4.domain.tld --- This is a bug? Someone could help me? I should use KVM instead qemu? Any help is usefull. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1281295/+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 1482066] [NEW] cannot delete nova instance if volume is not active
| | | six.reraise(self.type_, self.value, self.tb) | | | File \"/opt/stack/nova/nova/compute/manager.py\", line 2307, in _delete_instance | | | self._shutdown_instance(context, instance, bdms) | | | File \"/opt/stack/nova/nova/compute/manager.py\", line 2234, in _shutdown_instance | | | requested_networks) | | | File \"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py\", line 119, in __exit__ | | | six.reraise(self.type_, self.value, self.tb) | | | File \"/opt/stack/nova/nova/compute/manager.py\", line 2223, in _shutdown_instance | | | block_device_info) | | | File \"/opt/stack/nova/nova/virt/libvirt/driver.py\", line 768, in destroy | | | destroy_disks, migrate_data) | | | File \"/opt/stack/nova/nova/virt/libvirt/driver.py\", line 844, in cleanup | | | encryptor.detach_volume(**encryption) | | | File \"/opt/stack/nova/nova/volume/encryptors/cryptsetup.py\", line 101, in detach_volume | | | self._close_volume(**kwargs) | | | File \"/opt/stack/nova/nova/volume/encryptors/luks.py\", line 128, in _close_volume | | | attempts=3) | | | File \"/opt/stack/nova/nova/utils.py\", line 229, in execute | | | return processutils.execute(*cmd, **kwargs) | | | File \"/usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py\", line 275, in execute | | | cmd=sanitized_cmd) | | | ", "created": "2015-08-06T03:30:52Z"}
[Yahoo-eng-team] [Bug 1281295] Re: Live-migration nova fails with qemu and libvirt
** Changed in: nova Status: Incomplete => 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/1281295 Title: Live-migration nova fails with qemu and libvirt Status in OpenStack Compute (nova): Fix Released Bug description: Hi, I posted two messages to ask.ubuntu about my problem without solution: https://ask.openstack.org/en/question/12033/live-migration-with-qemu-is-possible/ https://ask.openstack.org/en/question/12134/live-migration-with-qemu-is-really-possible/ and I reported the problem in #openstack. Until now, I can't find a solution. I'm using Openstack Havana in CentOS. I've installed 1 controller and 2 compute nodes, with NFS. Controller folder is shared by the compute nodes (folder /var/lib/nova/instances). All nodes are accessible among them without password. I can perform a migration in the dashboard. In the shell, I exaustivelly tried live migration without sucess. I'm setting /etc/nova/nova.conf and uncomment all live-migration options. I'm trying the following in the shell: # nova live-migration MY_UUID_VM_INSTANCE my_host_destine But silenty this command not works. Finally, my log of /var/log/nova-all.log: --- <0>Feb 17 20:19:43 node-4 ¿<179>nova-nova.openstack.common.rpc.amqp ERROR: Exception during message handling Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py", line 461, in _process_data **args) File "/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/dispatcher.py", line 172, in dispatch result = getattr(proxyobj, method)(ctxt, **kwargs) File "/usr/lib/python2.6/site-packages/nova/exception.py", line 90, in wrapped payload) File "/usr/lib/python2.6/site-packages/nova/exception.py", line 73, in wrapped return f(self, context, *args, **kw) File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 4016, in pre_live_migration migrate_data) File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 4162, in pre_live_migration self._create_images_and_backing(context, instance, instance_dir, UnboundLocalError: local variable 'instance_dir' referenced before assignment <0>Feb 17 20:20:16 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Auditing locally available compute resources <0>Feb 17 20:20:16 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free ram (MB): 1494 <0>Feb 17 20:20:16 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free disk (GB): 14 <0>Feb 17 20:20:16 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free VCPUS: 2 <0>Feb 17 20:20:16 node-4 ¿<182>nova-nova.compute.resource_tracker INFO: Compute_service record updated for node-4.domain.tld:node-4.domain.tld <0>Feb 17 20:21:15 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Auditing locally available compute resources <0>Feb 17 20:21:15 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free ram (MB): 1494 <0>Feb 17 20:21:15 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free disk (GB): 14 <0>Feb 17 20:21:15 node-4 ¿<180>nova-nova.compute.resource_tracker AUDIT: Free VCPUS: 2 <0>Feb 17 20:21:15 node-4 ¿<182>nova-nova.compute.resource_tracker INFO: Compute_service record updated for node-4.domain.tld:node-4.domain.tld --- This is a bug? Someone could help me? I should use KVM instead qemu? Any help is usefull. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1281295/+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 1483486] [NEW] Ironic: get_available_resource doesn't report numa_topology
Public bug reported: in update_available_resource of RT we have # TODO(berrange): remove this once all virt drivers are updated # to report topology if "numa_topology" not in resources: resources["numa_topology"] = None by searching codes, all other hypervisor report numa_topology in get_available_resource except ironic driver. this can be improved. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: ironic ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1483486 Title: Ironic: get_available_resource doesn't report numa_topology Status in OpenStack Compute (nova): New Bug description: in update_available_resource of RT we have # TODO(berrange): remove this once all virt drivers are updated # to report topology if "numa_topology" not in resources: resources["numa_topology"] = None by searching codes, all other hypervisor report numa_topology in get_available_resource except ironic driver. this can be improved. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1483486/+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 1437154] Re: instance 's host was not updated after live-migration if source compute host crash
another blue print is working on https://blueprints.launchpad.net/nova/+spec/manager-restart-during- migration ** Changed in: nova Status: Opinion => Incomplete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1437154 Title: instance 's host was not updated after live-migration if source compute host crash Status in OpenStack Compute (nova): Incomplete Bug description: I do a live-migration from host1 to host2 live-migration successfully to but the instance's host is not set back to host2 yet before host1's nova-compute service crash(ctrl+c to stop it) nova list show that the instance is still active(actually , it is done the migration and I can see it host2 by virsh list) taget@liyong:~/devstack$ nova list +--+---+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+--+ | 1d114104-9a62-49ba-b209-6a42beff4133 | test1 | ACTIVE | - | NOSTATE | private_net=10.0.0.9 | show this instance, the instance's host is still host1(due to host1's compute crashed an no chance to set it yet). after that. do a reboot on this instance, failed due to the instance can not be found from host1 host(yes, it is) and nova set it to error status(but the instance is still running on host2) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1437154/+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 1483943] [NEW] ChanceScheduler doesn't sne notifier.info
Public bug reported: if user chose ChanceScheduler as scheduler driver, then nova scheduler won't send out notifier information. we need to align ChanceScheduler with FilterScheduler ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: scheduler ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1483943 Title: ChanceScheduler doesn't sne notifier.info Status in OpenStack Compute (nova): New Bug description: if user chose ChanceScheduler as scheduler driver, then nova scheduler won't send out notifier information. we need to align ChanceScheduler with FilterScheduler To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1483943/+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 1484776] [NEW] Nova api doesn't handle InstanceUnknownCell when doing live-migration
Public bug reported: compute_api.live_migrate may raise InstanceUnknownCell exception when doing check_instance_cell. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: api live-migration ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Tags added: api live-migration -- 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/1484776 Title: Nova api doesn't handle InstanceUnknownCell when doing live-migration Status in OpenStack Compute (nova): New Bug description: compute_api.live_migrate may raise InstanceUnknownCell exception when doing check_instance_cell. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1484776/+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 1484775] [NEW] Nova api doesn't handle MigrationError and will return 500 to user
Public bug reported: 1 conductor task will raise exception.MigrationError but no handler in REST api layer https://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L656 ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: api live-migration ** Tags added: api live-migration ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1484775 Title: Nova api doesn't handle MigrationError and will return 500 to user Status in OpenStack Compute (nova): New Bug description: 1 conductor task will raise exception.MigrationError but no handler in REST api layer https://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L656 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1484775/+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 1484830] [NEW] Fail early when live-migrate with block-migration and bdm
Public bug reported: If user do live-migration with block migrate and mapped volumes, user won't get an exception in nova-api. This exception will raise in nova-compute node, so user need to check log on compute node to tell why he/she trigger a live-migration but the instance is still in running state. Migration error: Cannot block migrate instance 41b1d849-6a29-448e-8ace- 4f4750514d72 with mapped volumes We can make this happen early when doing can-live-migration-source/destination etc.. by doing this, user will get the exception in nova-api this will bring good user experience, and besides if we raise this exception early , then nova won't do pre-live-migration and _rollback_live_migration. and it will partially fix https://bugs.launchpad.net/nova/+bug/1457291 ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: live-migration ** Tags added: live-migration ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1484830 Title: Fail early when live-migrate with block-migration and bdm Status in OpenStack Compute (nova): New Bug description: If user do live-migration with block migrate and mapped volumes, user won't get an exception in nova-api. This exception will raise in nova-compute node, so user need to check log on compute node to tell why he/she trigger a live-migration but the instance is still in running state. Migration error: Cannot block migrate instance 41b1d849-6a29-448e- 8ace-4f4750514d72 with mapped volumes We can make this happen early when doing can-live-migration-source/destination etc.. by doing this, user will get the exception in nova-api this will bring good user experience, and besides if we raise this exception early , then nova won't do pre-live- migration and _rollback_live_migration. and it will partially fix https://bugs.launchpad.net/nova/+bug/1457291 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1484830/+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 1484775] Re: Nova api doesn't handle MigrationError and will return 500 to user
@Alex, thanks for the clarify. ** Changed in: nova Status: In Progress => 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/1484775 Title: Nova api doesn't handle MigrationError and will return 500 to user Status in OpenStack Compute (nova): Invalid Bug description: conductor task will raise exception.MigrationError but no handler in REST api layer see https://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L656 for reference. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1484775/+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 1486880] [NEW] Can't delete an instance if boot from encryption volume
ompute/manager.py", line 316, in decorated_function ** Affects: nova Importance: High Assignee: Eli Qiao (taget-9) Status: Confirmed ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1486880 Title: Can't delete an instance if boot from encryption volume Status in OpenStack Compute (nova): Confirmed Bug description: nova configuration: [ephemeral_storage_encryption] enabled = True cipher = aes-xts-plain64 key_size = 512 [default] # use lvm as images_type | images_type=lvm | # use that volume group | # /opt/stack/data/stack-volumes-default-backing-file | images_volume_group=stack-volumes-default | reproduce: +--+---+++-+--+ root@taget-ThinkStation-P300:/opt/stack/nova# nova boot --security-groups default --key-name testkey --image 57b26b8f-0e8c-4ffd-87b9-0177e6331 b29 --nic net-id=e1d6382e-0e01-4172-9772-19d83058f8f3 --flavor 1 test3 root@taget-ThinkStation-P300:/opt/stack/nova# nova delete test3 root@taget-ThinkStation-P300:/opt/stack/nova# nova list +--+---+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+--+ | 9ac19e94-06e0-42c9-bbb5-aff44a70959e | test1 | ERROR | deleting | NOSTATE | | | 6b8c201c-6e83-4eed-a12e-190e2fa9c1a5 | test2 | ERROR | deleting | NOSTATE | | | d58b12ca-f983-47b8-93d8-a570fe4458d0 | test3 | ERROR | - | Shutdown| | +--+---+++-+--+ 2015-08-20 15:52:22.113 ERROR oslo_messaging.rpc.dispatcher [req-5a58977e-04d6-47d4-b962-a98601d400d6 admin admin] Exception during message handling: Failed to remove volume(s): (Unexpected error while running command. Command: sudo nova-rootwrap /etc/nova/rootwrap.conf lvremove -f /dev/stack-volumes-default/d58b12ca-f983-47b8-93d8-a570fe4458d0_disk Exit code: 5 Stdout: u'' Stderr: u' WARNING: Ignoring duplicate config node: global_filter (seeking global_filter)\n WARNING: Ignoring duplicate config node: global_filter (seeking global_filter)\n Logical volume stack-volumes-default/d58b12ca-f983-47b8-93d8-a570fe4458d0_disk is used by another device.\n') 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher Traceback (most recent call last): 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher executor_callback)) 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 186, in _dispatch 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher executor_callback) 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 129, in _do_dispatch 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher result = func(ctxt, **new_args) 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/nova/nova/exception.py", line 89, in wrapped 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher payload) 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 119, in __exit__ 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/nova/nova/exception.py", line 72, in wrapped 2015-08-20 15:52:22.113 TRACE oslo_messaging.rpc.dispatcher return f(self, context, *args, **kw) 2015-08-20 15:52:22.113
[Yahoo-eng-team] [Bug 1491275] [NEW] Failed to create swarm bay
Public bug reported: m-cond reports KeyError: 'number_of_minions' when creating a new swarm bay commit 97ad930147527fbb76acc320676d7c8a2a32e13e Merge: 4089b1b 86ed292 Author: Jenkins Date: Wed Sep 2 01:27:21 2015 + Merge "Add roles to context" taget@taget-ThinkStation-P300:~/nova$ magnum bay-create --name swarmbay --baymodel swarmmodel --node-count 2 ++--+ | Property | Value| ++--+ | status | None | | uuid | abb8213d-ceab-44af-afa2-fb7a99a24035 | | status_reason | None | | created_at | 2015-09-02T07:57:32+00:00| | updated_at | None | | bay_create_timeout | 0| | api_address| None | | baymodel_id| ec0647b3-9285-41fe-be10-edfd3e357c4b | | node_count | 2| | node_addresses | None | | master_count | 1| | discovery_url | None | | name | swarmbay | ++--+ 2015-09-02 15:57:33.492 ERROR oslo.service.loopingcall [req-bf80d962-74cd-4e82-89bb-09095578cb0e admin admin] Fixed interval looping call 'magnum.conductor.handlers.bay_conductor.HeatPoller.poll_and_check' failed 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall Traceback (most recent call last): 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall File "/usr/local/lib/python2.7/dist-packages/oslo_service/loopingcall.py", line 113, in _run_loop 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall result = func(*self.args, **self.kw) 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall File "/opt/stack/magnum/magnum/conductor/handlers/bay_conductor.py", line 249, in poll_and_check 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall self.bay.node_count = stack.parameters['number_of_minions'] 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall KeyError: 'number_of_minions' 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall ** Affects: magnum Importance: Undecided Assignee: Eli Qiao (taget-9) Status: Confirmed ** Description changed: + m-cond reports KeyError: 'number_of_minions' when creating a new swarm + bay + + commit 97ad930147527fbb76acc320676d7c8a2a32e13e + Merge: 4089b1b 86ed292 + Author: Jenkins + Date: Wed Sep 2 01:27:21 2015 + + + Merge "Add roles to context" + + taget@taget-ThinkStation-P300:~/nova$ magnum bay-create --name swarmbay --baymodel swarmmodel --node-count 2 + ++--+ + | Property | Value| + ++--+ + | status | None | + | uuid | abb8213d-ceab-44af-afa2-fb7a99a24035 | + | status_reason | None | + | created_at | 2015-09-02T07:57:32+00:00| + | updated_at | None | + | bay_create_timeout | 0| + | api_address| None | + | baymodel_id| ec0647b3-9285-41fe-be10-edfd3e357c4b | + | node_count | 2| + | node_addresses | None | + | master_count | 1| + | discovery_url | None | + | name | swarmbay | + ++--+ + + 2015-09-02 15:57:33.492 ERROR oslo.service.loopingcall [req-bf80d962-74cd-4e82-89bb-09095578cb0e admin admin] Fixed interval looping call 'magnum.conductor.handlers.bay_conductor.HeatPoller.poll_and_check' failed 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall Traceback (most recent call last): 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall File "/usr/local/lib/python2.7/dist-packages/oslo_service/loopingcall.py", line 113, in _run_loop 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall result = func(*self.args, **self.kw) 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall File "/opt/stack/magnum/magnum/conductor/handlers/bay_conductor.py", line 249, in poll_and_check 2015-09-02 15:57:33.492 TRACE oslo.service.loopingcall self.bay.node_count = stack.parameters['number_of_minions'] 2015-09-02 1
[Yahoo-eng-team] [Bug 1368661] Re: Unit tests sometimes fail because of stale pyc files
** Also affects: magnum Importance: Undecided Status: New ** Changed in: magnum Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1368661 Title: Unit tests sometimes fail because of stale pyc files Status in Ironic: Fix Released Status in Magnum: In Progress Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) icehouse series: Fix Released Bug description: Because python creates pyc files during tox runs, certain changes in the tree, like deletes of files, or switching branches, can create spurious errors. This can be suppressed by PYTHONDONTWRITEBYTECODE=1 in the tox.ini. To manage notifications about this bug go to: https://bugs.launchpad.net/ironic/+bug/1368661/+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 1432465] [NEW] nova detach interface will get inconsistent if hypervisor failed to detach a port
Public bug reported: Currently, in compute api, detach_interface will delete neutron port first then calls hypervisor driver to do detach_interface on the guest. If the driver does detach_interface failed, in case of the driver raise an exception.InterfaceDetachFailed or other NovaExcptions, there is no handler for them. Besides this is an asyn rpc call, so nova-api will not notice this exception. End user will find the port has been deleted in neutron side, but guest still can see this port on guest, this is inconsistent. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1432465 Title: nova detach interface will get inconsistent if hypervisor failed to detach a port Status in OpenStack Compute (Nova): In Progress Bug description: Currently, in compute api, detach_interface will delete neutron port first then calls hypervisor driver to do detach_interface on the guest. If the driver does detach_interface failed, in case of the driver raise an exception.InterfaceDetachFailed or other NovaExcptions, there is no handler for them. Besides this is an asyn rpc call, so nova-api will not notice this exception. End user will find the port has been deleted in neutron side, but guest still can see this port on guest, this is inconsistent. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1432465/+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 1433843] [NEW] live-migration failed but give wrong refer url
Public bug reported: taget@liyong:~/devstack$ nova live-migration test1 liyong2 ERROR (BadRequest): Migration pre-check error: CPU doesn't have compatibility. Requested operation is not valid: no CPU model specified Refer to http://libvirt.org/html/libvirt- libvirt.html#virCPUCompareResult (HTTP 400) (Request-ID: req-a022c4bc- 06c6-40a6-ba2e-ab6f22f51229) the reference like is not correctly. it should be http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: libvirt ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1433843 Title: live-migration failed but give wrong refer url Status in OpenStack Compute (Nova): New Bug description: taget@liyong:~/devstack$ nova live-migration test1 liyong2 ERROR (BadRequest): Migration pre-check error: CPU doesn't have compatibility. Requested operation is not valid: no CPU model specified Refer to http://libvirt.org/html/libvirt- libvirt.html#virCPUCompareResult (HTTP 400) (Request-ID: req-a022c4bc- 06c6-40a6-ba2e-ab6f22f51229) the reference like is not correctly. it should be http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1433843/+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 1433933] [NEW] live migration failed no CPU model specified
Public bug reported: 1" threads="1"/>\n\n',) from (pid=2305) to_xml /opt/stack/nova/nova/virt/libvirt/config.py:82 2015-03-19 15:35:37.697 DEBUG nova.virt.libvirt.config [req-b2abf15d-cb2c-4af9-8356-181e16ee091a admin admin] Generated XML ('\n \n\n',) from (pid=2305) to_xml /opt/stack/nova/nova/virt/libvirt/config.py:82 2015-03-19 15:35:37.699 ERROR nova.virt.libvirt.driver [req-b2abf15d-cb2c-4af9-8356-181e16ee091a admin admin] CPU doesn't have compatibility. Requested operation is not valid: no CPU model specified Refer to http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult 2015-03-19 15:35:37.702 DEBUG oslo_messaging._drivers.amqpdriver [req-b2abf15d-cb2c-4af9-8356-181e16ee091a admin admin] MSG_ID is 374d071984dd497ba58b9c0fe6ad0ea1 from (pid=2305) _send /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:310 2015-03-19 15:35:37.702 DEBUG oslo_messaging._drivers.amqp [req-b2abf15d-cb2c-4af9-8356-181e16ee091a admin admin] UNIQUE_ID is f11d04094b1d4614b06a17fe7ffe3fae. from (pid=2305) _add_unique_id /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqp.py:226 2015-03-19 15:35:37.747 ERROR oslo_messaging.rpc.dispatcher [req-b2abf15d-cb2c-4af9-8356-181e16ee091a admin admin] Exception during message handling: Migration pre-check error: CPU doesn't have compatibility. Requested operation is not valid: no CPU model specified ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1433933 Title: live migration failed no CPU model specified Status in OpenStack Compute (Nova): New Bug description: 1" threads="1"/>\n\n',) from (pid=2305) to_xml /opt/stack/nova/nova/virt/libvirt/config.py:82 2015-03-19 15:35:37.697 DEBUG nova.virt.libvirt.config [req-b2abf15d-cb2c-4af9-8356-181e16ee091a admin admin] Generated XML ('\n \n\n',) from (pid=2305) to_xml /opt/stack/nova/nova/virt/libvirt/config.py:82 2015-03-19 15:35:37.699 ERROR nova.virt.libvirt.driver [req-b2abf15d-cb2c-4af9-8356-181e16ee091a admin admin] CPU doesn't have compatibility. Requested operation is not valid: no CPU model specified Refer to http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult 2015-03-19 15:35:37.702 DEBUG oslo_messaging._drivers.amqpdriver [req-b2abf15d-cb2c-4af9-8356-181e16ee091a admin admin] MSG_ID is 374d071984dd497ba58b9c0fe6ad0ea1 from (pid=2305) _send /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:310 2015-03-19 15:35:37.702 DEBUG oslo_messaging._drivers.amqp [req-b2abf15d-cb2c-4af9-8356-181e16ee091a admin admin] UNIQUE_ID is f11d04094b1d4614b06a17fe7ffe3fae. from (pid=2305) _add_unique_id /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqp.py:226 2015-03-19 15:35:37.747 ERROR oslo_messaging.rpc.dispatcher [req-b2abf15d-cb2c-4af9-8356-181e16ee091a admin admin] Exception during message handling: Migration pre-check error: CPU doesn't have compatibility. Requested operation is not valid: no CPU model specified To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1433933/+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 1435265] [NEW] nova flavor consider Lower case when create and but not in update
Public bug reported: taget@taget-ThinkStation-P300:~/devstack$ nova flavor-create Test1 100 ^C11 1 1 when create/delete a flavor, nova considers the name as lower case letter. but it doesn't for update for example: 1. I have a flavor named TEST1 taget@taget-ThinkStation-P300:~/devstack$ nova flavor-list +--+---+---+--+---+--+---+-+---+ | ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | +--+---+---+--+---+--+---+-+---+ | 1| m1.tiny | 512 | 1| 0 | | 1 | 1.0 | True | | 101 | TEST1 | 511 | 1| 0 | | 1 | 1.0 | True | | 2| m1.small | 2048 | 20 | 0 | | 1 | 1.0 | True | | 3| m1.medium | 4096 | 40 | 0 | | 2 | 1.0 | True | | 31eb8c58-2b0a-4892-80d6-ee36d4e64871 | test | 512 | 3| 0 | | 2 | 1.0 | True | | 4| m1.large | 8192 | 80 | 0 | | 4 | 1.0 | True | | 42 | m1.nano | 64| 0| 0 | | 1 | 1.0 | True | | 5| m1.xlarge | 16384 | 160 | 0 | | 8 | 1.0 | True | | 78cd18c8-aa73-4cfc-8b01-9fbdad87b61b | controller-flavor | 4096 | 20 | 5 | 1| 4 | 1.0 | True | | 84 | m1.micro | 128 | 0| 0 | | 1 | 1.0 | True | +--+---+---+--+---+--+---+-+---+ 2. I can not create a flavor named Test1, nova consider they are same. taget@taget-ThinkStation-P300:~/devstack$ nova flavor-create Test1 100 511 1 1 ERROR (Conflict): Flavor with name Test1 already exists. (HTTP 409) (Request-ID: req-9d3a652b-84c8-4580-96f2-c684a95be5f9) 3. but When I try to update it by Test1, failed, nova considers it not exists. taget@taget-ThinkStation-P300:~/devstack$ nova flavor-key Test1 set ram 510 ERROR (CommandError): No flavor with a name or ID of 'Test1' exists. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: Confirmed ** Tags: nova ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Changed in: nova Status: New => Confirmed ** Tags added: 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/1435265 Title: nova flavor consider Lower case when create and but not in update Status in OpenStack Compute (Nova): Confirmed Bug description: taget@taget-ThinkStation-P300:~/devstack$ nova flavor-create Test1 100 ^C11 1 1 when create/delete a flavor, nova considers the name as lower case letter. but it doesn't for update for example: 1. I have a flavor named TEST1 taget@taget-ThinkStation-P300:~/devstack$ nova flavor-list +--+---+---+--+---+--+---+-+---+ | ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | +--+---+---+--+---+--+---+-+---+ | 1| m1.tiny | 512 | 1 | 0 | | 1 | 1.0 | True | | 101 | TEST1 | 511 | 1 | 0 | | 1 | 1.0 | True | | 2| m1.small | 2048 | 20 | 0 | | 1 | 1.0 | True | | 3| m1.medium | 4096 | 40 | 0 | | 2 | 1.0 | True | | 31eb8c58-2b0a-4892-80d6-ee36d4e64871 | test | 512 | 3 | 0 | | 2 | 1.0 | True | | 4| m1.large | 8192 | 80 | 0 | | 4 | 1.0 | True | | 42 | m1.nano | 64| 0 | 0 | | 1 | 1.0 | True | | 5
[Yahoo-eng-team] [Bug 1435265] Re: nova flavor consider Lower case when create and but not in update
this should be related to mysql. after some investigate. the model of InstanceTypes has this constraint, but it's not case-sensitive, so it consider test1-0 and TEST1-0 same thing. schema.UniqueConstraint("name", "deleted", name="uniq_instance_types0name0deleted") ** Project changed: nova => oslo.db ** Changed in: oslo.db Assignee: Eli Qiao (taget-9) => (unassigned) -- 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/1435265 Title: nova flavor consider Lower case when create and but not in update Status in Oslo Database library: Confirmed Bug description: taget@taget-ThinkStation-P300:~/devstack$ nova flavor-create Test1 100 ^C11 1 1 when create/delete a flavor, nova considers the name as lower case letter. but it doesn't for update for example: 1. I have a flavor named TEST1 taget@taget-ThinkStation-P300:~/devstack$ nova flavor-list +--+---+---+--+---+--+---+-+---+ | ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | +--+---+---+--+---+--+---+-+---+ | 1| m1.tiny | 512 | 1 | 0 | | 1 | 1.0 | True | | 101 | TEST1 | 511 | 1 | 0 | | 1 | 1.0 | True | | 2| m1.small | 2048 | 20 | 0 | | 1 | 1.0 | True | | 3| m1.medium | 4096 | 40 | 0 | | 2 | 1.0 | True | | 31eb8c58-2b0a-4892-80d6-ee36d4e64871 | test | 512 | 3 | 0 | | 2 | 1.0 | True | | 4| m1.large | 8192 | 80 | 0 | | 4 | 1.0 | True | | 42 | m1.nano | 64| 0 | 0 | | 1 | 1.0 | True | | 5| m1.xlarge | 16384 | 160 | 0 | | 8 | 1.0 | True | | 78cd18c8-aa73-4cfc-8b01-9fbdad87b61b | controller-flavor | 4096 | 20 | 5 | 1| 4 | 1.0 | True | | 84 | m1.micro | 128 | 0 | 0 | | 1 | 1.0 | True | +--+---+---+--+---+--+---+-+---+ 2. I can not create a flavor named Test1, nova consider they are same. taget@taget-ThinkStation-P300:~/devstack$ nova flavor-create Test1 100 511 1 1 ERROR (Conflict): Flavor with name Test1 already exists. (HTTP 409) (Request-ID: req-9d3a652b-84c8-4580-96f2-c684a95be5f9) 3. but When I try to update it by Test1, failed, nova considers it not exists. taget@taget-ThinkStation-P300:~/devstack$ nova flavor-key Test1 set ram 510 ERROR (CommandError): No flavor with a name or ID of 'Test1' exists. To manage notifications about this bug go to: https://bugs.launchpad.net/oslo.db/+bug/1435265/+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 1436643] [NEW] nova usage-list doesn't show all instance
Public bug reported: nova usage-list (os-simple-tenant-usage) will query a period instance it will return 2 kinds of instances: query = query.filter(or_(models.Instance.terminated_at == null(), models.Instance.terminated_at > begin)) in my devstack environment, query from db I see there are some instance which mysql> select count(*) from instances where launched_at is NULL; +--+ | count(*) | +--+ |3 | +--+ 1 row in set (0.00 sec) mysql> select count(*) from instances ; +--+ | count(*) | +--+ | 22 | +--+ but usage-list doesn't show 22, it doesn't count the instance which launched_at is NULL (I don't know why they are NULL , maybe live-migration failed) Usage from 2015-02-26 to 2015-03-27: +--+-+--+---+---+ | Tenant ID| Servers | RAM MB-Hours | CPU Hours | Disk GB-Hours | +--+-+--+---+---+ | 0d028ada663f41cd869acc5cdb488ad6 | 19 | 229321.36| 447.89| 447.89| +--+-+--+---+---+ do we need to count launched_at instances ? ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1436643 Title: nova usage-list doesn't show all instance Status in OpenStack Compute (Nova): New Bug description: nova usage-list (os-simple-tenant-usage) will query a period instance it will return 2 kinds of instances: query = query.filter(or_(models.Instance.terminated_at == null(), models.Instance.terminated_at > begin)) in my devstack environment, query from db I see there are some instance which mysql> select count(*) from instances where launched_at is NULL; +--+ | count(*) | +--+ |3 | +--+ 1 row in set (0.00 sec) mysql> select count(*) from instances ; +--+ | count(*) | +--+ | 22 | +--+ but usage-list doesn't show 22, it doesn't count the instance which launched_at is NULL (I don't know why they are NULL , maybe live-migration failed) Usage from 2015-02-26 to 2015-03-27: +--+-+--+---+---+ | Tenant ID| Servers | RAM MB-Hours | CPU Hours | Disk GB-Hours | +--+-+--+---+---+ | 0d028ada663f41cd869acc5cdb488ad6 | 19 | 229321.36| 447.89| 447.89| +--+-+--+---+---+ do we need to count launched_at instances ? To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1436643/+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 1405069] Re: nova client list not working when pass sort parameter
patch in oslo.db get merged. https://review.openstack.org/#/c/143632/ ** No longer affects: nova ** No longer affects: python-novaclient -- 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/1405069 Title: nova client list not working when pass sort parameter Status in Oslo Database library: Fix Committed Bug description: nova client send error request url to nova-api nova --debug list --all-tenants --deleted --sort name ... DEBUG (session:162) REQ: curl -i -X GET http://cloudcontroller:8774/v2/d7beb7f28e0b4f41901215000339361d/servers/detail?all_tenants=1&deleted=True&sort_dir=desc&sort_key=name -H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: {SHA1}6ba6e70be8c8367deec4e1696758b7dc4a1a891a" ... ClientException: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-c2a132da-05b0-4db3-84ee-1b8aeb7d0f61) ERROR (ClientException): The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-c2a132da-05b0-4db3-84ee-1b8aeb7d0f61) the url parameter should be passed as 'sort_keys' instead of 'sort_key' beside, nova-api/nova should handle this exception instead of raise an internal error(500) this to customer. To manage notifications about this bug go to: https://bugs.launchpad.net/oslo.db/+bug/1405069/+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 1437111] [NEW] os-migrateLive fault but rest api raise a incorrect conflict message
Public bug reported: when do a live migration which the instance is in a state like this taget@liyong:~/devstack$ nova list +--+---+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+--+ | 1d114104-9a62-49ba-b209-6a42beff4133 | test1 | ACTIVE | - | NOSTATE | private_net=10.0.0.9 | +--+---+++-+--+ rest api raise conflictRequest, this is correct, but the message is not correct. (0, '{"conflictingRequest": {"message": "Instance 1d114104-9a62-49ba-b209-6a42beff4133 is in an invalid state for \'os- migrateLive\'", "code": 409}}', ' % Total% Received % Xferd Average Speed TimeTime Time Current\n Dload Upload Total SpentLeft Speed\n\r 0 00 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0\r100920 0 10092 0 76 0:00:01 0:00:01 --:--:--76\r100 233 100 141 10092 78 51 0:00:01 0:00:01 --:--:--78\r100 233 100 141 10092 78 51 0:00:01 0:00:01 --:--:-- 78\n') in live_migrate.py, we check if instance in active state, it do the right thing. def _check_instance_is_active(self): if self.instance.power_state not in (power_state.RUNNING, power_state.PAUSED): raise exception.InstanceInvalidState( instance_uuid = self.instance.uuid, attr = 'power_state', state = self.instance.power_state, method = 'live migrate') but in this case, power_state is an Integer zero, the logic in raise_http_conflict_for_instance_invalid_state by checking code of raise_http_conflict_for_instance_invalid_state def raise_http_conflict_for_instance_invalid_state(exc, action, server_id): """Raises a webob.exc.HTTPConflict instance containing a message appropriate to return via the API based on the original InstanceInvalidState exception. """ attr = exc.kwargs.get('attr') state = exc.kwargs.get('state') not_launched = exc.kwargs.get('not_launched') if attr and state: <<<<<<<<<<<<< should go this condition but state is zero. msg = _("Cannot '%(action)s' instance %(server_id)s while it is in " "%(attr)s %(state)s") % {'action': action, 'attr': attr, 'state': state, 'server_id': server_id} ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: Confirmed ** Tags: api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Changed in: nova Status: New => Confirmed -- 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/1437111 Title: os-migrateLive fault but rest api raise a incorrect conflict message Status in OpenStack Compute (Nova): Confirmed Bug description: when do a live migration which the instance is in a state like this taget@liyong:~/devstack$ nova list +--+---+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+--+ | 1d114104-9a62-49ba-b209-6a42beff4133 | test1 | ACTIVE | - | NOSTATE | private_net=10.0.0.9 | +--+---+++-+--+ rest api raise conflictRequest, this is correct, but the message is not correct. (0, '{"conflictingRequest": {"message": "Instance 1d114104-9a62-49ba-b209-6a42beff4133 is in an invalid state for \'os- migrateLive\'", "code": 409}}', ' % Total% Received % Xferd Average Speed TimeTime Time Current\n Dload Upload Total SpentLeft Speed\n\r 0 00 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0\r100920 0 10092 0 76 0:00:01 0:00:01 --:--:--76\r100 233 100 141 10092 78 51 0:00:01 0:00:01 --:--:-- 78\r100 233 100 141 10092 78
[Yahoo-eng-team] [Bug 1437154] [NEW] instance 's host was not updated after live-migration if source compute host crash
Public bug reported: I do a live-migration from host1 to host2 live-migration successfully to but the instance's host is not set back to host2 yet before host1's nova-compute service crash(ctrl+c to stop it) nova list show that the instance is still active(actually , it is done the migration and I can see it host2 by virsh list) taget@liyong:~/devstack$ nova list +--+---+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+--+ | 1d114104-9a62-49ba-b209-6a42beff4133 | test1 | ACTIVE | - | NOSTATE | private_net=10.0.0.9 | show this instance, the instance's host is still host1(due to host1's compute crashed an no chance to set it yet). after that. do a reboot on this instance, failed due to the instance can not be found from host1 host(yes, it is) and nova set it to error status(but the instance is still running on host2) ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1437154 Title: instance 's host was not updated after live-migration if source compute host crash Status in OpenStack Compute (Nova): New Bug description: I do a live-migration from host1 to host2 live-migration successfully to but the instance's host is not set back to host2 yet before host1's nova-compute service crash(ctrl+c to stop it) nova list show that the instance is still active(actually , it is done the migration and I can see it host2 by virsh list) taget@liyong:~/devstack$ nova list +--+---+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+--+ | 1d114104-9a62-49ba-b209-6a42beff4133 | test1 | ACTIVE | - | NOSTATE | private_net=10.0.0.9 | show this instance, the instance's host is still host1(due to host1's compute crashed an no chance to set it yet). after that. do a reboot on this instance, failed due to the instance can not be found from host1 host(yes, it is) and nova set it to error status(but the instance is still running on host2) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1437154/+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 1437992] [NEW] policy file in policy.d will be reloaded every rest api call
Public bug reported: the policy file in policy.d will be reloaded every time when do a rest api call. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1437992 Title: policy file in policy.d will be reloaded every rest api call Status in OpenStack Compute (Nova): New Bug description: the policy file in policy.d will be reloaded every time when do a rest api call. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1437992/+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 1437992] Re: policy file in policy.d will be reloaded every rest api call
olso.policy patch. https://review.openstack.org/#/c/168798/ ** Also affects: oslo.policy Importance: Undecided Status: New ** Changed in: oslo.policy Status: New => Confirmed ** Changed in: oslo.policy Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1437992 Title: policy file in policy.d will be reloaded every rest api call Status in OpenStack Compute (Nova): In Progress Status in Oslo Policy: Confirmed Bug description: the policy file in policy.d will be reloaded every time when do a rest api call. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1437992/+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 1437992] Re: policy file in policy.d will be reloaded every rest api call
** Also affects: oslo-incubator 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/1437992 Title: policy file in policy.d will be reloaded every rest api call Status in OpenStack Compute (Nova): In Progress Status in The Oslo library incubator: New Status in Oslo Policy: Confirmed Bug description: the policy file in policy.d will be reloaded every time when do a rest api call. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1437992/+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 1438663] Re: neutronv2 api unit test case error
** No longer affects: oslo-incubator -- 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/1438663 Title: neutronv2 api unit test case error Status in OpenStack Compute (Nova): Incomplete Bug description: if neutron has port binding extension, the port client should be an admin user, which should be a different client with neutron. check this link https://github.com/openstack/nova/blob/master/nova/tests/unit/network/test_neutronv2.py#L375-L379 line 376 and 379 should use difference mock client object. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1438663/+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 1440981] [NEW] live-migration failed due to invalid value of cpu set
Public bug reported: Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 457, in fire_timers timer() File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/timer.py", line 58, in __call__ cb(*args, **kw) File "/usr/local/lib/python2.7/dist-packages/eventlet/event.py", line 168, in _do_send waiter.switch(result) File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 214, in main result = function(*args, **kwargs) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 5433, in _live_migration_operation instance=instance) File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 85, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 5402, in _live_migration_operation CONF.libvirt.live_migration_bandwidth) File "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 183, in doit result = proxy_call(self._autowrap, f, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 141, in proxy_call rv = execute(f, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 122, in execute six.reraise(c, e, tb) File "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 80, in tworker rv = meth(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1582, in migrateToURI2 if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed', dom=self) libvirtError: Invalid value '0-15' for 'cpuset.cpus': Invalid argument Reproduce steps: there are 2 compute hosts: hostA: 16 cpu hostB: 4cpu 1. create an instance test1 (which run on hostA) 2. do live migration on test1 from hostA to hostB Expected result: test1 live migrate to hostB Actual result: failed due to cpu set invalid. findings: workaround is set vcpu_pin_set = "0-3" on hostA's nova.conf default section. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1440981 Title: live-migration failed due to invalid value of cpu set Status in OpenStack Compute (Nova): New Bug description: Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 457, in fire_timers timer() File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/timer.py", line 58, in __call__ cb(*args, **kw) File "/usr/local/lib/python2.7/dist-packages/eventlet/event.py", line 168, in _do_send waiter.switch(result) File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 214, in main result = function(*args, **kwargs) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 5433, in _live_migration_operation instance=instance) File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 85, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 5402, in _live_migration_operation CONF.libvirt.live_migration_bandwidth) File "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 183, in doit result = proxy_call(self._autowrap, f, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 141, in proxy_call rv = execute(f, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 122, in execute six.reraise(c, e, tb) File "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 80, in tworker rv = meth(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1582, in migrateToURI2 if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed', dom=self) libvirtError: Invalid value '0-15' for 'cpuset.cpus': Invalid argument Reproduce steps: there are 2 compute hosts: hostA: 16 cpu hostB: 4cpu 1. create an instance test1 (which run on hostA) 2. do live migration on test1 from hostA to hostB Expected result: test1 live migrate to hostB Actual result: failed due to cpu set invalid. findings: workaround is set vcpu_pin_set = "0-3" on hostA's nova.conf default section. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1440981/+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 1441000] [NEW] live migration gives wrong log infor
Public bug reported: when doing live migration , from source host, we see 2015-04-07 14:18:54.164 INFO nova.virt.libvirt.driver [-] [instance: 807c89f2-4818-4020-96dc-8080a8c9fcec] Migration running for 0 secs, memory 0% remaining; (bytes processed=0, remaining=0, total=0) ^^ this will lead confusion to admins ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: libvirt ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Tags added: libvirt ** Description changed: when doing live migration , from source host, we see - 2015-04-07 14:18:54.164 INFO nova.virt.libvirt.driver [-] [instance: 807c89f2-4818-4020-96dc-8080a8c9fcec] Migration running for 0 secs, memory 0% remaining; (bytes processed=0, remaining=0, total=0) - ^^^ + 2015-04-07 14:18:54.164 INFO nova.virt.libvirt.driver [-] [instance: 807c89f2-4818-4020-96dc-8080a8c9fcec] Migration running for 0 secs, memory 0% remaining; (bytes processed=0, + + remaining=0, total=0) + ^^ this will lead confusion to admins -- 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/1441000 Title: live migration gives wrong log infor Status in OpenStack Compute (Nova): New Bug description: when doing live migration , from source host, we see 2015-04-07 14:18:54.164 INFO nova.virt.libvirt.driver [-] [instance: 807c89f2-4818-4020-96dc-8080a8c9fcec] Migration running for 0 secs, memory 0% remaining; (bytes processed=0, remaining=0, total=0) ^^ this will lead confusion to admins To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1441000/+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 1409613] Re: nova evacuate allows to evacuate to a host which are not in same aggregate with origin host
admin need to take case if they want to break the aggregate rule. ** Changed in: nova Status: In Progress => 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/1409613 Title: nova evacuate allows to evacuate to a host which are not in same aggregate with origin host Status in OpenStack Compute (Nova): Invalid Bug description: nova allows evacuate an instance to a host which doesn't have specify feature. how to reproduce : 1 create aggregate [tagett@stack-01 devstack]$ nova aggregate-details 2 ++--+---++--+ | Id | Name | Availability Zone | Hosts | Metadata | ++--+---++--+ | 2 | s| nova | 'stack-kvm110' | 'availability_zone=nova', 'ssd=true' 2 create flavor [tagett@stack-01 devstack]$ nova flavor-show 100 ++--+ | Property | Value| ++--+ | OS-FLV-DISABLED:disabled | False| | OS-FLV-EXT-DATA:ephemeral | 0| | disk | 10 | | extra_specs| {"ssd": "true", "availability_zone": "nova"} | | id | 100 | | name | stack110 | | os-flavor-access:is_public | True | | ram| 1024 | | rxtx_factor| 1.0 | | swap | | | vcpus | 2| ++--+ 3 create an instance with flavor 100 [tagett@stack-01 devstack]$ nova list +--+--+-++-++ | ID | Name | Status | Task State | Power State | Networks | +--+--+-++-++ | 428f0235-be54-462f-8916-f32965d42e63 | boot_from_volume | SHUTOFF | - | Shutdown| public=172.24.4.3 | | b48aa410-769e-4f10-bb9c-181250bb4441 | test | ACTIVE | 1 | Running | public=172.24.4.21 | 4 stop compute service on stack-kvm110 5 nova evacuate test to another host which don't in aggregate 2 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1409613/+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 1447946] [NEW] nova report DeprecationWarning message when using exception.message
Public bug reported: taget@taget-ThinkStation-P300:~/nova$ tox -e py27 nova.tests.unit.compute.test_flavors.CreateFlavorTestCase.test_create_flavor_ram_error py27 develop-inst-nodeps: /home/taget/nova py27 runtests: PYTHONHASHSEED='0' py27 runtests: commands[0] | find . -type f -name *.pyc -delete py27 runtests: commands[1] | bash tools/pretty_tox.sh nova.tests.unit.compute.test_flavors.CreateFlavorTestCase.test_create_flavor_ram_error running testr running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run discover -t ./ ${OS_TEST_PATH:-./nova/tests} --list running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run discover -t ./ ${OS_TEST_PATH:-./nova/tests} --load-list /tmp/tmpBqJXFX {0} nova.tests.unit.compute.test_flavors.CreateFlavorTestCase.test_create_flavor_ram_error [0.086535s] ... ok Captured stderr: nova/tests/unit/compute/test_flavors.py:45: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 self.assertIn("ram", e.message) and this can be fixed by overwrite NovaException.message see [1] [1] http://stackoverflow.com/questions/1319615/proper-way-to-declare-custom-exceptions-in-modern-python/26938914#26938914 ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: Confirmed ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Changed in: nova Status: New => Confirmed ** Summary changed: - nova report DeprecationWarning message is using exception.message + nova report DeprecationWarning message when using exception.message -- 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/1447946 Title: nova report DeprecationWarning message when using exception.message Status in OpenStack Compute (Nova): Confirmed Bug description: taget@taget-ThinkStation-P300:~/nova$ tox -e py27 nova.tests.unit.compute.test_flavors.CreateFlavorTestCase.test_create_flavor_ram_error py27 develop-inst-nodeps: /home/taget/nova py27 runtests: PYTHONHASHSEED='0' py27 runtests: commands[0] | find . -type f -name *.pyc -delete py27 runtests: commands[1] | bash tools/pretty_tox.sh nova.tests.unit.compute.test_flavors.CreateFlavorTestCase.test_create_flavor_ram_error running testr running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run discover -t ./ ${OS_TEST_PATH:-./nova/tests} --list running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run discover -t ./ ${OS_TEST_PATH:-./nova/tests} --load-list /tmp/tmpBqJXFX {0} nova.tests.unit.compute.test_flavors.CreateFlavorTestCase.test_create_flavor_ram_error [0.086535s] ... ok Captured stderr: nova/tests/unit/compute/test_flavors.py:45: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 self.assertIn("ram", e.message) and this can be fixed by overwrite NovaException.message see [1] [1] http://stackoverflow.com/questions/1319615/proper-way-to-declare-custom-exceptions-in-modern-python/26938914#26938914 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1447946/+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 1449811] [NEW] nova lock/unlock api return code is not accurate
Public bug reported: Currently, lock server api only returns 202(accepted) and 404(not found). The api return code is not accurate. The lock/unlock api in compute-api is a sync function, so the return code of nova-api should be: * 200 : successfully lock/unlock an instance * 404 : instance not found * 409 : locking/unlocking a locked/unlocked instance ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1449811 Title: nova lock/unlock api return code is not accurate Status in OpenStack Compute (Nova): New Bug description: Currently, lock server api only returns 202(accepted) and 404(not found). The api return code is not accurate. The lock/unlock api in compute-api is a sync function, so the return code of nova-api should be: * 200 : successfully lock/unlock an instance * 404 : instance not found * 409 : locking/unlocking a locked/unlocked instance To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1449811/+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 1449858] [NEW] nova don't create local disk if specify device=vda in block_device_mapping_v2
Public bug reported: I wish to create a instance with local disk(1G) and attaching a blank(new created) volume(2G). using follow nova command line api, but I specify the bdm's device=vda nova --debug boot --image baaece45-58a2-4e4c-b8b7-7b3f12fe4bc6 --flavor 1 --nic net-id=9af3d913-dd65-4864-88b5-cd42bce3f672 --block-device source=blank,dest=volume,device=vda,size=2 test12 I got a instance , by checking domain xml I only got 1 block device(2G), but no local disk was created. expect result. 1. raise badrequest if sepcify device=vda in block-device. or 2. just ignore device=vda in block-device and create 2 device for this instance. I prefer option 1. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Description changed: I wish to create a instance with local disk(1G) and attaching a blank(new created) volume(2G). using follow nova command line api, but I specify the bdm's device=vda nova --debug boot --image baaece45-58a2-4e4c-b8b7-7b3f12fe4bc6 --flavor 1 --nic net-id=9af3d913-dd65-4864-88b5-cd42bce3f672 --block-device source=blank,dest=volume,device=vda,size=2 test12 I got a instance , by checking domain xml I only got 1 block device(2G), but no local disk was created. expect result. 1. raise badrequest if sepcify device=vda in block-device. or 2. just ignore device=vda in block-device and create 2 device for this instance. - I am prefer option 1. + I prefer option 1. ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1449858 Title: nova don't create local disk if specify device=vda in block_device_mapping_v2 Status in OpenStack Compute (Nova): New Bug description: I wish to create a instance with local disk(1G) and attaching a blank(new created) volume(2G). using follow nova command line api, but I specify the bdm's device=vda nova --debug boot --image baaece45-58a2-4e4c-b8b7-7b3f12fe4bc6 --flavor 1 --nic net-id=9af3d913-dd65-4864-88b5-cd42bce3f672 --block- device source=blank,dest=volume,device=vda,size=2 test12 I got a instance , by checking domain xml I only got 1 block device(2G), but no local disk was created. expect result. 1. raise badrequest if sepcify device=vda in block-device. or 2. just ignore device=vda in block-device and create 2 device for this instance. I prefer option 1. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1449858/+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 1452522] [NEW] nova-api: remove unuseful expect error in v2.1 service delete method
Public bug reported: in nova/api/openstack/compute/plugins/v3/services.py we found : @extensions.expected_errors((400, 404)) def delete(self, req, id): by checking code, there isn't any badrequest exception raising, we need to remove 400 from expected code. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Tags added: api -- 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/1452522 Title: nova-api: remove unuseful expect error in v2.1 service delete method Status in OpenStack Compute (Nova): New Bug description: in nova/api/openstack/compute/plugins/v3/services.py we found : @extensions.expected_errors((400, 404)) def delete(self, req, id): by checking code, there isn't any badrequest exception raising, we need to remove 400 from expected code. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1452522/+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 1456017] [NEW] devstack create role filed
Public bug reported: 2015-05-17 19:23:18.238 | + get_or_add_group_project_role 66765e5f063c4688aeb2cc5b4f843ba7 4869405de194496da69b72002bcce377 bf066ef86c0e44128da8bc1849c13532 2015-05-17 19:23:18.240 | ++ get_field 1 2015-05-17 19:23:18.241 | ++ local data field 2015-05-17 19:23:18.242 | ++ grep ' 66765e5f063c4688aeb2cc5b4f843ba7 ' 2015-05-17 19:23:18.243 | ++ read data 2015-05-17 19:23:18.244 | ++ openstack role list --group 4869405de194496da69b72002bcce377 --project bf066ef86c0e44128da8bc1849c13532 --column ID --column Name 2015-05-17 19:23:18.898 | usage: openstack role list [-h] [-f {csv,html,json,table,yaml}] [-c COLUMN] 2015-05-17 19:23:18.898 |[--max-width ] 2015-05-17 19:23:18.898 |[--quote {all,minimal,none,nonnumeric}] 2015-05-17 19:23:18.898 |[--project ] [--user ] We need to use --os-identity-api-version=3 ** Affects: nova Importance: Undecided Status: New ** Tags: devstack -- 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/1456017 Title: devstack create role filed Status in OpenStack Compute (Nova): New Bug description: 2015-05-17 19:23:18.238 | + get_or_add_group_project_role 66765e5f063c4688aeb2cc5b4f843ba7 4869405de194496da69b72002bcce377 bf066ef86c0e44128da8bc1849c13532 2015-05-17 19:23:18.240 | ++ get_field 1 2015-05-17 19:23:18.241 | ++ local data field 2015-05-17 19:23:18.242 | ++ grep ' 66765e5f063c4688aeb2cc5b4f843ba7 ' 2015-05-17 19:23:18.243 | ++ read data 2015-05-17 19:23:18.244 | ++ openstack role list --group 4869405de194496da69b72002bcce377 --project bf066ef86c0e44128da8bc1849c13532 --column ID --column Name 2015-05-17 19:23:18.898 | usage: openstack role list [-h] [-f {csv,html,json,table,yaml}] [-c COLUMN] 2015-05-17 19:23:18.898 |[--max-width ] 2015-05-17 19:23:18.898 |[--quote {all,minimal,none,nonnumeric}] 2015-05-17 19:23:18.898 |[--project ] [--user ] We need to use --os-identity-api-version=3 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1456017/+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 1456437] [NEW] Devstack can not install openstack due to bad md5 hash code
Public bug reported: when using devstack to install stable branch openstack project, there may fail due to bad md5 hash .. 2015-05-18 19:51:25.980 | Obtaining file:///opt/stack/kilo/nova 2015-05-18 19:51:27.563 | Requirement already satisfied (use --upgrade to upgrade): pbr!=0.7,<1.0,>=0.6 in /usr/local/lib/python2.7/dist-packages (from nova==2015.1.1.dev13) 2015-05-18 19:51:27.566 | Requirement already satisfied (use --upgrade to upgrade): SQLAlchemy<=0.9.99,>=0.9.7 in /usr/local/lib/python2.7/dist-packages (from nova==2015.1.1.dev13) 2015-05-18 19:51:27.586 | Collecting boto>=2.32.1 (from nova==2015.1.1.dev13) 2015-05-18 19:51:27.692 | Using cached boto-2.38.0-py2.py3-none-any.whl 2015-05-18 19:51:27.694 | Hash of the package https://pypi.python.org/packages/2.7/b/boto/boto-2.38.0-py2.py3-none-any.whl#md5=dd00fcddc668880494987bcb6102ecf2 (from https://pypi.python.org/simple/boto/) (39c6ea46c7f78b4ac829a0cf4ed6bbd3) doesn't match the expected hash dd00fcddc668880494987bcb6102ecf2! 2015-05-18 19:51:27.696 | Bad md5 hash for package https://pypi.python.org/packages/2.7/b/boto/boto-2.38.0-py2.py3-none-any.whl#md5=dd00fcddc668880494987bcb6102ecf2 (from https://pypi.python.org/simple/boto/) ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1456437 Title: Devstack can not install openstack due to bad md5 hash code Status in OpenStack Compute (Nova): New Bug description: when using devstack to install stable branch openstack project, there may fail due to bad md5 hash .. 2015-05-18 19:51:25.980 | Obtaining file:///opt/stack/kilo/nova 2015-05-18 19:51:27.563 | Requirement already satisfied (use --upgrade to upgrade): pbr!=0.7,<1.0,>=0.6 in /usr/local/lib/python2.7/dist-packages (from nova==2015.1.1.dev13) 2015-05-18 19:51:27.566 | Requirement already satisfied (use --upgrade to upgrade): SQLAlchemy<=0.9.99,>=0.9.7 in /usr/local/lib/python2.7/dist-packages (from nova==2015.1.1.dev13) 2015-05-18 19:51:27.586 | Collecting boto>=2.32.1 (from nova==2015.1.1.dev13) 2015-05-18 19:51:27.692 | Using cached boto-2.38.0-py2.py3-none-any.whl 2015-05-18 19:51:27.694 | Hash of the package https://pypi.python.org/packages/2.7/b/boto/boto-2.38.0-py2.py3-none-any.whl#md5=dd00fcddc668880494987bcb6102ecf2 (from https://pypi.python.org/simple/boto/) (39c6ea46c7f78b4ac829a0cf4ed6bbd3) doesn't match the expected hash dd00fcddc668880494987bcb6102ecf2! 2015-05-18 19:51:27.696 | Bad md5 hash for package https://pypi.python.org/packages/2.7/b/boto/boto-2.38.0-py2.py3-none-any.whl#md5=dd00fcddc668880494987bcb6102ecf2 (from https://pypi.python.org/simple/boto/) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1456437/+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 1515860] [NEW] No sql_connection parameter is established when nova-manage api_db sync
Public bug reported: ./stack.sh taget@liyong:/opt/stack/nova$ git log --oneline | head -n3 98af6b1 Merge "Deprecate Extensible Resource Tracker" 7c5acd4 Merge "Remove vcpu resource from extensible resource tracker" b587881 Merge "Split up test_is_volume_backed_instance() into five functions" taget@liyong:~/devstack$ /usr/local/bin/nova-manage api_db sync No handlers could be found for logger "oslo_config.cfg" 2015-11-13 11:49:34.620 DEBUG migrate.versioning.repository [-] Loading repository /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo... from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/repository.py:76 2015-11-13 11:49:34.621 DEBUG migrate.versioning.script.base [-] Loading script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/001_cell_mapping.py... from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:27 2015-11-13 11:49:34.621 DEBUG migrate.versioning.script.base [-] Script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/001_cell_mapping.py loaded successfully from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:30 2015-11-13 11:49:34.621 DEBUG migrate.versioning.script.base [-] Loading script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/002_instance_mapping.py... from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:27 2015-11-13 11:49:34.622 DEBUG migrate.versioning.script.base [-] Script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/002_instance_mapping.py loaded successfully from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:30 2015-11-13 11:49:34.622 DEBUG migrate.versioning.script.base [-] Loading script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/003_host_mapping.py... from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:27 2015-11-13 11:49:34.622 DEBUG migrate.versioning.script.base [-] Script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/003_host_mapping.py loaded successfully from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:30 2015-11-13 11:49:34.623 DEBUG migrate.versioning.repository [-] Repository /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo loaded successfully from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/repository.py:82 2015-11-13 11:49:34.623 DEBUG migrate.versioning.repository [-] Config: OrderedDict([('db_settings', OrderedDict([('__name__', 'db_settings'), ('repository_id', 'nova_api'), ('version_table', 'migrate_version'), ('required_dbs', '[]')]))]) from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/repository.py:83 Command failed, please check log for more info 2015-11-13 11:49:34.624 CRITICAL nova [-] CantStartEngineError: No sql_connection parameter is established 2015-11-13 11:49:34.624 TRACE nova Traceback (most recent call last): 2015-11-13 11:49:34.624 TRACE nova File "/usr/local/bin/nova-manage", line 10, in 2015-11-13 11:49:34.624 TRACE nova sys.exit(main()) 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/cmd/manage.py", line 1425, in main 2015-11-13 11:49:34.624 TRACE nova ret = fn(*fn_args, **fn_kwargs) 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/cmd/manage.py", line 976, in sync 2015-11-13 11:49:34.624 TRACE nova return migration.db_sync(version, database='api') 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/db/migration.py", line 26, in db_sync 2015-11-13 11:49:34.624 TRACE nova return IMPL.db_sync(version=version, database=database) 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/db/sqlalchemy/migration.py", line 53, in db_sync 2015-11-13 11:49:34.624 TRACE nova current_version = db_version(database) 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/db/sqlalchemy/migration.py", line 66, in db_version 2015-11-13 11:49:34.624 TRACE nova return versioning_api.db_version(get_engine(database), repository) 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/db/sqlalchemy/migration.py", line 43, in get_engine 2015-11-13 11:49:34.624 TRACE nova return db_session.get_api_engine() 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 167, in get_api_engine 2015-11-13 11:49:34.624 TRACE nova return api_context_manager._factory.get_legacy_facade().get_engine() 2015-11-13 11:49:34.624 TRACE nova File "/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 256, in get_legacy_facade 2015-11-13 11:49:34.624 TRACE nova self._start() 2015-11-13 11:49:34.624 TRACE nova File
[Yahoo-eng-team] [Bug 1515860] Re: No sql_connection parameter is established when nova-manage api_db sync
what a stupid, nova will search ~/nova.conf , and I happened have an old nova.conf in ~/ so, /etc/nova/nova.conf will be ignored. ** Changed in: nova Status: New => 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/1515860 Title: No sql_connection parameter is established when nova-manage api_db sync Status in OpenStack Compute (nova): Invalid Bug description: ./stack.sh taget@liyong:/opt/stack/nova$ git log --oneline | head -n3 98af6b1 Merge "Deprecate Extensible Resource Tracker" 7c5acd4 Merge "Remove vcpu resource from extensible resource tracker" b587881 Merge "Split up test_is_volume_backed_instance() into five functions" taget@liyong:~/devstack$ /usr/local/bin/nova-manage api_db sync No handlers could be found for logger "oslo_config.cfg" 2015-11-13 11:49:34.620 DEBUG migrate.versioning.repository [-] Loading repository /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo... from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/repository.py:76 2015-11-13 11:49:34.621 DEBUG migrate.versioning.script.base [-] Loading script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/001_cell_mapping.py... from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:27 2015-11-13 11:49:34.621 DEBUG migrate.versioning.script.base [-] Script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/001_cell_mapping.py loaded successfully from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:30 2015-11-13 11:49:34.621 DEBUG migrate.versioning.script.base [-] Loading script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/002_instance_mapping.py... from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:27 2015-11-13 11:49:34.622 DEBUG migrate.versioning.script.base [-] Script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/002_instance_mapping.py loaded successfully from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:30 2015-11-13 11:49:34.622 DEBUG migrate.versioning.script.base [-] Loading script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/003_host_mapping.py... from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:27 2015-11-13 11:49:34.622 DEBUG migrate.versioning.script.base [-] Script /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/003_host_mapping.py loaded successfully from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/base.py:30 2015-11-13 11:49:34.623 DEBUG migrate.versioning.repository [-] Repository /opt/stack/nova/nova/db/sqlalchemy/api_migrations/migrate_repo loaded successfully from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/repository.py:82 2015-11-13 11:49:34.623 DEBUG migrate.versioning.repository [-] Config: OrderedDict([('db_settings', OrderedDict([('__name__', 'db_settings'), ('repository_id', 'nova_api'), ('version_table', 'migrate_version'), ('required_dbs', '[]')]))]) from (pid=15818) __init__ /usr/local/lib/python2.7/dist-packages/migrate/versioning/repository.py:83 Command failed, please check log for more info 2015-11-13 11:49:34.624 CRITICAL nova [-] CantStartEngineError: No sql_connection parameter is established 2015-11-13 11:49:34.624 TRACE nova Traceback (most recent call last): 2015-11-13 11:49:34.624 TRACE nova File "/usr/local/bin/nova-manage", line 10, in 2015-11-13 11:49:34.624 TRACE nova sys.exit(main()) 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/cmd/manage.py", line 1425, in main 2015-11-13 11:49:34.624 TRACE nova ret = fn(*fn_args, **fn_kwargs) 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/cmd/manage.py", line 976, in sync 2015-11-13 11:49:34.624 TRACE nova return migration.db_sync(version, database='api') 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/db/migration.py", line 26, in db_sync 2015-11-13 11:49:34.624 TRACE nova return IMPL.db_sync(version=version, database=database) 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/db/sqlalchemy/migration.py", line 53, in db_sync 2015-11-13 11:49:34.624 TRACE nova current_version = db_version(database) 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/db/sqlalchemy/migration.py", line 66, in db_version 2015-11-13 11:49:34.624 TRACE nova return versioning_api.db_version(get_engine(database), repository) 2015-11-13 11:49:34.624 TRACE nova File "/opt/stack/nova/nova/db/sqlalchemy/migration.py", line 43,
[Yahoo-eng-team] [Bug 1522239] [NEW] Useless element in migrate_server shcema
Public bug reported: -host = copy.deepcopy(parameter_types.hostname) -host['type'] = ['string', 'null'] These 2 lines could be removed from schema file ** Affects: nova Importance: Low Assignee: Eli Qiao (taget-9) Status: Confirmed ** Tags: api ** Changed in: nova Status: New => Confirmed ** Changed in: nova Importance: Undecided => Low ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Tags added: api -- 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/1522239 Title: Useless element in migrate_server shcema Status in OpenStack Compute (nova): Confirmed Bug description: -host = copy.deepcopy(parameter_types.hostname) -host['type'] = ['string', 'null'] These 2 lines could be removed from schema file To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1522239/+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 1371406] [NEW] should error when unshelve an volume backed instance which the image was deleted
Public bug reported: shelve an instance first. nova will create an snapshot of image with instance name-shelved like: t2-shelved manually delete the image with nova image-delte t2-shelved then do an unshelve, it should report image not found error and mark the instance vm_state ERROR this is the output of glance in conductor, the image is deleted, but nova don't get the deleted status of image. 2014-09-19 11:12:20.534 DEBUG glanceclient.common.http [req-d2aaa493-b507-4f75-a185-c83d347f82b0 admin admin] HTTP/1.1 200 OK content-length: 0 x-image-meta-id: 2a6ce744-b96b-4f71-882e-13c4fc1c9da1 date: Fri, 19 Sep 2014 03:12:20 GMT x-image-meta-deleted: True <<<=== x-image-meta-container_format: ami x-image-meta-checksum: 1b31d2e911494696c6d190ccef2f4d64 x-image-meta-deleted_at: 2014-09-19T02:41:27 x-image-meta-min_disk: 0 x-image-meta-protected: False x-image-meta-created_at: 2014-09-18T04:03:09 x-image-meta-size: 10616832 x-image-meta-status: deleted <<<=== etag: 1b31d2e911494696c6d190ccef2f4d64 x-image-meta-is_public: False x-image-meta-min_ram: 0 x-image-meta-owner: d7beb7f28e0b4f41901215000339361d x-image-meta-updated_at: 2014-09-19T02:41:27 content-type: text/html; charset=UTF-8 x-openstack-request-id: req-e95ddab3-bee5-4847-ba55-13be02bc1a14 x-image-meta-disk_format: ami x-image-meta-name: t2-shelved ** 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/1371406 Title: should error when unshelve an volume backed instance which the image was deleted Status in OpenStack Compute (Nova): New Bug description: shelve an instance first. nova will create an snapshot of image with instance name-shelved like: t2-shelved manually delete the image with nova image-delte t2-shelved then do an unshelve, it should report image not found error and mark the instance vm_state ERROR this is the output of glance in conductor, the image is deleted, but nova don't get the deleted status of image. 2014-09-19 11:12:20.534 DEBUG glanceclient.common.http [req-d2aaa493-b507-4f75-a185-c83d347f82b0 admin admin] HTTP/1.1 200 OK content-length: 0 x-image-meta-id: 2a6ce744-b96b-4f71-882e-13c4fc1c9da1 date: Fri, 19 Sep 2014 03:12:20 GMT x-image-meta-deleted: True <<<=== x-image-meta-container_format: ami x-image-meta-checksum: 1b31d2e911494696c6d190ccef2f4d64 x-image-meta-deleted_at: 2014-09-19T02:41:27 x-image-meta-min_disk: 0 x-image-meta-protected: False x-image-meta-created_at: 2014-09-18T04:03:09 x-image-meta-size: 10616832 x-image-meta-status: deleted <<<=== etag: 1b31d2e911494696c6d190ccef2f4d64 x-image-meta-is_public: False x-image-meta-min_ram: 0 x-image-meta-owner: d7beb7f28e0b4f41901215000339361d x-image-meta-updated_at: 2014-09-19T02:41:27 content-type: text/html; charset=UTF-8 x-openstack-request-id: req-e95ddab3-bee5-4847-ba55-13be02bc1a14 x-image-meta-disk_format: ami x-image-meta-name: t2-shelved To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1371406/+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 1372812] [NEW] instance task status keep for long time when reboot
tate | Networks | +--+---+++-+---+ | bb44fafb-7a63-4c93-974f-031a9cceeaa3 | instance0 | ACTIVE | - | Running | private=192.168.1.74, 172.24.4.41 | | 990a03e7-4487-4137-9b51-e8f20986ffcb | t2| REBOOT | reboot_started | Running | private=192.168.1.91 | +--+---+++-+---+ ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: 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/1372812 Title: instance task status keep for long time when reboot Status in OpenStack Compute (Nova): In Progress Bug description: When doing reboot, the task status will be REBOOT_STARTED for long time in some cases, it's better to add this status when polling the rebooting instances and try to trigger reboot again. [tagett@stack-01 devstack]$ nova list +--+---+++-+---+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+---+ | bb44fafb-7a63-4c93-974f-031a9cceeaa3 | instance0 | ACTIVE | - | Running | private=192.168.1.74, 172.24.4.41 | | 990a03e7-4487-4137-9b51-e8f20986ffcb | t2| REBOOT | reboot_started | Running | private=192.168.1.91 | +--+---+++-+---+ [tagett@stack-01 devstack]$ nova reboot t2 ERROR (Conflict): Cannot 'reboot' while instance is in task_state reboot_started (HTTP 409) (Request-ID: req-9006c602-dd74-41ef-b154-2e5e0ed53d65) [tagett@stack-01 devstack]$ date 2014年 09月 23日 星期二 16:11:54 CST [tagett@stack-01 devstack]$ nova list +--+---+++-+---+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+---+ | bb44fafb-7a63-4c93-974f-031a9cceeaa3 | instance0 | ACTIVE | - | Running | private=192.168.1.74, 172.24.4.41 | | 990a03e7-4487-4137-9b51-e8f20986ffcb | t2| REBOOT | reboot_started | Running | private=192.168.1.91 | +--+---+++-+---+ [tagett@stack-01 devstack]$ date 2014年 09月 23日 星期二 16:12:00 CST [tagett@stack-01 devstack]$ nova list +--+---+++-+---+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+---+ | bb44fafb-7a63-4c93-974f-031a9cceeaa3 | instance0 | ACTIVE | - | Running | private=192.168.1.74, 172.24.4.41 | | 990a03e7-4487-4137-9b51-e8f20986ffcb | t2| REBOOT | reboot_started | Running | private=192.168.1.91 | +--+---+++-+---+ [tagett@stack-01 devstack]$ nova list +--+---+++-+---+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+---+ | bb44fafb-7a63-4c93-974f-031a9cceeaa3 | instance0 | ACTIVE | - | Running | private=192.168.1.74, 172.24.4.41 | | 990a03e7-4487-4137-9b51-e8f20986ffcb | t2| REBOOT | reboot_started | Running | private=192.168.1.91 | +--+---+++-+---+ [tagett@stack-01 devstack]$ date 2014年 09月 23日 星期二 16:12:08 CST [tagett
[Yahoo-eng-team] [Bug 1387945] Re: "nova volume-attach" is giving wrong device ID
i'd like to mark this as invalid in nova. if you specify an device name, libvirt will use it as just a hint nova pass this device to libvirt, and libvirt treat is as just a hint. cause it can not know how guest kernel treat it. 2014-11-03 15:10:17.982 DEBUG nova.virt.libvirt.config [req-71da8b06 -befb-40e0-8cb3-7553f62eceef admin admin] Generated XML ('\n \n \n \n 3f629777-ccf5-43fa-92e8-da6bd9d8d282\n\n',) from (pid=2970) to_xml /opt/stack/nova/nova/virt/libvirt/config.py:81 see :http://libvirt.org/formatdomain.html#elementsDisks target The target element controls the bus / device under which the disk is exposed to the guest OS. The dev attribute indicates the "logical" device name. The actual device name specified is not guaranteed to map to the device name in the guest OS. Treat it as a device ordering hint. The optional bus attribute specifies the type of disk device to emulate; possible values are driver specific, with typical values being "ide", "scsi", "virtio", "xen", "usb", "sata", or "sd" "sd" since 1.1.2. If omitted, the bus type is inferred from the style of the device name (e.g. a device named 'sda' will typically be exported using a SCSI bus). The optional attribute tray indicates the tray status of the removable disks (i.e. CDROM or Floppy disk), the value can be either "open" or "closed", defaults to "closed". NB, the value of tray could be updated while the domain is running. The optional attribute removable sets the removable flag for USB disks, and its value can be either "on" or "off", defaulting to "off". Since 0.0.3; bus attribute since 0.4.3; tray attribute since 0.9.11; "usb" attribute value since after 0.4.4; "sata" attribute value since 0.9.7; "removable" attribute value since 1.1.3 ** Changed in: nova Status: New => 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/1387945 Title: "nova volume-attach" is giving wrong device ID Status in Cinder: Invalid Status in OpenStack Compute (Nova): Invalid Bug description: Sometimes while attaching volume to the instance using "nova volume- attach" it is giving wrong device ID (mountpoint : /dev/vdb). root@techpatron:~# nova volume-attach VM1 201b2fe8-7f77-446d-a6e4-5d077914329c +--+--+ | Property | Value| +--+--+ | device | /dev/vdd | | id | 201b2fe8-7f77-446d-a6e4-5d077914329c | | serverId | 2f319155-06d2-4aca-9f0f-49b415112568 | | volumeId | 201b2fe8-7f77-446d-a6e4-5d077914329c | +--+--+ Here it is showing "/dev/vdd", but volume actually attached as "/dev/vdc" to the instance "VM1". Because of this when I am running some automation scripts (which will perform operations on the attached device with in the instance) facing problem. From the output that script taking the device id as "/dev/vdd" but device is attached to some other mount point. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1387945/+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 1389127] [NEW] instance can not recovery from resize status when nova-compute down after resize starting
Public bug reported: reproduce steps: [tagett@stack-01 devstack]$ nova resize test1 4 [tagett@stack-01 devstack]$ nova list +--+---++-+-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---++-+-+--+ | fb326f1c-05cb-4080-a133-2688a1580bdb | spacewalk | ACTIVE | - | Running | | | d7ba639c-d261-4dbe-ae70-3aaefc4de339 | test1 | RESIZE | resize_prep | Running | private=192.168.1.94 | +--+---++-+-+--+ kill nova-compute, then restart it. [tagett@stack-01 devstack]$ nova list +--+---++-+-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---++-+-+--+ | fb326f1c-05cb-4080-a133-2688a1580bdb | spacewalk | ACTIVE | - | Running | | | d7ba639c-d261-4dbe-ae70-3aaefc4de339 | test1 | RESIZE | resize_prep | Running | private=192.168.1.94 | +--+---++-+-+-- [tagett@stack-01 devstack]$ nova list +--+---++-+-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---++-+-+--+ | fb326f1c-05cb-4080-a133-2688a1580bdb | spacewalk | ACTIVE | - | Running | | | d7ba639c-d261-4dbe-ae70-3aaefc4de339 | test1 | RESIZE | resize_prep | Running | private=192.168.1.94 | +--+---++-+-+--+ [tagett@stack-01 devstack]$ nova reboot test1 ERROR (Conflict): Cannot 'reboot' instance d7ba639c-d261-4dbe-ae70-3aaefc4de339 while it is in task_state resize_prep (HTTP 409) (Request-ID: req-7a9f4e54-388a-48b1-b361-4b82496542da) ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) 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/1389127 Title: instance can not recovery from resize status when nova-compute down after resize starting Status in OpenStack Compute (Nova): New Bug description: reproduce steps: [tagett@stack-01 devstack]$ nova resize test1 4 [tagett@stack-01 devstack]$ nova list +--+---++-+-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---++-+-+--+ | fb326f1c-05cb-4080-a133-2688a1580bdb | spacewalk | ACTIVE | - | Running | | | d7ba639c-d261-4dbe-ae70-3aaefc4de339 | test1 | RESIZE | resize_prep | Running | private=192.168.1.94 | +--+---++-+-+--+ kill nova-compute, then restart it. [tagett@stack-01 devstack]$ nova list +--+---++-+-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---++-+-+--+ | fb326f1c-05cb-4080-a133-2688a1580bdb | spacewalk | ACTIVE | - | Running | | | d7ba639c-d261-4dbe-ae70-3aaefc4de339 | test1 | RESIZE | resize_prep | Running | private=192.168.1.94 | +--+---++-+-+-- [tagett@stack-01 devstack]$ nova list +--+---++-+-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---++-+-+--+ | fb326f1c-05cb-4080-a133-2688a1580bdb | spacewal
[Yahoo-eng-team] [Bug 1389094] Re: Can not get instance's detail info by server-name
I don't think this is a bug, you can not get the detail information of an instance if the status is in ERROR status. ** Changed in: nova Status: New => 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/1389094 Title: Can not get instance's detail info by server-name Status in OpenStack Compute (Nova): Invalid Bug description: use 2014.2. RDO build. Launch one instance. But it got a error. Detail info can not be got by server-name. [root@compute_1_basefunc ~]# nova list --all-tenants +--+-+++-+--+ | ID | Name| Status | Task State | Power State | Networks | +--+-+++-+--+ | 290455f3-ca69-46ed-97f3-20087b66646a | vm-test | ERROR | - | NOSTATE | demo-net=192.168.1.2 | +--+-+++-+--+ [root@compute_1_basefunc ~]# nova --debug show vm-test REQ: curl -i 'http://controller:35357/v2.0/tokens' -X POST -H "Accept: application/json" -H "Content-Type: application/json" -H "User-Agent: python-novaclient" -d '{"auth": {"tenantName": "admin", "passwordCredentials": {"username": "admin", "password": "{SHA1}d033e22ae348aeb5660fc2140aec35850c4da997"}}}' INFO (connectionpool:187) Starting new HTTP connection (1): controller DEBUG (connectionpool:357) "POST /v2.0/tokens HTTP/1.1" 200 1768 RESP: [200] {'date': 'Tue, 04 Nov 2014 03:58:20 GMT', 'content-type': 'application/json', 'content-length': '1768', 'vary': 'X-Auth-Token'} RESP BODY: {"access": {"token": {"issued_at": "2014-11-04T03:58:20.525598", "expires": "2014-11-04T04:58:20Z", "id": "{SHA1}02535f90545a4ba33e8a2ef492de345dd6341f40", "tenant": {"enabled": true, "description": "Admin Tenant", "name": "admin", "id": "5a4fbbd028994aaba30a6039dbcbca1b"}, "audit_ids": ["tLtROYguTmqA7uxU0IfaaA"]}, "serviceCatalog": [{"endpoints_links": [], "endpoints": [{"adminURL": "http://controller:9292";, "region": "regionOne", "publicURL": "http://controller:9292";, "internalURL": "http://controller:9292";, "id": "72379ef6c74c4113af91a32e0a7d5222"}], "type": "image", "name": "glance"}, {"endpoints_links": [], "endpoints": [{"adminURL": "http://controller:8774/v2/5a4fbbd028994aaba30a6039dbcbca1b";, "region": "regionOne", "publicURL": "http://controller:8774/v2/5a4fbbd028994aaba30a6039dbcbca1b";, "internalURL": "http://controller:8774/v2/5a4fbbd028994aaba30a6039dbcbca1b";, "id": "ab7072f893794c9eb5e54dc99c43d682"}], "type": "compute", "name": "nova"}, {"endpoints_links": [ ], "endpoints": [{"adminURL": "http://controller:9696";, "region": "regionOne", "publicURL": "http://controller:9696";, "internalURL": "http://controller:9696";, "id": "52dee6859db84ff598f5d11f945f65db"}], "type": "network", "name": "neutron"}, {"endpoints_links": [], "endpoints": [{"adminURL": "http://controller:35357/v2.0";, "region": "regionOne", "publicURL": "http://controller:5000/v2.0";, "internalURL": "http://controller:5000/v2.0";, "id": "24a7bc3364fa482c9170cdbf06b683ba"}], "type": "identity", "name": "keystone"}], "user": {"username": "admin", "roles_links": [], "id": "ff19b28fa8f84660824942748105fe4d", "roles": [{"name": "_member_"}, {"name": "admin"}], "name": "admin"}, "metadata": {"is_admin": 0, "roles": ["158058dbe2c84403b544f563a4545c11", "8b8cf97a08fb4b4b90682900f52c1595"]}}} REQ: curl -i 'http://controller:8774/v2/5a4fbbd028994aaba30a6039dbcbca1b/servers?name=vm-test' -X GET -H "Accept: application/json" -H "User-Agent: python-novaclient" -H "X-Auth-Project-Id: admin" -H "X-Auth-Token: {SHA1}02535f90545a4ba33e8a2ef492de345dd6341f40" INFO (connectionpool:187) Starting new HTTP connection (1): controller DEBUG (connectionpool:357) "GET /v2/5a4fbbd028994aaba30a6039dbcbca1b/servers?name=vm-test HTTP/1.1" 200 15 RESP: [200] {'date': 'Tue, 04 Nov 2014 03:58:20 GMT', 'content-length': '15', 'content-type': 'application/json', 'x-compute-request-id': 'req-ce7df0d9-fd76-4fc8-bc31-5bd30bb75f53'} RESP BODY: {"servers": []} REQ: curl -i 'http://controller:8774/v2/5a4fbbd028994aaba30a6039dbcbca1b/servers?name=vm-test' -X GET -H "Accept: application/json" -H "User-Agent: python-novaclient" -H "X-Auth-Project-Id: admin" -H "X-Auth-Token: {SHA1}02535f90545a4ba33e8a2ef492de345dd6341f40" INFO (connectionpool:187) Starting new HTTP connection (1): controller DEBUG (connectionpool:357) "GET /v2/5a4fbbd028994aaba30a6039dbcbca1b/servers?name=vm-test HTTP/1.1" 200 15 RESP: [200] {'date': 'Tue, 04 Nov 2014 03:58:20 GMT', 'content-length': '15', 'content-type': 'application/json', 'x-compute-request-id': 'req-f899b52f-a13a-4b60-9d45-8d155
[Yahoo-eng-team] [Bug 1390380] Re: 'ascii' codec can't decode when create a instance
** Also affects: oslo.i18n 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/1390380 Title: 'ascii' codec can't decode when create a instance Status in OpenStack Compute (Nova): New Status in Oslo Internationalization Library: New Bug description: when creating a new instance given the instance as a Chinese name. nova compute failed to create with error message 2014-11-07 16:49:58.105 TRACE nova.compute.manager [instance: 57557a92-9331-4608-a3bf-324c2dd7f2ec] % domain.XMLDesc(0) 2014-11-07 16:49:58.105 TRACE nova.compute.manager [instance: 57557a92-9331-4608-a3bf-324c2dd7f2ec] UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6 in position 251: ordinal not in range(128) we need to restrict it from nova-api layer or, we need to handle this in libvirt driver domain xml is below: 2014-11-07 16:49:58.104 ERROR nova.virt.libvirt.driver [-] Error defining a domain with XML: 57557a92-9331-4608-a3bf-324c2dd7f2ec instance-02a1 65536 1 http://openstack.org/xmlns/libvirt/nova/1.0";> 测试 --- '测试' 2014-11-07 08:49:56 64 0 0 0 1 admin admin OpenStack Foundation OpenStack Nova 2014.2 24cbc683-3b5c-4b3a-be40-5661739c9352 57557a92-9331-4608-a3bf-324c2dd7f2ec To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1390380/+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 1390380] Re: 'ascii' codec can't decode when create a instance
a fix found commit 60c90f73261efb8c73ecc02152307c81265cab13 Author: Rick Harris Date: Tue Jun 24 14:03:17 2014 -0500 libvirt+lxc: Unmount guest FS from host on error If an error occurs during `_create_domain`, we need to ensure that the guest's FS is unmounted from the host in all cases. This is necessary because, if we leave the FS mounted to the host, the `lvremove` triggered by `delete` won't work because the filesystem will 'still be in use'. The solution is to wrap the code in a `try/finally` to ensure the cleanup routines (which unmount) are always called. Change-Id: If863cf813dddc1e4554fb87b945c68b75b25f9a2 Closes-Bug: 1333827 ** Changed in: nova Status: New => Invalid ** Changed in: oslo.i18n Status: New => 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/1390380 Title: 'ascii' codec can't decode when create a instance Status in OpenStack Compute (Nova): Invalid Status in Oslo Internationalization Library: Invalid Bug description: when creating a new instance given the instance as a Chinese name. nova compute failed to create with error message 2014-11-07 16:49:58.105 TRACE nova.compute.manager [instance: 57557a92-9331-4608-a3bf-324c2dd7f2ec] % domain.XMLDesc(0) 2014-11-07 16:49:58.105 TRACE nova.compute.manager [instance: 57557a92-9331-4608-a3bf-324c2dd7f2ec] UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6 in position 251: ordinal not in range(128) we need to restrict it from nova-api layer or, we need to handle this in libvirt driver domain xml is below: 2014-11-07 16:49:58.104 ERROR nova.virt.libvirt.driver [-] Error defining a domain with XML: 57557a92-9331-4608-a3bf-324c2dd7f2ec instance-02a1 65536 1 http://openstack.org/xmlns/libvirt/nova/1.0";> 测试 --- '测试' 2014-11-07 08:49:56 64 0 0 0 1 admin admin OpenStack Foundation OpenStack Nova 2014.2 24cbc683-3b5c-4b3a-be40-5661739c9352 57557a92-9331-4608-a3bf-324c2dd7f2ec To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1390380/+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 1530010] [NEW] Rescued instance failed to boot from cirros image
Public bug reported: Steps: 1 boot a centos instance 2 nova rescue centos --image=cirros 3 check centos instance status "no bootable instance" Root cause is: $ glance image-show ccefc63d-6eb7-486e-b3a2-e63f09fb9e5d +--+--+ | Property | Value| +--+--+ | checksum | eb9139e4942121f22bbc2afc0400b2a4 | | container_format | ami | | created_at | 2015-11-23T11:38:12Z | | disk_format | ami | | id | ccefc63d-6eb7-486e-b3a2-e63f09fb9e5d | | kernel_id| e6eb027f-55a5-465e-9fce-5ebdb3d13d0a | <<<<<<< | min_disk | 0| | min_ram | 0| | name | cirros-0.3.4-x86_64-uec | | owner| e62253640b9c478f9c15c97e6ca40cb4 | | protected| False| | ramdisk_id | 6425cc10-eaff-4f35-bd6e-941a3b439878 | <<<<<<< | size | 25165824 | | status | active | | tags | [] | | updated_at | 2015-11-23T11:38:13Z | | virtual_size | None | | visibility | public | +--+--+ cirros image needs to boot from kernel file and initrd file. I debuged the rescue process, image_meta = {'status': u'active', 'name': u'cirros-0.3.4-x86_64-uec', 'deleted': False, 'container_format': u'ami', 'created_at': datetime.datetime(2015, 11, 23, 11, 38, 12, tzinfo=), 'disk_format': u'ami', 'updated_at': datetime.datetime(2015, 11, 23, 11, 38, 13, tzinfo=), 'id': u'ccefc63d-6eb7-486e-b3a2-e63f09fb9e5d', 'owner': u'e62253640b9c478f9c15c97e6ca40cb4', 'min_ram': 0, 'checksum': u'eb9139e4942121f22bbc2afc0400b2a4', 'min_disk': 0, 'is_public': True, 'deleted_at': None, 'properties': {u'kernel_id': u'e6eb027f-55a5-465e-9fce-5ebdb3d13d0a', u'ramdisk_id': u'6425cc10-eaff-4f35-bd6e-941a3b439878'}, 'size': 25165824} But check libvirt driver, we don't populate kernel_id and ramdisk_id from image_meta. rescue_image_id = None if image_meta is not None: image_meta = objects.ImageMeta.from_dict(image_meta) if image_meta.obj_attr_is_set("id"): rescue_image_id = image_meta.id To fix it, grab kernel_id and ramdisk_id from image_meta ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1530010 Title: Rescued instance failed to boot from cirros image Status in OpenStack Compute (nova): New Bug description: Steps: 1 boot a centos instance 2 nova rescue centos --image=cirros 3 check centos instance status "no bootable instance" Root cause is: $ glance image-show ccefc63d-6eb7-486e-b3a2-e63f09fb9e5d +--+--+ | Property | Value| +--+--+ | checksum | eb9139e4942121f22bbc2afc0400b2a4 | | container_format | ami | | created_at | 2015-11-23T11:38:12Z | | disk_format | ami | | id | ccefc63d-6eb7-486e-b3a2-e63f09fb9e5d | | kernel_id| e6eb027f-55a5-465e-9fce-5ebdb3d13d0a | <<<<<<< | min_disk | 0| | min_ram | 0| | name | cirros-0.3.4-x86_64-uec | | owner| e62253640b9c478f9c15c97e6ca40cb4 | | protected| False| | ramdisk_id | 6425cc10-eaff-4f35-bd6e-941a3b439878 | <<<<<<< | size | 25165824 | | status | active | | tags | [] | | updated_at | 2015-11-23T11:38:13Z | | virtual_size | None | |
[Yahoo-eng-team] [Bug 1531473] [NEW] Move graphics and serial console check to can_live_migrate_source/dest
Public bug reported: _check_graphics_addresses_can_live_migrate(listen_addrs) and _verify_serial_console_is_disabled() should be move to can_live_migrate_source/dest method to reduce extra operations of pre_live_migration and roll_back calling. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: live-migration ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Tags added: live-migration -- 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/1531473 Title: Move graphics and serial console check to can_live_migrate_source/dest Status in OpenStack Compute (nova): New Bug description: _check_graphics_addresses_can_live_migrate(listen_addrs) and _verify_serial_console_is_disabled() should be move to can_live_migrate_source/dest method to reduce extra operations of pre_live_migration and roll_back calling. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1531473/+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 1527061] Re: Nova should not throw exception when port binding fails for Ironic
hi Johnson, actually, I don't know well about VMware VCDriver, and have no idea no whey Neutron return a port with {'binding:vif_type': binding_failed} , in case this happened, nova should though it as a bad port and is not usable. I personal suggest that we connect Neutron team to take care about this. Eli. ** Project changed: nova => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1527061 Title: Nova should not throw exception when port binding fails for Ironic Status in neutron: Confirmed Bug description: Neutron tries to bind port on compute where instance is launched. It doesn't make sense when hypervisor_type is ironic, since VM does not live on hypervisor in this case. Furthermore it leads to failed provisioning of baremetal node, when neutron is not configured on ironic compute node. When binding fails, nova starts cleanup and then throws exception. As part of cleanup ironic port is deleted. This should not be the case when virt-driver being used is Ironic. Nova versions: liberty on-wards. Setup: node-1: controller with neutron node-2: ironic-compute without neutron/neutron agents Register a BM node and perform nova boot. From Nova: = nova-compute.log:21147:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s) nova-compute.log:21148:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager Traceback (most recent call last): nova-compute.log:21149:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager File "/opt/stack/venv/nova-20151204T044743Z/lib/python2.7/site-packages/nova/compute/manager.py", line 1564, in _allocate_network_async nova-compute.log:21150:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager dhcp_options=dhcp_options) nova-compute.log:21151:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager File "/opt/stack/venv/nova-20151204T044743Z/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 727, in allocate_for_instance nova-compute.log:21152:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager self._delete_ports(neutron, instance, created_port_ids) nova-compute.log:21153:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager File "/opt/stack/venv/nova-20151204T044743Z/lib/python2.7/site-packages/oslo_utils/excutils.py", line 204, in __exit__ nova-compute.log:21154:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager six.reraise(self.type_, self.value, self.tb) nova-compute.log:21155:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager File "/opt/stack/venv/nova-20151204T044743Z/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 719, in allocate_for_instance nova-compute.log:21156:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager security_group_ids, available_macs, dhcp_opts) nova-compute.log:21157:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager File "/opt/stack/venv/nova-20151204T044743Z/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 342, in _create_port nova-compute.log:21158:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager raise exception.PortBindingFailed(port_id=port_id) nova-compute.log:21159:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager PortBindingFailed: Binding failed for port 0514b7e8-0408-4d5e-9b48-8292e686494f, please check neutron logs for more information. nova-compute.log:21160:2015-12-05 02:57:38.542 7649 ERROR nova.compute.manager 2015-12-05 02:57:43.375 7649 DEBUG nova.virt.ironic.driver [req-25ba4c81-4333-43e4-b8d9-e460827435e0 a989fe7fc89e4825b98d7e6584cc 1308f1a382ef43c79eeed0ebf8a9db3b] unplug: instance_uuid=d9295d4d-1104-47ab-8e75-5b30d0a3838b vif=[] _unp 2015-12-05 02:57:43.376 7649 ERROR nova.compute.manager [req-25ba4c81-4333-43e4-b8d9-e460827435e0 a989fe7fc89e4825b98d7e6584cc 1308f1a382ef43c79eeed0ebf8a9db3b] [instance: d9295d4d-1104-47ab-8e75-5b30d0a3838b] Instance failed to spawn 2015-12-05 02:57:43.376 7649 ERROR nova.compute.manager [instance: d9295d4d-1104-47ab-8e75-5b30d0a3838b] Traceback (most recent call last): 2015-12-05 02:57:43.376 7649 ERROR nova.compute.manager [instance: d9295d4d-1104-47ab-8e75-5b30d0a3838b] File "/opt/stack/venv/nova-20151204T044743Z/lib/python2.7/site-packages/nova/compute/manager.py", line 2157, in _build_resources 2015-12-05 02:57:43.376 7649 ERROR nova.compute.manager [instance: d9295d4d-1104-47ab-8e75-5b30d0a3838b] yield resources 2015-12-05 02:57:43.376 7649 ERROR nova.compute.manager [instance: d9295d4d-1104-47ab-8e75-5b30d0a3838b] File "/opt/stack/venv/nova-20151204T044743Z/lib/python2.7/site-packages/nova/compute/manager.py", line 2011, in _build_and_run_inst 2015-12-05 02:57:43.376 7649 ERROR nova.compute.manager [instance: d9295d
[Yahoo-eng-team] [Bug 1536513] [NEW] os-getConsoleOutput fail with 500
Public bug reported: 2016-01-21 07:12:24.667 DEBUG nova.api.openstack.wsgi [req-62cccfc1-478e-415b-8f12-51637bfd78e7 tempest-ServerActionsTestJSON-1139043036 tempest-ServerActionsTestJSON-2088121350] Action: 'action', calling method: >, body: {"os-getConsoleOutput": {}} _process_stack /opt/stack/new/nova/nova/api/openstack/wsgi.py:806 2016-01-21 07:12:24.668 DEBUG nova.compute.api [req-62cccfc1-478e-415b-8f12-51637bfd78e7 tempest-ServerActionsTestJSON-1139043036 tempest-ServerActionsTestJSON-2088121350] [instance: c2294c61-b6cf-4ffa-8e87-d382e0205235] Fetching instance by UUID get /opt/stack/new/nova/nova/compute/api.py:1945 2016-01-21 07:12:24.853 ERROR nova.api.openstack.extensions [req-62cccfc1-478e-415b-8f12-51637bfd78e7 tempest-ServerActionsTestJSON-1139043036 tempest-ServerActionsTestJSON-2088121350] Unexpected exception in API method 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/opt/stack/new/nova/nova/api/openstack/extensions.py", line 478, in wrapped 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 73, in wrapper 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/opt/stack/new/nova/nova/api/openstack/compute/console_output.py", line 54, in get_console_output 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions length) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/opt/stack/new/nova/nova/compute/api.py", line 171, in wrapped 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions return func(self, context, target, *args, **kwargs) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/opt/stack/new/nova/nova/compute/api.py", line 151, in wrapped 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions return function(self, context, instance, *args, **kwargs) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/opt/stack/new/nova/nova/compute/api.py", line 2917, in get_console_output 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions instance=instance, tail_length=tail_length) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/opt/stack/new/nova/nova/compute/rpcapi.py", line 498, in get_console_output 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions instance=instance, tail_length=tail_length) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/client.py", line 158, in call 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions retry=self.retry) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/transport.py", line 90, in _send 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions timeout=timeout, retry=retry) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 464, in send 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions retry=retry) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 455, in _send 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions raise result 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions NovaException_Remote: Guest does not have a console available 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 143, in _dispatch_and_reply 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions executor_callback)) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 189, in _dispatch 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions executor_callback) 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions 2016-01-21 07:12:24.853 12292 ERROR nova.api.openstack.extensions File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 130, in _do_dispatch 2016-01-21 07:12:24.853 12292 ERROR nova.api
[Yahoo-eng-team] [Bug 1537629] [NEW] No HTTPBadRequest(400) error will be raised from get_console_output.
Public bug reported: No HTTPBadRequest(400) error will be raised from get_console_output. @extensions.expected_errors((400, 404, 409, 501)) @wsgi.action('os-getConsoleOutput') @validation.schema(console_output.get_console_output) def get_console_output(self, req, id, body): extensions.expected_errors should contain all errors which would be raised from the function which is decorated, but there is no 400 error come out from the body of get_console_output() ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1537629 Title: No HTTPBadRequest(400) error will be raised from get_console_output. Status in OpenStack Compute (nova): In Progress Bug description: No HTTPBadRequest(400) error will be raised from get_console_output. @extensions.expected_errors((400, 404, 409, 501)) @wsgi.action('os-getConsoleOutput') @validation.schema(console_output.get_console_output) def get_console_output(self, req, id, body): extensions.expected_errors should contain all errors which would be raised from the function which is decorated, but there is no 400 error come out from the body of get_console_output() To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1537629/+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 1538381] [NEW] nova backup allows any sting of bake_type
Public bug reported: taget@taget-ThinkStation-P300:~/devstack$ nova help backup usage: nova backup Backup a server by creating a 'backup' type snapshot. Positional arguments: Name or ID of server. Name of the backup image. The backup type, like "daily" or "weekly". Int parameter representing how many backups to keep around. But we can create a backup by nova backup cent_from_snap cent_from_sna_bak weeklydd 2 follow schema need to be improved. create_backup = { 'type': 'object', 'properties': { 'createBackup': { 'type': 'object', 'properties': { 'name': parameter_types.name, 'backup_type': { 'type': 'string', }, 'rotation': parameter_types.non_negative_integer, 'metadata': { 'type': 'object', } }, 'required': ['name', 'backup_type', 'rotation'], 'additionalProperties': False, }, }, 'required': ['createBackup'], 'additionalProperties': False, } ** Affects: nova Importance: Low Assignee: Eli Qiao (taget-9) Status: Confirmed ** Tags: api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Changed in: nova Importance: Undecided => Low ** Changed in: nova Status: New => Confirmed ** Tags added: api -- 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/1538381 Title: nova backup allows any sting of bake_type Status in OpenStack Compute (nova): Confirmed Bug description: taget@taget-ThinkStation-P300:~/devstack$ nova help backup usage: nova backup Backup a server by creating a 'backup' type snapshot. Positional arguments: Name or ID of server. Name of the backup image. The backup type, like "daily" or "weekly". Int parameter representing how many backups to keep around. But we can create a backup by nova backup cent_from_snap cent_from_sna_bak weeklydd 2 follow schema need to be improved. create_backup = { 'type': 'object', 'properties': { 'createBackup': { 'type': 'object', 'properties': { 'name': parameter_types.name, 'backup_type': { 'type': 'string', }, 'rotation': parameter_types.non_negative_integer, 'metadata': { 'type': 'object', } }, 'required': ['name', 'backup_type', 'rotation'], 'additionalProperties': False, }, }, 'required': ['createBackup'], 'additionalProperties': False, } To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1538381/+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 1538411] [NEW] exception.AutoDiskConfigDisabledByImage is expected 2 times in _resize
Public bug reported: exception.AutoDiskConfigDisabledByImage is expected 2 times in _resize Please check: https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L912 and https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L928 ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Tags added: api -- 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/1538411 Title: exception.AutoDiskConfigDisabledByImage is expected 2 times in _resize Status in OpenStack Compute (nova): New Bug description: exception.AutoDiskConfigDisabledByImage is expected 2 times in _resize Please check: https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L912 and https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L928 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1538411/+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 1538448] [NEW] REST api layer doesn't handle TooManyInstances while doing resize
Public bug reported: compute_api may raise TooManyInstances if over quota, but no handler in REST Api layer. ** Affects: nova Importance: Low Assignee: Eli Qiao (taget-9) Status: Confirmed ** Tags: api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Changed in: nova Importance: Undecided => Low ** Changed in: nova Status: New => Confirmed ** Tags added: api -- 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/1538448 Title: REST api layer doesn't handle TooManyInstances while doing resize Status in OpenStack Compute (nova): Confirmed Bug description: compute_api may raise TooManyInstances if over quota, but no handler in REST Api layer. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1538448/+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 1484992] Re: Converting image from qcow2 to raw is slow for images with large virtual size
This is already fixed by this commit I2c3df909a783e1480d3ab4ca10b34b84ac9e4b5f ** Changed in: nova Status: In Progress => Won't Fix -- 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/1484992 Title: Converting image from qcow2 to raw is slow for images with large virtual size Status in OpenStack Compute (nova): Won't Fix Bug description: In this thread: http://lists.openstack.org/pipermail/openstack/2015-August/013614.html [qote] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf qemu-img convert -O raw /var/lib/nova/instances/_base/999f7fff2521e4a7243c9e1d21599fd64a19b42e /dev/openstack-controller01-ky01-vg/5f831046-435c-4636-8b71-a662327b608c_disk Well, I understand what this step is doing - it's copying raw image to lvm. How can we speed it up? I don't wanna have instance from 100GB image booted for 4 hours [/quote] Regardless of how much data is in the source file, qemu-img has to write out the full virtual size on the target block dev to ensure any pre-existing data is overwritten. THis may involve writing 100's of GB of zeros for large images. qemu-img does has an optimization to let it use 'discard' as a fast alternative to writing zeros, but this requires that qemu-img has disk caching disabled , eg -t none. We should investigate to see if this improves performance for converting large images to block devices, and if so, enable this flag. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1484992/+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 1593526] Re: compute host reports wrong cpu topology
As from my environment also I dig into libvirt source code, it requires to install numactl and libnuma to let libvirt know the topology of host. Installed numactl and libnuma, libvirt will report correct topology numa of host. so we can close as this is not a valid bug. Eli. ** Changed in: nova Status: In Progress => 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/1593526 Title: compute host reports wrong cpu topology Status in OpenStack Compute (nova): Invalid Bug description: This is my host's cpu: ubuntu@jfz1r04h06:~$ lscpu Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):72 On-line CPU(s) list: 0-71 Thread(s) per core:2 Core(s) per socket:18 Socket(s): 2 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:6 Model: 63 Model name:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz Stepping: 2 CPU MHz: 1209.386 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS: 4590.93 Virtualization:VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 46080K NUMA node0 CPU(s): 0-71 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc dtherm ida arat pln pts Seen from nova-scheduler. Update host state from compute node: ComputeNode(cpu_allocation_ratio=16.0,cpu_info='{"vendor": "Intel", "model": "Haswell-noTSX", "arch": "x86_64", "features": ["pge", "avx", "xsaveopt", "clflush", "sep", "syscall", "tsc_adjust", "vme", "dtes64", "invpcid", "msr", "sse", "xsave", "vmx", "erms", "xtpr", "cmov", "smep", "nx", "est", "pat", "monitor", "smx", "pbe", "lm", "tsc", "fpu", "fxsr", "tm", "sse4.1", "pae", "sse4.2", "pclmuldq", "pcid", "fma", "tsc-deadline", "mmx", "osxsave", "cx8", "mce", "de", "tm2", "ht", "dca", "pni", "abm", "popcnt", "mca", "pdpe1gb", "apic", "fsgsbase", "f16c", "pse", "ds", "invtsc", "lahf_lm", "aes", "avx2", "sse2", "ss", "ds_cpl", "arat", "bmi1", "bmi2", "acpi", "ssse3", "rdtscp", "cx16", "pse36", "mtrr", "movbe", "pdcm", "rdrand", "x2apic"], "topology": {"cores": 18, "cells": 1, "threads": 2, "sockets": 1}}' Expected result === "topology": {"cores": 18, "cells": 1, "threads": 2, "sockets": 2}}' <<-- Actual result = "topology": {"cores": 18, "cells": 1, "threads": 2, "sockets": 1}}' This is most likely libvirt bug, reported here : https://bugzilla.redhat.com/show_bug.cgi?id=1347458 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1593526/+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 1636688] [NEW] 500 error while create instance with numa flavor setting
16-10-26 11:53:01.735 TRACE nova.api.openstack.extensions return func(*args, **kwargs) │·2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/api/validation/__init__.py", line 73, in wrapper │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions return func(*args, **kwargs) │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/api/validation/__init__.py", line 73, in wrapper │·2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions return func(*args, **kwargs) │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/api/validation/__init__.py", line 73, in wrapper │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions return func(*args, **kwargs) │·2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/api/validation/__init__.py", line 73, in wrapper │·2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions return func(*args, **kwargs) │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/api/openstack/compute/servers.py", line 631, in create │·2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions **create_kwargs) │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/hooks.py", line 154, in inner │·2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions rv = f(*args, **kwargs) │·2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/compute/api.py", line 1525, in create │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions check_server_group_quota=check_server_group_quota) │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/compute/api.py", line 1127, in _create_instance │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions reservation_id, max_count) │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/compute/api.py", line 850, in _validate_and_build_base_options │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions instance_type, image_meta) │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/virt/hardware.py", line 1236, in numa_get_constraints │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions return _add_cpu_pinning_constraint(flavor, image_meta, numa_topology) │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions File "/opt/stack/nova/nova/virt/hardware.py", line 1155, in _add_cpu_pinning_constraint│· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions raise exception.CPUThreadPolicyConfigurationInvalid() │· 2016-10-26 11:53:01.735 TRACE nova.api.openstack.extensions CPUThreadPolicyConfigurationInvalid: Cannot set cpu thread pinning policy in a non dedicated cpu pinning policy ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1636688 Title: 500 error while create instance with numa flavor setting Status in OpenStack Compute (nova): New Bug description: stack@s2600wt:~/devstack$ openstack flavor create --vcpus 6 --ram 6144 --disk 40 --p
[Yahoo-eng-team] [Bug 1620445] [NEW] Correct Correct PERF_EVENTS_CPU_FLAG_MAPPING due to libvirt changes
Public bug reported: Libvirt 2.0.0 has merge cpu_map.xml: add cmt/mbm feature to x86 (Qiaowei Ren), but the capabilities are: Need to adopt this in nova code. ** Affects: nova Importance: Medium Assignee: Eli Qiao (taget-9) Status: Confirmed ** Changed in: nova Status: New => Confirmed ** Changed in: nova Importance: Undecided => Medium ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1620445 Title: Correct Correct PERF_EVENTS_CPU_FLAG_MAPPING due to libvirt changes Status in OpenStack Compute (nova): Confirmed Bug description: Libvirt 2.0.0 has merge cpu_map.xml: add cmt/mbm feature to x86 (Qiaowei Ren), but the capabilities are: Need to adopt this in nova code. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1620445/+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 1587780] [NEW] power_state of nova diagnostics is number instead of string
Public bug reported: taget@taget-ThinkStation-P300:~/devstack$ nova diagnostics 87c91515-acc7-4953-b0a3-f942484e986e ERROR (Conflict): Cannot 'get_diagnostics' instance 87c91515-acc7-4953-b0a3-f942484e986e while it is in power_state 4 (HTTP 409) (Request-ID: req-caaf21fc-fa11-4382-9f87-c23928b46eb1) We need to map instance.power_state to string by STATE_MAP = { NOSTATE: 'pending', RUNNING: 'running', PAUSED: 'paused', SHUTDOWN: 'shutdown', CRASHED: 'crashed', SUSPENDED: 'suspended', } ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Tags added: api -- 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/1587780 Title: power_state of nova diagnostics is number instead of string Status in OpenStack Compute (nova): New Bug description: taget@taget-ThinkStation-P300:~/devstack$ nova diagnostics 87c91515-acc7-4953-b0a3-f942484e986e ERROR (Conflict): Cannot 'get_diagnostics' instance 87c91515-acc7-4953-b0a3-f942484e986e while it is in power_state 4 (HTTP 409) (Request-ID: req-caaf21fc-fa11-4382-9f87-c23928b46eb1) We need to map instance.power_state to string by STATE_MAP = { NOSTATE: 'pending', RUNNING: 'running', PAUSED: 'paused', SHUTDOWN: 'shutdown', CRASHED: 'crashed', SUSPENDED: 'suspended', } To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1587780/+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 1593526] [NEW] compute host reports wrong cpu topology
Public bug reported: This is my host's cpu: ubuntu@jfz1r04h06:~$ lscpu Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):72 On-line CPU(s) list: 0-71 Thread(s) per core:2 Core(s) per socket:18 Socket(s): 2 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:6 Model: 63 Model name:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz Stepping: 2 CPU MHz: 1209.386 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS: 4590.93 Virtualization:VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 46080K NUMA node0 CPU(s): 0-71 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc dtherm ida arat pln pts Seen from nova-scheduler. Update host state from compute node: ComputeNode(cpu_allocation_ratio=16.0,cpu_info='{"vendor": "Intel", "model": "Haswell-noTSX", "arch": "x86_64", "features": ["pge", "avx", "xsaveopt", "clflush", "sep", "syscall", "tsc_adjust", "vme", "dtes64", "invpcid", "msr", "sse", "xsave", "vmx", "erms", "xtpr", "cmov", "smep", "nx", "est", "pat", "monitor", "smx", "pbe", "lm", "tsc", "fpu", "fxsr", "tm", "sse4.1", "pae", "sse4.2", "pclmuldq", "pcid", "fma", "tsc- deadline", "mmx", "osxsave", "cx8", "mce", "de", "tm2", "ht", "dca", "pni", "abm", "popcnt", "mca", "pdpe1gb", "apic", "fsgsbase", "f16c", "pse", "ds", "invtsc", "lahf_lm", "aes", "avx2", "sse2", "ss", "ds_cpl", "arat", "bmi1", "bmi2", "acpi", "ssse3", "rdtscp", "cx16", "pse36", "mtrr", "movbe", "pdcm", "rdrand", "x2apic"], "topology": {"cores": 18, "cells": 1, "threads": 2, "sockets": 1}}' Expected result === "topology": {"cores": 18, "cells": 1, "threads": 2, "sockets": 2}}' <<-- Actual result = "topology": {"cores": 18, "cells": 1, "threads": 2, "sockets": 1}}' This is most likely libvirt bug, reported here : https://bugzilla.redhat.com/show_bug.cgi?id=1347458 ** Affects: nova Importance: High Assignee: Eli Qiao (taget-9) Status: New ** Tags: libvirt ** Tags added: libvirt ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Changed in: nova Importance: Undecided => High ** Description changed: This is my host's cpu: ubuntu@jfz1r04h06:~$ lscpu Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):72 On-line CPU(s) list: 0-71 Thread(s) per core:2 Core(s) per socket:18 Socket(s): 2 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:6 Model: 63 Model name:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz Stepping: 2 CPU MHz: 1209.386 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS: 4590.93 Virtualization:VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 46080K NUMA node0 CPU(s): 0-71 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmp
[Yahoo-eng-team] [Bug 1597963] [NEW] cleanup never used migratable flag checking
Public bug reported: On commit gerrit id Ib73cfbd9fc01114ac513730d182ed127710a9e5d , we changed MIN_LIBVIRT_VERSION=1.2.1, which has VIR_DOMAIN_XML_MIGRATABLE always, so we don't need to check it anymore. ** Affects: nova Importance: Wishlist Assignee: Eli Qiao (taget-9) Status: Confirmed ** Tags: libvirt live-migration ** Changed in: nova Status: New => Confirmed ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Changed in: nova Importance: Undecided => Low ** Changed in: nova Importance: Low => Wishlist ** Summary changed: - Cleanup cleanup never used migratable flag checking + cleanup never used migratable flag checking ** Tags added: libvirt ** Tags added: live-migration -- 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/1597963 Title: cleanup never used migratable flag checking Status in OpenStack Compute (nova): Confirmed Bug description: On commit gerrit id Ib73cfbd9fc01114ac513730d182ed127710a9e5d , we changed MIN_LIBVIRT_VERSION=1.2.1, which has VIR_DOMAIN_XML_MIGRATABLE always, so we don't need to check it anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1597963/+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 1599377] [NEW] nova should raise http 409 instead of 500 when get a error instance diagnostics
Public bug reported: When retrieving server diagnostics, nova should raise 409 instead of 500 in case the instance has no host yet. ** Affects: nova Importance: Low Assignee: Eli Qiao (taget-9) Status: In Progress ** Tags: api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Changed in: nova Importance: Undecided => Low -- 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/1599377 Title: nova should raise http 409 instead of 500 when get a error instance diagnostics Status in OpenStack Compute (nova): In Progress Bug description: When retrieving server diagnostics, nova should raise 409 instead of 500 in case the instance has no host yet. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1599377/+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 1550282] [NEW] Remove exception.LiveMigrationWithOldNovaNotSafe
Public bug reported: This exception LiveMigrationWithOldNovaNotSafe won't used any where, we can clean up it for now. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Tags added: api -- 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/1550282 Title: Remove exception.LiveMigrationWithOldNovaNotSafe Status in OpenStack Compute (nova): New Bug description: This exception LiveMigrationWithOldNovaNotSafe won't used any where, we can clean up it for now. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1550282/+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 1551104] [NEW] get-XXX-console returns 500 while an expected exception ConsoleTypeInvalid raised
Public bug reported: 1. Exact version of Nova/OpenStack you are running: Master 791e5421cdc2130ed80e067e43b6006a6859138b 2. Relevant log files: taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console testvm ee ERROR (BadRequest): Invalid input for field/attribute type. Value: ee. u'ee' is not one of ['novnc', 'xvpvnc', 'rdp-html5', 'spice-html5', 'serial', 'webmks'] (HTTP 400) (Request-ID: req-8bd1cada-caf4-4c9f-afa3-1afe7655472d) taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console testvm xvpvnc ++--+ | Type | Url | ++--+ | xvpvnc | http://10.238.157.49:6081/console?token=a7275c37-7397-414a-ba3f-1da4a03d2115 | ++--+ taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console testvm rdp-html5 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-dfd46bc0-fa46-41ea-adda-83929f8f94d8) taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console testvm spice-html5 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-61028912-7436-4ac5-9217-13813f55f7fa) taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console testvm serial 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-5f83283d-9b75-40b1-9dae-81cf30890749) taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console testvm webmks 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-ec419562-f7c2-43ed-9d61-333633f45e5d) 3. Reproduce steps: create a testvm(default configurtion) with nova boot bla bla bla .. nova get-vnc-console testvm webmks Expected result: HTTP 400, bad request Invalid console type %(console_type)s" Actual result: HTTP 500 ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: api ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Tags added: api -- 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/1551104 Title: get-XXX-console returns 500 while an expected exception ConsoleTypeInvalid raised Status in OpenStack Compute (nova): New Bug description: 1. Exact version of Nova/OpenStack you are running: Master 791e5421cdc2130ed80e067e43b6006a6859138b 2. Relevant log files: taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console testvm ee ERROR (BadRequest): Invalid input for field/attribute type. Value: ee. u'ee' is not one of ['novnc', 'xvpvnc', 'rdp-html5', 'spice-html5', 'serial', 'webmks'] (HTTP 400) (Request-ID: req-8bd1cada-caf4-4c9f-afa3-1afe7655472d) taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console testvm xvpvnc ++--+ | Type | Url | ++--+ | xvpvnc | http://10.238.157.49:6081/console?token=a7275c37-7397-414a-ba3f-1da4a03d2115 | ++--+ taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console testvm rdp-html5 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-dfd46bc0-fa46-41ea-adda-83929f8f94d8) taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console testvm spice-html5 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-61028912-7436-4ac5-9217-13813f55f7fa) taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console testvm serial 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-5f83283d-9b75-40b1-9dae-81cf30890749) taget@taget-ThinkStation-P300:~/devstack$ nova get-vnc-console
[Yahoo-eng-team] [Bug 1553011] [NEW] total_memory in migration-list is 0 while live-migration
Public bug reported: 1: Nova api microversion v2.25 2: This is the log of source compute node: 2016-03-04 02:25:44.598 INFO nova.virt.libvirt.driver [req-baf2d5a5-1e19-4f78-b38b-ef6ae67ae3f3 admin admin] [instance: d514ae11-3118-4adf-ab6d-9bc437173de3] Increasing downtime to 46 ms after 0 sec elapsed time 2016-03-04 02:25:44.930 INFO nova.virt.libvirt.driver [req-baf2d5a5-1e19-4f78-b38b-ef6ae67ae3f3 admin admin] [instance: d514ae11-3118-4adf-ab6d-9bc437173de3] Migration running for 0 secs, memory 100% remaining; (bytes processed=0, remaining=0, total=0) < 2016-03-04 02:25:48.084 DEBUG nova.virt.libvirt.host [req-baf2d5a5-1e19-4f78-b38b-ef6ae67ae3f3 admin admin] Domain has shutdown/gone away: Requested operation is not valid: domain is not running from (pid=5066) for_domain /opt/stack/nova/nova/virt/libvirt/host.py:180 2016-03-04 02:25:48.086 INFO nova.virt.libvirt.driver [req-baf2d5a5-1e19-4f78-b38b-ef6ae67ae3f3 admin admin] [instance: d514ae11-3118-4adf-ab6d-9bc437173de3] Migration operation has completed 3 steps: 3.1 create an instance 3.2 nova --debug --os-compute-api-version 2.25 live-migration test2 3.3 nova --debug --os-compute-api-version 2.25 server-migration-list test2 ++-+---++--+---+-+--++++++--+--+--+ | Id | Source Node | Dest Node | Source Compute | Dest Compute | Dest Host | Status | Server UUID | Created At | Updated At | Total Memory Bytes | Processed Memory Bytes | Remaining Memory Bytes | Total Disk Bytes | Processed Disk Bytes | Remaining Disk Bytes | ++-+---++--+---+-+--++++++--+--+--+ | 41 | - | - | lm-2 | lm-1 | - | running | d514ae11-3118-4adf-ab6d-9bc437173de3 | 2016-03-04T02:09:26.00 | 2016-03-04T02:09:40.00 | 0 | 0 | 0 | 0| 0| 0 | ++-+---++--+---+-+--++++++--+--+--+ see from nova table: mysql> select * from migrations where id=41; +-+-++++--+---+---+--+--+--+-+---+-+++--+--+--++++ | created_at | updated_at | deleted_at | id | source_compute | dest_compute | dest_host | status| instance_uuid| old_instance_type_id | new_instance_type_id | source_node | dest_node | deleted | migration_type | hidden | memory_total | memory_processed | memory_remaining | disk_total | disk_processed | disk_remaining | +-+-++++--+---+---+--+--+--+-+---+-+++--+--+--++++ | 2016-03-04 02:09:26 | 2016-03-04 02:09:50 | NULL | 41 | lm-2 | lm-1 | NULL | completed | d514ae11-3118-4adf-ab6d-9bc437173de3 | 2 |2 | NULL| NULL | 0 | live-migration | 0 |0 |0 |0 | 0 | 0 | 0 | +-+-++++--+---+---+--+--+--+-+---+-+++--+--+--++++ 1 row in set (0.00 sec) Expected result: * Total Memory Bytes should not 0 * Processed Memory Bytes should be equal Total Memory Bytes after migration finished. Actual result: * Total Memory Bytes is 0 * Processed Memory By
[Yahoo-eng-team] [Bug 1556717] [NEW] live_migration_force_complete surprised error message on compute node in some situation
Public bug reported: On master branch trigger live-migration-force-complete after invoke live-migration test3 ubuntu@lm-1:~/devstack$ nova live-migration-force-complete test3 64 on the source compute node, we can see follow error trace, but it doesn't effect running instance. expect: No error message come out. actual: 2016-03-14 01:18:13.770 ERROR oslo_messaging.rpc.dispatcher [req-6d6ceb08-561b-4638-b813-0c8f8c6c4669 admin admin] Exception during message handling: Instance instance-002b could not be found. 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher Traceback (most recent call last): 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 138, in _dispatch_and_reply 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher incoming.message)) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 183, in _dispatch 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 127, in _do_dispatch 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher result = func(ctxt, **new_args) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/nova/nova/exception.py", line 110, in wrapped 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher payload) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher self.force_reraise() 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/nova/nova/exception.py", line 89, in wrapped 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher return f(self, context, *args, **kw) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/nova/nova/compute/manager.py", line 375, in decorated_function 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher return function(self, context, *args, **kwargs) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/nova/nova/compute/manager.py", line 5281, in live_migration_force_complete 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher self.driver.live_migration_force_complete(instance) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 6544, in live_migration_force_complete 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher self.pause(instance) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 2519, in pause 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher self._host.get_guest(instance).pause() 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/host.py", line 617, in get_guest 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher self.get_domain(instance)) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/host.py", line 607, in get_domain 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher return self._get_domain_by_name(instance.name) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/nova/nova/virt/libvirt/host.py", line 654, in _get_domain_by_name 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher raise exception.InstanceNotFound(instance_id=instance_name) 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher InstanceNotFound: Instance instance-002b could not be found. 2016-03-14 01:18:13.770 TRACE oslo_messaging.rpc.dispatcher ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: live-migration ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Tags added: live-migration -- 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/1556717 Title: live_migration_force_complete surprised error message on compute node in some situation Status
[Yahoo-eng-team] [Bug 1441903] Re: rootwrap.d ln doesn't work for non iSCSI volumes
fixed by I181b594a3119f7ad74c595fc7059d521079b1d74 ** Changed in: nova Assignee: lvmxh (shaohef) => (unassigned) ** Changed in: nova Status: Incomplete => 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/1441903 Title: rootwrap.d ln doesn't work for non iSCSI volumes Status in OpenStack Compute (nova): Fix Released Bug description: The compute.filters line for ln doesn't allow for anything other than iSCSI volumes. It should allow for FC based volumes as well. # nova/virt/libvirt/volume.py: sginfo: CommandFilter, sginfo, root sg_scan: CommandFilter, sg_scan, root ln: RegExpFilter, ln, root, ln, --symbolic, --force, /dev/mapper/ip-.*-iscsi-iqn.*, /dev/disk/by-path/ip-.*-iscsi-iqn.* To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1441903/+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 1574512] [NEW] python-glanceclient doesn't support $HOME while uploading image
Public bug reported: ~/devstack$ glance --debug image-create --name ubuntu-16 --visibility public --disk-format=qcow2 --container-format=bare \--os-distro=ubuntu --file=~/Downloads/xenial-server-cloudimg-amd64-disk1.img File ~/Downloads/xenial-server-cloudimg-amd64-disk1.img does not exist or user does not have read privileges to it ~/devstack$ glance image-create --name ubuntu-16 --visibility public --disk-format=qcow2 --container-format=bare \--os-distro=ubuntu --file=/home/user/Downloads/xenial-server-cloudimg-amd64-disk1.img +--+--+ | Property | Value| +--+--+ | checksum | b27130a877734d9ec938a63ca63c4ee7 | | container_format | bare | | created_at | 2016-04-25T08:38:29Z | | disk_format | qcow2| | id | 22bc8d04-c77b-4780-b6bb-1a37f11d6deb | | min_disk | 0| | min_ram | 0| | name | ubuntu-16| | os_distro| ubuntu | | owner| 959eedbf87534e28a64f94c250b785ac | | protected| False| | size | 303235072| | status | active | | tags | [] | | updated_at | 2016-04-25T08:38:32Z | | virtual_size | None | | visibility | public | +--+--+ ** Affects: python-glanceclient Importance: Undecided Status: New ** Project changed: glance => python-glanceclient -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1574512 Title: python-glanceclient doesn't support $HOME while uploading image Status in python-glanceclient: New Bug description: ~/devstack$ glance --debug image-create --name ubuntu-16 --visibility public --disk-format=qcow2 --container-format=bare \--os-distro=ubuntu --file=~/Downloads/xenial-server-cloudimg-amd64-disk1.img File ~/Downloads/xenial-server-cloudimg-amd64-disk1.img does not exist or user does not have read privileges to it ~/devstack$ glance image-create --name ubuntu-16 --visibility public --disk-format=qcow2 --container-format=bare \--os-distro=ubuntu --file=/home/user/Downloads/xenial-server-cloudimg-amd64-disk1.img +--+--+ | Property | Value| +--+--+ | checksum | b27130a877734d9ec938a63ca63c4ee7 | | container_format | bare | | created_at | 2016-04-25T08:38:29Z | | disk_format | qcow2| | id | 22bc8d04-c77b-4780-b6bb-1a37f11d6deb | | min_disk | 0| | min_ram | 0| | name | ubuntu-16| | os_distro| ubuntu | | owner| 959eedbf87534e28a64f94c250b785ac | | protected| False| | size | 303235072| | status | active | | tags | [] | | updated_at | 2016-04-25T08:38:32Z | | virtual_size | None | | visibility | public | +--+--+ To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1574512/+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 1575007] [NEW] Bad libvirt version 1.2.21 when doing live migration
Public bug reported: Description of problem: Unable to change target guest XML during migration, the argument dxml in virDomainMigrateToURI2 is not used in libvirt 1.2.21 check https://bugzilla.redhat.com/show_bug.cgi?id=1295405 Bug is fixed by libvirt 1.3.1: Jan 17 2016 check http://libvirt.org/news.html libvirt-domain: fix dxml passing in virDomainMigrateToURI2 (Ján Tomko) So we need to blacklist libvirt 1.2.21 when using virDomainMigrateToURI2 ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1575007 Title: Bad libvirt version 1.2.21 when doing live migration Status in OpenStack Compute (nova): New Bug description: Description of problem: Unable to change target guest XML during migration, the argument dxml in virDomainMigrateToURI2 is not used in libvirt 1.2.21 check https://bugzilla.redhat.com/show_bug.cgi?id=1295405 Bug is fixed by libvirt 1.3.1: Jan 17 2016 check http://libvirt.org/news.html libvirt-domain: fix dxml passing in virDomainMigrateToURI2 (Ján Tomko) So we need to blacklist libvirt 1.2.21 when using virDomainMigrateToURI2 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1575007/+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 1576093] [NEW] block migration fail with libvirt 1.3.1
Public bug reported: Try to do block migration but fail and libvirt reports that "Selecting disks to migrate is not implemented for tunneled migration" Nova: a4e15e329f9adbcfe72fbcd6acb94f0743ad02f8 libvirt: 1.3.1 reproduce: default devstack setting and do block migration (no shared instance_dir and shared instance storage used) ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: libvirt live-migration ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) -- 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/1576093 Title: block migration fail with libvirt 1.3.1 Status in OpenStack Compute (nova): New Bug description: Try to do block migration but fail and libvirt reports that "Selecting disks to migrate is not implemented for tunneled migration" Nova: a4e15e329f9adbcfe72fbcd6acb94f0743ad02f8 libvirt: 1.3.1 reproduce: default devstack setting and do block migration (no shared instance_dir and shared instance storage used) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1576093/+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 1576245] [NEW] block live-migration fails if source/dest have different instance dir
Public bug reported: block live migration fails if using libvirt python inter face migrationTOURI3 if source/dest have different instance dir. migrationTOURI3 requires a xml on the dest host, but we don't update instance dir. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: New ** Tags: libvirt live-migration ** Changed in: nova Assignee: (unassigned) => Eli Qiao (taget-9) ** Tags added: libvirt live-migration -- 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/1576245 Title: block live-migration fails if source/dest have different instance dir Status in OpenStack Compute (nova): New Bug description: block live migration fails if using libvirt python inter face migrationTOURI3 if source/dest have different instance dir. migrationTOURI3 requires a xml on the dest host, but we don't update instance dir. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1576245/+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