[Yahoo-eng-team] [Bug 1811330] [NEW] Error when creating a VM with flavour t3.xsmall
Public bug reported: I tried to create a VM with flavour t3.xsmalland got this error message Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req- e1f3be31-f0e6-4d6f-8b04-6c5175f486fe) regards Simon ** 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/1811330 Title: Error when creating a VM with flavour t3.xsmall Status in OpenStack Compute (nova): New Bug description: I tried to create a VM with flavour t3.xsmalland got this error message Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-e1f3be31-f0e6-4d6f-8b04-6c5175f486fe) regards Simon To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1811330/+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 1811327] [NEW] No confirm message for the instance resize/revert operation.
Public bug reported: When user click instance resize/revert button, the tasks will take long time and no response from the webpage. We can give the user confirmation when they click on confirm/revert instance resize, so they don't keep pressing it and see errors ** Affects: horizon Importance: Undecided Assignee: Yan Chen (ychen2u) Status: New ** Changed in: horizon Assignee: (unassigned) => Yan Chen (ychen2u) -- 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/1811327 Title: No confirm message for the instance resize/revert operation. Status in OpenStack Dashboard (Horizon): New Bug description: When user click instance resize/revert button, the tasks will take long time and no response from the webpage. We can give the user confirmation when they click on confirm/revert instance resize, so they don't keep pressing it and see errors To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1811327/+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 1804502] Re: Rebuild server with NUMATopologyFilter enabled fails (in some cases)
@sean-k-mooney the bug still exist so please don't disqualify the bug if you don't like the PR attached to it. also the PR solves most of the issue without causing new issues, the only scenario it does not fix is the one you rightfully mentioned but to solve it will require an extremely large change and it is not likely that it will be done any time soon. please reconsider the PR (as mentioned it fixes some not all of the cases). ** Changed in: nova Status: Invalid => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1804502 Title: Rebuild server with NUMATopologyFilter enabled fails (in some cases) Status in OpenStack Compute (nova): In Progress Bug description: Description === server rebuild will fail in nova scheduler on NUMATopologyFilter if the computes do not have enough capacity (even though clearly the running server is already accounted into that calculation) to resolve the issue a fix is required in NUMATopologyFilter to not perform the rebuild operation in the case that the request is due to rebuild. the result of such a case will be that server rebuild will fail with error of "no valid host found" (do not mix resize with rebuild functions...) Steps to reproduce == 1. create a flavor that contain metadata that will point to a specific compute (use host aggregate with same key:value metadata make sure flavor contain topology related metadata: hw:cpu_cores='1', hw:cpu_policy='dedicated', hw:cpu_sockets='6', hw:cpu_thread_policy='prefer', hw:cpu_threads='1', hw:mem_page_size='large', location='area51' 2. create a server on that compute (preferably using heat stack) 3. (try to) rebuild the server using stack update 4. issue reproduced Expected result === server in an active running state (if image was replaced in the rebuild command than with a reference to the new image in the server details. Actual result = server in error state with error of no valid host found. Message No valid host was found. There are not enough hosts available. Code 500 Details File "/usr/lib/python2.7/site-packages/nova/conductor/manager.py", line 966, in rebuild_instance return_alternates=False) File "/usr/lib/python2.7/site-packages/nova/conductor/manager.py", line 723, in _schedule_instances return_alternates=return_alternates) File "/usr/lib/python2.7/site-packages/nova/scheduler/utils.py", line 907, in wrapped return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/__init__.py", line 53, in select_destinations instance_uuids, return_objects, return_alternates) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/__init__.py", line 37, in __run_method return getattr(self.instance, __name)(*args, **kwargs) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/query.py", line 42, in select_destinations instance_uuids, return_objects, return_alternates) File "/usr/lib/python2.7/site-packages/nova/scheduler/rpcapi.py", line 158, in select_destinations return cctxt.call(ctxt, 'select_destinations', **msg_args) File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 179, in call retry=self.retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 133, in _send retry=retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 584, in send call_monitor_timeout, retry=retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 575, in _send raise result Environment === detected in Rocky release KVM hypervisor Ceph storage Neutron networks Logs & Configs == in nova.conf: enabled_filters=AggregateInstanceExtraSpecsFilter,RetryFilter,AvailabilityZoneFilter,NUMATopologyFilter,PciPassthroughFilter,RamFilter,ComputeFilter,ImagePropertiesFilter,CoreFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter,DiskFilter,ComputeCapabilitiesFilter,AggregateRamFilter,SameHostFilter,DifferentHostFilter logs: tbd To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1804502/+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 1804502] Re: Rebuild server with NUMATopologyFilter enabled fails (in some cases)
as per my comment https://review.openstack.org/#/c/629646/4/nova/scheduler/filters/numa_topology_filter.py@103 we cannont skip valdiating the numa toplogy of a host on rebuild as the image can alter the guest numa toplogy. if we rebuilt with the same image we skip going back to the schduler so the only time we go to the schduler on rebuild if if the image changed which means we cannot assume there is enough space on the current host. as presented this bug is invalid however if you can present a way to re validate that the existing numa toplogy is valid with the new image instad of just skiping that may be reasonable. ** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1804502 Title: Rebuild server with NUMATopologyFilter enabled fails (in some cases) Status in OpenStack Compute (nova): Invalid Bug description: Description === server rebuild will fail in nova scheduler on NUMATopologyFilter if the computes do not have enough capacity (even though clearly the running server is already accounted into that calculation) to resolve the issue a fix is required in NUMATopologyFilter to not perform the rebuild operation in the case that the request is due to rebuild. the result of such a case will be that server rebuild will fail with error of "no valid host found" (do not mix resize with rebuild functions...) Steps to reproduce == 1. create a flavor that contain metadata that will point to a specific compute (use host aggregate with same key:value metadata make sure flavor contain topology related metadata: hw:cpu_cores='1', hw:cpu_policy='dedicated', hw:cpu_sockets='6', hw:cpu_thread_policy='prefer', hw:cpu_threads='1', hw:mem_page_size='large', location='area51' 2. create a server on that compute (preferably using heat stack) 3. (try to) rebuild the server using stack update 4. issue reproduced Expected result === server in an active running state (if image was replaced in the rebuild command than with a reference to the new image in the server details. Actual result = server in error state with error of no valid host found. Message No valid host was found. There are not enough hosts available. Code 500 Details File "/usr/lib/python2.7/site-packages/nova/conductor/manager.py", line 966, in rebuild_instance return_alternates=False) File "/usr/lib/python2.7/site-packages/nova/conductor/manager.py", line 723, in _schedule_instances return_alternates=return_alternates) File "/usr/lib/python2.7/site-packages/nova/scheduler/utils.py", line 907, in wrapped return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/__init__.py", line 53, in select_destinations instance_uuids, return_objects, return_alternates) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/__init__.py", line 37, in __run_method return getattr(self.instance, __name)(*args, **kwargs) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/query.py", line 42, in select_destinations instance_uuids, return_objects, return_alternates) File "/usr/lib/python2.7/site-packages/nova/scheduler/rpcapi.py", line 158, in select_destinations return cctxt.call(ctxt, 'select_destinations', **msg_args) File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 179, in call retry=self.retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 133, in _send retry=retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 584, in send call_monitor_timeout, retry=retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 575, in _send raise result Environment === detected in Rocky release KVM hypervisor Ceph storage Neutron networks Logs & Configs == in nova.conf: enabled_filters=AggregateInstanceExtraSpecsFilter,RetryFilter,AvailabilityZoneFilter,NUMATopologyFilter,PciPassthroughFilter,RamFilter,ComputeFilter,ImagePropertiesFilter,CoreFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter,DiskFilter,ComputeCapabilitiesFilter,AggregateRamFilter,SameHostFilter,DifferentHostFilter logs: tbd To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1804502/+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 1292084] Re: User can't select rules while creating a security group
Reviewed: https://review.openstack.org/628100 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=90aa4b2b7ed07647acbcd55675c2d7eb01b94611 Submitter: Zuul Branch:master commit 90aa4b2b7ed07647acbcd55675c2d7eb01b94611 Author: Sam Wright Date: Wed Jan 17 15:05:05 2018 +1300 SG creation user taken straight to edit rules When the user creates a security group they are taken straight to manage security group and can select and make changes to rules. Change-Id: I2b3422e7816fabf59aca87a76f19cba96f01bddc closes-bug: #1292084 ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1292084 Title: User can't select rules while creating a security group Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In order to assign rules to a new security group, the user has to create the security group first and then edit the rules, which option in fact opens a new tab with no reference to security groups. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1292084/+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 1801862] Re: User details page, the name needs to be word wrap
Reviewed: https://review.openstack.org/615741 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=3d899d9078a1de5ec76a50f23830be8178deed0e Submitter: Zuul Branch:master commit 3d899d9078a1de5ec76a50f23830be8178deed0e Author: pengyuesheng Date: Tue Nov 6 14:42:02 2018 +0800 the name needs to be word wrap if the name is too long, it will affect the display. Change-Id: Ib1e35d32b0b3f82a0f949d94a2f4c8bcfd4eff41 Closes-Bug: #1801862 ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1801862 Title: User details page, the name needs to be word wrap Status in OpenStack Dashboard (Horizon): Fix Released Bug description: User details page, if the name is too long, it will affect the display. Many pages have display problems due to long names，Not just the user details page To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1801862/+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 1811046] Re: Current progress bar for a status column is always 100%, we need to provide a way to show incompleted status.
Reviewed: https://review.openstack.org/629378 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=cc2a9c0503b1777f2e623b5d911231f98736ed00 Submitter: Zuul Branch:master commit cc2a9c0503b1777f2e623b5d911231f98736ed00 Author: Yan Chen Date: Wed Dec 19 21:01:22 2018 +0800 Provide partial-completed progress bar for DataTable status columns. Current progress bar for a status column is always 100%. We need to provide a way for the DataTable to show incompleted status. For some long operations, this is not so user friendly. Closes-Bug: 1811046 Change-Id: Idf1ff00e5989ff347419faad2218becbe6d4415e Signed-off-by: Yan Chen ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1811046 Title: Current progress bar for a status column is always 100%, we need to provide a way to show incompleted status. Status in OpenStack Dashboard (Horizon): Fix Released Bug description: We need to provide a way for the DataTable to show incompleted status. Currently the progress bar is always 100%. For some long operations, this is not so user friendly. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1811046/+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 1777358] Re: Charm does not create database entries due to use of deprecated syncdb command
Reviewed: https://review.openstack.org/628988 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=8cc055157dde9e885bae29f4bad4518da427ce97 Submitter: Zuul Branch:master commit 8cc055157dde9e885bae29f4bad4518da427ce97 Author: Akihiro Motoki Date: Mon Jan 7 23:48:27 2019 +0900 doc: Use `manage.py migrate` `syncdb` subcommand was deprecated in django 1.7 and subsequently removed in 1.9. We need to use 'manage.py migrate'. This commit also drops a sample output of 'manage.py migrate'. I don't think we need to maintain this kind of output and it can change per Django release. Closes-Bug: #1777358 Reference: https://docs.djangoproject.com/en/dev/topics/http/sessions/#using-database-backed-sessions Change-Id: Ib3a7e50584a8deb9bee409335464163b7b1258d1 ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1777358 Title: Charm does not create database entries due to use of deprecated syncdb command Status in OpenStack openstack-dashboard charm: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Bug description: I'm trying to deploy the openstack-dashboard charm in a bionic LXD container. As I want to be able to use Keystone v3, I have related the charm to the percona-cluster charm through the use of the shared-db interface. However, during the charm's installation I see the following error in the logs; unit-openstack-dashboard-4: 20:39:39 DEBUG unit.openstack-dashboard/4.shared-db-relation-changed Unknown command: 'syncdb' unit-openstack-dashboard-4: 20:39:39 DEBUG unit.openstack-dashboard/4.shared-db-relation-changed Type 'manage.py help' for usage. Despite this, the charm completes installation and can be reached via the browser. However, upon login an error is thrown in the Apache logs - attached as openstack-dashboard-charm-traceback.txt - and the login fails. Due to the syncdb error during the installation, the database is never created on the shared-db - hence the traceback on login. The syncdb command was deprecated in Django 1.7 and removed in 1.9. The version of Django in this charm/bionic is 1.11.11, hence the error. Instead, the syncdb command has been replaced with makemigrations and migrate, see https://docs.djangoproject.com/en/dev/topics/migrations/ . As this was a fresh installation, I manually ran manage.py migrate. After this, no tracebacks were observed in the Apache logs. Charm version: 259 To manage notifications about this bug go to: https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1777358/+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 1810314] Re: neutron objects base get_values() fails with KeyError
I don't think this is a neutron bug. The error happened only in the case that the fake query class is used in unit tests. It should be resolved once the testing code is updated. See if this patch fixes your issue: https://review.openstack.org/#/c/629922/ ** Changed in: neutron Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1810314 Title: neutron objects base get_values() fails with KeyError Status in neutron: Won't Fix Status in Tricircle: In Progress Bug description: As of December 20 2018 the python unit test jobs for the tricircle project have been failing [1]. After going through the tricircle/neutron commits since that date, it seems some changes went into neutron that caused the breakage. If I run tricircle python 3.5 unit test with neutron commit 55c5139d79ef09869eea1201c736eee8de3ec651 (the last commit on neutron from Dec 19, 2018) the unit tests all pass. If I run the same UTs with neutron (latest) master they fail with the same errors found in the results of [2]. While this is just a guess, I suspect that maybe neutron changes that landed on Dec 20 related to "Convert Subnet to OVO in ipam_pluggable_backend.py" [3] introduced the breakage. In any case, something landed in neutron around Dec 20, 2018 that has broken tricircle. [1] http://zuul.openstack.org/builds?branch=master&project=openstack%2Ftricircle&job_name=openstack-tox-py35 [2] https://review.openstack.org/#/c/627888/ [3] https://review.openstack.org/#/c/610184/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1810314/+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 1804274] Re: Neutron error agreggation interfaces
** Changed in: neutron
Status: Confirmed => In Progress
** 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/1804274
Title:
Neutron error agreggation interfaces
Status in neutron:
Fix Released
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
[Yahoo-eng-team] [Bug 1811261] [NEW] Osprofiler not working with Redis in Horizon
Public bug reported: Hi, I wanted to have osprofiler support in horizon ( openstack-dashboard ) with redis driver. I found several issues >> 1. Horizon UnicodeDecodeError : UnicodeDecodeError at /auth/login/ 'ascii' codec can't decode byte 0xe2 in position 63097: ordinal not in range(128) Request Method: GET Request URL:http://openstack-controller/auth/login/?next=/ Django Version: 1.10.7 Exception Type: UnicodeDecodeError Exception Value: 'ascii' codec can't decode byte 0xe2 in position 63097: ordinal not in range(128) Exception Location: /usr/lib/python3.5/encodings/ascii.py in decode, line 26 Python Executable: /usr/bin/python3 Python Version: 3.5.3 Python Path: ['/usr/share/openstack-dashboard', '/usr/lib/python35.zip', '/usr/lib/python3.5', '/usr/lib/python3.5/plat-x86_64-linux-gnu', '/usr/lib/python3.5/lib-dynload', '/usr/local/lib/python3.5/dist-packages', '/usr/lib/python3/dist-packages', '/usr/share/openstack-dashboard/', '/usr/share/openstack-dashboard/openstack_dashboard'] Server time:Thu, 10 Jan 2019 16:38:25 + Error during template rendering In template /usr/lib/python3/dist-packages/horizon/templates/auth/login.html, error at line 0 Above error is causing three dot in >> openstack_dashboard/contrib/developer/static/dashboard/developer/theme-preview/theme-preview.html: One fine body… openstack_dashboard/contrib/developer/static/dashboard/developer/theme-preview/theme-preview.html: One small body… openstack_dashboard/contrib/developer/static/dashboard/developer/theme-preview/theme-preview.html: One tiny body… openstack_dashboard/contrib/developer/static/dashboard/developer/theme-preview/theme-preview.html: One large body… openstack_dashboard/contrib/developer/static/dashboard/developer/theme-preview/theme-preview.html: One super large body… 2. Horizon missing fields in list_traces function , bad calling engine.list_traces: -fields = ['base_id', 'timestamp', 'info.request.path'] +fields = ['base_id', 'timestamp', 'info.request.path', 'info'] -traces = engine.list_traces(query, fields) +traces = engine.list_traces(fields) 3. Horizon python3 binary issue : TypeError at /project/ b'eyJobWFjX2tleSI6ICJzZWNyZXQiLCAicGFyZW50X2lkIjogIjQ2MzlmNDQzLTk5ODgtNDUwNy1hODkzLWZkZGI2NGU5MGM2YiIsICJiYXNlX2lkIjogImVkYTgyMDFlLWQxYzctNGYyNS04YTQ5LTMxN2QxNGE3ZGNlNSJ9' is not JSON serializable Osprofiler bug report >> https://bugs.launchpad.net/osprofiler/+bug/1811260 ** Affects: horizon Importance: Undecided Assignee: Michal Arbet (michalarbet) Status: In Progress ** Changed in: horizon Assignee: (unassigned) => Michal Arbet (michalarbet) ** Changed in: horizon Status: New => 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/1811261 Title: Osprofiler not working with Redis in Horizon Status in OpenStack Dashboard (Horizon): In Progress Bug description: Hi, I wanted to have osprofiler support in horizon ( openstack-dashboard ) with redis driver. I found several issues >> 1. Horizon UnicodeDecodeError : UnicodeDecodeError at /auth/login/ 'ascii' codec can't decode byte 0xe2 in position 63097: ordinal not in range(128) Request Method: GET Request URL: http://openstack-controller/auth/login/?next=/ Django Version: 1.10.7 Exception Type: UnicodeDecodeError Exception Value: 'ascii' codec can't decode byte 0xe2 in position 63097: ordinal not in range(128) Exception Location: /usr/lib/python3.5/encodings/ascii.py in decode, line 26 Python Executable:/usr/bin/python3 Python Version: 3.5.3 Python Path: ['/usr/share/openstack-dashboard', '/usr/lib/python35.zip', '/usr/lib/python3.5', '/usr/lib/python3.5/plat-x86_64-linux-gnu', '/usr/lib/python3.5/lib-dynload', '/usr/local/lib/python3.5/dist-packages', '/usr/lib/python3/dist-packages', '/usr/share/openstack-dashboard/', '/usr/share/openstack-dashboard/openstack_dashboard'] Server time: Thu, 10 Jan 2019 16:38:25 + Error during template rendering In template /usr/lib/python3/dist-packages/horizon/templates/auth/login.html, error at line 0 Above error is causing three dot in >> openstack_dashboard/contrib/developer/static/dashboard/developer/theme-preview/theme-preview.html: One fine body… openstack_dashboard/contrib/developer/static/dashboard/developer/theme-preview/theme-preview.html: One small body… openstack_dashboard/contrib/developer/static/dashboard/developer/theme-preview/theme-preview.html: One tiny body… openstack_dashboard/contrib/developer/static/dashboard/developer/theme-preview/theme-preview.html: One large body… openstack_dashboard/contrib/developer/static/dashboard/developer/theme-preview/theme-preview.html: One super large body… 2. Horizon missing fields in list_traces function , bad calling engine.lis
[Yahoo-eng-team] [Bug 1811238] [NEW] Install and configure controller node in neutron (manual) - Prerequisites
Public bug reported: - [X] This doc is inaccurate in this way: In section 1 the command: # mysql should be: # mysql -u root -p for reference check: https://docs.openstack.org/nova/rocky/install/controller-install-rdo.html --- Release: 13.0.3.dev26 on 2019-01-04 17:45 SHA: 025e767b94cf29e522a67e3c1ddd8aa3dba9140a Source: https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/controller-install-rdo.rst URL: https://docs.openstack.org/neutron/rocky/install/controller-install-rdo.html ** Affects: neutron Importance: Undecided Status: New ** Tags: doc -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1811238 Title: Install and configure controller node in neutron (manual) - Prerequisites Status in neutron: New Bug description: - [X] This doc is inaccurate in this way: In section 1 the command: # mysql should be: # mysql -u root -p for reference check: https://docs.openstack.org/nova/rocky/install/controller-install-rdo.html --- Release: 13.0.3.dev26 on 2019-01-04 17:45 SHA: 025e767b94cf29e522a67e3c1ddd8aa3dba9140a Source: https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/controller-install-rdo.rst URL: https://docs.openstack.org/neutron/rocky/install/controller-install-rdo.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1811238/+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 1811235] [NEW] instance's vm-state becomes error when cold-migrate instance to same host failed
Public bug reported:
step 1: boot a simple instance
step 2: stop the running instance which is booted in step 1
step 3: migrate the instance to same host，but the driver in the host doesn't
support migrate to same host
step 4: nova show uuid(instance uuid), the instance's vm-state becomes error,
and the fault show {"message": "Unable to migrate instance ( instance uuid) to
current host (hostname)
step 5: nova instance-action-list uuid(instance uuid), you will see migrate
error.
** 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/1811235
Title:
instance's vm-state becomes error when cold-migrate instance to same
host failed
Status in OpenStack Compute (nova):
New
Bug description:
step 1: boot a simple instance
step 2: stop the running instance which is booted in step 1
step 3: migrate the instance to same host，but the driver in the host doesn't
support migrate to same host
step 4: nova show uuid(instance uuid), the instance's vm-state becomes error,
and the fault show {"message": "Unable to migrate instance ( instance uuid) to
current host (hostname)
step 5: nova instance-action-list uuid(instance uuid), you will see migrate
error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1811235/+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 1562758] Re: generate an uuid for image id
** Changed in: glance
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1562758
Title:
generate an uuid for image id
Status in Glance:
Won't Fix
Bug description:
Why not use `oslo_utils.uuidutils.generate_uuid` function
def new_image(self, image_id=None, name=None, visibility='private',
min_disk=0, min_ram=0, protected=False, owner=None,
disk_format=None, container_format=None,
extra_properties=None, tags=None, **other_args):
extra_properties = extra_properties or {}
self._check_readonly(other_args)
self._check_unexpected(other_args)
self._check_reserved(extra_properties)
if image_id is None:
image_id = str(uuid.uuid4())
created_at = timeutils.utcnow()
updated_at = created_at
status = 'queued'
I think :
image_id = uuidtils.generate_uuid()
don't use
mage_id = str(uuid.uuid4())
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1562758/+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 1811213] [NEW] Floatingip status changed to error when restart l3-agent
Public bug reported: When l3 agent is restarted on a dvr_snat node that is configured for L3_HA and has a centralized FloatingIP configured to the qg-interface in the snat_namespace, that status of FloatingIP changed to be ERROR l3-agent.log: 2019-01-08 18:03:25.759 2193 WARNING neutron.agent.l3.dvr_edge_router [-] Unable to configure IP address for centralized floating IP: a5715ce8-e26d-4b1a-8260-8ce82cc86a14: IpAddressAlreadyExists: IP address 172.24.4.31 already configured on qg-2c8abdd4-15. 2019-01-08 18:03:25.760 2193 INFO neutron.agent.l3.router_info [-] Floating ip a5715ce8-e26d-4b1a-8260-8ce82cc86a14 added, status ERROR ** Affects: neutron Importance: Undecided Assignee: hujin (hujin) Status: New ** Project changed: snapcraft => neutron ** Changed in: neutron Assignee: (unassigned) => hujin (hujin) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1811213 Title: Floatingip status changed to error when restart l3-agent Status in neutron: New Bug description: When l3 agent is restarted on a dvr_snat node that is configured for L3_HA and has a centralized FloatingIP configured to the qg-interface in the snat_namespace, that status of FloatingIP changed to be ERROR l3-agent.log: 2019-01-08 18:03:25.759 2193 WARNING neutron.agent.l3.dvr_edge_router [-] Unable to configure IP address for centralized floating IP: a5715ce8-e26d-4b1a-8260-8ce82cc86a14: IpAddressAlreadyExists: IP address 172.24.4.31 already configured on qg-2c8abdd4-15. 2019-01-08 18:03:25.760 2193 INFO neutron.agent.l3.router_info [-] Floating ip a5715ce8-e26d-4b1a-8260-8ce82cc86a14 added, status ERROR To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1811213/+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 1811213] [NEW] Floatingip status changed to error when restart l3-agent
You have been subscribed to a public bug: When l3 agent is restarted on a dvr_snat node that is configured for L3_HA and has a centralized FloatingIP configured to the qg-interface in the snat_namespace, that status of FloatingIP changed to be ERROR l3-agent.log: 2019-01-08 18:03:25.759 2193 WARNING neutron.agent.l3.dvr_edge_router [-] Unable to configure IP address for centralized floating IP: a5715ce8-e26d-4b1a-8260-8ce82cc86a14: IpAddressAlreadyExists: IP address 172.24.4.31 already configured on qg-2c8abdd4-15. 2019-01-08 18:03:25.760 2193 INFO neutron.agent.l3.router_info [-] Floating ip a5715ce8-e26d-4b1a-8260-8ce82cc86a14 added, status ERROR ** Affects: neutron Importance: Undecided Status: New -- Floatingip status changed to error when restart l3-agent https://bugs.launchpad.net/bugs/1811213 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- 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 1807421] Re: Open vSwitch hardware offloading in neutron updates
Reviewed: https://review.openstack.org/625000 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7197079a3f632cc4b7d7cc27b4aab35da8ba4b3f Submitter: Zuul Branch:master commit 7197079a3f632cc4b7d7cc27b4aab35da8ba4b3f Author: Bence Romsics Date: Thu Dec 13 14:38:37 2018 +0100 doc: Add NICs known to support ovs offload Add cards to the known-to-work list as requested in a bug report. Change-Id: I2dc1c36df5610d8927c3de3675fb186f5ea2e462 Closes-Bug: #1807421 ** 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/1807421 Title: Open vSwitch hardware offloading in neutron updates Status in neutron: Fix Released Bug description: - [X] This doc is inaccurate in this way: The "Supported Ethernet Controllers" list only the Mellanox CX-4 and CX-5. A more complete list would be: Broadcom NetXtreme-S, NetXtreme-E series NICs Mellanox ConnectX-4 NIC (VLAN Offload) Mellanox ConnectX-4 Lx/ConnectX-5 NICs (VLAN/VXLAN Offload) --- Release: 13.0.3.dev14 on 2018-12-05 13:31 SHA: 8f3fd6815cf34fcb9a60896b996c52a50c428aee Source: https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/admin/config-ovs-offload.rst URL: https://docs.openstack.org/neutron/rocky/admin/config-ovs-offload.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1807421/+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
