[Yahoo-eng-team] [Bug 1804292] [NEW] Remove obsolete region policies from policy.v3cloudsample.json
Public bug reported: Once support for scope types landed in the region API policies, the policies in policy.v3cloudsample.json became obsolete [0]. We should add formal protection for the policies with enforce_scope = True in keystone.tests.unit.protection.v3 and remove the old policies from the v3 sample policy file. This will reduce confusion by having a true default policy for regions. [0] https://review.openstack.org/#/c/525698/ ** Affects: keystone Importance: Medium Status: Triaged ** Tags: policy system-scope ** Changed in: keystone Status: New => Triaged ** Changed in: keystone Importance: Undecided => Medium ** Tags added: policy system-scope -- 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/1804292 Title: Remove obsolete region policies from policy.v3cloudsample.json Status in OpenStack Identity (keystone): Triaged Bug description: Once support for scope types landed in the region API policies, the policies in policy.v3cloudsample.json became obsolete [0]. We should add formal protection for the policies with enforce_scope = True in keystone.tests.unit.protection.v3 and remove the old policies from the v3 sample policy file. This will reduce confusion by having a true default policy for regions. [0] https://review.openstack.org/#/c/525698/ To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1804292/+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 1804325] [NEW] InstanceNotFound traceback errors in n-api logs while polling for server delete
Public bug reported: As a result of this change: https://review.openstack.org/#/c/591658/ The nova-api logs now traceback InstanceNotFound errors when polling a server to be deleted, which is an expected situation and we shouldn't be logging errors in the API logs for that: http://logs.openstack.org/58/591658/22/check/tempest- full/04cf08b/controller/logs/screen-n-api.txt.gz?level=ERROR Nov 05 11:46:49.066760 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context [None req-8b6e5657-8ac9-4c33-9337-87c58b32fc7a tempest-DeleteServersAdminTestJSON-984972888 tempest-DeleteServersAdminTestJSON-984972888] Error gathering result from cell f40f1143-3d61-4e69-8377-a35e2fd47356: InstanceNotFound: Instance 45cbaca4-7e53-45df-99da-13674d0a241f could not be found. Nov 05 11:46:49.067002 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context Traceback (most recent call last): Nov 05 11:46:49.067223 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context File "/opt/stack/nova/nova/context.py", line 441, in gather_result Nov 05 11:46:49.067463 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context result = fn(cctxt, *args, **kwargs) Nov 05 11:46:49.067708 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context File "/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 184, in wrapper Nov 05 11:46:49.067932 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context result = fn(cls, context, *args, **kwargs) Nov 05 11:46:49.068173 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context File "/opt/stack/nova/nova/objects/instance.py", line 503, in get_by_uuid Nov 05 11:46:49.068408 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context use_slave=use_slave) Nov 05 11:46:49.068639 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 212, in wrapper Nov 05 11:46:49.068954 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context return f(*args, **kwargs) Nov 05 11:46:49.069175 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context File "/opt/stack/nova/nova/objects/instance.py", line 495, in _db_instance_get_by_uuid Nov 05 11:46:49.069399 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context columns_to_join=columns_to_join) Nov 05 11:46:49.069814 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context File "/opt/stack/nova/nova/db/api.py", line 758, in instance_get_by_uuid Nov 05 11:46:49.070036 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context return IMPL.instance_get_by_uuid(context, uuid, columns_to_join) Nov 05 11:46:49.070262 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 170, in wrapper Nov 05 11:46:49.070523 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context return f(*args, **kwargs) Nov 05 11:46:49.070766 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 257, in wrapped Nov 05 11:46:49.071002 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context return f(context, *args, **kwargs) Nov 05 11:46:49.071221 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 1845, in instance_get_by_uuid Nov 05 11:46:49.071517 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context columns_to_join=columns_to_join) Nov 05 11:46:49.071756 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 1854, in _instance_get_by_uuid Nov 05 11:46:49.071990 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context raise exception.InstanceNotFound(instance_id=uuid) Nov 05 11:46:49.07 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context InstanceNotFound: Instance 45cbaca4-7e53-45df-99da-13674d0a241f could not be found. Nov 05 11:46:49.072481 ubuntu-xenial-rax-dfw-329307 devstack@n-api.service[5952]: ERROR nova.context ** Affects: nova Importance: High Status: Triaged ** Tags: cells logging serviceability -- 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/1804325 Title: InstanceNotFound traceback errors in n-api logs while polling for server delete Status in OpenStack Compute
[Yahoo-eng-team] [Bug 1804289] [NEW] LOCALE_PATH causes message mo files not found
Public bug reported: Current default LOCALE_PATH is defined in openstack_dashboard/settings.py, like LOCALE_PATHS = [ 'horizon/locale', 'openstack_dashboard/locale' ] They work fine in the development environment. However if Horizon path installed in production is like /opt/stack/venv/horizon-20180814T161452Z/srv/www/openstack-dashboard/openstack_dashboard /opt/stack/venv/horizon-20180814T161452Z/lib/python2.7/site-packages/horizon/ when reset locale in the settings, the selected settings won't get saved and the translation won't happen. because of the relative locale path in settings.py, without overwriting the path in local_settings.py. /openstack_dashboard/dashboards/settings/user/forms.py check_for_language returns false if lang_code and translation.check_for_language(lang_code): response = functions.save_config_value( request, response, settings.LANGUAGE_COOKIE_NAME, lang_code) updated settings.py seem to fix the problem, however, still not clear what to do with horizon/locale Change LOCALE_PATHS = [ 'horizon/locale', # 'openstack_dashboard/locale', os.path.join(ROOT_PATH, "locale") ] ** Affects: horizon Importance: Undecided Assignee: Gloria Gu (gloria-gu) Status: New ** Changed in: horizon Assignee: (unassigned) => Gloria Gu (gloria-gu) -- 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/1804289 Title: LOCALE_PATH causes message mo files not found Status in OpenStack Dashboard (Horizon): New Bug description: Current default LOCALE_PATH is defined in openstack_dashboard/settings.py, like LOCALE_PATHS = [ 'horizon/locale', 'openstack_dashboard/locale' ] They work fine in the development environment. However if Horizon path installed in production is like /opt/stack/venv/horizon-20180814T161452Z/srv/www/openstack-dashboard/openstack_dashboard /opt/stack/venv/horizon-20180814T161452Z/lib/python2.7/site-packages/horizon/ when reset locale in the settings, the selected settings won't get saved and the translation won't happen. because of the relative locale path in settings.py, without overwriting the path in local_settings.py. /openstack_dashboard/dashboards/settings/user/forms.py check_for_language returns false if lang_code and translation.check_for_language(lang_code): response = functions.save_config_value( request, response, settings.LANGUAGE_COOKIE_NAME, lang_code) updated settings.py seem to fix the problem, however, still not clear what to do with horizon/locale Change LOCALE_PATHS = [ 'horizon/locale', # 'openstack_dashboard/locale', os.path.join(ROOT_PATH, "locale") ] To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1804289/+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 1798472] Re: Fullstack tests fails because process is not killed properly
Reviewed: https://review.openstack.org/618024 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9b23abbdb68f7e0c80c305ec1874281f6dea7e9e Submitter: Zuul Branch:master commit 9b23abbdb68f7e0c80c305ec1874281f6dea7e9e Author: Slawek Kaplonski Date: Wed Nov 14 21:31:04 2018 +0100 Add kill_timeout to AsyncProcess AsyncProcess.stop() method has now additional parameter kill_timeout. If this is set to some value different than None, eventlet.green.subprocess.Popen.wait() will be called with this timeout, so TimeoutExpired exception will be raised in case if process will not be killed for this "kill_timeout" time. In such case process will be killed "again" with SIGKILL signal to make sure that it is gone. This should fix problem with failing fullstack tests, when ovs_agent process is sometimes not killed and test timeout was reached in this wait() method. Change-Id: I1e12255e5e142c395adf4e67be9d9da0f7a3d4fd Closes-Bug: #1798472 ** 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/1798472 Title: Fullstack tests fails because process is not killed properly Status in neutron: Fix Released Bug description: Fullstack tests are failing quite often recently. There are different tests failed in CI runs but it looks that the culprit each time is the same. Some of processes spawned during the test is not killed properly, hangs and test got timeout exception. Examples: http://logs.openstack.org/97/602497/5/check/neutron-fullstack/f110a1f/logs/testr_results.html.gz http://logs.openstack.org/68/564668/7/check/neutron-fullstack- python36/c4223c2/logs/testr_results.html.gz In second example it looks that some process wasn't exited properly: http://logs.openstack.org/68/564668/7/check/neutron-fullstack-python36/c4223c2/logs/dsvm-fullstack-logs/TestOvsConnectivitySameNetwork.test_connectivity_GRE-l2pop-arp_responder,openflow-native_.txt.gz#_2018-10-16_02_43_49_755 and in this example it looks that it is openvswitch-agent: http://logs.openstack.org/68/564668/7/check/neutron-fullstack-python36/c4223c2/logs/dsvm-fullstack-logs/TestOvsConnectivitySameNetwork.test_connectivity_GRE-l2pop-arp_responder,openflow-native_/neutron-openvswitch-agent--2018-10-16--02-42-43-987526.txt.gz Looking at logs of this ovs agent it looks that there is no log like "Agent caught SIGTERM, quitting daemon loop." at the end To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1798472/+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 1804327] [NEW] occasional connection reset on SNATed after tcp retries
Public bug reported: When neutron ports are connected to DVR routers that are without floating ip, the traffic is going via SNAT on the network node. In some cases when the tcp connections that are nat'ed end up retransmitting, sometimes a packet is being retransmitted by the remote that is outside what the Linux kernel connection tracking considers part of valid tcp window. When this happens, the flow is receiving a RST, terminating the connection on the sender side, while leaving the receiver side (the neutron port attached VM) hanging. A similar issue is described elsewhere, e.g. https://github.com/docker/libnetwork/issues/1090 and the workaround documented there of setting ip_conntrack_tcp_be_liberal seems to help in avoiding conntrack to dismiss packets outside the observed tcp window size which lets the tcp retransmit logic to eventually recover the connection. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1804327 Title: occasional connection reset on SNATed after tcp retries Status in neutron: New Bug description: When neutron ports are connected to DVR routers that are without floating ip, the traffic is going via SNAT on the network node. In some cases when the tcp connections that are nat'ed end up retransmitting, sometimes a packet is being retransmitted by the remote that is outside what the Linux kernel connection tracking considers part of valid tcp window. When this happens, the flow is receiving a RST, terminating the connection on the sender side, while leaving the receiver side (the neutron port attached VM) hanging. A similar issue is described elsewhere, e.g. https://github.com/docker/libnetwork/issues/1090 and the workaround documented there of setting ip_conntrack_tcp_be_liberal seems to help in avoiding conntrack to dismiss packets outside the observed tcp window size which lets the tcp retransmit logic to eventually recover the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1804327/+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 1788631] Re: KeyError: 'used' security_group_rule quota missing 'used' key
Mark this as Won't Fix in horizon considering this only happens when the
deprecated neutron quota driver is used.
** Changed in: horizon
Milestone: stein-1 => None
** Changed in: horizon
Importance: Medium => Undecided
** Changed in: horizon
Status: In Progress => Won't Fix
** Changed in: horizon
Assignee: Corey Bryant (corey.bryant) => (unassigned)
** Tags removed: rocky-backport-potential
--
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/1788631
Title:
KeyError: 'used' security_group_rule quota missing 'used' key
Status in OpenStack neutron-api charm:
Fix Released
Status in OpenStack Dashboard (Horizon):
Won't Fix
Bug description:
On rocky rc1, after attempting to log in to the dashboard I hit:
Internal Server Error: /horizon/project/
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/django/core/handlers/exception.py",
line 41, in inner
response = get_response(request)
...
File "/usr/lib/python2.7/dist-packages/openstack_dashboard/usage/views.py",
line 163, in _process_chart_section
used = self.usage.limits[key]['used']
KeyError: 'used'
Full traceback: https://paste.ubuntu.com/p/RcMCjWs8HG/
From openstack_dashboard/usage/views.py:
def _process_chart_section(self, chart_defs):
charts = []
for t in chart_defs:
if t.quota_key not in self.usage.limits:
continue
key = t.quota_key
used = self.usage.limits[key]['used'] # <--- KeyError
quota = self.usage.limits[key]['quota']
Further debugging shows we're failing on key='security_group_rule'
chart_def=ChartDef(quota_key='security_group_rule', label=u'Security Group
Rules', used_phrase=None, filters=None)
self.usage.limits[key]={'quota': 100}
Notice there's no 'used' key in self.usage.limits. Compare that vs
'security_group' which has:
chart_def=ChartDef(quota_key='security_group', label=u'Security Groups',
used_phrase=None, filters=None)
self.usage.limits[key]={'available': 9, 'used': 1, 'quota': 10}
From openstack_dashboard/usage/quotas.py:
def tally(self, name, value):
"""Adds to the "used" metric for the given quota."""
value = value or 0 # Protection against None.
# Start at 0 if this is the first value.
if 'used' not in self.usages[name]:
self.usages[name]['used'] = 0
I haven't confirmed but it seems that tally does the initialization of
the 'used' key and for some reason that's not happening.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-api/+bug/1788631/+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 1792532] Re: can't update image metadata
*** This bug is a duplicate of bug 1789172 *** https://bugs.launchpad.net/bugs/1789172 ** This bug has been marked a duplicate of bug 1789172 Can't update image metadata in 14.0.0.0rc2.dev44 -- 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/1792532 Title: can't update image metadata Status in OpenStack Dashboard (Horizon): Confirmed Bug description: Horizon 14.0.0 Glance 17.0.0 Through openstack client everything is fine - i can change properties, but not in Horizon. Here is error from httpd/horizon log: [Fri Sep 14 10:21:53.412709 2018] [:error] [pid 1334] Traceback (most recent call last): [Fri Sep 14 10:21:53.412717 2018] [:error] [pid 1334] File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line 127, in _wrapped [Fri Sep 14 10:21:53.412723 2018] [:error] [pid 1334] data = function(self, request, *args, **kw) [Fri Sep 14 10:21:53.412730 2018] [:error] [pid 1334] File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/glance.py", line 110, in patch [Fri Sep 14 10:21:53.412736 2018] [:error] [pid 1334] **request.DATA['updated'] [Fri Sep 14 10:21:53.412742 2018] [:error] [pid 1334] File "/usr/share/openstack-dashboard/openstack_dashboard/api/glance.py", line 564, in image_update_properties [Fri Sep 14 10:21:53.412748 2018] [:error] [pid 1334] **kwargs) [Fri Sep 14 10:21:53.412754 2018] [:error] [pid 1334] File "/usr/lib/python2.7/site-packages/glanceclient/v2/images.py", line 343, in update [Fri Sep 14 10:21:53.412776 2018] [:error] [pid 1334] raise TypeError(encodeutils.exception_to_unicode(e)) [Fri Sep 14 10:21:53.412783 2018] [:error] [pid 1334] TypeError: Unable to set 'os_hidden' to 'False' To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1792532/+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 1804356] [NEW] Delete instance while resize instance to other compute nodes
Public bug reported: Description === Delete instance while instance resize to other compute_nodes. If the deletion action starts before instance's vm_state is "resized", source compute_node or dest compute_node will remain "_resize" directory. Steps to reproduce == 1) Create a new instance 2) Resize the instance 3) Delete the instance before vm_state is "resized" 4) Repeat 1 through 3 in a loop Expected result === Clean up instance related file and directory. Actual result = Some compute_node exist d0d3c75f-30a9-4c67-bcb5-c9f3f65d5a4e_resize directory. Environment === 1. Exact version of OpenStack you are running. See the following Openstack pike 2. Which hypervisor did you use? Libvirt + KVM 3. Which networking type did you use? OpenVSwitch nova-compute timed task "_cleanup_incomplete_migrations" only clean up instance with "error" state migration. ** 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/1804356 Title: Delete instance while resize instance to other compute nodes Status in OpenStack Compute (nova): New Bug description: Description === Delete instance while instance resize to other compute_nodes. If the deletion action starts before instance's vm_state is "resized", source compute_node or dest compute_node will remain "_resize" directory. Steps to reproduce == 1) Create a new instance 2) Resize the instance 3) Delete the instance before vm_state is "resized" 4) Repeat 1 through 3 in a loop Expected result === Clean up instance related file and directory. Actual result = Some compute_node exist d0d3c75f-30a9-4c67-bcb5-c9f3f65d5a4e_resize directory. Environment === 1. Exact version of OpenStack you are running. See the following Openstack pike 2. Which hypervisor did you use? Libvirt + KVM 3. Which networking type did you use? OpenVSwitch nova-compute timed task "_cleanup_incomplete_migrations" only clean up instance with "error" state migration. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1804356/+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 1799892] Re: Placement API crashes with 500s in Rocky upgrade with downed compute nodes
Reviewed: https://review.openstack.org/613305 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cdbedac920f407e102a6916f2d943e50a1b0943d Submitter: Zuul Branch:master commit cdbedac920f407e102a6916f2d943e50a1b0943d Author: Tetsuro Nakamura Date: Fri Oct 19 23:12:20 2018 +0900 Consider root id is None in the database case There are cases where ``root_provider_id`` of a resource provider is set to NULL just after it is upgraded to the Rocky release. In such cases getting allocation candidates raises a Keyerror. This patch fixes that bug for cases there is no sharing or nested providers in play. Change-Id: I9639d852078c95de506110f24d3f35e7cf5e361e Closes-Bug:#1799892 ** 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/1799892 Title: Placement API crashes with 500s in Rocky upgrade with downed compute nodes Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) rocky series: In Progress Bug description: I ran into this upgrading another environment into Rocky, deleted the problematic resource provider, but just ran into it again in another upgrade of another environment so there's something wonky. Here's the traceback: = 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap [req-8ad1c999-7646-4b0a-91c0-cd26a3581766 b61d42657d364008bfdc6fa715e67daf a894e8109af3430aa7ae03e0c49a0aa0 - default default] Placement API unexpected error: 19: KeyError: 19 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap Traceback (most recent call last): 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap File "/usr/lib/python2.7/site-packages/nova/api/openstack/placement/fault_wrap.py", line 40, in __call__ 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap return self.application(environ, start_response) 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap File "/usr/lib/python2.7/site-packages/webob/dec.py", line 129, in __call__ 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap resp = self.call_func(req, *args, **kw) 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap File "/usr/lib/python2.7/site-packages/webob/dec.py", line 193, in call_func 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap return self.func(req, *args, **kwargs) 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap File "/usr/lib/python2.7/site-packages/microversion_parse/middleware.py", line 80, in __call__ 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap response = req.get_response(self.application) 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap File "/usr/lib/python2.7/site-packages/webob/request.py", line 1313, in send 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap application, catch_exc_info=False) 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap File "/usr/lib/python2.7/site-packages/webob/request.py", line 1277, in call_application 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap app_iter = application(self.environ, start_response) 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap File "/usr/lib/python2.7/site-packages/nova/api/openstack/placement/handler.py", line 209, in __call__ 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap return dispatch(environ, start_response, self._map) 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap File "/usr/lib/python2.7/site-packages/nova/api/openstack/placement/handler.py", line 146, in dispatch 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap return handler(environ, start_response) 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap File "/usr/lib/python2.7/site-packages/webob/dec.py", line 129, in __call__ 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap resp = self.call_func(req, *args, **kw) 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap File "/usr/lib/python2.7/site-packages/nova/api/openstack/placement/wsgi_wrapper.py", line 29, in call_func 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap super(PlacementWsgify, self).call_func(req, *args, **kwargs) 2018-10-25 09:18:29.853 7431 ERROR nova.api.openstack.placement.fault_wrap File "/usr/lib/python2.7/site-packages/webob/dec.py", line 193, in call_func 2018-10-25
[Yahoo-eng-team] [Bug 1804347] Re: neutron can't loading metering driver iptables
** 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/1804347 Title: neutron can't loading metering driver iptables Status in neutron: Invalid Bug description: nf.d/common --config-dir /etc/neutron/conf.d/neutron-metering-agent --log-file /var/log/neutron/metering-agent.log setup_logging /usr/lib/python2.7/site-packages/neutron/common/config.py:104 2018-11-21 10:02:12.042 3717 INFO neutron.services.metering.agents.metering_agent [-] Loading Metering driver iptables 2018-11-21 10:02:12.042 3717 ERROR neutron.services.metering.drivers.utils [-] Error loading metering driver 'iptables' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1804347/+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 1804347] [NEW] neutron can't loading metering driver iptables
Public bug reported: nf.d/common --config-dir /etc/neutron/conf.d/neutron-metering-agent --log-file /var/log/neutron/metering-agent.log setup_logging /usr/lib/python2.7/site-packages/neutron/common/config.py:104 2018-11-21 10:02:12.042 3717 INFO neutron.services.metering.agents.metering_agent [-] Loading Metering driver iptables 2018-11-21 10:02:12.042 3717 ERROR neutron.services.metering.drivers.utils [-] Error loading metering driver 'iptables' ** Affects: neutron Importance: Undecided Assignee: caoyuan (cao-yuan) Status: New ** Changed in: neutron Assignee: (unassigned) => caoyuan (cao-yuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1804347 Title: neutron can't loading metering driver iptables Status in neutron: New Bug description: nf.d/common --config-dir /etc/neutron/conf.d/neutron-metering-agent --log-file /var/log/neutron/metering-agent.log setup_logging /usr/lib/python2.7/site-packages/neutron/common/config.py:104 2018-11-21 10:02:12.042 3717 INFO neutron.services.metering.agents.metering_agent [-] Loading Metering driver iptables 2018-11-21 10:02:12.042 3717 ERROR neutron.services.metering.drivers.utils [-] Error loading metering driver 'iptables' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1804347/+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 1795432] Re: neutron does not create the necessary iptables rules for dhcp agents when linuxbridge is used
After checking it with Rodolfo help, I can check that it is fixed in the lass queens(13) version. The fix that solve this issue is: https://review.openstack.org/#/c/568907/1 ** Changed in: neutron Status: New => 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/1795432 Title: neutron does not create the necessary iptables rules for dhcp agents when linuxbridge is used Status in neutron: Fix Released Bug description: Reproduction: Create a enviroment with controller and compute in different hosts: controller: [root@controller1 ~]# brctl show bridge name bridge id STP enabled interfaces brq37841a31-d78000.0a7e069299a3 no tap80087b5b-33 tap94526e09-2c vxlan-46 brqbab8fb94-c88000.1275449f51ef no eth3 tap4baecbed-83 tap8924b588-55 [root@controller1 ~]# ip netns qrouter-bcb8c407-ab4c-4916-89a5-d1ba8ac786ae (id: 2) qdhcp-37841a31-d744-4c9f-b084-37cfaafe71ca (id: 1) qdhcp-bab8fb94-c849-4c6c-ada7-98ec9bc33b87 (id: 0) Compute host: [root@compute1 ~]# brctl show bridge name bridge id STP enabled interfaces brq37841a31-d78000.5e530dd5073b no tap171ccdb9-66 vxlan-46 brqbab8fb94-c88000.525400fec4c7 no eth3 tap80b3e489-a6 tapfec914c0-0e virbr08000.525400ed85d9 yes virbr0-nic [root@compute1 ~]# virsh list IdName State 28instance-002f running 39instance-0044 running 41instance-0047 running Then when dhcp namespace and vms are in different hosts, dhcp traffic(in provider and selfservice network mode) is dropped in the controller bridge. Because no rule for permiting that the dhcp reply goes out of the controller: Iptables: -A neutron-filter-top -j neutron-linuxbri-local -A neutron-linuxbri-FORWARD -m physdev --physdev-out tap4baecbed-83 --physdev-is-bridged -m comment --comment "Accept all packets when port is trusted." -j ACCEPT -A neutron-linuxbri-FORWARD -m physdev --physdev-out tap80087b5b-33 --physdev-is-bridged -m comment --comment "Accept all packets when port is trusted." -j ACCEPT -A neutron-linuxbri-FORWARD -m physdev --physdev-out tap94526e09-2c --physdev-is-bridged -m comment --comment "Accept all packets when port is trusted." -j ACCEPT -A neutron-linuxbri-FORWARD -m physdev --physdev-out tap8924b588-55 --physdev-is-bridged -m comment --comment "Accept all packets when port is trusted." -j ACCEPT interfaces: [root@controller1 ~]# ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:d6:e9:8f brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:7a:23:a5 brd ff:ff:ff:ff:ff:ff 4: eth2: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:5f:07:d9 brd ff:ff:ff:ff:ff:ff 28: eth3: mtu 1500 qdisc pfifo_fast master brqbab8fb94-c8 state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:b2:b7:bc brd ff:ff:ff:ff:ff:ff 30: tap4baecbed-83@if2: mtu 1500 qdisc noqueue master brqbab8fb94-c8 state UP mode DEFAULT group default qlen 1000 link/ether c6:e3:d5:e8:49:78 brd ff:ff:ff:ff:ff:ff link-netnsid 0 31: brqbab8fb94-c8: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 12:75:44:9f:51:ef brd ff:ff:ff:ff:ff:ff 32: tap80087b5b-33@if2: mtu 1450 qdisc noqueue master brq37841a31-d7 state UP mode DEFAULT group default qlen 1000 link/ether 0a:7e:06:92:99:a3 brd ff:ff:ff:ff:ff:ff link-netnsid 1 33: vxlan-46: mtu 1450 qdisc noqueue master brq37841a31-d7 state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 92:6d:dd:cd:ab:43 brd ff:ff:ff:ff:ff:ff 34: brq37841a31-d7: mtu 1450 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 0a:7e:06:92:99:a3 brd ff:ff:ff:ff:ff:ff 35: tap94526e09-2c@if2: mtu 1450 qdisc noqueue master brq37841a31-d7 state UP mode DEFAULT group default qlen 1000 link/ether
[Yahoo-eng-team] [Bug 1757151] Re: Token and scope documentation needs an update
Reviewed: https://review.openstack.org/554727 Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=a383867cdb044bf5ea59fbc28afd9beefcb1ee33 Submitter: Zuul Branch:master commit a383867cdb044bf5ea59fbc28afd9beefcb1ee33 Author: Lance Bragstad Date: Tue Mar 20 22:52:27 2018 + Add scope documentation for service developers We have a document that attempts to help describe keystone concepts to other OpenStack developers. Now that we've added system scope to keystone, it makes sense to refresh this document and make it more helpful for services. This should help services consume various scopes to protect APIs at various levels (project, domain, system, et cetera). Change-Id: I1a92ed0b6bbba44d1050a857c3609d918bb25b86 Closes-Bug: 1757151 ** 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/1757151 Title: Token and scope documentation needs an update Status in OpenStack Identity (keystone): Fix Released Bug description: We have a document in our administrator guide that describes what tokens are, different scope types, and token providers [0]. While this is good information, we could elaborate on it a bit more to make the document even more useful: - Different types of scopes should have examples (e.g. project-scope == instance management) - Remove references to the UUID token provider, which has already been removed - Consider breaking the Authorization Scopes section out of the admin guide and into the user guide (it contains information that would be useful for end users as well as operators) We get comments from developers of other services about how scopes work (See Michael's comment in patch set 8 [1]). I think most people close to the system-scope work understand it because we've been exposed to the problem for so long and are familiar with the implementation. It'd be nice to work a fresh perspective into the Authorization Types document, or even have a separate document that explains the different scopes and how they relate to other services [2]. [0] https://docs.openstack.org/keystone/latest/admin/identity-tokens.html [1] https://review.openstack.org/#/c/523973/ [2] https://docs.openstack.org/keystone/latest/contributor/services.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1757151/+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 1804372] [NEW] Linux, Ubuntu, 18.04, CI, NB13, SUT can't connect to network by Salomon Dock's LOM Port.(FR:10%)
Public bug reported: Description: Connect a Single-c Salomin Dock to SUT, connect a LAN cable to dock't LOM port, the RJ45 port left LED is blink, but right LED not turn on, SUT can't connect to netwok, show cable unplugged. Unplug dock AC adapter, replug it, can connect to network. Expected Behavior: SUT can connect to network by Salomon Dock's LOM Port normally. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS: CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:0.0.7.0 Note: 1. VP on TBT/None TBT config 2. VNP on IE-Dock 3. VP on TBT Salomon Dock: DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 Cross Platform: N/A Test case: [CSV-TC-5166][WIS-TC-4406] Linux_NB_Salomon-Wired-Dock-The "Programmable MAC Address" Test step:8 Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04; 2. Boot to OS, connect a Salomon Dock to SUT; 3. Connect a LAN cable to Dock't LOM port, the RJ45 port left LED is blink, but right LED not turn on; 4. SUT can't connect tp netwok and show Cable unplugged.>problem(refer to pic) 5. Unplug dock AC adapter, replug it, can connect to network. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "IMG_no network.jpg" https://bugs.launchpad.net/bugs/1804372/+attachment/5214820/+files/IMG_no%20network.jpg -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804372 Title: Linux, Ubuntu, 18.04, CI, NB13, SUT can't connect to network by Salomon Dock's LOM Port.(FR:10%) Status in Glance: New Bug description: Description: Connect a Single-c Salomin Dock to SUT, connect a LAN cable to dock't LOM port, the RJ45 port left LED is blink, but right LED not turn on, SUT can't connect to netwok, show cable unplugged. Unplug dock AC adapter, replug it, can connect to network. Expected Behavior: SUT can connect to network by Salomon Dock's LOM Port normally. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS: CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:0.0.7.0 Note: 1. VP on TBT/None TBT config 2. VNP on IE-Dock 3. VP on TBT Salomon Dock: DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 Cross Platform: N/A Test case: [CSV-TC-5166][WIS-TC-4406] Linux_NB_Salomon-Wired-Dock-The "Programmable MAC Address" Test step:8 Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04; 2. Boot to OS, connect a Salomon Dock to SUT; 3. Connect a LAN cable to Dock't LOM port, the RJ45 port left LED is blink, but right LED not turn on; 4. SUT can't connect tp netwok and show Cable unplugged.>problem(refer to pic) 5. Unplug dock AC adapter, replug it, can connect to network. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804372/+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 1804374] [NEW] in Create network page, the step page content disappears
Public bug reported: Steps： 1、Click the Create Network button 2、Enter 123 in the Allocation Pools 3、Then click on the created button 4、When the page returns to the Create Network page, click the Back button and then click the Next button, you will find that the page content disappears. ** Affects: horizon Importance: Undecided Assignee: pengyuesheng (pengyuesheng) Status: In Progress -- 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/1804374 Title: in Create network page, the step page content disappears Status in OpenStack Dashboard (Horizon): In Progress Bug description: Steps： 1、Click the Create Network button 2、Enter 123 in the Allocation Pools 3、Then click on the created button 4、When the page returns to the Create Network page, click the Back button and then click the Next button, you will find that the page content disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1804374/+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 1804376] [NEW] Instance Action Log miss some translation of actions
Public bug reported: Access Project->Compute->Instances->[detailed_page]->Action Log; The Action column misses some actions translation, like shelve/unshelve/migrate. ** Affects: horizon Importance: Undecided Status: New -- 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/1804376 Title: Instance Action Log miss some translation of actions Status in OpenStack Dashboard (Horizon): New Bug description: Access Project->Compute->Instances->[detailed_page]->Action Log; The Action column misses some actions translation, like shelve/unshelve/migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1804376/+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 1804073] Re: Keystone fails to log policy target data
Added Oslo.policy to the bug report, as this is going to be an issue across all of the projects. Barbican, especially, needs target info, but the same is true for anything that enforces the scope check. ** Also affects: oslo.policy Importance: Undecided Status: New -- 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/1804073 Title: Keystone fails to log policy target data Status in OpenStack Identity (keystone): New Status in oslo.policy: New Bug description: The Oslo Policy Enforcer requires 3 pieces of run-time information in addition to the policy rules to issue a RBAC decision: 1) the name of the rule to be evaluated (called target in the oslo-policy doc) 2) the auth context (called credentials in the oslo-policy doc) 3) the target data (resource data relevant to the rule) If you are trying to debug policy enforcement or simply validate your policy works as expect one can use the oslopolicy-checker tool. But the oslopolicy-checker tool needs the *exact* same data keystone passes to the policy enforcement engine. The fact the target data needs to be logged but isn't is captured in this comment from Henry Nash in authorize.py # TODO(henry-nash) need to log the target attributes as well https://github.com/openstack/keystone/blob/stable/rocky/keystone/common/authorization.py#L139 But that is not the best location to log, the best place is where oslo.policy is called to evaluate a policy rule, that occurs in Policy.enforce() in keystone/policy/backends/policy.py https://github.com/openstack/keystone/blob/stable/rocky/keystone/policy/backends/rules.py#L29:#L34 Here we can see it logs the rule name (e.g. action) and the auth context (credentials) msg = 'enforce %(action)s: %(credentials)s' but the target data is not logged. Besides the fact the target data is not logged is the fact the logging relies on Python's str() method to convert an object into a string representation. This has two problems, 1) all contained objects must also have __str__() methods that fully log their contents, 2) the formatting is often in Python's "representation" style which only humans and Python can parse. Since both the credential and targets parameters to the enforce method are dicts (with arbitrary complex nesting) and the fact JSON is the data format we use for data exchange and the format used by oslopolicy-checker it makes sense to log the enforcement parameters in JSON format. This way no data is lost (because there wasn't an appropriate formatter for the object) and it makes it easy import the data to another tool (again, without loss of data). To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1804073/+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 1804217] [NEW] Linux, Ubuntu, 18.04, CI, NB13, 4k movie can't play smoothly with fast-forward and rewind.(FR:100%)
Public bug reported: Description: While the 4K capable movie is playing, perform fast forward and backward, the video is not smoothly. Expected Behavior: Play video without any problem. Severity: Sev-2 P3 C3 L3 Test Environment: 1. Project: Northbay 13 SKU9 2. BIOS: 0.4.0 3. OS: CI Ubuntu 18.04 4. Player: Videos Note: 1. VP on All Northbay TBT SKU Cross Platform: N/A Test case: CSV-TC-4603[WIS-TC-4189] Linux_USB - USB Type-C With Dell Ultra-HD 4K Display/Monitor Test (HDMI) step:7 Steps to Reproduce: 1. Install ubuntu 18.4 OS; 2. Check to make sure that the SUT is up and running without any problems; 3. Play a 4K capable movie on the SUT, While the 4K capable movie is playing, perform fast forward and backward, the video will be nonfluency.-->problem(refer tp mp4) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "nonfluency.mp4" https://bugs.launchpad.net/bugs/1804217/+attachment/5214499/+files/nonfluency.mp4 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804217 Title: Linux, Ubuntu, 18.04, CI, NB13, 4k movie can't play smoothly with fast-forward and rewind.(FR:100%) Status in Glance: New Bug description: Description: While the 4K capable movie is playing, perform fast forward and backward, the video is not smoothly. Expected Behavior: Play video without any problem. Severity: Sev-2 P3 C3 L3 Test Environment: 1. Project: Northbay 13 SKU9 2. BIOS: 0.4.0 3. OS: CI Ubuntu 18.04 4. Player: Videos Note: 1. VP on All Northbay TBT SKU Cross Platform: N/A Test case: CSV-TC-4603[WIS-TC-4189] Linux_USB - USB Type-C With Dell Ultra-HD 4K Display/Monitor Test (HDMI) step:7 Steps to Reproduce: 1. Install ubuntu 18.4 OS; 2. Check to make sure that the SUT is up and running without any problems; 3. Play a 4K capable movie on the SUT, While the 4K capable movie is playing, perform fast forward and backward, the video will be nonfluency.-->problem(refer tp mp4) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804217/+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 1804220] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Can't switch display mode with lid closed when press"Win+P"(FR:100%)
Public bug reported: Description: Connect a BME Dock to SUT, Connect a HDMI/DP/VGA Monitor to BME Dock, Connect USB KB to BME DOCK.Then closed the SUT lid ,And press"Win+P"to switch dispaly mode,Find can't switch mode. Expected Behavior: Switch mode no any problem when when connected to three display. Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 4.DELL BME DOCK-114:REV-A05 FW:1.0.0 5.Display1:DELL SE2216H Display2:DELL S2718HN/HX Display3:DELL U2917W Note: 1. VP on External only mode 2. VP on connect two and one external monitor. Cross Platform: N/A Test case: CSV-TC-4664[WIS-TC-4210] Linux_NB_BME-Wired-Dock-The Docked SUT "Power Management (S3)" Test step:32step:32 Steps to Reproduce: 1.Connect a BME Dock to SUT, Connect a HDMI/DP/VGA Monitor to BME Dock, 2.Connect USB KB to BME DOCK.Then closed the SUT lid ,And press"Win+P"to switch dispaly mode,Find can't switch mode.-->problem ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-cantswitch.4210-20181120012419.tar.xz.md5" https://bugs.launchpad.net/bugs/1804220/+attachment/5214507/+files/sosreport-cantswitch.4210-20181120012419.tar.xz.md5 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804220 Title: Linux, Ubuntu, 18.04, CI, NB13, Can't switch display mode with lid closed when press"Win+P"(FR:100%) Status in Glance: New Bug description: Description: Connect a BME Dock to SUT, Connect a HDMI/DP/VGA Monitor to BME Dock, Connect USB KB to BME DOCK.Then closed the SUT lid ,And press"Win+P"to switch dispaly mode,Find can't switch mode. Expected Behavior: Switch mode no any problem when when connected to three display. Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 4.DELL BME DOCK-114:REV-A05 FW:1.0.0 5.Display1:DELL SE2216H Display2:DELL S2718HN/HX Display3:DELL U2917W Note: 1. VP on External only mode 2. VP on connect two and one external monitor. Cross Platform: N/A Test case: CSV-TC-4664[WIS-TC-4210] Linux_NB_BME-Wired-Dock-The Docked SUT "Power Management (S3)" Test step:32step:32 Steps to Reproduce: 1.Connect a BME Dock to SUT, Connect a HDMI/DP/VGA Monitor to BME Dock, 2.Connect USB KB to BME DOCK.Then closed the SUT lid ,And press"Win+P"to switch dispaly mode,Find can't switch mode.-->problem To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804220/+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 1804223] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Can't switch to mirror mode when connected to three display(FR:100%)
Public bug reported: Description: Connect a BME Dock to SUT, connect a HDMI/DP/VGA Monitor to BME Dock, in Displays setting, turn on all External monitor and turn off the Built-in display, then Press"Win+P"to switch dispaly mode, find can't switch to mirror mode. Expected Behavior: Switch mode no any problem when when connected to three display. Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 4.DELL BME DOCK-114:REV-A05 FW:1.0.0 5.Display1:DELL SE2216H Display2:DELL S2718HN/HX Display3:DELL U2917W Note: 1. VP on External only mode 2. VNP on Built-in Only mode 3. VNP on connect two or one external monitor. Cross Platform: N/A Test case: CSV-TC-4664[WIS-TC-4210] Linux_NB_BME-Wired-Dock-The Docked SUT "Power Management (S3)" Test step:32 Steps to Reproduce: 1.Connect a BME Dock to SUT, Connect a HDMI/DP/VGA Monitor to BME Dock, 2.Open Displays setting,Turn on all External monitor ,And turn off the Built-in display . 3.Then Press"Win+P"to switch dispaly mode,Find can't switch to mirror mode. -->problem(refer to mp4) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "video_20181120_131710.mp4" https://bugs.launchpad.net/bugs/1804223/+attachment/5214508/+files/video_20181120_131710.mp4 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804223 Title: Linux, Ubuntu, 18.04, CI, NB13, Can't switch to mirror mode when connected to three display(FR:100%) Status in Glance: New Bug description: Description: Connect a BME Dock to SUT, connect a HDMI/DP/VGA Monitor to BME Dock, in Displays setting, turn on all External monitor and turn off the Built-in display, then Press"Win+P"to switch dispaly mode, find can't switch to mirror mode. Expected Behavior: Switch mode no any problem when when connected to three display. Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 4.DELL BME DOCK-114:REV-A05 FW:1.0.0 5.Display1:DELL SE2216H Display2:DELL S2718HN/HX Display3:DELL U2917W Note: 1. VP on External only mode 2. VNP on Built-in Only mode 3. VNP on connect two or one external monitor. Cross Platform: N/A Test case: CSV-TC-4664[WIS-TC-4210] Linux_NB_BME-Wired-Dock-The Docked SUT "Power Management (S3)" Test step:32 Steps to Reproduce: 1.Connect a BME Dock to SUT, Connect a HDMI/DP/VGA Monitor to BME Dock, 2.Open Displays setting,Turn on all External monitor ,And turn off the Built-in display . 3.Then Press"Win+P"to switch dispaly mode,Find can't switch to mirror mode. -->problem(refer to mp4) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804223/+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 1804174] [NEW] horizon fails if the policy file is not found
Public bug reported: Internal Server Error: /project/ Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 217, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 215, in _get_response response = response.render() File "/usr/lib/python2.7/site-packages/django/template/response.py", line 107, in render self.content = self.rendered_content File "/usr/lib/python2.7/site-packages/django/template/response.py", line 84, in rendered_content content = template.render(context, self._request) File "/usr/lib/python2.7/site-packages/django/template/backends/django.py", line 66, in render return self.template.render(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 207, in render return self._render(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/lib/python2.7/site-packages/django/template/loader_tags.py", line 177, in render return compiled_parent._render(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/lib/python2.7/site-packages/django/template/loader_tags.py", line 72, in render result = block.nodelist.render(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/lib/python2.7/site-packages/django/template/loader_tags.py", line 72, in render result = block.nodelist.render(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/lib/python2.7/site-packages/django/template/loader_tags.py", line 216, in render return template.render(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 209, in render return self._render(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/lib/python2.7/site-packages/django/template/library.py", line 225, in render _dict = self.func(*resolved_args, **resolved_kwargs) File "/usr/lib/python2.7/site-packages/horizon/templatetags/horizon.py", line 74, in horizon_nav panel.can_access(context)): File "/usr/lib/python2.7/site-packages/horizon/base.py", line 149, in can_access return self.allowed(context) File "/usr/lib/python2.7/site-packages/horizon/base.py", line 158, in allowed return self._can_access(context['request']) File "/usr/lib/python2.7/site-packages/horizon/base.py", line 170, in _can_access if policy_check(rule_param, request): File "/usr/lib/python2.7/site-packages/openstack_auth/policy.py", line 155, in check enforcer = _get_enforcer() File "/usr/lib/python2.7/site-packages/openstack_auth/policy.py", line 64, in _get_enforcer if os.path.isfile(enforcer.policy_path): File "/usr/lib64/python2.7/genericpath.py", line 37, in isfile st = os.stat(path) TypeError: coercing to Unicode: need string or buffer, NoneType found Internal Server Error: /project/ oslo_policy.policy_file can be None which causes this problem ** Affects: horizon Importance: Undecided Assignee: sumitjami (sumitjami) Status: In Progress -- 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/1804174 Title: horizon fails if the policy file is not found Status in OpenStack Dashboard (Horizon): In Progress
[Yahoo-eng-team] [Bug 1804191] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Touch can't open the "show applicotions" setting(FR:100%)
Public bug reported: Description: Touch can't open the "show applicotions" setting Expected Behavior: Touch can be open the "show applicotions" setting Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 SKU7 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Touch LCD :FHD OTP HHYCY Note: 1.VP on LCD MC2FY 2.VNP on use Touchpad Cross Platform: N/A Test case: CSV-TC-5001[WIS-TC-4402] Linux_NB_Touchscreen - Basic Functionality Test step:5 Steps to Reproduce: 1.Install Ubuntu 18.4 OS. 2.Boot to OS,and Check that touch functions 3.Touch " the "show applicotions" in lower left corner of screen .Find can't be open-->problem(refer to mp4) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-Ubuntu18.04LTSCILatitude1-5380.tar11.xz" https://bugs.launchpad.net/bugs/1804191/+attachment/5214460/+files/sosreport-Ubuntu18.04LTSCILatitude1-5380.tar11.xz ** Tags added: north-bay-13 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804191 Title: Linux, Ubuntu, 18.04, CI, NB13, Touch can't open the "show applicotions" setting(FR:100%) Status in Glance: New Bug description: Description: Touch can't open the "show applicotions" setting Expected Behavior: Touch can be open the "show applicotions" setting Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 SKU7 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Touch LCD :FHD OTP HHYCY Note: 1.VP on LCD MC2FY 2.VNP on use Touchpad Cross Platform: N/A Test case: CSV-TC-5001[WIS-TC-4402] Linux_NB_Touchscreen - Basic Functionality Test step:5 Steps to Reproduce: 1.Install Ubuntu 18.4 OS. 2.Boot to OS,and Check that touch functions 3.Touch " the "show applicotions" in lower left corner of screen .Find can't be open-->problem(refer to mp4) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804191/+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 1804190] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Can't copy file to USB-C v3.1 Storage if change port on Salomon.(FR:3/5times)
Public bug reported: Description: 1. Connect a Salomon Dock to SUT, Connect a Type-c USB 3.1(Gen1) storage Device on Salomon front Type-c Port, copy some file from PC to it, after complete transfer, then unplug to another Type-c Port on Salomon Dock, Find Can't copy file from PC to Storage device. 2.Unplug/Plug Salomon Dock from SUT, the file can be copy from PC to Memory Key again. Expected Behavior: Type-c USB 3.1 storage Can copy file after change Type-c port on Salomon. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 5. Storage device: Sandisk USB3.1 Type-c Key-17 Note: 1. VP on USB3.1 / 480G SanDisk SSD-26 Cross Platform: N/A Test case: [CSV-TC-5195][WIS-TC-4408] Linux_NB_Salomon-Wired-Dock-The "USB-C" Connectors/Ports Test with "USB-C v3.1 (Gen-2) Storage Devices" step:10/11 Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, Connect a Salomon Dock to SUT; 3. Connect a Type-c USB 3.1(Gen1) Storage Devices on Salomon front Type-c Port. 4. Copy some file from PC to it. 5. Then unplug to another Type-c Port on Salomon Dock, find Can't copy file from PC to Storage device.>problem(refer to Video) 6. Unplug/Plug Salomon Dock from SUT, the file can be copy to Storage Devices again. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "VID_Can't copy file.mp4" https://bugs.launchpad.net/bugs/1804190/+attachment/5214458/+files/VID_Can%27t%20copy%20file.mp4 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804190 Title: Linux, Ubuntu, 18.04, CI, NB13, Can't copy file to USB-C v3.1 Storage if change port on Salomon.(FR:3/5times) Status in Glance: New Bug description: Description: 1. Connect a Salomon Dock to SUT, Connect a Type-c USB 3.1(Gen1) storage Device on Salomon front Type-c Port, copy some file from PC to it, after complete transfer, then unplug to another Type-c Port on Salomon Dock, Find Can't copy file from PC to Storage device. 2.Unplug/Plug Salomon Dock from SUT, the file can be copy from PC to Memory Key again. Expected Behavior: Type-c USB 3.1 storage Can copy file after change Type-c port on Salomon. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 5. Storage device: Sandisk USB3.1 Type-c Key-17 Note: 1. VP on USB3.1 / 480G SanDisk SSD-26 Cross Platform: N/A Test case: [CSV-TC-5195][WIS-TC-4408] Linux_NB_Salomon-Wired-Dock-The "USB-C" Connectors/Ports Test with "USB-C v3.1 (Gen-2) Storage Devices" step:10/11 Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, Connect a Salomon Dock to SUT; 3. Connect a Type-c USB 3.1(Gen1) Storage Devices on Salomon front Type-c Port. 4. Copy some file from PC to it. 5. Then unplug to another Type-c Port on Salomon Dock, find Can't copy file from PC to Storage device.>problem(refer to Video) 6. Unplug/Plug Salomon Dock from SUT, the file can be copy to Storage Devices again. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804190/+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 1804192] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Network icon show "?" after connected LAN/WLAN.(FR:2/10times)
Public bug reported: Description: Connect a LAN/WLAN to SUT, the Network icon show "?" all the time on the right top corner,but SUT can surf the internet normally. Expected Behavior: Connect a LAN/WLAN to SUT, the Network icon should show Connected on the right top corner. Severity: Sev-3 P3 C3 L3 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 Note: 1. VP on LAN 2. VP on WLAN Cross Platform: N/A Test case: [CSV-TC-4572][WIS-TC-4167] Linux_Wired - Basic Functionality Test step:11 Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, Connect a Lan Cable to SUT. 3. Network icon show "?" after connected.>problem1(refer to pic) 4. Connect a WLAN to SUT, Network icon show "?" after connected.>problem2 ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "network icon.jpg" https://bugs.launchpad.net/bugs/1804192/+attachment/5214462/+files/network%20icon.jpg ** Description changed: Description: - Connect a LAN/WLAN to SUT, the Network icon show "?" all the time on the right top corner,but SUT can surf the internet normally.(FR:2/10times) + Connect a LAN/WLAN to SUT, the Network icon show "?" all the time on the right top corner,but SUT can surf the internet normally. Expected Behavior: Connect a LAN/WLAN to SUT, the Network icon should show Connected on the right top corner. Severity: Sev-3 P3 C3 L3 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 Note: 1. VP on LAN 2. VP on WLAN Cross Platform: N/A Test case: [CSV-TC-4572][WIS-TC-4167] Linux_Wired - Basic Functionality Test step:11 - + Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, Connect a Lan Cable to SUT. 3. Network icon show "?" after connected.>problem1(refer to pic) 4. Connect a WLAN to SUT, Network icon show "?" after connected.>problem2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804192 Title: Linux, Ubuntu, 18.04, CI, NB13, Network icon show "?" after connected LAN/WLAN.(FR:2/10times) Status in Glance: New Bug description: Description: Connect a LAN/WLAN to SUT, the Network icon show "?" all the time on the right top corner,but SUT can surf the internet normally. Expected Behavior: Connect a LAN/WLAN to SUT, the Network icon should show Connected on the right top corner. Severity: Sev-3 P3 C3 L3 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 Note: 1. VP on LAN 2. VP on WLAN Cross Platform: N/A Test case: [CSV-TC-4572][WIS-TC-4167] Linux_Wired - Basic Functionality Test step:11 Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, Connect a Lan Cable to SUT. 3. Network icon show "?" after connected.>problem1(refer to pic) 4. Connect a WLAN to SUT, Network icon show "?" after connected.>problem2 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804192/+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 1804205] [NEW] libvirtError: operation failed: domain 'instance-00000003' already exists with uuid e017717e-9647-4740-8efa-4ec2aa25f35c
Public bug reported: Description == Testing the Nova component, I figured out that many times the instances (servers) were not created or instantiated because the following error: libvirtError: operation failed: domain 'instance-0003' already exists with uuid e017717e-9647-4740-8efa-4ec2aa25f35c I don't understand how that is possible. There exist a way of circumventing that? Can OpenStack solve it before creating an instance? Worth noticing that I ran the unstack script before starting creating new instances, so it is a residual instance from another time I ran stack script. Steps to Reproduce = I don't know. Expected Result == Not sure, but I think that the system needs to be prepared against this situation. The worst case is the scenario where it is not possible to create instances because a range of names is being used. Actual Result Many instances been set to error state because a name of an existent instance already exists. Environment == Devstack/Queens/Stable. Ubuntu 16.04. Logs & Configs Attached. ** 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/1804205 Title: libvirtError: operation failed: domain 'instance-0003' already exists with uuid e017717e-9647-4740-8efa-4ec2aa25f35c Status in OpenStack Compute (nova): New Bug description: Description == Testing the Nova component, I figured out that many times the instances (servers) were not created or instantiated because the following error: libvirtError: operation failed: domain 'instance-0003' already exists with uuid e017717e-9647-4740-8efa-4ec2aa25f35c I don't understand how that is possible. There exist a way of circumventing that? Can OpenStack solve it before creating an instance? Worth noticing that I ran the unstack script before starting creating new instances, so it is a residual instance from another time I ran stack script. Steps to Reproduce = I don't know. Expected Result == Not sure, but I think that the system needs to be prepared against this situation. The worst case is the scenario where it is not possible to create instances because a range of names is being used. Actual Result Many instances been set to error state because a name of an existent instance already exists. Environment == Devstack/Queens/Stable. Ubuntu 16.04. Logs & Configs Attached. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1804205/+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 1804231] [NEW] Linux, Ubuntu, 18.04, CI, NB13, After changing level, run "dmesg", show errors. (FR:100%)
Public bug reported: Description: Run 'dmesg -T | grep "error" ' will show some error messages after change level 5 to level 3. Expected Behavior: No issue occured after change level. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 SKU9 2. BIOS: 0.4.0 3. OS: CI Ubuntu 18.04 Note: 1. VP on all North Bay13 SKU 2. VP on change level 3 to level 5 3. VP on 'shutdown -h now' command Cross Platform: N/A Test case: [CSV-TC-4575][WIS-TC-4170] Linux_ACPI - Power Cycle Testing step2 Steps to Reproduce: 1. Boot to Ubuntu OS and open Terminal via "Ctrl + Alt + T". 2. Change level 5 to level 3 via "systemctl set-default multi-user.target" command. 3. Reboot to level 3. 4. Run "dmesg -T | grep "error" command will find some error messages.--->Problem(refer to PIC). ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "Level3.jpg" https://bugs.launchpad.net/bugs/1804231/+attachment/5214516/+files/Level3.jpg -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804231 Title: Linux, Ubuntu, 18.04, CI, NB13, After changing level, run "dmesg", show errors. (FR:100%) Status in Glance: New Bug description: Description: Run 'dmesg -T | grep "error" ' will show some error messages after change level 5 to level 3. Expected Behavior: No issue occured after change level. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 SKU9 2. BIOS: 0.4.0 3. OS: CI Ubuntu 18.04 Note: 1. VP on all North Bay13 SKU 2. VP on change level 3 to level 5 3. VP on 'shutdown -h now' command Cross Platform: N/A Test case: [CSV-TC-4575][WIS-TC-4170] Linux_ACPI - Power Cycle Testing step2 Steps to Reproduce: 1. Boot to Ubuntu OS and open Terminal via "Ctrl + Alt + T". 2. Change level 5 to level 3 via "systemctl set-default multi-user.target" command. 3. Reboot to level 3. 4. Run "dmesg -T | grep "error" command will find some error messages.--->Problem(refer to PIC). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804231/+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 1804214] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Can't detect Salomon TBT3 Dock after hot plug/unplug(.FR:2/10 times)
Public bug reported: Description: Boot to OS and connect Salomon Dock to SUT. Plugin the USB keyboard, USB Mouse, "USB v3.0 Storage Memory Keys", "USB Type-C v3.1 Storage Memory Keys",external stereo speakers, "Thunderbolt-3 HDD/SSD", two external DP monitors, external HDMI monitor, Ethernet cable to Salomon Dock. Then hot plug Salomon Dock connector cable then plug in, find SUT can't detect Salomon TBT3 cable dock. Restart SUT with Salomon dock connected, salomon TBT3 dock can be detected again. Expected Behavior: Salomon TBT3 dock can be detected successfully after hot plug/unplug. Severity: Sev-2 P3 C3 L2 Test environment: 1. Project:Northbay 13 2. BIOS:0.4.0 3. Driver list:V27 4. OS:CI Ubuntu 18.04 5. Dock info: DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 Notes: 1. VP on Northbay TBT sku 2. VNP on Salomon single-c cable Dock 3. VP on BME dock(REV-A05 Dock-114 FW:0.1.17) Cross Platform: NA Test case: [CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Plug/Unplug" Test Step32 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS and connect Salomon Dock to SUT. 3. Plugin the USB keyboard, USB Mouse, "USB v3.0 Storage Memory Keys", "USB Type-C v3.1 Storage Memory Keys",external stereo speakers, "Thunderbolt-3 HDD/SSD", two external DP monitors, external HDMI monitor, Ethernet cable to Salomon Dock. 4. Then hot plug Salomon Dock connector cable then plug in, find SUT can't detect Salomon TBT3 cable dock.-->Problem(Refer to video) 5. Restart SUT with Salomon dock connected, salomon TBT3 dock can be detected again. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-Generic.4407-201811191.tar.xz" https://bugs.launchpad.net/bugs/1804214/+attachment/5214498/+files/sosreport-Generic.4407-201811191.tar.xz -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804214 Title: Linux, Ubuntu, 18.04, CI, NB13, Can't detect Salomon TBT3 Dock after hot plug/unplug(.FR:2/10 times) Status in Glance: New Bug description: Description: Boot to OS and connect Salomon Dock to SUT. Plugin the USB keyboard, USB Mouse, "USB v3.0 Storage Memory Keys", "USB Type-C v3.1 Storage Memory Keys",external stereo speakers, "Thunderbolt-3 HDD/SSD", two external DP monitors, external HDMI monitor, Ethernet cable to Salomon Dock. Then hot plug Salomon Dock connector cable then plug in, find SUT can't detect Salomon TBT3 cable dock. Restart SUT with Salomon dock connected, salomon TBT3 dock can be detected again. Expected Behavior: Salomon TBT3 dock can be detected successfully after hot plug/unplug. Severity: Sev-2 P3 C3 L2 Test environment: 1. Project:Northbay 13 2. BIOS:0.4.0 3. Driver list:V27 4. OS:CI Ubuntu 18.04 5. Dock info: DOCK-126REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 Notes: 1. VP on Northbay TBT sku 2. VNP on Salomon single-c cable Dock 3. VP on BME dock(REV-A05 Dock-114 FW:0.1.17) Cross Platform: NA Test case: [CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Plug/Unplug" Test Step32 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS and connect Salomon Dock to SUT. 3. Plugin the USB keyboard, USB Mouse, "USB v3.0 Storage Memory Keys", "USB Type-C v3.1 Storage Memory Keys",external stereo speakers, "Thunderbolt-3 HDD/SSD", two external DP monitors, external HDMI monitor, Ethernet cable to Salomon Dock. 4. Then hot plug Salomon Dock connector cable then plug in, find SUT can't detect Salomon TBT3 cable dock.-->Problem(Refer to video) 5. Restart SUT with Salomon dock connected, salomon TBT3 dock can be detected again. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804214/+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 1804229] [NEW] Linux, Ubuntu, 18.04, CI, NB13, External display connect on Salomon flicker screen when play Movie.(FR:100%)
Public bug reported: Description: Connect a Single-c Salomin Dock to SUT, Connect a QHD Monitor to SUT, set display mode to Join Display mode, play a 1080P movie on it. external monitor show flicker.(FR:100%) Expected Behavior: Movie can play normally on external Monitor connected on Salomon Dock. Severity: Sev-1 P2 C2 L2 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 Note: 1. VP on TBT/None TBT config 2. VP on Type-c to Type-c Connected QHD Monitor on Salomon Dock 3. VP on HDMI Connected QHD Monitor on Salomon Dock 4. VP on Mirror/Join Displays/External Only display mode Cross Platform: N/A Test case: [CSV-TC-5221][WIS-TC-4398] Linux_NB_Salomon-Wired-Dock-The "DisplayPort Over USB-C" Connector/Port Video Test with "USB-C to USB-C Cable" step:15 Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, Connect a Salomon Dock to SUT; 3. Connect a QHD Monitor on Salomon Dock by Type-c to Type-c Cable; 4. Set display mode to Join Displays. 5. Play a 1080P movie on it, external monitor show flicker.>problem(refer to video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "VID_play movie flicker screen.mp4" https://bugs.launchpad.net/bugs/1804229/+attachment/5214513/+files/VID_play%20movie%20flicker%20screen.mp4 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804229 Title: Linux, Ubuntu,18.04, CI, NB13, External display connect on Salomon flicker screen when play Movie.(FR:100%) Status in Glance: New Bug description: Description: Connect a Single-c Salomin Dock to SUT, Connect a QHD Monitor to SUT, set display mode to Join Display mode, play a 1080P movie on it. external monitor show flicker.(FR:100%) Expected Behavior: Movie can play normally on external Monitor connected on Salomon Dock. Severity: Sev-1 P2 C2 L2 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 Note: 1. VP on TBT/None TBT config 2. VP on Type-c to Type-c Connected QHD Monitor on Salomon Dock 3. VP on HDMI Connected QHD Monitor on Salomon Dock 4. VP on Mirror/Join Displays/External Only display mode Cross Platform: N/A Test case: [CSV-TC-5221][WIS-TC-4398] Linux_NB_Salomon-Wired-Dock-The "DisplayPort Over USB-C" Connector/Port Video Test with "USB-C to USB-C Cable" step:15 Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, Connect a Salomon Dock to SUT; 3. Connect a QHD Monitor on Salomon Dock by Type-c to Type-c Cable; 4. Set display mode to Join Displays. 5. Play a 1080P movie on it, external monitor show flicker.>problem(refer to video) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804229/+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 1804227] [NEW] "common" administrative security group is removed by user
Public bug reported: If an administrator is adding a security group to a server and the security group is not in the servers project,horizon deletes it again when the user edits the instances security group. Steps: admin create security group common server add security group common server-in-another-project horizon login as user of another-project edit security groups on server-in-another-project Result the not visible "common" sec group is removed from server-in-another-project ** Affects: horizon Importance: Undecided Status: New -- 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/1804227 Title: "common" administrative security group is removed by user Status in OpenStack Dashboard (Horizon): New Bug description: If an administrator is adding a security group to a server and the security group is not in the servers project,horizon deletes it again when the user edits the instances security group. Steps: admin create security group common server add security group common server-in-another-project horizon login as user of another-project edit security groups on server-in-another-project Result the not visible "common" sec group is removed from server-in-another-project To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1804227/+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 1804228] [NEW] Linux, Ubuntu, 18.04, CI, NB13, The displays setting can't persist after plug/unplug BME Dock.
Public bug reported: Description: After the Undock/Dock BME Dock, the displays setting can't persist, display mode will switch from duplication to Extended mode.(FR:100%) Expected Behavior: After undock/dock, the connection to the "Trinity Big Mountain Express Wired Docking Station" working without any problems Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 SKU7 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4.DELL BME DOCK-114:REV-A05 FW:1.0.0 5.Monitor:Dell SE2216H Note: 1. VP on other Northbay TBT SKU Cross Platform: N/A Test case: CSV-TC-4652[WIS-TC-4206] Linux_NB_BME-Wired-Dock-The "USB Type-C" With "Thunderbolt Devices" Test step:17 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2.While the SUT is up and running and successfully connected to the BME DOCK via the dock cable, unplug the cable to disconnect the dock or undock 3. Wait for 30-seconds and plug back in the dock cable to the SUT. 4. After the Undock/Dock BME Dock , find the displays setting can't persist,display mode will switch from duplication to Extended mode.-->problem(Refer to .MP4) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "video_20181119_185014~1.mp4" https://bugs.launchpad.net/bugs/1804228/+attachment/5214512/+files/video_20181119_185014~1.mp4 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804228 Title: Linux, Ubuntu, 18.04, CI, NB13, The displays setting can't persist after plug/unplug BME Dock. Status in Glance: New Bug description: Description: After the Undock/Dock BME Dock, the displays setting can't persist, display mode will switch from duplication to Extended mode.(FR:100%) Expected Behavior: After undock/dock, the connection to the "Trinity Big Mountain Express Wired Docking Station" working without any problems Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 SKU7 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4.DELL BME DOCK-114:REV-A05 FW:1.0.0 5.Monitor:Dell SE2216H Note: 1. VP on other Northbay TBT SKU Cross Platform: N/A Test case: CSV-TC-4652[WIS-TC-4206] Linux_NB_BME-Wired-Dock-The "USB Type-C" With "Thunderbolt Devices" Test step:17 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2.While the SUT is up and running and successfully connected to the BME DOCK via the dock cable, unplug the cable to disconnect the dock or undock 3. Wait for 30-seconds and plug back in the dock cable to the SUT. 4. After the Undock/Dock BME Dock , find the displays setting can't persist,display mode will switch from duplication to Extended mode.-->problem(Refer to .MP4) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804228/+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 1804180] [NEW] Neutron ovs cleanup cannot run on Windows
Public bug reported: The ovs cleanup script fails to run on Windows due to an import error. The linux utils module will always get imported, which uses platform specific modules. Trace: http://paste.openstack.org/raw/735711/ ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1804180 Title: Neutron ovs cleanup cannot run on Windows Status in neutron: New Bug description: The ovs cleanup script fails to run on Windows due to an import error. The linux utils module will always get imported, which uses platform specific modules. Trace: http://paste.openstack.org/raw/735711/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1804180/+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 1804181] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Display connect on Salomon via Dongle splash screen when play video.(FR:100%)
Public bug reported: Description: Connect a Single-c Salomin Dock to SUT, connect a Monitor to Salomin Dock Type-c port by Type-c to DP dongle, set display mode to Join Display mode, play a 1080P movie on it. External display will flicker screen.(FR:100%). Expected Behavior: Movie can play normally on external Monitor connected on Salomon Dock by dongle. Severity: Sev-1 P2 C2 L2 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 5. Dongle: Type-C to DP DELL TYPEC-DP-03 (REV-A00) 0YJ3Y6 Note: 1. VP on Type-c to DVI/VGA/HDMI Dongle Cross Platform: N/A Test case: [CSV-TC-5224][WIS-TC-4400] Linux_NB_Salomon-Wired-Dock-The "DisplayPort Over USB-C" Connector/Port Video Test with "USB-C to DVI" Adapter/Dongle step:15 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to OS, Connect a Salomon Dock to SUT; 3. Connect a Monitor on Salomon Dock Type-c Display Port by Type-c to DP dongle; 4. Set display mode to Join Displays. 5. Play a 1080P movie on it, Display will flicker screen.>problem(refer to video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "VID_flicker screen with dongle.mp4" https://bugs.launchpad.net/bugs/1804181/+attachment/5214450/+files/VID_flicker%20screen%20with%20dongle.mp4 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804181 Title: Linux, Ubuntu, 18.04, CI, NB13, Display connect on Salomon via Dongle splash screen when play video.(FR:100%) Status in Glance: New Bug description: Description: Connect a Single-c Salomin Dock to SUT, connect a Monitor to Salomin Dock Type-c port by Type-c to DP dongle, set display mode to Join Display mode, play a 1080P movie on it. External display will flicker screen.(FR:100%). Expected Behavior: Movie can play normally on external Monitor connected on Salomon Dock by dongle. Severity: Sev-1 P2 C2 L2 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 5. Dongle: Type-C to DP DELL TYPEC-DP-03 (REV-A00) 0YJ3Y6 Note: 1. VP on Type-c to DVI/VGA/HDMI Dongle Cross Platform: N/A Test case: [CSV-TC-5224][WIS-TC-4400] Linux_NB_Salomon-Wired-Dock-The "DisplayPort Over USB-C" Connector/Port Video Test with "USB-C to DVI" Adapter/Dongle step:15 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to OS, Connect a Salomon Dock to SUT; 3. Connect a Monitor on Salomon Dock Type-c Display Port by Type-c to DP dongle; 4. Set display mode to Join Displays. 5. Play a 1080P movie on it, Display will flicker screen.>problem(refer to video) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804181/+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 1804189] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Show extra audio device when connected Dock.(FR:100%)
Public bug reported:
Description:
Open ''Sound" option, found show extra audio device under"output" tab when
connected IE/Salomon dock.
Expected Behavior:
Sound output device should show normally.
Severity:
Sev-2
P3
C3
L2
Test Environment:
1. Project: Northbay 13 SKU11
2. BIOS: 0.4.0
3. OS:CI Ubuntu 18.04
4. IE dock FW: 1.0.4 (REV A05)
Note:
1. VP on Northbay all skus
2. VP on Salomon dock
Cross Platform:
N/A
Test case:
[CSV-TC-4669][WIS-TC-4213] Linux_NB_IE-Wired-Dock-The "Single "4K@30-Hz"
Display/Monitor Support" Test, step13
Steps to Reproduce:
1. Connected IE dock to SUT.
2. Open "Settings" from "Show Application"->"Sound".
3. Found show extra output device.-->problem(refert to pic)
** Affects: glance
Importance: Undecided
Status: New
** Tags: north-bay-13
** Attachment added: "sosreport-Audio device{WIS-IS-4213]-20181119003325.tar.xz"
https://bugs.launchpad.net/bugs/1804189/+attachment/5214455/+files/sosreport-Audio%20device%7BWIS-IS-4213%5D-20181119003325.tar.xz
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1804189
Title:
Linux, Ubuntu, 18.04, CI, NB13, Show extra audio device when connected
Dock.(FR:100%)
Status in Glance:
New
Bug description:
Description:
Open ''Sound" option, found show extra audio device under"output" tab when
connected IE/Salomon dock.
Expected Behavior:
Sound output device should show normally.
Severity:
Sev-2
P3
C3
L2
Test Environment:
1. Project: Northbay 13 SKU11
2. BIOS: 0.4.0
3. OS:CI Ubuntu 18.04
4. IE dock FW: 1.0.4 (REV A05)
Note:
1. VP on Northbay all skus
2. VP on Salomon dock
Cross Platform:
N/A
Test case:
[CSV-TC-4669][WIS-TC-4213] Linux_NB_IE-Wired-Dock-The "Single "4K@30-Hz"
Display/Monitor Support" Test, step13
Steps to Reproduce:
1. Connected IE dock to SUT.
2. Open "Settings" from "Show Application"->"Sound".
3. Found show extra output device.-->problem(refert to pic)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804189/+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 1804210] [NEW] Linux, Ubuntu, 18.04, CI, NB13, No dialogue pops up when plug in speaker to Salomon dock.(FR:100%)
Public bug reported: Description: Boot to Ubuntu OS and connect Salomon dock to SUT, then plug in external speaker to Salomon Dock audio jack, find there is no dialogue pop up to select playback device. Expected Behavior: SUT should pops up dialogue when connected external speaker to Salomon Dock. Severity: Sev-2 P3 C3 L1 Test environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. Driver list:V27 4. OS:CI Ubuntu 18.04 5. Dock info: DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 6. Speaker: Dell SPEAKER-43(REV-A00) 360 Speaker-AE715(WILLIE NELSON)- CN-0101KW-71623-71E-0073-A00 Notes: 1. VP on Salomon single-c cable Dock 2. VP on BME dock(REV-A05 Dock-114 FW:0.1.17) 3. VNP on derectly connect external speaker to SUT Cross Platform: NA Test case: [CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Plug/Unplug" Test Step16 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, dock the salomon dock to SUT. 3. Plug external speaketr to audio port of Salomon dock, find there is no dialogue popping up.-->Problem(refer to video) 4. Plug external speaketr to audio port of SUT and find there is a dialogue poping up. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-Generic.4407-201811191.tar.xz" https://bugs.launchpad.net/bugs/1804210/+attachment/5214496/+files/sosreport-Generic.4407-201811191.tar.xz ** Tags added: north-bay-13 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804210 Title: Linux, Ubuntu, 18.04, CI, NB13, No dialogue pops up when plug in speaker to Salomon dock.(FR:100%) Status in Glance: New Bug description: Description: Boot to Ubuntu OS and connect Salomon dock to SUT, then plug in external speaker to Salomon Dock audio jack, find there is no dialogue pop up to select playback device. Expected Behavior: SUT should pops up dialogue when connected external speaker to Salomon Dock. Severity: Sev-2 P3 C3 L1 Test environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. Driver list:V27 4. OS:CI Ubuntu 18.04 5. Dock info: DOCK-126REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 6. Speaker: Dell SPEAKER-43 (REV-A00) 360 Speaker-AE715(WILLIE NELSON)- CN-0101KW-71623-71E-0073-A00 Notes: 1. VP on Salomon single-c cable Dock 2. VP on BME dock(REV-A05 Dock-114 FW:0.1.17) 3. VNP on derectly connect external speaker to SUT Cross Platform: NA Test case: [CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Plug/Unplug" Test Step16 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, dock the salomon dock to SUT. 3. Plug external speaketr to audio port of Salomon dock, find there is no dialogue popping up.-->Problem(refer to video) 4. Plug external speaketr to audio port of SUT and find there is a dialogue poping up. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804210/+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 1784155] Re: nova_placement service start not coordinated with api db sync on multiple controllers
Fix for tripleo master released with:
https://review.openstack.org/610966
Backport to rocky tracked in:
https://review.openstack.org/618958
Backport to queens tracked in:
https://review.openstack.org/618984
** Changed in: tripleo
Status: Triaged => 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/1784155
Title:
nova_placement service start not coordinated with api db sync on
multiple controllers
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) rocky series:
In Progress
Status in tripleo:
Fix Released
Bug description:
On a loaded HA / galera environment using VMs I can fairly
consistently reproduce a race condition where the nova_placement
service is started on controllers where the database is not yet
available. The nova_placement service itself does not seem to be
able to tolerate this condition upon startup and it then fails to
recover. Mitigation here can either involve synchronizing these
conditions or getting nova-placement to be more resilient.
The symptoms of overcloud deploy failure look like two out of three
controllers having the nova_placement container in an unhealthy state:
TASK [Debug output for task which failed: Check for unhealthy containers
after step 3] ***
Saturday 28 July 2018 10:19:29 + (0:00:00.663) 0:30:26.152
*
fatal: [stack2-overcloud-controller-2]: FAILED! => {
"failed_when_result": true,
"outputs.stdout_lines|default([])|union(outputs.stderr_lines|default([]))": [
"3597b92e9714
192.168.25.1:8787/tripleomaster/centos-binary-nova-placement-api:959e1d7f755ee681b6f23b498d262a9e4dd6326f_4cbb1814
\"kolla_start\" 2 minutes ago Up 2 minutes (unhealthy)
nova_placement"
]
}
fatal: [stack2-overcloud-controller-1]: FAILED! => {
"failed_when_result": true,
"outputs.stdout_lines|default([])|union(outputs.stderr_lines|default([]))": [
"322c5ea53895
192.168.25.1:8787/tripleomaster/centos-binary-nova-placement-api:959e1d7f755ee681b6f23b498d262a9e4dd6326f_4cbb1814
\"kolla_start\" 2 minutes ago Up 2 minutes (unhealthy)
nova_placement"
]
}
ok: [stack2-overcloud-controller-0] => {
"failed_when_result": false,
"outputs.stdout_lines|default([])|union(outputs.stderr_lines|default([]))": []
}
ok: [stack2-overcloud-compute-0] => {
"failed_when_result": false,
"outputs.stdout_lines|default([])|union(outputs.stderr_lines|default([]))": []
}
NO MORE HOSTS LEFT
*
inspecting placement_wsgi_error.log shows the first stack trace that the
nova_placement database is missing the "traits" table:
[Sat Jul 28 10:17:06.525018 2018] [:error] [pid 14] [remote 10.1.20.15:0]
mod_wsgi (pid=14): Target WSGI script
'/var/www/cgi-bin/nova/nova-placement-api' cannot be loaded as Python module.
[Sat Jul 28 10:17:06.525067 2018] [:error] [pid 14] [remote 10.1.20.15:0]
mod_wsgi (pid=14): Exception occurred processing WSGI script
'/var/www/cgi-bin/nova/nova-placement-api'.
[Sat Jul 28 10:17:06.525101 2018] [:error] [pid 14] [remote 10.1.20.15:0]
Traceback (most recent call last):
[Sat Jul 28 10:17:06.525124 2018] [:error] [pid 14] [remote 10.1.20.15:0]
File "/var/www/cgi-bin/nova/nova-placement-api", line 54, in
[Sat Jul 28 10:17:06.525165 2018] [:error] [pid 14] [remote 10.1.20.15:0]
application = init_application()
[Sat Jul 28 10:17:06.525174 2018] [:error] [pid 14] [remote 10.1.20.15:0]
File "/usr/lib/python2.7/site-packages/nova/api/openstack/placement/wsgi.py",
line 88, in init_application
[Sat Jul 28 10:17:06.525198 2018] [:error] [pid 14] [remote 10.1.20.15:0]
return deploy.loadapp(conf.CONF)
[Sat Jul 28 10:17:06.525205 2018] [:error] [pid 14] [remote 10.1.20.15:0]
File "/usr/lib/python2.7/site-packages/nova/api/openstack/placement/deploy.py",
line 111, in loadapp
[Sat Jul 28 10:17:06.525300 2018] [:error] [pid 14] [remote 10.1.20.15:0]
update_database()
[Sat Jul 28 10:17:06.525310 2018] [:error] [pid 14] [remote 10.1.20.15:0]
File "/usr/lib/python2.7/site-packages/nova/api/openstack/placement/deploy.py",
line 92, in update_database
[Sat Jul 28 10:17:06.525329 2018] [:error] [pid 14] [remote 10.1.20.15:0]
resource_provider.ensure_trait_sync(ctx)
[Sat Jul 28 10:17:06.525337 2018] [:error] [pid 14] [remote 10.1.20.15:0]
File
"/usr/lib/python2.7/site-packages/nova/api/openstack/placement/objects/resource_provider.py",
line 146, in ensure_trait_sync
[Sat Jul 28 10:17:06.526277 2018] [:error] [pid 14] [remote 10.1.20.15:0]
_trait_sync(ctx)
...
[Sat Jul 28 10:17:06.531950 2018] [:error] [pid 14] [remote 10.1.20.15:0]
raise
[Yahoo-eng-team] [Bug 1804199] [NEW] Linux, Ubuntu, 18.04, CI, NB13, No dialogue pops up when plug in speaker to BME dock.(FR:100%)
Public bug reported: Description: Boot to Ubuntu OS and connect BME dock to SUT, then plug in external speaker to BME Dock, find there is no dialogue pop up to select playback device Expected Behavior: SUT should pops up dialogue when connected external speaker to BME Dock. Severity: Sev-2 P3 C3 L1 Test environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. Driver list:V27 4. OS:CI Ubuntu 18.04 5. Dock info: BME dock(REV-A05 Dock-114 FW:0.1.17) 6. Speaker: Dell SPEAKER-22 (REV-A00) Dell 2.0speaker (AE215)AE215 Notes: 1. VP on Salomon single-c cable Dock 2. VP on DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 3. VNP on derectly connect external speaker to SUT Cross Platform: NA Test case: CSV-TC-4664[WIS-TC-4210] Linux_NB_BME-Wired-Dock-The Docked SUT "Power Management (S3)" Test step:15 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, dock the BME dock to SUT. 3. Plug external speaketr to audio port of BME dock, find there is no dialogue popping up.-->Problem(refer to video) 4. Plug external speaketr to audio port of SUT and find there is a dialogue poping up. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-cantswitch.4012-15-20181120012419.tar.xz.md5" https://bugs.launchpad.net/bugs/1804199/+attachment/5214466/+files/sosreport-cantswitch.4012-15-20181120012419.tar.xz.md5 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804199 Title: Linux, Ubuntu, 18.04, CI, NB13, No dialogue pops up when plug in speaker to BME dock.(FR:100%) Status in Glance: New Bug description: Description: Boot to Ubuntu OS and connect BME dock to SUT, then plug in external speaker to BME Dock, find there is no dialogue pop up to select playback device Expected Behavior: SUT should pops up dialogue when connected external speaker to BME Dock. Severity: Sev-2 P3 C3 L1 Test environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. Driver list:V27 4. OS:CI Ubuntu 18.04 5. Dock info: BME dock(REV-A05 Dock-114 FW:0.1.17) 6. Speaker: Dell SPEAKER-22 (REV-A00) Dell 2.0speaker (AE215)AE215 Notes: 1. VP on Salomon single-c cable Dock 2. VP on DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 3. VNP on derectly connect external speaker to SUT Cross Platform: NA Test case: CSV-TC-4664[WIS-TC-4210] Linux_NB_BME-Wired-Dock-The Docked SUT "Power Management (S3)" Test step:15 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, dock the BME dock to SUT. 3. Plug external speaketr to audio port of BME dock, find there is no dialogue popping up.-->Problem(refer to video) 4. Plug external speaketr to audio port of SUT and find there is a dialogue poping up. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804199/+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 1804200] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Can't detect BME Dock after hot plug/unplug.(FR:1/10 times)
Public bug reported: Description: Boot to OS and connect Salomon Dock to SUT. Plugin the USB keyboard, USB Mouse, "USB v3.0 Storage Memory Keys", "USB Type-C v3.1 Storage Memory Keys",external stereo speakers, "Thunderbolt-3 HDD/SSD", External DP/HDMI/VGA monitor, Ethernet cable to BME Dock. Then hot plug BME Dock connector cable, then plug in , find SUT can't detect BME dock. Restart SUT with BME dock connected,BME dock can be detected again. Expected Behavior: BME dock can be detected successfully after dock/undock. Severity: Sev-3 P3 C3 L4 Test environment: 1. Project:Northbay 13 2. BIOS:0.4.0 3. Driver list:V27 4. OS:CI Ubuntu 18.04 5. Dock info: BME dock(REV-A05 Dock-114 FW:0.1.17) Notes: 1. VP on Northbay TBT sku 2. VP on Salomon TBT cable Dock Cross Platform: NA Test case: CSV-TC-4668[WIS-TC-4212] Linux_NB_BME-Wired-Dock-The Docked SUT "Plug/Unplug" Test step:29 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS and connect Salomon Dock to SUT. 3. Plugin the USB keyboard, USB Mouse, "USB v3.0 Storage Memory Keys", "USB Type-C v3.1 Storage Memory Keys",external stereo speakers, external DP/HDMI/VGA monitors, Ethernet cable to BME Dock. 4. Hot plug BME Dock connector cable then plug in, find SUT can't detect BME dock.-->Problem 5. Restart SUT with Salomon dock connected, BME dock can be detected again. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-cantswitch.4212-15-20181120012419.tar.xz.md5" https://bugs.launchpad.net/bugs/1804200/+attachment/5214467/+files/sosreport-cantswitch.4212-15-20181120012419.tar.xz.md5 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804200 Title: Linux, Ubuntu, 18.04, CI, NB13, Can't detect BME Dock after hot plug/unplug.(FR:1/10 times) Status in Glance: New Bug description: Description: Boot to OS and connect Salomon Dock to SUT. Plugin the USB keyboard, USB Mouse, "USB v3.0 Storage Memory Keys", "USB Type-C v3.1 Storage Memory Keys",external stereo speakers, "Thunderbolt-3 HDD/SSD", External DP/HDMI/VGA monitor, Ethernet cable to BME Dock. Then hot plug BME Dock connector cable, then plug in , find SUT can't detect BME dock. Restart SUT with BME dock connected,BME dock can be detected again. Expected Behavior: BME dock can be detected successfully after dock/undock. Severity: Sev-3 P3 C3 L4 Test environment: 1. Project:Northbay 13 2. BIOS:0.4.0 3. Driver list:V27 4. OS:CI Ubuntu 18.04 5. Dock info: BME dock(REV-A05 Dock-114 FW:0.1.17) Notes: 1. VP on Northbay TBT sku 2. VP on Salomon TBT cable Dock Cross Platform: NA Test case: CSV-TC-4668[WIS-TC-4212] Linux_NB_BME-Wired-Dock-The Docked SUT "Plug/Unplug" Test step:29 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS and connect Salomon Dock to SUT. 3. Plugin the USB keyboard, USB Mouse, "USB v3.0 Storage Memory Keys", "USB Type-C v3.1 Storage Memory Keys",external stereo speakers, external DP/HDMI/VGA monitors, Ethernet cable to BME Dock. 4. Hot plug BME Dock connector cable then plug in, find SUT can't detect BME dock.-->Problem 5. Restart SUT with Salomon dock connected, BME dock can be detected again. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804200/+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 1804187] [NEW] Linux, Ubuntu, 18.04, CI, NB13, SUT will open two APP UI when only tapped APP shortcut once(FR:100%)
Public bug reported: Description: eg:Touch Google Chrome shortcut, will open two Chrome Windows simultaneously. Expected Behavior: SUT should show one open window. Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 SKU7 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Touch LCD :FHD OTP HHYCY Note: 1.VP on LCD MC2FY Cross Platform: N/A Test case: CSV-TC-5001[WIS-TC-4402] Linux_NB_Touchscreen - Basic Functionality Test step:5 Steps to Reproduce: 1.Install Ubuntu 18.4 OS. 2.Boot to OS,and Check that touch functions 3.Touch " Google Chrome" shortcut, Find will open two Chrome Windows simultaneously.-->problem(refer to mp.4) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "video_20181115_190108.mp4" https://bugs.launchpad.net/bugs/1804187/+attachment/5214454/+files/video_20181115_190108.mp4 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804187 Title: Linux, Ubuntu, 18.04, CI, NB13, SUT will open two APP UI when only tapped APP shortcut once(FR:100%) Status in Glance: New Bug description: Description: eg:Touch Google Chrome shortcut, will open two Chrome Windows simultaneously. Expected Behavior: SUT should show one open window. Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 SKU7 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Touch LCD :FHD OTP HHYCY Note: 1.VP on LCD MC2FY Cross Platform: N/A Test case: CSV-TC-5001[WIS-TC-4402] Linux_NB_Touchscreen - Basic Functionality Test step:5 Steps to Reproduce: 1.Install Ubuntu 18.4 OS. 2.Boot to OS,and Check that touch functions 3.Touch " Google Chrome" shortcut, Find will open two Chrome Windows simultaneously.-->problem(refer to mp.4) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804187/+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 1804193] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Can't record voice by external Microphone.(FR:3/3units)
Public bug reported: Description: Plug in external Mic to SUT audio jack, record voice by external microphone , can't hear any Voice from Recorded file. Expected Behavior: Can record Voice normally by external Jack Mic on Ubuntu OS. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Microphone: MIC-18 REV-A.1 NEEWER NW-700 Note: 1. VP on Headset-42 A500I (only heard noise) Cross Platform: N/A Test case: [CSV-TC-4588][WIS-TC-4176] Linux_OS - Basic OS Functionality Test step:11 Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, insert a Jack Mic to SUT. 3. Select Microphone at pop up windows. 4. Open a sound record Application, record a voice. 5. Find no record voice output .>problem ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-genericlog.1-20181120045802.tar.xz" https://bugs.launchpad.net/bugs/1804193/+attachment/5214464/+files/sosreport-genericlog.1-20181120045802.tar.xz ** Description changed: - Description: - Plug in external Mic to SUT audio jack, record voice by external microphone , can't hear any Voice from Recorded file.(FR:3/3units) + Plug in external Mic to SUT audio jack, record voice by external microphone , can't hear any Voice from Recorded file. Expected Behavior: Can record Voice normally by external Jack Mic on Ubuntu OS. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Microphone: MIC-18 REV-A.1 NEEWER NW-700 Note: 1. VP on Headset-42 A500I (only heard noise) Cross Platform: N/A Test case: [CSV-TC-4588][WIS-TC-4176] Linux_OS - Basic OS Functionality Test step:11 - + Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, insert a Jack Mic to SUT. 3. Select Microphone at pop up windows. 4. Open a sound record Application, record a voice. 5. Find no record voice output .>problem -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804193 Title: Linux, Ubuntu, 18.04, CI, NB13, Can't record voice by external Microphone.(FR:3/3units) Status in Glance: New Bug description: Description: Plug in external Mic to SUT audio jack, record voice by external microphone , can't hear any Voice from Recorded file. Expected Behavior: Can record Voice normally by external Jack Mic on Ubuntu OS. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Microphone: MIC-18 REV-A.1 NEEWER NW-700 Note: 1. VP on Headset-42 A500I (only heard noise) Cross Platform: N/A Test case: [CSV-TC-4588][WIS-TC-4176] Linux_OS - Basic OS Functionality Test step:11 Steps to Reproduce: 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, insert a Jack Mic to SUT. 3. Select Microphone at pop up windows. 4. Open a sound record Application, record a voice. 5. Find no record voice output .>problem To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804193/+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 1804184] [NEW] Linux, Ubuntu, 18.04, CI, NB13, BT status still show "turned off" after turn on BT (FR:1/10times)
Public bug reported: Description: Click the BT "On/Off" icon, set to On. The Bluetooth still show turned off. Expected Behavior: Bluetooth is enabled. And will show available bluetooth devices. Severity: Sev-2 P2 C3 L2 Test Environment: 1. Project: Northbay 13 SKU7 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. WLAN Device :9560 Card Note: VP on 1820 Cross Platform: N/A Test case: CSV-TC-4727[WIS-TC-4163] Linux_BT - Device Discovery and Pair Test step:3 Steps to Reproduce: 1.Go to "Setting"->Click "Bluetooth" 2. Click the On/Off icon, set to On. 3.Find The Bluetooth still show turned off.-->problem(refer to pic) 4.Need restart the SUT ,BT will be change normal. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-Ubuntu18.04LTSCILatitude-5380.tar11.xz" https://bugs.launchpad.net/bugs/1804184/+attachment/5214451/+files/sosreport-Ubuntu18.04LTSCILatitude-5380.tar11.xz -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804184 Title: Linux, Ubuntu, 18.04, CI, NB13, BT status still show "turned off" after turn on BT (FR:1/10times) Status in Glance: New Bug description: Description: Click the BT "On/Off" icon, set to On. The Bluetooth still show turned off. Expected Behavior: Bluetooth is enabled. And will show available bluetooth devices. Severity: Sev-2 P2 C3 L2 Test Environment: 1. Project: Northbay 13 SKU7 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. WLAN Device :9560 Card Note: VP on 1820 Cross Platform: N/A Test case: CSV-TC-4727[WIS-TC-4163] Linux_BT - Device Discovery and Pair Test step:3 Steps to Reproduce: 1.Go to "Setting"->Click "Bluetooth" 2. Click the On/Off icon, set to On. 3.Find The Bluetooth still show turned off.-->problem(refer to pic) 4.Need restart the SUT ,BT will be change normal. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804184/+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 1777129] Re: live migration doc says "convergence" while config uses "converge"
** Changed in: nova/pike Status: Fix Committed => Fix Released ** Changed in: nova Status: Fix Committed => 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/1777129 Title: live migration doc says "convergence" while config uses "converge" Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) pike series: Fix Released Bug description: The documentation mentions the configuration option live_migration_permit_auto_convergence while the actual config file uses live_migration_permit_auto_converge. There seems to be some spelling issues in the titles + text + config options. --- Release: 16.1.4.dev15 on 2018-06-04 05:37 SHA: 2c9c4a09cb5fd31ccff368315534eaa788e90e67 Source: https://git.openstack.org/cgit/openstack/nova/tree/doc/source/admin/live-migration-usage.rst URL: https://docs.openstack.org/nova/pike/admin/live-migration-usage.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1777129/+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 1800663] Re: docs: Flavors in nova - custom resource classes and overrides
Reviewed: https://review.openstack.org/616721 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0e718ddb7a43230fa1ae9ee2d78c4375a964cd48 Submitter: Zuul Branch:master commit 0e718ddb7a43230fa1ae9ee2d78c4375a964cd48 Author: Takashi NATSUME Date: Fri Nov 9 09:47:17 2018 +0900 Add description of custom resource classes Add the description about custom resource classes and overriding standard resource classes in the "Flavors" document. Change-Id: I5b804db70d229696e7b7c5b5db16946cf1f1c49f Closes-Bug: #1800663 ** 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/1800663 Title: docs: Flavors in nova - custom resource classes and overrides Status in OpenStack Compute (nova): Fix Released Bug description: - [x] This is a doc addition request. The nova flavor user guide doesn't mention the ability to specify custom resource classes on a flavor, or how to override standard resource classes, introduced in this spec in Pike: https://specs.openstack.org/openstack/nova- specs/specs/pike/implemented/custom-resource-classes-in-flavors.html #data-model-impact The ironic flavor guide is probably the most comprehensive for this, so maybe the nova flavor docs can just reference that for details: https://docs.openstack.org/ironic/latest/install/configure-nova- flavors.html --- Release: 18.1.0.dev629 on 2018-10-30 13:27 SHA: d1e38f06bb5282dd9bf81d979926a0ebbfd93caa Source: https://git.openstack.org/cgit/openstack/nova/tree/doc/source/user/flavors.rst URL: https://docs.openstack.org/nova/latest/user/flavors.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1800663/+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 1804262] [NEW] ComputeManager._run_image_cache_manager_pass times out when running on NFS
Public bug reported: Description === Under Pike we are operating a /var/lib/nova/instances mounted on a clustered Netapp A700 AFF. The share is mounted across the entire nova fleet of currently 29 hosts (10G networking) with ~ 720 instances. We are mounting the share with standard NFS options are considering actimeo as improvement, unless there are expected issues around metadata consistency issues: host:/share /var/lib/nova/instances nfs rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=,mountvers=3,mountport=635,mountproto=udp,local_lock=none,addr= But recently we noticed an increase of Error during ComputeManager._run_image_cache_manager_pass: MessagingTimeout: Timed out waiting for a reply t which we mitigated by increasing the rpc_response_timeout. As the result of the increased errors we saw nova-compute service flapping which caused other issues like volume attachments got delayed or erred out. Am I right with the assumption that the resource tracker and services updates are happening inside the same thread ? What else can we do to prevent these errors ? Actual result = 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task [req-73d6cf48-d94a-41e4-a59e-9965fec4972d - - - - -] Error during ComputeManager._run_image_cache_manager_pass: MessagingTimeout: Timed out waiting for a reply to message ID 29820aa832354e788c7d50a533823c2a 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/oslo_service/periodic_task.py", line 220, in run_periodic_tasks 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task task(self, context) 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/nova/compute/manager.py", line 7118, in _run_image_cache_manager_pass 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task self.driver.manage_image_cache(context, filtered_instances) 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 7563, in manage_image_cache 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task self.image_cache_manager.update(context, all_instances) 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/nova/virt/libvirt/imagecache.py", line 414, in update 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task running = self._list_running_instances(context, all_instances) 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/nova/virt/imagecache.py", line 54, in _list_running_instances 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task context, [instance.uuid for instance in all_instances]) 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/nova/objects/block_device.py", line 333, in bdms_by_instance_uuid 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task bdms = cls.get_by_instance_uuids(context, instance_uuids) 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 177, in wrapper 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task args, kwargs) 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/nova/conductor/rpcapi.py", line 240, in object_class_action_versions 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task args=args, kwargs=kwargs) 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 169, in call 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task retry=self.retry) 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/oslo_messaging/transport.py", line 123, in _send 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task timeout=timeout, retry=retry) 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 566, in send 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task retry=retry) 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task File "/openstack/venvs/nova-r16.2.4/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 555, in _send 2018-11-20 14:09:40.413 4294 ERROR oslo_service.periodic_task result = self._waiter.wait(msg_id,
[Yahoo-eng-team] [Bug 1804259] [NEW] DB: sorting on elements which are AssociationProxy fails
Public bug reported:
If I do a DB query trying to sort by a column which is an
AssociationProxy I get the following exception:
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers File
"/opt/stack/neutron/neutron/db/db_base_plugin_v2.py", line 1438, in get_ports
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers page_reverse=page_reverse)
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers File
"/opt/stack/neutron/neutron/plugins/ml2/plugin.py", line 1935, in _get_ports_qu
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers *args, **kwargs)
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers File
"/opt/stack/neutron/neutron/db/db_base_plugin_v2.py", line 1418, in _get_ports_
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers *args, **kwargs)
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers File
"/opt/stack/neutron/neutron/db/_model_query.py", line 159, in get_collection_qu
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers sort_keys =
db_utils.get_and_validate_sort_keys(sorts, model)
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers File
"/usr/lib/python2.7/site-packages/neutron_lib/db/utils.py", line 45, in get_and
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers if isinstance(sort_key_attr.property,
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers AttributeError: 'AssociationProxy' object has no
attribute 'property'
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers
This is reproducible for example by querying ports sorted by 'created_at'
attribute:
ports = self._plugin.get_ports(context, sorts=[('created_at', True)])
Looks like we may need to special case the AssociationProxy columns such as we
already do in the filtering code at:
https://github.com/openstack/neutron/blob/0bb6136919a31751242d2efbefedbd8922b6bd0a/neutron/db/_model_query.py#L88
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1804259
Title:
DB: sorting on elements which are AssociationProxy fails
Status in neutron:
New
Bug description:
If I do a DB query trying to sort by a column which is an
AssociationProxy I get the following exception:
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers File
"/opt/stack/neutron/neutron/db/db_base_plugin_v2.py", line 1438, in get_ports
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers page_reverse=page_reverse)
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers File
"/opt/stack/neutron/neutron/plugins/ml2/plugin.py", line 1935, in _get_ports_qu
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers *args, **kwargs)
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers File
"/opt/stack/neutron/neutron/db/db_base_plugin_v2.py", line 1418, in _get_ports_
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers *args, **kwargs)
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers File
"/opt/stack/neutron/neutron/db/_model_query.py", line 159, in get_collection_qu
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers sort_keys =
db_utils.get_and_validate_sort_keys(sorts, model)
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers File
"/usr/lib/python2.7/site-packages/neutron_lib/db/utils.py", line 45, in get_and
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers if isinstance(sort_key_attr.property,
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers AttributeError: 'AssociationProxy' object has no
attribute 'property'
Nov 20 14:41:20 centos.rdocloud neutron-server[11934]: ERROR
neutron.plugins.ml2.managers
This is reproducible for example by querying ports sorted by 'created_at'
attribute:
ports = self._plugin.get_ports(context, sorts=[('created_at', True)])
Looks like we may need to special case the AssociationProxy columns such as
we already do in the filtering code at:
https://github.com/openstack/neutron/blob/0bb6136919a31751242d2efbefedbd8922b6bd0a/neutron/db/_model_query.py#L88
To manage
[Yahoo-eng-team] [Bug 1804271] [NEW] nova-api is broken in postgresql jobs
Public bug reported: We noticed in neutron-tempest-postgres-full periodic job that since 14.11.2018 it's failing because of issue in nova-api. Example of failure are on http://logs.openstack.org/periodic/git.openstack.org/openstack/neutron/master/neutron-tempest-postgres-full/1de7427/logs/screen-n-api.txt.gz?level=ERROR Stacktrace: Nov 20 06:34:20.578714 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi Traceback (most recent call last): Nov 20 06:34:20.578885 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/openstack/wsgi.py", line 655, in wrapped Nov 20 06:34:20.579046 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return f(*args, **kwargs) Nov 20 06:34:20.579218 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 110, in wrapper Nov 20 06:34:20.579379 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return func(*args, **kwargs) Nov 20 06:34:20.579537 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 110, in wrapper Nov 20 06:34:20.579737 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return func(*args, **kwargs) Nov 20 06:34:20.579899 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 110, in wrapper Nov 20 06:34:20.580070 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return func(*args, **kwargs) Nov 20 06:34:20.580236 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 110, in wrapper Nov 20 06:34:20.580396 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return func(*args, **kwargs) Nov 20 06:34:20.580616 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 110, in wrapper Nov 20 06:34:20.581036 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return func(*args, **kwargs) Nov 20 06:34:20.581205 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 110, in wrapper Nov 20 06:34:20.581364 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return func(*args, **kwargs) Nov 20 06:34:20.581523 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 110, in wrapper Nov 20 06:34:20.581693 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return func(*args, **kwargs) Nov 20 06:34:20.581852 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 110, in wrapper Nov 20 06:34:20.582008 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return func(*args, **kwargs) Nov 20 06:34:20.582170 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 110, in wrapper Nov 20 06:34:20.582336 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return func(*args, **kwargs) Nov 20 06:34:20.582505 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 110, in wrapper Nov 20 06:34:20.582663 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return func(*args, **kwargs) Nov 20 06:34:20.582835 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/validation/__init__.py", line 110, in wrapper Nov 20 06:34:20.582987 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi return func(*args, **kwargs) Nov 20 06:34:20.583285 ubuntu-xenial-inap-mtl01-583998 devstack@n-api.service[24452]: ERROR nova.api.openstack.wsgi File "/opt/stack/new/nova/nova/api/openstack/compute/servers.py",
[Yahoo-eng-team] [Bug 1804274] [NEW] Neutron error agreggation interfaces
Public bug reported:
Hello, I need to report a bug that consume cpu process a lot, its only a
warning, but makes controller slowly.
Everybody that use link-aggregation to improve in netwrok troughtput, for
example IFENSLAVE 2.6 or similar, have this issue below:
WARNING neutron.services.trunk.drivers.linuxbridge.agent.trunk_plumber
[...] : Bad interface line: addrgenmode eui64 : IndexError: list index
out of range
This occurs because the file
(neutron/services/trunk/drivers/linuxbridge/agent/trunk_plumber.py) try
to get interfaces name ("ip", "-d", "link", "list"), and If have an
interface member of an aggregation, some additional lines is on output
like this:
3: eno2: mtu 9000 qdisc mq master bond0
state UP mode DEFAULT group default qlen 1000
link/ether ... brd ff:ff:ff:ff:ff:ff promiscuity 1
bond_slave state ACTIVE mii_status UP link_failure_count 0 perm_hwaddr
ff:ab:12:ad:33:1a queue_id 0 ad_aggregator_id 3 ad_actor_oper_port_state 63
ad_partner_oper_port_state 61
addrgenmode eui64
Is possible a fix to this Warning, bypassing ifaces member of
aggregations?
Thanks, we use Openstack Queens.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: addrgenmode bad ifenslave indexerror linuxbridge neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1804274
Title:
Neutron error agreggation interfaces
Status in neutron:
New
Bug description:
Hello, I need to report a bug that consume cpu process a lot, its only a
warning, but makes controller slowly.
Everybody that use link-aggregation to improve in netwrok troughtput, for
example IFENSLAVE 2.6 or similar, have this issue below:
WARNING neutron.services.trunk.drivers.linuxbridge.agent.trunk_plumber
[...] : Bad interface line: addrgenmode eui64 : IndexError: list index
out of range
This occurs because the file
(neutron/services/trunk/drivers/linuxbridge/agent/trunk_plumber.py)
try to get interfaces name ("ip", "-d", "link", "list"), and If have
an interface member of an aggregation, some additional lines is on
output like this:
3: eno2: mtu 9000 qdisc mq master
bond0 state UP mode DEFAULT group default qlen 1000
link/ether ... brd ff:ff:ff:ff:ff:ff promiscuity 1
bond_slave state ACTIVE mii_status UP link_failure_count 0 perm_hwaddr
ff:ab:12:ad:33:1a queue_id 0 ad_aggregator_id 3 ad_actor_oper_port_state 63
ad_partner_oper_port_state 61
addrgenmode eui64
Is possible a fix to this Warning, bypassing ifaces member of
aggregations?
Thanks, we use Openstack Queens.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1804274/+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
