[Yahoo-eng-team] [Bug 1658590] Re: Windows2012 r2 OS deployment getting Blue Screen death using .qcow2
** Bug watch added: bugs.centos.org/ #13449 https://bugs.centos.org/view.php?id=13449 ** Also affects: centos via https://bugs.centos.org/view.php?id=13449 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1658590 Title: Windows2012 r2 OS deployment getting Blue Screen death using .qcow2 Status in Glance: New Status in CentOS: Unknown Bug description: I was tried to deploy windows 2012 operating system as instance in my open stack set (Newton) To create instance I followed the below mentioned url http://docs.openstack.org/image-guide/windows-image.html Even I tried direct download qcow2 deployment also by using following url https://cloudbase.it/windows-cloud-images/ in all these cases we are getting Blue Screen Death with following error message "DRIVER_IRQL_NOT_LESS_OR_EQUAL" Please find the attached screenshot for your reference To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1658590/+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 1699006] [NEW] tempest: _create_router_with_client ignores enable_snat=False
Public bug reported: _create_router_with_client ignores enable_snat=False, rather than disabling snat. it's counter-intuitive at least. ** Affects: neutron Importance: Undecided Assignee: YAMAMOTO Takashi (yamamoto) Status: In Progress ** Tags: midokura-jira-tracked tempest ** Tags added: tempest -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1699006 Title: tempest: _create_router_with_client ignores enable_snat=False Status in neutron: In Progress Bug description: _create_router_with_client ignores enable_snat=False, rather than disabling snat. it's counter-intuitive at least. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1699006/+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 1698092] Re: Protocols for websocket should not be hardcorded
Reviewed: https://review.openstack.org/474520 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=4493b6f75ff40c7f12f2bd0b4305bc2562b468a6 Submitter: Jenkins Branch:master commit 4493b6f75ff40c7f12f2bd0b4305bc2562b468a6 Author: Shu Muto Date: Thu Jun 15 18:06:47 2017 +0900 Enable to set protocols of WebSocket for serial console This patch enables to set protocols of WebSocket for serial console. Also, this enables to use serial console not only from instance but also plugins. e.g. Zun UI can access container console provided by docker. Change-Id: Ib0df9ddfc74f98bfea75abce3b5d5479e3cd47bd Needed-By: I41f236f2762613e56748bb05eb7ce0e4c26158d2 Closes-Bug: #1698092 ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1698092 Title: Protocols for websocket should not be hardcorded Status in OpenStack Dashboard (Horizon): Fix Released Status in Zun-UI: In Progress Bug description: To use serial console with any websocket protocol, the protocols should not be hardcoded. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1698092/+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 1587847] Re: flavorRef is missing from the parameter list of Resize server
The 'flavorRef' parameter of resize action has been added in API Reference by the following patch. https://review.openstack.org/#/c/455570/ There isn't flavorRef parameter in "Change Administrative Password " API. https://github.com/openstack/nova/blob/8a7a2b8f92afd170d0ac9b536c1af2d90b802bdd/nova/api/openstack/compute/schemas/admin_password.py ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1587847 Title: flavorRef is missing from the parameter list of Resize server Status in OpenStack Compute (nova): Fix Released Bug description: According to the example Change administrative password has a parameter called "flavorRef". This "flavorRef" parameter is not listed in the Parameter list of Change administrative password in the web API reference [1] and not mentioned in Chapter 4.4.20 of the pdf API reference [2]. [1]: http://developer.openstack.org/api-ref-compute-v2.1.html#changePassword [2]: http://api.openstack.org/api-ref-guides/bk-api-ref.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1587847/+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 1414556] Re: "if not host:" never holds in function get_instance_availability_zone() of module nova.availability_zones
The code has been changed in stable/newton, stable/ocata and master. So the issue does not exist currently (in stable/newton, stable/ocata and master). ** 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/1414556 Title: "if not host:" never holds in function get_instance_availability_zone() of module nova.availability_zones Status in OpenStack Compute (nova): Invalid Bug description: Version: stable/juno Description: This bug report is created to separate two issues found in this link: https://bugs.launchpad.net/nova/+bug/1390033. The purpose is to fix at first the bug that the "if not host:" never holds in function get_instance_availability_zone() of module nova.availability_zones in case host is None. This is because str(None) is never interpreted False. For proof, please look at the output of the Python interactive session: Python 2.7.6 (default, Mar 22 2014, 22:59:56) [GCC 4.8.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> host = str(None) >>> print host None >>> if not host: ...print "if not host" else: .. print "else" ... else >>> var = None >>> if not var: ...print "if not var" else: ...print "else" ... if not var So, it can be seen that str(None) returns an object whose value is None, but it is not interpreted False as expected! To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1414556/+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 1698963] [NEW] Admin users can't edit/delete images in other projects
Public bug reported: Currently on the angular images panel, edit image/update metadata/delete image actions are not available for any users for images that are created in a different project. This is incorrect because admin users should be able to update or delete any non-protected images. ** Affects: horizon Importance: Undecided Assignee: Ying Zuo (yingzuo) Status: New ** Changed in: horizon Assignee: (unassigned) => Ying Zuo (yingzuo) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1698963 Title: Admin users can't edit/delete images in other projects Status in OpenStack Dashboard (Horizon): New Bug description: Currently on the angular images panel, edit image/update metadata/delete image actions are not available for any users for images that are created in a different project. This is incorrect because admin users should be able to update or delete any non- protected images. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1698963/+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 1698953] [NEW] The owner column in angular images panel should be renamed as "project"
Public bug reported: Currently, the first column in angular images panel is labeled as "owner" which actually means "project" in Horizon. "owner" is used in the Openstack CLI, but "project" is used in other Horizon admin panels. So I think we should rename it to "project" to be consistent. ** Affects: horizon Importance: Undecided Assignee: Ying Zuo (yingzuo) Status: New ** Changed in: horizon Assignee: (unassigned) => Ying Zuo (yingzuo) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1698953 Title: The owner column in angular images panel should be renamed as "project" Status in OpenStack Dashboard (Horizon): New Bug description: Currently, the first column in angular images panel is labeled as "owner" which actually means "project" in Horizon. "owner" is used in the Openstack CLI, but "project" is used in other Horizon admin panels. So I think we should rename it to "project" to be consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1698953/+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 1697926] Re: linuxbridge ensure_bridge report errror
Reviewed: https://review.openstack.org/474170 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ba5e8468599d5edfa0dad68457739fa03237b16a Submitter: Jenkins Branch:master commit ba5e8468599d5edfa0dad68457739fa03237b16a Author: wlfightup Date: Wed Jun 14 17:45:25 2017 +0800 Linuxbridge agent: detect existing IP on bridge If bridge IP address already exists, when we try and add it an error will be raised. Check for the existence of the IP to avoid the error. Closes-Bug: #1697926 Change-Id: I9aae3b4f0fab053e8c215887f58b983d9549582d ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1697926 Title: linuxbridge ensure_bridge report errror Status in neutron: Fix Released Bug description: 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/agent/_common_agent.py", line 453, in daemon_loop 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent sync = self.process_network_devices(device_info) 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 153, in wrapper 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent return f(*args, **kwargs) 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/agent/_common_agent.py", line 210, in process_network_devices 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent resync_a = self.treat_devices_added_updated(devices_added_updated) 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 153, in wrapper 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent return f(*args, **kwargs) 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/agent/_common_agent.py", line 227, in treat_devices_added_updated 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent self._process_device_if_exists(device_details) 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/agent/_common_agent.py", line 254, in _process_device_if_exists 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent device, device_details['device_owner']) 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py", line 504, in plug_interface 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent tap_name, device_owner) 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py", line 453, in add_tap_interface 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent return False 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent self.force_reraise() 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent six.reraise(self.type_, self.value, self.tb) 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py", line 445, in add_tap_interface 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent tap_device_name, device_owner) 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py", line 476, in _add_tap_interface 2017-06-14 05:00:13.747 16708 ERROR neutron.plugins.ml2.drivers.agent._common_agent segmentation_id): 2017-06-14 05:00:13.747
[Yahoo-eng-team] [Bug 1698596] Re: Segments plugin with ML2 core plugin not storing in the DB the segmentation_id attribute when creating a segment
Reviewed: https://review.openstack.org/475151 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=323c29fd054913493325ad0e987007181fb48976 Submitter: Jenkins Branch:master commit 323c29fd054913493325ad0e987007181fb48976 Author: Miguel Lavalle Date: Sat Jun 17 19:49:32 2017 -0500 Store segmentation_id during segment create The segmentation_id of a new segment is assigned by the _handle_segment_change callback in the ML2 plugin, which is executed after the segment was created, before commiting it to the DB. This patchset adds code to update the newly created segment with the segmentation_id assigned by the callback. Change-Id: I493278a0bf5a3a0aadad10e5bee546d83b949fdc Closes-Bug: #1698596 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1698596 Title: Segments plugin with ML2 core plugin not storing in the DB the segmentation_id attribute when creating a segment Status in neutron: Fix Released Bug description: With ML2 as the core plugin, the segmentation_id of a newly created segment is assigned by a type manager that is executed by a callback subscribed to this PRECOMMIT_CREATE notification: https://github.com/openstack/neutron/blob/master/neutron/services/segments/db.py#L114. Since the new_segment.create() OVO call is one line above the notification, the segmentation_id attribute doesn't get stored in the DB. This can have various undesired results. As an example, with segment type VLAN and under Python 2.7, such a segment might never be released when not used anymore. This is because the VLAN type code will determine here https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/type_vlan.py#L221 that the is outside the configured tenant vlan ranges and the corresponding DB row will never be updated as not allocated. This same example under Python 3.5 generates the following exception in the Neutron server: http://paste.openstack.org/show/612964/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1698596/+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 1696010] Re: binding errors during network deletion
Reviewed: https://review.openstack.org/471154 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=781b8f41498521041f7c9d4b4e0c0fa438736fc4 Submitter: Jenkins Branch:master commit 781b8f41498521041f7c9d4b4e0c0fa438736fc4 Author: Kevin Benton Date: Mon Jun 5 15:50:34 2017 -0700 Stop binding attempts when network has no segments There is no point in retrying binding if the network has no segments to bind to. This occurs during normal operations when a network is being quickly created/deleted and the DHCP port gets created during the network deletion. By skipping binding we avoid misleading error messages and wasted CPU cycles. Closes-Bug: #1696010 Change-Id: I0b987ab7c3f65c1d860064a1b437b92a1dc1cb81 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1696010 Title: binding errors during network deletion Status in neutron: Fix Released Bug description: The server logs have several errors like the following: Jun 02 21:08:04.559663 ubuntu-xenial-citycloud-lon1-9112444 neutron- server[18208]: ERROR neutron.plugins.ml2.managers [None req- 9d2a2fbc-f777-4b55-8390-bfafc514668f None None] Failed to bind port 03819448-f86f-4d2b-810b-a456366c3afb on host ubuntu-xenial-citycloud- lon1-9112444 for vnic_type normal using segments [] These occur while a port is trying to bind while the network is being deleted. We should just stop binding attempts if there are no segments. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1696010/+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 1698797] Re: I cannot launch Instance
It appears that auth_type is not set correctly in the config ** 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/1698797 Title: I cannot launch Instance Status in OpenStack Compute (nova): Invalid Bug description: Hello everyone, I try install openstack ocata in ubuntu 16.02 when i try to start one instance received the next message. Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) The log shows the following: root@controller# tail -f /var/log/nova/nova-api.log 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions neutron = get_client(context, admin=True) 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 138, in get_client 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions _ADMIN_AUTH = _load_auth_plugin(CONF) 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 74, in _load_auth_plugin 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions raise neutron_client_exc.Unauthorized(message=err_msg) 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions Unauthorized: Unknown auth type: None 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions 2017-06-19 13:55:24.250 2689 INFO nova.api.openstack.wsgi [req-86a15257-65c7-44a2-a7a2-d792f1b166b3 c070e9c342824ef3ba41336373a17b91 05696ec4daa44a1c89a26761b621a507 - default default] HTTP exception thrown: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. 2017-06-19 13:55:24.250 2689 INFO nova.osapi_compute.wsgi.server [req-86a15257-65c7-44a2-a7a2-d792f1b166b3 c070e9c342824ef3ba41336373a17b91 05696ec4daa44a1c89a26761b621a507 - default default] 192.168.1.2 "POST /v2.1/servers HTTP/1.1" status: 500 len: 585 time: 0.2191169 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions [req-1a79e323-fe00-464d-9b86-aac9fe4e4117 c070e9c342824ef3ba41336373a17b91 05696ec4daa44a1c89a26761b621a507 - default default] Unexpected exception in API method 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/openstack/extensions.py", line 338, in wrapped 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/openstack/compute/servers.py", line 642, in create 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions **create_kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/hooks.py", line 154, in inner 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions rv = f(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/
[Yahoo-eng-team] [Bug 1533970] Re: NotFound exception of registry client should not show trace logs with ERROR
As Images API v1 has been deprecated since Newton release, this does not seem critical enough bug to address. https://docs.openstack.org/developer/glance/glanceapi.html#images-v1-api ** Changed in: glance Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1533970 Title: NotFound exception of registry client should not show trace logs with ERROR Status in Glance: Won't Fix Bug description: registry client shows trace logs when images are not found: = ERROR glance.registry.client.v1.client [req-fa5967e3-7ee8-4eb9-adc1-f6c4b152089f e4f950c8940da8fb3f1ac086e9550a35538da9d135813666495525abadaf9d8c 852967d9dcb34ac3ae16452f24f4e74c - - -] Registry client request GET /images/26e5f7a4-84d0-41fb-b5cb-bbf04af7d90f raised NotFound ERROR glance.registry.client.v1.client Traceback (most recent call last): ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/registry/client/v1/client.py", line 121, in do_request ERROR glance.registry.client.v1.client **kwargs) ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 71, in wrapped ERROR glance.registry.client.v1.client return func(self, *args, **kwargs) ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 375, in do_request ERROR glance.registry.client.v1.client headers=copy.deepcopy(headers)) ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 88, in wrapped ERROR glance.registry.client.v1.client return func(self, method, url, body, headers) ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 521, in _do_request ERROR glance.registry.client.v1.client raise exception.NotFound(res.read()) ERROR glance.registry.client.v1.client NotFound: 404 Not Found ERROR glance.registry.client.v1.client ERROR glance.registry.client.v1.client The resource could not be found. ERROR glance.registry.client.v1.client ERROR glance.registry.client.v1.client ERROR glance.registry.client.v1.client INFO eventlet.wsgi.server [req-fa5967e3-7ee8-4eb9-adc1-f6c4b152089f e4f950c8940da8fb3f1ac086e9550a35538da9d135813666495525abadaf9d8c 852967d9dcb34ac3ae16452f24f4e74c - - -] 100.72.17.170 - - [18/Nov/2015 10:26:12] "HEAD /v1/images/26e5f7a4-84d0-41fb-b5cb-bbf04af7d90f HTTP/1.1" 404 213 0.071243 = This is mostly caused by requests from Horizon. It requests deleted images to show instance details, and these logs show at every request. However, this is a relatively common case because users can delete old images even instances based on the images are running. (Of course, users can't create new instances based on these old images.) Logs should be both necessary and sufficient. Following HEAD shows 404 as INFO level, so I think one-line DEBUG is enough for this 404 error instead of trace logs. In the case of other status codes, registry client should show trace logs as ERROR. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1533970/+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 1654270] Re: Glance image not found should be logged as WARNING and not ERROR
As Images API v1 has been deprecated since Newton release, this does not seem critical enough bug to address. https://docs.openstack.org/developer/glance/glanceapi.html#images-v1-api ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1654270 Title: Glance image not found should be logged as WARNING and not ERROR Status in Glance: Won't Fix Bug description: We refresh public glance images in our public cloud every month, and we set the old images to private. When you do: openstack server show uuid of course the instance knows the uuid of the glance image that was originally used to create the instance. We noticed that Horizon, to write on the web interface the description of the image used to start the instance, makes a lot of requests for public images that are not public anymore. This is okay, but the 404 is not logged as a WARNING, but as an ERROR with a long stack trace. This is 18 lines for each 404 and is poisoning our log files: 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client [req-334f1f81-c661-4dda-b69f-2e84b8a48acf 870aab4e3af6441b8b5ebfb0dcaa8412 8fcf0992e82943089de7dabe728b78fa - - -] Registry client request GET /images/b34f66bc-02ea-4125-b4ed-8eca7b90de5a raised NotFound 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client Traceback (most recent call last): 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/registry/client/v1/client.py", line 123, in do_request 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client **kwargs) 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 70, in wrapped 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client return func(self, *args, **kwargs) 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 373, in do_request 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client headers=copy.deepcopy(headers)) 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 87, in wrapped 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client return func(self, method, url, body, headers) 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 528, in _do_request 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client raise exception.NotFound(read_body(res)) 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client NotFound: 404 Not Found 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client The resource could not be found. 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1654270/+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 1698907] [NEW] [RFE] Add 'api_status' attribute to API extensions
Public bug reported:
This is a feature request for API extensions.
Based on the discussion in [1], it seems there maybe some use in
introducing a 'api_status' attribute on all API extensions. This
attribute would be defined in the API's definition
(neutron_lib.api.defintions.) and would be returned in the
extension body(s) for GETs (/v2.0/extensions, /v2.0/extensions/{alias}).
The api_status should be a static set of values. For example:
- EXPERIMENTAL --> The API is in "beta mode" and not fully hardened.
- SUPPORTED --> Current supported API.
- DEPRECATED --> The API is not actively supported any maybe removed in a
future release.
[1] https://review.openstack.org/#/c/415817/
** Affects: neutron
Importance: Undecided
Status: New
** Tags: rfe
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1698907
Title:
[RFE] Add 'api_status' attribute to API extensions
Status in neutron:
New
Bug description:
This is a feature request for API extensions.
Based on the discussion in [1], it seems there maybe some use in
introducing a 'api_status' attribute on all API extensions. This
attribute would be defined in the API's definition
(neutron_lib.api.defintions.) and would be returned in the
extension body(s) for GETs (/v2.0/extensions,
/v2.0/extensions/{alias}).
The api_status should be a static set of values. For example:
- EXPERIMENTAL --> The API is in "beta mode" and not fully hardened.
- SUPPORTED --> Current supported API.
- DEPRECATED --> The API is not actively supported any maybe removed in a
future release.
[1] https://review.openstack.org/#/c/415817/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1698907/+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 1698900] [NEW] DB check appears to not be working right
Public bug reported: Using current master of keystone, executing a keystone-manage db_sync --check seems to always return the RC of 2 regardless of the steps previously confirmed. This happens until the contract is done, then it returns 0. Steps to reproduce: root@keystone1:/# mysqladmin drop keystone; mysql create keystone root@keystone1:/# keystone-manage db_sync --check; echo $? 2 root@keystone1:/# keystone-manage db_sync --expand; echo $? 0 root@keystone1:/# keystone-manage db_sync --check; echo $? 2 root@keystone1:/# keystone-manage db_sync --migrate; echo $? 0 root@keystone1:/# keystone-manage db_sync --check; echo $? 2 root@keystone1:/# keystone-manage db_sync --contract; echo $? 0 root@keystone1:/# keystone-manage db_sync --check; echo $? 0 Not getting the right return codes or advise from the check can spell disaster for automation that uses it, or humans following the documented migration process. ** Affects: keystone Importance: High Status: Confirmed ** Tags: sql -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1698900 Title: DB check appears to not be working right Status in OpenStack Identity (keystone): Confirmed Bug description: Using current master of keystone, executing a keystone-manage db_sync --check seems to always return the RC of 2 regardless of the steps previously confirmed. This happens until the contract is done, then it returns 0. Steps to reproduce: root@keystone1:/# mysqladmin drop keystone; mysql create keystone root@keystone1:/# keystone-manage db_sync --check; echo $? 2 root@keystone1:/# keystone-manage db_sync --expand; echo $? 0 root@keystone1:/# keystone-manage db_sync --check; echo $? 2 root@keystone1:/# keystone-manage db_sync --migrate; echo $? 0 root@keystone1:/# keystone-manage db_sync --check; echo $? 2 root@keystone1:/# keystone-manage db_sync --contract; echo $? 0 root@keystone1:/# keystone-manage db_sync --check; echo $? 0 Not getting the right return codes or advise from the check can spell disaster for automation that uses it, or humans following the documented migration process. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1698900/+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 1696830] Re: nova-placement-api default config files is too strict
Reviewed: https://review.openstack.org/474212 Committed: https://git.openstack.org/cgit/openstack/oslo.config/commit/?id=21e70e28b3015c1619dacfad8a2218b09e8109ec Submitter: Jenkins Branch:master commit 21e70e28b3015c1619dacfad8a2218b09e8109ec Author: Corey Bryant Date: Wed Jun 14 09:57:23 2017 -0400 Add snap package paths to default config dirs With snap packaging (see snapcraft.io) the package is installed into a read-only squashfs filesystem, which includes the default config. For example, $SNAP/etc/nova/nova.conf. To override the defaults, a separate writable directory is used, and this directory is also unique to the snap. For example, either $SNAP_COMMON/etc/nova/nova.conf, or $SNAP_COMMON/etc/nova/nova.conf.d/ can be used to override config. This patch adds these snap directories to the default config paths where oslo looks for config. For more details on $SNAP and $SNAP_COMMON please refer to https://snapcraft.io/docs/reference/env. Change-Id: I83627e0f215382aedc7b32163e0303b39e8bccf8 Closes-Bug: 1696830 ** Changed in: oslo.config Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1696830 Title: nova-placement-api default config files is too strict Status in OpenStack Compute (nova): Confirmed Status in oslo.config: Fix Released Status in Glance Snap: New Status in Keystone Snap: New Status in Neutron Snap: New Status in Nova Snap: In Progress Status in Nova Hypervisor Snap: New Bug description: If nova.conf doesn't exist in the typical location of /etc/nova/nova.conf and OS_PLACEMENT_CONFIG_DIR isn't set, nova- placement-api's wsgi application will fail. In our case with the OpenStack snap, we have two possible paths we may pick nova.conf up from, based on what --config-file specifies. I think the right answer here is to be a bit more flexible and not set the default config file if it's path doesn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1696830/+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 1698852] [NEW] port in mechanism driver's create_port_postcommit has no extra_dhcp_opts
Public bug reported:
The port in the following code of a mechanism driver will always have
extra_dhcp_opts = [], regardless of whether it has dhcp options or not.
def create_port_postcommit(self, context):
port = context.current
port.get('extra_dhcp_opts') # always an empty list
The create_port_precommit port does have the correct extra_dhcp_opts.
Seen on stable/ocata
** Affects: neutron
Importance: Undecided
Status: New
** Description changed:
The port in the following code of a mechanism driver will always have
extra_dhcp_opts = [], regardless of whether it has dhcp options or not.
-
- def create_port_postcommit(self, context):
- port = context.current
- port.get('extra_dhcp_opts') # always an empty list
-
+ def create_port_postcommit(self, context):
+ port = context.current
+ port.get('extra_dhcp_opts') # always an empty list
The create_port_precommit port does have the correct extra_dhcp_opts.
+
+ Seen on stable/ocata
** Summary changed:
- port in mechanism driver's create_port_postcommit has no extra_hdcp_options
+ port in mechanism driver's create_port_postcommit has no extra_dhcp_opts
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1698852
Title:
port in mechanism driver's create_port_postcommit has no
extra_dhcp_opts
Status in neutron:
New
Bug description:
The port in the following code of a mechanism driver will always have
extra_dhcp_opts = [], regardless of whether it has dhcp options or
not.
def create_port_postcommit(self, context):
port = context.current
port.get('extra_dhcp_opts') # always an empty list
The create_port_precommit port does have the correct extra_dhcp_opts.
Seen on stable/ocata
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1698852/+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 1694220] Re: Neutron agents fail to start on Windows
Reviewed: https://review.openstack.org/468833 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=572deac00be43b87546d9dd6d3d9886b0963ae1e Submitter: Jenkins Branch:master commit 572deac00be43b87546d9dd6d3d9886b0963ae1e Author: Claudiu Belu Date: Mon May 29 02:44:03 2017 -0700 Fixes import_modules_recursively for Windows The neutron agents fail to start on Windows, due to the fact that neutron.common.utils.import_modules_recursively expects the paths to be forwardslash separated, while on Windows they are backslash separated. Change-Id: I5e15273c2f70b70fad0cf1216ef0b33c6a99d702 Closes-Bug: #1694220 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1694220 Title: Neutron agents fail to start on Windows Status in neutron: Fix Released Bug description: The Neutron agents fail to start on Windows, due to an import issue: [1] The issue is caused by neutron.common.utils.import_modules_recursively, which expects the paths to be forwardslash separated, while on Windows they are backslash separated. [2] [1] http://64.119.130.115/nova/441183/10/Hyper-V_logs/c2-r22-u02-n02-compute01/process_error.txt.gz [2] https://github.com/openstack/neutron/blob/master/neutron/common/utils.py#L763 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1694220/+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 1698812] [NEW] security group callbacks regression
Public bug reported:
after_create callback gets empty security_group_rules.
eg. http://logs.openstack.org/87/199387/79/check/gate-tempest-dsvm-
networking-midonet-ml2-ubuntu-xenial/331d691/logs/screen-q-svc.txt.gz
Jun 19 10:51:51.378599 ubuntu-xenial-rax-ord-9385124 neutron-
server[10764]: DEBUG midonet.neutron.ml2.sg_callback [None req-
d097915b-1336-4fb8-bcdc-cd49486aee54 admin admin]
midonet.neutron.ml2.sg_callback.MidonetSecurityGroupsHandler method
create_security_group called with arguments ('security_group',
'after_create', ) {'security_group': {'description': u'Default security
group', 'tenant_id': u'1108c275750141b38d25d8fb05b19b82', 'created_at':
'2017-06-19T10:51:51Z', 'updated_at': '2017-06-19T10:51:51Z',
'security_group_rules': [], 'revision_number': 5, 'project_id':
u'1108c275750141b38d25d8fb05b19b82', 'id':
'7e0bc780-7257-4506-a978-df7fb767bcc6', 'name': u'default'},
'is_default': True, 'context': } {{(pid=10854) wrapper /usr/local/lib/python2.7/dist-
packages/oslo_log/helpers.py:47}}
** Affects: networking-midonet
Importance: Critical
Assignee: YAMAMOTO Takashi (yamamoto)
Status: In Progress
** Affects: neutron
Importance: Undecided
Status: New
** Tags: gate-failure midokura-jira-tracked
** Tags added: gate-failure midokura-jira-tracked
** Changed in: networking-midonet
Importance: Undecided => Critical
** Changed in: networking-midonet
Status: New => In Progress
** Changed in: networking-midonet
Milestone: None => 5.0.0
** Changed in: networking-midonet
Assignee: (unassigned) => YAMAMOTO Takashi (yamamoto)
** Also affects: neutron
Importance: Undecided
Status: New
** Summary changed:
- sg regression
+ security group callbacks regression
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1698812
Title:
security group callbacks regression
Status in networking-midonet:
In Progress
Status in neutron:
New
Bug description:
after_create callback gets empty security_group_rules.
eg. http://logs.openstack.org/87/199387/79/check/gate-tempest-dsvm-
networking-midonet-ml2-ubuntu-xenial/331d691/logs/screen-q-svc.txt.gz
Jun 19 10:51:51.378599 ubuntu-xenial-rax-ord-9385124 neutron-
server[10764]: DEBUG midonet.neutron.ml2.sg_callback [None req-
d097915b-1336-4fb8-bcdc-cd49486aee54 admin admin]
midonet.neutron.ml2.sg_callback.MidonetSecurityGroupsHandler method
create_security_group called with arguments ('security_group',
'after_create', ) {'security_group': {'description': u'Default security
group', 'tenant_id': u'1108c275750141b38d25d8fb05b19b82',
'created_at': '2017-06-19T10:51:51Z', 'updated_at':
'2017-06-19T10:51:51Z', 'security_group_rules': [], 'revision_number':
5, 'project_id': u'1108c275750141b38d25d8fb05b19b82', 'id':
'7e0bc780-7257-4506-a978-df7fb767bcc6', 'name': u'default'},
'is_default': True, 'context': } {{(pid=10854) wrapper /usr/local/lib/python2.7/dist-
packages/oslo_log/helpers.py:47}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-midonet/+bug/1698812/+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 1466451] Re: Nova should verify that devname in pci_passthrough_whitelist is not empty
> According to
> https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking:
> "The devname can be a valid PCI device name. The only device names that are
> supported are those displayed by the Linux utility ifconfig -a and correspond
> to either a PF or a VF on a vNIC"
>
> However it's possible to supply an empty string as devname
> e.g. pci_passthrough_whitelist = {"devname": "",
> "physical_network":"physnet2"}
>
> It's also possible to have an entry:
> pci_passthrough_whitelist = {"physical_network":"physnet2"}
> which shouldn't be valid.
I'm not sure why this isn't valid. IMO, this equates to a wildcard. We
should test to validate this and perhaps update the docs.
> Nova should verify that devname is not an empty string and that
devname,address or product_id/vendor_id are supplied.
** Changed in: nova
Status: In Progress => Invalid
** Changed in: nova
Assignee: Stephen Finucane (stephenfinucane) => (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/1466451
Title:
Nova should verify that devname in pci_passthrough_whitelist is not
empty
Status in OpenStack Compute (nova):
Invalid
Bug description:
According to
https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking:
"The devname can be a valid PCI device name. The only device names that are
supported are those displayed by the Linux utility ifconfig -a and correspond
to either a PF or a VF on a vNIC"
However it's possible to supply an empty string as devname
e.g. pci_passthrough_whitelist = {"devname": "",
"physical_network":"physnet2"}
It's also possible to have an entry:
pci_passthrough_whitelist = {"physical_network":"physnet2"}
which shouldn't be valid.
Nova should verify that devname is not an empty string and that
devname,address or product_id/vendor_id are supplied.
Version
==
python-nova-2015.1.0-4.el7ost.noarch
Expected result
=
Nova compute should fail to start when specifying an empty string for devname
when using physical_network or when not specifying devname,address or
product_id/vendor_id
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1466451/+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 1698797] [NEW] launch
Public bug reported: Hello everyone, I try install openstack ocata in ubuntu 16.02 when i try to start one instance received the next message. Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) The log shows the following: root@controller# tail -f /var/log/nova/nova-api.log 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions neutron = get_client(context, admin=True) 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 138, in get_client 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions _ADMIN_AUTH = _load_auth_plugin(CONF) 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 74, in _load_auth_plugin 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions raise neutron_client_exc.Unauthorized(message=err_msg) 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions Unauthorized: Unknown auth type: None 2017-06-19 13:55:24.249 2689 ERROR nova.api.openstack.extensions 2017-06-19 13:55:24.250 2689 INFO nova.api.openstack.wsgi [req-86a15257-65c7-44a2-a7a2-d792f1b166b3 c070e9c342824ef3ba41336373a17b91 05696ec4daa44a1c89a26761b621a507 - default default] HTTP exception thrown: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. 2017-06-19 13:55:24.250 2689 INFO nova.osapi_compute.wsgi.server [req-86a15257-65c7-44a2-a7a2-d792f1b166b3 c070e9c342824ef3ba41336373a17b91 05696ec4daa44a1c89a26761b621a507 - default default] 192.168.1.2 "POST /v2.1/servers HTTP/1.1" status: 500 len: 585 time: 0.2191169 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions [req-1a79e323-fe00-464d-9b86-aac9fe4e4117 c070e9c342824ef3ba41336373a17b91 05696ec4daa44a1c89a26761b621a507 - default default] Unexpected exception in API method 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/openstack/extensions.py", line 338, in wrapped 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 108, in wrapper 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/api/openstack/compute/servers.py", line 642, in create 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions **create_kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/hooks.py", line 154, in inner 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions rv = f(*args, **kwargs) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 1613, in create 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions check_server_group_quota=check_server_group_quota) 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 1186, in _create_instance 2017-06-19 14:02:57.521 2688 ERROR nova.api.openstack.extensions reservation_id, max_count
[Yahoo-eng-team] [Bug 1696682] Re: port_range validator should allow a single integer
Reviewed: https://review.openstack.org/472155 Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=29a31c152caacdb4d73acb534260443fd07801b0 Submitter: Jenkins Branch:master commit 29a31c152caacdb4d73acb534260443fd07801b0 Author: YAMAMOTO Takashi Date: Thu Jun 8 17:39:58 2017 +0900 Make port_range validator accept an integer It used to accept an integer but it has been changed for some reasons when migrating to neutron-lib. For compatibility, it's better to keep the original behaviour. After all, the original behaviour seems reasonable to me. Closes-Bug: #1696682 Related-Bug: #1696389 Change-Id: I60e1a99780202de14522f592288d3a9af7a75592 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1696682 Title: port_range validator should allow a single integer Status in neutron: Fix Released Bug description: neutron-lib version of the validator assumes it's a string. but it used to accept an integer. for compatibility it should accept an integer. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1696682/+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 1698791] [NEW] [RFE] Add support getting segment vlan usage
Public bug reported: In some private cloud, admin user need to know which VLAN ids are available for the purpose of management, and this also helpful for create VLAN provider network with specified VLAN id. We can implement an API, which can get used VLAN ids from database. ** Affects: neutron Importance: Undecided Assignee: Dongcan Ye (hellochosen) Status: New ** Tags: rfe ** Changed in: neutron Assignee: (unassigned) => Dongcan Ye (hellochosen) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1698791 Title: [RFE] Add support getting segment vlan usage Status in neutron: New Bug description: In some private cloud, admin user need to know which VLAN ids are available for the purpose of management, and this also helpful for create VLAN provider network with specified VLAN id. We can implement an API, which can get used VLAN ids from database. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1698791/+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 1695147] Re: Unnecessary query is running to update the resource of the security group
This is expected. A resource deletion should trigger a recalculation of
the available security group quota for the tenant.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1695147
Title:
Unnecessary query is running to update the resource of the security
group
Status in neutron:
Invalid
Bug description:
When we try to delete a security group, unnecessary query is running
to update the resource of the security group which we are deleting.
Example: At the time of delete operation 'quotausages' table is being updated
by resource (security_group_rule) which are not available in it,
UPDATE query is below:-
UPDATE quotausages SET dirty=1 WHERE quotausages.resource =
'security_group_rule' AND
quotausages.tenant_id = '{ID}';
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1695147/+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 1696125] Re: Detach interface failed - timeout waiting to detach tap device in linuxbridge job (pike)
It seems vif_type='tap' is just broken with libvirt so it's not safe to use. There isn't anything we can do on the Neutron side to fix this other than suggest plugins not use that vif_type until a fix is found in libvirt. ** Changed in: neutron Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1696125 Title: Detach interface failed - timeout waiting to detach tap device in linuxbridge job (pike) Status in neutron: Opinion Status in OpenStack Compute (nova): Confirmed Bug description: Seeing this in Tempest runs on master (pike): http://logs.openstack.org/24/471024/2/check/gate-tempest-dsvm-neutron- linuxbridge-ubuntu- xenial/6b98d38/logs/screen-n-cpu.txt.gz?level=TRACE#_Jun_06_02_16_02_855503 Jun 06 02:16:02.855503 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: WARNING nova.compute.manager [None req-b4a50024-a2fd-4279-b284-340d2074f1c1 tempest-TestNetworkBasicOps-1479445685 tempest-TestNetworkBasicOps-1479445685] [instance: 2668bcb9-b13d-4b5b-8ee5-edbdee3b15a8] Detach interface failed, port_id=3843caa3-ab04-45f1-94d8-f330390e40fe, reason: Device detach failed for fa:16:3e:ab:e3:3f: Unable to detach from guest transient domain.: DeviceDetachFailed: Device detach failed for fa:16:3e:ab:e3:3f: Unable to detach from guest transient domain. Jun 06 02:16:02.884007 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server [None req-b4a50024-a2fd-4279-b284-340d2074f1c1 tempest-TestNetworkBasicOps-1479445685 tempest-TestNetworkBasicOps-1479445685] Exception during message handling: InterfaceDetachFailed: Failed to detach network adapter device from 2668bcb9-b13d-4b5b-8ee5-edbdee3b15a8 Jun 06 02:16:02.884180 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server Traceback (most recent call last): Jun 06 02:16:02.884286 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 157, in _process_incoming Jun 06 02:16:02.884395 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) Jun 06 02:16:02.884538 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 213, in dispatch Jun 06 02:16:02.884669 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) Jun 06 02:16:02.884777 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 183, in _do_dispatch Jun 06 02:16:02.884869 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) Jun 06 02:16:02.884968 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/exception_wrapper.py", line 77, in wrapped Jun 06 02:16:02.885069 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server function_name, call_dict, binary) Jun 06 02:16:02.885171 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ Jun 06 02:16:02.885272 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server self.force_reraise() Jun 06 02:16:02.885367 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise Jun 06 02:16:02.885461 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) Jun 06 02:16:02.885554 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/exception_wrapper.py", line 68, in wrapped Jun 06 02:16:02.885649 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw) Jun 06 02:16:02.885755 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/compute/manager.py", line 214, in decorated_function Jun 06 02:16:02.885856 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server kwargs['instance'], e, sys.exc_info()) Jun 06 02:16:02.885950 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", li
[Yahoo-eng-team] [Bug 1655182] Re: keystone-manage mapping_engine tester problems
** Also affects: cloud-archive/mitaka Importance: Undecided Status: New ** Also affects: cloud-archive/newton Importance: Undecided Status: New ** Also affects: keystone (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: keystone (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: cloud-archive/mitaka Status: New => Triaged ** Changed in: cloud-archive/newton Status: New => Triaged ** Changed in: keystone (Ubuntu Xenial) Status: New => Triaged ** Changed in: keystone (Ubuntu Yakkety) Status: New => Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1655182 Title: keystone-manage mapping_engine tester problems Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive mitaka series: Triaged Status in Ubuntu Cloud Archive newton series: Triaged Status in OpenStack Identity (keystone): Fix Released Status in keystone package in Ubuntu: Fix Released Status in keystone source package in Xenial: Triaged Status in keystone source package in Yakkety: Triaged Bug description: [Impact] * A bug in keystone-manage tool prohibits the use of the mapping_engine command for testing federation rules. * Users of Keystone Federation will not be able to verify their mapping rules before pushing these to production. * Not being able to test rules before pushing to production is a major operational challenge for our users. * The proposed upload fixes this by backporting a fix for this issue from upstream stable/ocata. [Test Case] * Deploy keystone using Juju with this bundle: http://pastebin.ubuntu.com/24855409/ * ssh to keystone unit, grab artifacts and run command: - mapping.json: http://pastebin.ubuntu.com/24855419/ - input.txt: http://pastebin.ubuntu.com/24855420/ - command: 'keystone-manage mapping_engine --rules mapping.json --input input.txt' * Observe that command provides no output and that a Python Traceback is printed in /var/log/keystone/keystone.log * Install the proposed package, repeat the above steps and observe that the command now outputs its interpretation and effect of the rules. [Regression Potential] * keystone-manage mapping_engine is a operational test tool and is solely used by the operator to test their rules. * The distributed version of this command in Xenial and Yakkety does currently not work at all. * The change will make the command work as our users expect it to. [Original bug description] There are several problems with keystone-manage mapping_engine * It aborts with a backtrace because of wrong number of arguments passed to the RuleProcessor * The --engine-debug option does not work. * Error messages related to input data are cryptic and inprecise. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1655182/+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 1697873] Re: neutron-vpnaas failed to execute tox -e dsvm-functional-sswan
I think this is a question about how to run VPNaaS functional tests. Can
you ask on openstack-dev with [neutron] and [vpnaas] in the subject
please?
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1697873
Title:
neutron-vpnaas failed to execute tox -e dsvm-functional-sswan
Status in neutron:
Invalid
Bug description:
After I installed openstack with devstack,
Execute in the neutron-vpnaas directory
Tox -e dsvm-functional-sswan
The results are as follows:
==
Totals
==
Ran: 27 tests in 7. sec.
- Passed: 0
- Skipped: 7
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 20
Sum of execute time for each test: 5.5638 sec.
Some error info：
Traceback (most recent call last):
File
"/opt/stack/neutron/neutron/tests/functional/db/test_migrations.py", line 136,
in setUp
super(_TestModelsMigrations, self).setUp()
File "/opt/stack/neutron/neutron/tests/unit/testlib_api.py", line 289,
in setUp
self._setup_database_fixtures()
File "/opt/stack/neutron/neutron/tests/unit/testlib_api.py", line 326,
in _setup_database_fixtures
self.fail(msg)
File "/usr/lib/python2.7/site-packages/unittest2/case.py", line 690, in
fail
raise self.failureException(msg)
AssertionError: backend 'mysql' unavailable
Traceback (most recent call last):
File
"/opt/stack/neutron/neutron/tests/functional/db/test_migrations.py", line 136,
in setUp
super(_TestModelsMigrations, self).setUp()
File "/opt/stack/neutron/neutron/tests/unit/testlib_api.py", line 289,
in setUp
self._setup_database_fixtures()
File "/opt/stack/neutron/neutron/tests/unit/testlib_api.py", line 326,
in _setup_database_fixtures
self.fail(msg)
File "/usr/lib/python2.7/site-packages/unittest2/case.py", line 690, in
fail
raise self.failureException(msg)
AssertionError: backend 'postgresql' unavailable
Traceback (most recent call last):
File
"neutron_vpnaas/tests/functional/strongswan/test_strongswan_driver.py", line
142, in setUp
self.router.router_namespace.create()
File "/opt/stack/neutron/neutron/agent/l3/namespaces.py", line 93, in
create
ip_wrapper = self.ip_wrapper_root.ensure_namespace(self.name)
File "/opt/stack/neutron/neutron/agent/linux/ip_lib.py", line 210, in
ensure_namespace
if not self.netns.exists(name):
File "/opt/stack/neutron/neutron/agent/linux/ip_lib.py", line 905, in
exists
run_as_root=cfg.CONF.AGENT.use_helper_for_ns_read)
File "/opt/stack/neutron/neutron/agent/linux/ip_lib.py", line 109, in
_execute
log_fail_as_error=log_fail_as_error)
File "/opt/stack/neutron/neutron/agent/linux/utils.py", line 127, in
execute
execute_rootwrap_daemon(cmd, process_input, addl_env))
File "/opt/stack/neutron/neutron/agent/linux/utils.py", line 114, in
execute_rootwrap_daemon
LOG.error(_LE("Rootwrap error running command: %s"), cmd)
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line
220, in __exit__
self.force_reraise()
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line
196, in force_reraise
six.reraise(self.type_, self.value, self.tb)
File "/opt/stack/neutron/neutron/agent/linux/utils.py", line 111, in
execute_rootwrap_daemon
return client.execute(cmd, process_input)
File "/usr/lib/python2.7/site-packages/oslo_rootwrap/client.py", line
125, in execute
self._ensure_initialized()
File "/usr/lib/python2.7/site-packages/oslo_rootwrap/client.py", line
110, in _ensure_initialized
self._initialize()
File "/usr/lib/python2.7/site-packages/oslo_rootwrap/client.py", line
80, in _initialize
(stderr,))
Exception: Failed to spawn rootwrap process.
stderr:
sudo:
/opt/stack/neutron-vpnaas/.tox/dsvm-functional-sswan/bin/neutron-rootwrap-daemon:
command not found
Why does this happen? What should I do?
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1697873/+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 1698779] [NEW] aggregate related notification samples are missing from the notification dev-ref
Public bug reported: The list in the devref [1] shall contain the already transformed aggregate notifications [2] but it doesn't due to a missing import in the doc generation code [3]. As an improvement the doc generation shall automatically pick up the new modules under nova.notifications.objects to avoid similar regression in the future. [1] https://docs.openstack.org/developer/nova/notifications.html#existing-versioned-notifications [2] https://github.com/openstack/nova/blob/master/nova/notifications/objects/aggregate.py#L45 [3] https://github.com/openstack/nova/blob/master/doc/ext/versioned_notifications.py#L35 ** Affects: nova Importance: Undecided Assignee: Balazs Gibizer (balazs-gibizer) Status: New ** Tags: doc notification ** Tags added: doc notification ** Changed in: nova Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer) -- 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/1698779 Title: aggregate related notification samples are missing from the notification dev-ref Status in OpenStack Compute (nova): New Bug description: The list in the devref [1] shall contain the already transformed aggregate notifications [2] but it doesn't due to a missing import in the doc generation code [3]. As an improvement the doc generation shall automatically pick up the new modules under nova.notifications.objects to avoid similar regression in the future. [1] https://docs.openstack.org/developer/nova/notifications.html#existing-versioned-notifications [2] https://github.com/openstack/nova/blob/master/nova/notifications/objects/aggregate.py#L45 [3] https://github.com/openstack/nova/blob/master/doc/ext/versioned_notifications.py#L35 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1698779/+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 1698773] [NEW] vm stuck "deleting" when delete vm after enable iscsi_use_multipath
Public bug reported: Hi Guys: I found vm stuck "deleting" when delete vm after enable iscsi_use_multipath. If I set iscsi_use_multipath=False, It's ok when delete vm. Meanwhile, If I restart nova-compute service on compute node, I will see the "deleting" vm is disappeared on horizon. version: Ocata. Environment === # rpm -qa | grep nova openstack-nova-compute-15.0.3-2.el7.noarch python2-novaclient-7.1.0-1.el7.noarch python-nova-15.0.3-2.el7.noarch openstack-nova-common-15.0.3-2.el7.noarch 1. Which hypervisor did you use? Libvirt + KVM, 2. Which storage type did you use? Netapp Storage. 3. Which networking type did you use? Neutron with OpenVSwitch ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1698773 Title: vm stuck "deleting" when delete vm after enable iscsi_use_multipath Status in OpenStack Compute (nova): New Bug description: Hi Guys: I found vm stuck "deleting" when delete vm after enable iscsi_use_multipath. If I set iscsi_use_multipath=False, It's ok when delete vm. Meanwhile, If I restart nova-compute service on compute node, I will see the "deleting" vm is disappeared on horizon. version: Ocata. Environment === # rpm -qa | grep nova openstack-nova-compute-15.0.3-2.el7.noarch python2-novaclient-7.1.0-1.el7.noarch python-nova-15.0.3-2.el7.noarch openstack-nova-common-15.0.3-2.el7.noarch 1. Which hypervisor did you use? Libvirt + KVM, 2. Which storage type did you use? Netapp Storage. 3. Which networking type did you use? Neutron with OpenVSwitch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1698773/+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 1546910] Re: args pass to securitygroup precommit event should include the complete info
Reviewed: https://review.openstack.org/448420 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=89abce3efe0645cc08e840b4cc4d455889ee8866 Submitter: Jenkins Branch:master commit 89abce3efe0645cc08e840b4cc4d455889ee8866 Author: Reedip Date: Wed Mar 22 07:24:33 2017 + Pass the complete info in sg/rules db into PRECOMMIT_XXX callback PRECOMMIT_XXX events callback need completed sg info, like the sg id and its related rules for registered driver. Change-Id: I6f49f25eb2ad16221357024f45a6bb6175d5cd55 Co-Authored-By: Rui Wang Co-Authored-By: Manjeet Singh Bhatia Co-Authored-By: Yalei Wang Closes-bug: #1546910 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1546910 Title: args pass to securitygroup precommit event should include the complete info Status in networking-odl: New Status in networking-odl 3.0-newton series: New Status in neutron: Fix Released Bug description: We introduced the PRECOMMIT_XXX event, but in securitygroups_db.py, the kwargs passed to it do not include the complete info of DB like AFTER_XXX event. For example, the id of the new created sg/rule. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-odl/+bug/1546910/+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 1698753] [NEW] nova interface-attach failing on MessagingTimeout
Public bug reported: We are continually creating new networks, subnets, routers and ports. Afterward created port is attached to one of two existing VMs. When this run come to around 30-35 networks an MessagingTimeout error starts to appear in log. Example of creating one network: neutron net-create vxlannet3 --shared --provider:network_type vxlan neutron subnet-create vxlannet3 1.1.3.0/24 --name vxlansubnet3 neutron router-create r3 neutron router-interface-add r3 subnet=vxlansubnet3 neutron port-create vxlannet3 --name vm-3-port nova interface-attach --port-id=`neutron port-list | grep vm-3-port | cut -f 2 -d " "` $vm1 Log attached. ** Affects: nova Importance: Undecided Status: New ** Attachment added: "nova-api.log-20170617.gz" https://bugs.launchpad.net/bugs/1698753/+attachment/4898442/+files/nova-api.log-20170617.gz -- 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/1698753 Title: nova interface-attach failing on MessagingTimeout Status in OpenStack Compute (nova): New Bug description: We are continually creating new networks, subnets, routers and ports. Afterward created port is attached to one of two existing VMs. When this run come to around 30-35 networks an MessagingTimeout error starts to appear in log. Example of creating one network: neutron net-create vxlannet3 --shared --provider:network_type vxlan neutron subnet-create vxlannet3 1.1.3.0/24 --name vxlansubnet3 neutron router-create r3 neutron router-interface-add r3 subnet=vxlansubnet3 neutron port-create vxlannet3 --name vm-3-port nova interface-attach --port-id=`neutron port-list | grep vm-3-port | cut -f 2 -d " "` $vm1 Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1698753/+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
