[Yahoo-eng-team] [Bug 1373359] Re: Vxlan UDP port value is not getting updated in db
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1373359
Title:
Vxlan UDP port value is not getting updated in db
Status in neutron:
Expired
Bug description:
The value for Vxlan UDP port should be changed in
'ml2_vxlan_endpoints' table according to the values configured in
ml2_conf.ini at L2 agent side.
Currently, it is hard coded with VXLAN_UDP_PORT = 4789 in
type_vxlan.py
def add_endpoint(self, ip, udp_port=VXLAN_UDP_PORT):
LOG.debug(_("add_vxlan_endpoint() called for ip %s"), ip).
The tunnel_sync() rpc should send the UDP port to it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1373359/+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 1713970] Re: Keystone Internal Server Error (HTTP 500) after apache restart when influxdb is installed
[Expired for OpenStack Identity (keystone) because there has been no activity for 60 days.] ** Changed in: keystone Status: Incomplete => Expired -- 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/1713970 Title: Keystone Internal Server Error (HTTP 500) after apache restart when influxdb is installed Status in OpenStack Identity (keystone): Expired Bug description: When influxdb is installed, a Internal Server Error is shown with this trace in /var/log/apache2/keystone.log after executing systemctl restart apache2. Influxdb version is- 1.3.5 Logs: 2017-08-30 17:32:36.492291 OSError: [Errno 13] Permission denied: '/usr/local/lib/python2.7/dist-packages/urllib3-1.22.dist-info' 2017-08-30 17:33:15.741127 mod_wsgi (pid=3736): Target WSGI script '/usr/bin/keystone-wsgi-public' cannot be loaded as Python module. 2017-08-30 17:33:15.741187 mod_wsgi (pid=3736): Exception occurred processing WSGI script '/usr/bin/keystone-wsgi-public'. 2017-08-30 17:33:15.741218 Traceback (most recent call last): 2017-08-30 17:33:15.741235 File "/usr/bin/keystone-wsgi-public", line 6, in 2017-08-30 17:33:15.741295 from keystone.server.wsgi import initialize_public_application 2017-08-30 17:33:15.741306 File "/usr/lib/python2.7/dist-packages/keystone/server/wsgi.py", line 18, in 2017-08-30 17:33:15.741360 from oslo_log import log 2017-08-30 17:33:15.741369 File "/usr/lib/python2.7/dist-packages/oslo_log/log.py", line 42, in 2017-08-30 17:33:15.741467 from oslo_config import cfg 2017-08-30 17:33:15.741476 File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 458, in 2017-08-30 17:33:15.742008 import debtcollector 2017-08-30 17:33:15.742031 File "/usr/lib/python2.7/dist-packages/debtcollector/init.py", line 15, in 2017-08-30 17:33:15.742077 import pbr.version 2017-08-30 17:33:15.742087 File "/usr/lib/python2.7/dist-packages/pbr/version.py", line 25, in 2017-08-30 17:33:15.742198 import pkg_resources 2017-08-30 17:33:15.742208 File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3019, in 2017-08-30 17:33:15.742784 @_call_aside 2017-08-30 17:33:15.742801 File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3003, in _call_aside 2017-08-30 17:33:15.742819 f(*args, **kwargs) 2017-08-30 17:33:15.742841 File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3032, in _initialize_master_working_set 2017-08-30 17:33:15.742852 working_set = WorkingSet._build_master() 2017-08-30 17:33:15.742858 File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 646, in _build_master 2017-08-30 17:33:15.742867 ws = cls() 2017-08-30 17:33:15.742872 File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 639, in init 2017-08-30 17:33:15.742879 self.add_entry(entry) 2017-08-30 17:33:15.742884 File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 695, in add_entry 2017-08-30 17:33:15.742892 for dist in find_distributions(entry, True): 2017-08-30 17:33:15.742897 File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2012, in find_on_path 2017-08-30 17:33:15.742905 if len(os.listdir(fullpath)) == 0: To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1713970/+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 1481622] Re: All workflow view miss url for a cancel action
As of Queens, we have 'Cancel' button in the workflow. ** Changed in: horizon Assignee: Sunkara Ramya Sree (ramyasunkara) => (unassigned) ** Changed in: horizon Status: In Progress => Invalid ** Changed in: horizon Milestone: next => None ** Changed in: horizon Importance: Low => Undecided -- 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/1481622 Title: All workflow view miss url for a cancel action Status in OpenStack Dashboard (Horizon): Invalid Bug description: All WorkflowView miss url for a cancel action, But all FormView has. When open the form modal in a the page, there has cancel button and cancel action, but the workflow modal in a new page does not have. please see the attachment picture for more detail, just give an example. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1481622/+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 1571733] Re: vol_create can not be configured
*** This bug is a duplicate of bug 1678109 *** https://bugs.launchpad.net/bugs/1678109 This is superseded by bug 1678109. ** This bug has been marked a duplicate of bug 1678109 Boot from volume default ** Changed in: horizon Milestone: next => None ** Changed in: horizon Assignee: Yosef Hoffman (yohoffman) => (unassigned) -- 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/1571733 Title: vol_create can not be configured Status in OpenStack Dashboard (Horizon): In Progress Bug description: Currently, there is no configuration option to set vol_create to true. The only way to achieve this is by manually altering the Javascript: https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/launch-instance-model.service.js#L175 This should be configurable via Launch Instance defaults: http://docs.openstack.org/developer/horizon/topics/settings.html#launch-instance-defaults To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1571733/+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 1643793] Re: Display incorrect flavor name in instance property after edit flavor
"Edit Flavor" in horizon is actually NOT "edit". It deletes a specified flavor and re-creates a new flavor with new values. Flavor ID will be changed (see bug 1276371). Thus this is an expected behavior. In addition, "Edit Flavor" in horizon is now deprecated in Pike (bug 1709056 for more detail) and will be dropped in near future. ** Changed in: horizon Status: Confirmed => Won't Fix ** Changed in: horizon Assignee: guoshan (guoshan) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1643793 Title: Display incorrect flavor name in instance property after edit flavor Status in OpenStack Dashboard (Horizon): Won't Fix Status in OpenStack Compute (nova): Invalid Bug description: Description === Display incorrect flavor name in instance property after edit flavor Steps to reproduce == All of the below steps are on the web page. 1.create a new flavor name is AAA 2.create vm with AAA flavor 3.check vm info that flavor name is AAA 4.edit the flavor, change flavor name AAA to BBB 5.check vm info again, the flavor name is not BBB Expected result === Display correct flavor name after edit flavor name. Actual result = The vm flavor name is not correct after edit flavor name. By the nova-api.log file, the edit flavor operation is that first to delete the origin flavor, second to create a new flavor. But vm flavor'id was original id, not the new id. Environment === 1. Devstack with newton version To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1643793/+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 1375820] Re: Html file uses for layout
routerrules extension was dropped from horizon, so it is no longer valid. ** Changed in: horizon Status: In Progress => Invalid ** Changed in: horizon Importance: Low => Undecided -- 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/1375820 Title: Html file uses for layout Status in OpenStack Dashboard (Horizon): Invalid Bug description: openstack_dashboard/dashboards/project/routers/templates/routers/extensions/routerrules/grid.html uses ' ' to add extra padding in places. The should be removed and instead use css to add in the padding To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1375820/+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 1655563] Re: launch a instance which name include spot failed
It happens even with CLI. http://paste.openstack.org/show/628012/ Looks line a nova bug. ** Changed in: horizon Milestone: next => None ** Changed in: horizon Assignee: yan tan (yetbing) => (unassigned) ** Project changed: horizon => nova ** Changed in: nova Status: Triaged => New ** Changed in: nova Importance: Wishlist => Undecided -- 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/1655563 Title: launch a instance which name include spot failed Status in OpenStack Compute (nova): New Bug description: can not launch a instance which name include spot and number like 14.4. nova-conductor.log find this error. 2017-01-11 16:27:46.928 23 ERROR nova.scheduler.utils [req-ed6f17d5-ef49-412e-8e7e-703b7ed5738b eef7aab2a2bf4067a4baf27cdbe62cc6 90e82be1b4a34c62a27d4fde986e00c2 - - -] [instance: 46fe3b71-0c90-458c-8be6-cd9dcd8733a3] Error from last host: compute1 (node compute1): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1926, in _do_build_and_run_instance\nfilter_properties)\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2116, in _build_and_run_instance\ninstance_uuid=instance.uuid, reason=six.text_type(e))\n', u"RescheduledException: Build of instance 46fe3b71-0c90-458c-8be6-cd9dcd8733a3 was re-scheduled: Invalid input for dns_name. Reason: '14.4' not a valid PQDN or FQDN. Reason: TLD '4' must not be all numeric.\nNeutron server returns request_ids: ['req-9a2fa7cb-35cd-462f-973d-5c618b72b18d']\n"] 2017-01-11 16:27:47.113 23 WARNING nova.scheduler.utils [req-ed6f17d5-ef49-412e-8e7e-703b7ed5738b eef7aab2a2bf4067a4baf27cdbe62cc6 90e82be1b4a34c62a27d4fde986e00c2 - - -] Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1655563/+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 1735557] Re: Failed HA router initialization can lead to exception
Reviewed: https://review.openstack.org/524404 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c62d54d0c21fc4a760d2ac6501f9493137c5eb8a Submitter: Zuul Branch:master commit c62d54d0c21fc4a760d2ac6501f9493137c5eb8a Author: Brian Haley Date: Thu Nov 30 16:47:43 2017 -0500 Fix HA router initialization exception When an HA router initialization fails early, it can lead to: AttributeError: 'HaRouter' object has no attribute 'process_monitor' Add init of 'self.process_monitor' in RouterInfo init code in case we try and cleanup early. Change-Id: Iddeaeef13adee10f7b130e3f9e584b6e9f037030 Closes-bug: #1735557 ** 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/1735557 Title: Failed HA router initialization can lead to exception Status in neutron: Fix Released Bug description: When an HA router initialization fails, it can lead to the following exception: ERROR neutron.agent.l3.ha_router [-] Unable to process HA router 59fad7c2-d393-464f-820b-334927047e64 without HA port TRACE neutron.agent.l3.ha_router None TRACE neutron.agent.l3.ha_router ERROR neutron.agent.l3.agent [-] Error while initializing router 59fad7c2-d393-464f-820b-334927047e64 TRACE neutron.agent.l3.agent Traceback (most recent call last): TRACE neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/neutron/agent/l3/agent.py", line 335, in _router_added TRACE neutron.agent.l3.agent ri.initialize(self.process_monitor) TRACE neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/neutron/agent/l3/ha_router.py", line 83, in initialize TRACE neutron.agent.l3.agent raise Exception(msg) TRACE neutron.agent.l3.agent Exception: Unable to process HA router 59fad7c2-d393-464f-820b-334927047e64 without HA port TRACE neutron.agent.l3.agent ERROR neutron.agent.l3.agent [-] Error while deleting router 59fad7c2-d393-464f-820b-334927047e64 TRACE neutron.agent.l3.agent Traceback (most recent call last): TRACE neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/neutron/agent/l3/agent.py", line 342, in _router_added TRACE neutron.agent.l3.agent ri.delete(self) TRACE neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/neutron/agent/l3/ha_router.py", line 359, in delete TRACE neutron.agent.l3.agent self.destroy_state_change_monitor(self.process_monitor) TRACE neutron.agent.l3.agent AttributeError: 'HaRouter' object has no attribute 'process_monitor' The problem is that self.process_monitor is added in RouterInfo.initialize(), but that isn't called after we verify an ha_port exists in HaRouter.initialize(). Adding 'self.process_monitor = None' in RouterInfo.__init__ should fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1735557/+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 1600540] Re: Show snapshot metadata key values in snapshot detailed view
Per #3, the issue has been addressed. Let's change the status to Fix Released. ** Changed in: horizon Status: Fix Committed => Fix Released ** Changed in: horizon Assignee: Vivek Agrawal (vivek-agrawal) => (unassigned) -- 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/1600540 Title: Show snapshot metadata key values in snapshot detailed view Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Show Snapshot metadata in the detailed view available for Snapshot(Just like we show volume metadata for volumes in Volume detailed view). This can be treated as an enhancement. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1600540/+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 1708671] Re: i18n javascript on login page requires login
Fix Committed means a fix is merged into the repository. In this case, this patch(https://review.openstack.org/#/c/490131/) is not a fix. The issue just disappears after that, so "Invalid' looks better. ** Changed in: horizon Status: Fix Committed => Invalid -- 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/1708671 Title: i18n javascript on login page requires login Status in OpenStack Dashboard (Horizon): Invalid Bug description: When using the Horizon version currently available on git, Angular is unable to load due to - it appears - the i18n JavaScript file being unable to load. The request for this JavaScript is being redirected when at the login screen. When logged in, loading this file is giving no problems. Browser consoles gives the following: /dashboard/auth/login/?next=/dashboard/i18n/js/horizon%2Bopenstack_dashboard/:5 Uncaught SyntaxError: Unexpected token < At which point the whole Angular app seems to fail due to not having gettext available. The redirect to the login page happens consistently on two instances of devstack (both set up this week), both http and https, Chrome 59 and Firefox 54. The impact of this bug is very small: - Keystone credential login appears to work as usual - Federated login/WEBSSO does not hide the user/pass fields, creating an inconvenience of having to fill in useless data for these users. This is how I found out about this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1708671/+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 1493998] Re: Integration tests should use unicode characters in user-provided data
We no longer maintain the integration tests, so let's mark it as Won't Fix. ** Changed in: horizon Milestone: next => None ** Changed in: horizon Status: New => Won't Fix -- 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/1493998 Title: Integration tests should use unicode characters in user-provided data Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: The bug 1488443 showed us that Unicode was broken in Horizon and we didn't even know this. Using unicode characters in every name generator in integration tests will help to catch some unicode issues before they hit us hard. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1493998/+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 1433522] Re: gate shouldn't rely on default values horizon.conf
We disabled the integration tests long ago, so we mark this as Won't Fix. ** Changed in: horizon Status: New => Won't Fix -- 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/1433522 Title: gate shouldn't rely on default values horizon.conf Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: Currently when any variable in horizon.conf is changed, it will be immediately reflected to gate job, because it uses untouched file as it is in repository. horizon.conf should be patched in gate job before run integration tests to be sure, that it will run much more independentely. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1433522/+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 1722417] Re: [Performance] Useless network API calls on instance panel
** Changed in: horizon Status: Opinion => In Progress ** Changed in: horizon Assignee: Feilong Wang (flwang) => Akihiro Motoki (amotoki) -- 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/1722417 Title: [Performance] Useless network API calls on instance panel Status in OpenStack Dashboard (Horizon): In Progress Bug description: The function calling at https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/views.py#L95 is useless because Horizon is using the detailed API to get server list, see https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/nova.py#L529 With detailed API, the addresses of server are returned. So there is no need to call Neutron API to get the addresses info. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1722417/+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 1731421] Re: nodejs-npm-run-test fails because of "No binary for Chrome browser on your platform"
As horizon perspective, the gate fix has been fixed, so let's mark it as Fix Released. ** 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/1731421 Title: nodejs-npm-run-test fails because of "No binary for Chrome browser on your platform" Status in OpenStack Dashboard (Horizon): Fix Released Bug description: nodejs-npm-run-test job fails with the following error: 2017-11-10 08:40:38.047617 | ubuntu-xenial | [32m10 11 2017 08:40:38.044:INFO [karma]: [39mKarma v1.1.2 server started at http://localhost:9876/ 2017-11-10 08:40:38.048797 | ubuntu-xenial | [32m10 11 2017 08:40:38.048:INFO [launcher]: [39mLaunching browser Chrome with unlimited concurrency 2017-11-10 08:40:38.056114 | ubuntu-xenial | [32m10 11 2017 08:40:38.056:INFO [launcher]: [39mStarting browser Chrome 2017-11-10 08:40:38.057322 | ubuntu-xenial | [31m10 11 2017 08:40:38.057:ERROR [launcher]: [39mNo binary for Chrome browser on your platform. 2017-11-10 08:40:38.057372 | ubuntu-xenial | Please, set "CHROME_BIN" env variable. http://logs.openstack.org/44/518844/1/check/nodejs-npm-run- test/19e8ef5/job-output.txt.gz#_2017-11-10_08_40_38_057322 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1731421/+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 1735935] [NEW] get_html_theme_path() is commented out in glance-specs doc conf.py
Public bug reported: Abhishek noticed that one of the changes to doc/source/conf.py committed in https://review.openstack.org/#/c/523233/ was commented out, but the patch was merged before this mistake was corrected. ** Affects: glance Importance: Low Assignee: Brian Rosmaita (brian-rosmaita) Status: Triaged ** Tags: glance-specs ** Summary changed: - get_theme() is commented out in glance-specs doc conf.py + get_html_theme_path() is commented out in glance-specs doc conf.py -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1735935 Title: get_html_theme_path() is commented out in glance-specs doc conf.py Status in Glance: Triaged Bug description: Abhishek noticed that one of the changes to doc/source/conf.py committed in https://review.openstack.org/#/c/523233/ was commented out, but the patch was merged before this mistake was corrected. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1735935/+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
