[Yahoo-eng-team] [Bug 1777671] Re: Incorrect use of translation _()
Reviewed: https://review.openstack.org/596683 Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=67435147ec4fc9762743c9474a17999a500fda07 Submitter: Zuul Branch:master commit 67435147ec4fc9762743c9474a17999a500fda07 Author: Vishakha Agarwal Date: Mon Aug 27 15:39:23 2018 +0530 Incorrect use of translation _() Keystone uses translated strings both in logging an exceptions. This is incorrect. All strings that are passed to logging should remain un-translated. This patch addresses above issue. Change-Id: Idf4f0bc1bd63eb8dc6dc61d8a49a9e2a93320474 Closes-Bug: #1777671 ** Changed in: keystone Status: In Progress => Fix Released -- 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/1777671 Title: Incorrect use of translation _() Status in OpenStack Identity (keystone): Fix Released Bug description: Keystone uses translated strings both in logging an exceptions. This is incorrect. All strings that are passed to logging should remain un-translated. The solution is to duplicate the string and pass the untranslated (not wrapped with `_()`) to the logger while passing the translated `_()` wrapped string to the exception. Relevant Discussion: http://eavesdrop.openstack.org/irclogs /%23openstack-oslo/%23openstack- oslo.2018-06-18.log.html#t2018-06-18T22:03:19 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1777671/+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 1790148] Re: Verify operation in keystone (Documentation fault)
Reviewed: https://review.openstack.org/599318 Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=0df5bb0d0c08e5b59d9139992113d607ca0ab5c0 Submitter: Zuul Branch:master commit 0df5bb0d0c08e5b59d9139992113d607ca0ab5c0 Author: chenxing Date: Mon Sep 3 16:59:13 2018 +0800 Update RDO install guide for v3 This is a supplement for https://review.openstack.org/556023 Change-Id: I20f698a0d820f4e99cea110f157f6ba53423bce5 Closes-Bug: #1790148 ** Changed in: keystone Status: In Progress => Fix Released -- 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/1790148 Title: Verify operation in keystone (Documentation fault) Status in OpenStack Identity (keystone): Fix Released Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [X] This doc is inaccurate in this way: Section 2: $ openstack --os-auth-url http://controller:35357/v3 \ --os-project-domain-name Default --os-user-domain-name Default \ --os-project-name admin --os-username admin token issue The port is wrong (or my installation is broken)-it should be 5000. - [ ] This is a doc addition request. - [X] I have a fix to the document that I can paste below including example: input and output. $ openstack --os-auth-url http://controller:5000/v3 \ --os-project-domain-name Default --os-user-domain-name Default \ --os-project-name admin --os-username admin token issue If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: on 2018-08-23 22:56 SHA: c767e254979c96858a81cc4bbe8d9773d4dd539b Source: https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/install/keystone-verify-rdo.rst URL: https://docs.openstack.org/keystone/rocky/install/keystone-verify-rdo.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1790148/+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 1790569] [NEW] resource was allocated repeatedly in some cases
Public bug reported: If rabbitMQ get error when creating a VM and resources has already allocated on node-1, the allocated resource can not be removed when rabbitMQ become OK and the VM has started on node-2 successfully. ** Affects: nova Importance: Undecided Assignee: fupingxie (fpxie) Status: New ** Changed in: nova Assignee: (unassigned) => fupingxie (fpxie) -- 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/1790569 Title: resource was allocated repeatedly in some cases Status in OpenStack Compute (nova): New Bug description: If rabbitMQ get error when creating a VM and resources has already allocated on node-1, the allocated resource can not be removed when rabbitMQ become OK and the VM has started on node-2 successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1790569/+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 1790143] Re: devstack/lib/ovs fails on fedora
Reviewed: https://review.openstack.org/598960 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=987e8b0cc4cc6a39ac0d4d32a47764f833c57a2e Submitter: Zuul Branch:master commit 987e8b0cc4cc6a39ac0d4d32a47764f833c57a2e Author: Lucas Alvares Gomes Date: Fri Aug 31 14:44:31 2018 +0100 Fix devstack/lib/ovs to run with Fedora 28 The patch is fixing two problems found when stacking DevStack on a Fedora 28 host OS. Problem 1: Account to the different patch versions between the kernel-devel and kernel-headers packages. Problem 2: Install the elfutils-libelf-devel package which is needed to compile OVS. For more a detailed information about each problem, check the bug linked in this patch. Closes-Bug: #1790143 Change-Id: Idfdee28124ff19272abcaaa3adade0435e3e474a ** 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/1790143 Title: devstack/lib/ovs fails on fedora Status in neutron: Fix Released Bug description: The devstack/lib/ovs module doesn't currently work on a Fedora 28 base host OS. Here's the failures I've bumped into when I've attempted to stack my DevStack cloud on a Fedora 28 host OS. Problem 1: NOTE: if kernel-devel-4.17.19_200.fc28.x86_64 or kernel-headers-4.17.19_200.fc28.x86_64 installation failed, please, provide a repository with the package, or yum update / reboot your machine to get the latest kernel. Last metadata expiration check: 0:25:41 ago on Fri 31 Aug 2018 09:13:54 AM UTC. No match for argument: kernel-devel-4.17.19_200.fc28.x86_64 Error: Unable to find a match YUM_FAILED 1 Last metadata expiration check: 0:25:43 ago on Fri 31 Aug 2018 09:13:54 AM UTC. No match for argument: kernel-devel-4.17.19_200.fc28.x86_64 Error: Unable to find a match YUM_FAILED 1 Error on exit World dumping... see /opt/stack/logs/worlddump-2018-08-31-093938.txt for details Apparently the kernel-devel and kernel-headers packages have different patch versions (all packages have been updated prior to starting devstack). See: kernel-devel: 4.17.19-200.fc28 kernel-headers: 4.17.19-1.fc28 We need to account for that. Problem 2: ln -s /opt/stack/ovs/datapath/linux/../linux/compat/utils.c ln -s /opt/stack/ovs/datapath/linux/../vport-geneve.c ln -s /opt/stack/ovs/datapath/linux/../vport-gre.c ln -s /opt/stack/ovs/datapath/linux/../vport-lisp.c ln -s /opt/stack/ovs/datapath/linux/../vport-stt.c ln -s /opt/stack/ovs/datapath/linux/../vport-vxlan.c make -C /lib/modules/4.17.19-200.fc28.x86_64/build M=/opt/stack/ovs/datapath/linux modules make[4]: Entering directory '/usr/src/kernels/4.17.19-200.fc28.x86_64' Makefile:974: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel". Stop. make[4]: Leaving directory '/usr/src/kernels/4.17.19-200.fc28.x86_64' make[3]: *** [Makefile.main:71: default] Error 2 make[3]: Leaving directory '/opt/stack/ovs/datapath/linux' make[2]: *** [Makefile:572: all-recursive] Error 1 make[2]: Leaving directory '/opt/stack/ovs/datapath' make[1]: *** [Makefile:5795: all-recursive] Error 1 make[1]: Leaving directory '/opt/stack/ovs' make: *** [Makefile:3411: all] Error 2 Error on exit World dumping... see /opt/stack/logs/worlddump-2018-08-31-104046.txt for details When compiling OVS. To fix this we just need to install the elfutils- libelf-devel package. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1790143/+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 1789074] Re: failed to boot guest with vnic_type direct when rx_queue_size and tx_queue_size are set
Reviewed: https://review.openstack.org/595592 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=622ebf2fab0a9bf75ee12437bef28f60e083f849 Submitter: Zuul Branch:master commit 622ebf2fab0a9bf75ee12437bef28f60e083f849 Author: Moshe Levi Date: Thu Aug 23 14:25:04 2018 +0300 libvirt: skip setting rx/tx queue sizes for not virto interfaces It seem that if driver name is None nova try to set rx_queue_size tx_queue_size config. (they define the virtio-net rx/tx queue sizes). Direct/Physical Direct vnic_types are not vritio so this kind of config is invalid and causing booting guest to failed. To avoid issues we skip such configuration these vnic_types Closes-Bug: #1789074 Change-Id: I45532896690ad9505f2b09c98d8d86b61bcfef2b ** 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/1789074 Title: failed to boot guest with vnic_type direct when rx_queue_size and tx_queue_size are set Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) rocky series: New Bug description: Description of problem: Nova compute forces the virtio RX/TX Queue Size also on SRIOV devices. This makes VM spawn to fail. The configurable RX/TX Queue Size code is similar all the way from OSP10 to OSP13, so it's possible the issue is present also on other releases. Version-Release number of selected component (if applicable): OSP13 z3 How reproducible: (quick and dirty way) Change nova config file # crudini --set /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt rx_queue_size 1024 # crudini --set /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt tx_queue_size 1024 # restart nova_compute container docker restart nova_compute # boot a VM with an SRIOV (PF or VF) interface Actual results: Nova add on the sriov port section rx_queue_size Expected results: Additional info: To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1789074/+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 1790498] [NEW] Error loading interface driver 'linuxbridge' when starting neutron-dhcp-agent
Public bug reported: When neutron-dhcp-server tries to start, the following logs are generated, then it will restart itself: http://paste.openstack.org/show/729337/ Openstack Release: Queens Neutron version: 12.0.3 (from Ubuntu cloud archive) OS: Ubuntu 16.04 Expected behaviour: Service starts, and DHCP leases are issued to running instances Actual behaviour: Service gets stuck in a restart loop, instances have no network connectivity due to not having an IP address ** Affects: neutron Importance: Undecided Status: New ** Tags: neutron neutron-dhcp-agent -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1790498 Title: Error loading interface driver 'linuxbridge' when starting neutron- dhcp-agent Status in neutron: New Bug description: When neutron-dhcp-server tries to start, the following logs are generated, then it will restart itself: http://paste.openstack.org/show/729337/ Openstack Release: Queens Neutron version: 12.0.3 (from Ubuntu cloud archive) OS: Ubuntu 16.04 Expected behaviour: Service starts, and DHCP leases are issued to running instances Actual behaviour: Service gets stuck in a restart loop, instances have no network connectivity due to not having an IP address To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1790498/+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 1790255] Re: Multiple IPs from ipv6 subnets on the associated network are allocated for port creation
** 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/1790255 Title: Multiple IPs from ipv6 subnets on the associated network are allocated for port creation Status in neutron: Invalid Bug description: From the spec[1], we will get one IP address from one of the v6 subnets. = Port-create operations without an explicit list of fixed IPs: There will be no change from the current design. When a port-create operation does not include an explicit list of fixed IPs, the following subnets on the associated network will be associated with the port: One subnet from all IPv4 subnets One subnet from all IPv6 DHCPv6-stateful subnets All SLAAC-enabled subnets === But actually we get multiple IPs from all of the v6 subnets. [1]https://specs.openstack.org/openstack/neutron-specs/specs/kilo/multiple-ipv6-prefixes.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1790255/+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 1790446] [NEW] Glance policy and image owner
Public bug reported: Trying to restrict glance to only allow editing/deleting a tenants own images. According the the docs, this should work. "is_owner": "tenant:%(owner)s", "modify_image": "rule:is_owner", "delete_image": "rule:is_owner", However, with this set, no user can then delete/modify images, as if the 'is_owner' rules never matches! With the default policy, a normal user is able to edit/delete public images that they dont own. If the public image is set as 'protected' they cant delete it. How are you meant to restrict actions to the owner of an image? ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1790446 Title: Glance policy and image owner Status in Glance: New Bug description: Trying to restrict glance to only allow editing/deleting a tenants own images. According the the docs, this should work. "is_owner": "tenant:%(owner)s", "modify_image": "rule:is_owner", "delete_image": "rule:is_owner", However, with this set, no user can then delete/modify images, as if the 'is_owner' rules never matches! With the default policy, a normal user is able to edit/delete public images that they dont own. If the public image is set as 'protected' they cant delete it. How are you meant to restrict actions to the owner of an image? To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1790446/+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 1790444] [NEW] Nova crashes when added new RPC interface
Public bug reported: For some reason I need to add a RPC interface to nova-compute. When I tested the new interface, I got this error: 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server [req-ff6e2750-98a2-4c13-95d0-548d9f66101d 3ff71b27e1e9446c8972c423e1b0d81e 123a45694881a8380faa009e752f - default default] Exception during message handling: AttributeError: 'SchedulerReportClient' object has no attribute 'obj_to_primitive' 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 268, in dispatch 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 195, in _do_dispatch 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server return self.serializer.serialize_entity(ctxt, result) 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server File "/openstack/lib/python2.7/site-packages/nova/rpc.py", line 130, in serialize_entity 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server return self._base.serialize_entity(context, entity) 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server File "/openstack/lib/python2.7/site-packages/nova/objects/base.py", line 237, in serialize_entity 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server entity) 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server File "/openstack/lib/python2.7/site-packages/nova/objects/base.py", line 223, in _process_iterable 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server for k, v in values.items()}) 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server File "/openstack/lib/python2.7/site-packages/nova/objects/base.py", line 223, in 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server for k, v in values.items()}) 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server File "/openstack/lib/python2.7/site-packages/nova/objects/base.py", line 240, in serialize_entity 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server entity = entity.obj_to_primitive() 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server File "/openstack/lib/python2.7/site-packages/nova/scheduler/client/__init__.py", line 39, in __run_method 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server return getattr(self.instance, __name)(*args, **kwargs) 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server AttributeError: 'SchedulerReportClient' object has no attribute 'obj_to_primitive' 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server The function`serialize_entity` in nova/nova/objects/base.py is: def serialize_entity(self, context, entity): if isinstance(entity, (tuple, list, set, dict)): entity = self._process_iterable(context, self.serialize_entity, entity) elif (hasattr(entity, 'obj_to_primitive') and callable(entity.obj_to_primitive)): entity = entity.obj_to_primitive() return entity (hasattr(entity, 'obj_to_primitive') and callable(entity.obj_to_primitive) are always return true because entity is a LazyLoader class and it implemented `__getattr__`. ** 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/1790444 Title: Nova crashes when added new RPC interface Status in OpenStack Compute (nova): New Bug description: For some reason I need to add a RPC interface to nova-compute. When I tested the new interface, I got this error: 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server [req-ff6e2750-98a2-4c13-95d0-548d9f66101d 3ff71b27e1e9446c8972c423e1b0d81e 123a45694881a8380faa009e752f - default default] Exception during message handling: AttributeError: 'SchedulerReportClient' object has no attribute 'obj_to_primitive' 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming 2018-09-03 02:23:56.870 70765 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message)
