[Yahoo-eng-team] [Bug 1503985] [NEW] Firewall-rule-update does not show ip_version, source_address or destination address but does in horizon
Public bug reported:
Following is the error message from firewall-rule-update
reedip@reedip-VirtualBox:~/DocNCode/devstack$ neutron firewall-rule-update
usage: neutron firewall-rule-update [-h] [--request-format {json,xml}]
[--protocol {tcp,udp,icmp,any}]
FIREWALL_RULE
However, the following is possible:
reedip@reedip-VirtualBox:~/DocNCode/devstack$ neutron firewall-rule-update
--ip-version=4 Test3
Updated firewall_rule: Test3
BEFORE:
reedip@reedip-VirtualBox:~/DocNCode/devstack$ neutron firewall-rule-show Test3
++--+
| Field | Value|
++--+
| action | allow|
| description| |
| destination_ip_address | |
| destination_port | |
| enabled| True |
| firewall_policy_id | |
| id | cd45f338-c4d7-4287-b42e-5b1c7a7d2cec |
| ip_version | 6|
| name | Test3|
| position | |
| protocol | tcp |
| shared | False|
| source_ip_address | |
| source_port| |
| tenant_id | 839568f2ae6b4ed4af320ddc66e39bbd |
++--+
AFTER:
reedip@reedip-VirtualBox:~/DocNCode/devstack$ neutron firewall-rule-show Test3
++--+
| Field | Value|
++--+
| action | allow|
| description| |
| destination_ip_address | |
| destination_port | |
| enabled| True |
| firewall_policy_id | |
| id | cd45f338-c4d7-4287-b42e-5b1c7a7d2cec |
| ip_version | 4|
| name | Test3|
| position | |
| protocol | tcp |
| shared | False|
| source_ip_address | |
| source_port| |
| tenant_id | 839568f2ae6b4ed4af320ddc66e39bbd |
++--+
As this possibility to change the firewall-rule exists, the same needs
to be shown in the help for firewall-rule-update
** Affects: python-neutronclient
Importance: Undecided
Assignee: Reedip (reedip-banerjee)
Status: New
** Tags: fwaas
** Changed in: horizon
Assignee: (unassigned) => Reedip (reedip-banerjee)
** Project changed: horizon => python-neutronclient
** Tags added: fwaas
--
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/1503985
Title:
Firewall-rule-update does not show ip_version, source_address or
destination address but does in horizon
Status in python-neutronclient:
New
Bug description:
Following is the error message from firewall-rule-update
reedip@reedip-VirtualBox:~/DocNCode/devstack$ neutron firewall-rule-update
usage: neutron firewall-rule-update [-h] [--request-format {json,xml}]
[--protocol {tcp,udp,icmp,any}]
FIREWALL_RULE
However, the following is possible:
reedip@reedip-VirtualBox:~/DocNCode/devstack$ neutron firewall-rule-update
--ip-version=4 Test3
Updated firewall_rule: Test3
BEFORE:
reedip@reedip-VirtualBox:~/DocNCode/devstack$ neutron firewall-rule-show Test3
++--+
| Field | Value|
++--+
| action | allow|
| description| |
| destination_ip_address | |
| destination_port
[Yahoo-eng-team] [Bug 1504033] [NEW] Insecure option missing in nova.conf section ironic
Public bug reported: For the ironic section in nova.conf the insecure option is not available. Mostly all other sections support that. Seen in stable Kilo. ** Affects: nova Importance: Undecided Assignee: Tom Patzig (tom-patzig) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Tom Patzig (tom-patzig) ** Changed in: nova Status: New => 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/1504033 Title: Insecure option missing in nova.conf section ironic Status in OpenStack Compute (nova): In Progress Bug description: For the ironic section in nova.conf the insecure option is not available. Mostly all other sections support that. Seen in stable Kilo. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1504033/+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 1504039] [NEW] Linuxbridge DVR
Public bug reported: Achieve DVR with Linuxbridge instead of Openvswitch. ** Affects: neutron Importance: Undecided Assignee: Hirofumi Ichihara (ichihara-hirofumi) Status: New ** Tags: rfe ** Changed in: neutron Assignee: (unassigned) => Hirofumi Ichihara (ichihara-hirofumi) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1504039 Title: Linuxbridge DVR Status in neutron: New Bug description: Achieve DVR with Linuxbridge instead of Openvswitch. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1504039/+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 1503975] [NEW] no such option: consoleauth_topic
Public bug reported: [gongysh@fedora22 nova]$ /usr/bin/nova-consoleauth --config-file /etc/nova/nova.conf No handlers could be found for logger "oslo_config.cfg" 2015-10-08 14:25:50.996 31923 CRITICAL nova [-] NoSuchOptError: no such option: consoleauth_topic 2015-10-08 14:25:50.996 31923 ERROR nova Traceback (most recent call last): 2015-10-08 14:25:50.996 31923 ERROR nova File "/usr/bin/nova-consoleauth", line 10, in 2015-10-08 14:25:50.996 31923 ERROR nova sys.exit(main()) 2015-10-08 14:25:50.996 31923 ERROR nova File "/mnt/data3/opt/stack/nova/nova/cmd/consoleauth.py", line 40, in main 2015-10-08 14:25:50.996 31923 ERROR nova topic=CONF.consoleauth_topic) 2015-10-08 14:25:50.996 31923 ERROR nova File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 1902, in __getattr__ 2015-10-08 14:25:50.996 31923 ERROR nova raise NoSuchOptError(name) 2015-10-08 14:25:50.996 31923 ERROR nova NoSuchOptError: no such option: consoleauth_topic 2015-10-08 14:25:50.996 31923 ERROR nova ** Affects: nova Importance: Undecided Assignee: yong sheng gong (gongysh) Status: In Progress ** Changed in: nova Assignee: (unassigned) => yong sheng gong (gongysh) -- 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/1503975 Title: no such option: consoleauth_topic Status in OpenStack Compute (nova): In Progress Bug description: [gongysh@fedora22 nova]$ /usr/bin/nova-consoleauth --config-file /etc/nova/nova.conf No handlers could be found for logger "oslo_config.cfg" 2015-10-08 14:25:50.996 31923 CRITICAL nova [-] NoSuchOptError: no such option: consoleauth_topic 2015-10-08 14:25:50.996 31923 ERROR nova Traceback (most recent call last): 2015-10-08 14:25:50.996 31923 ERROR nova File "/usr/bin/nova-consoleauth", line 10, in 2015-10-08 14:25:50.996 31923 ERROR nova sys.exit(main()) 2015-10-08 14:25:50.996 31923 ERROR nova File "/mnt/data3/opt/stack/nova/nova/cmd/consoleauth.py", line 40, in main 2015-10-08 14:25:50.996 31923 ERROR nova topic=CONF.consoleauth_topic) 2015-10-08 14:25:50.996 31923 ERROR nova File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 1902, in __getattr__ 2015-10-08 14:25:50.996 31923 ERROR nova raise NoSuchOptError(name) 2015-10-08 14:25:50.996 31923 ERROR nova NoSuchOptError: no such option: consoleauth_topic 2015-10-08 14:25:50.996 31923 ERROR nova To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1503975/+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 1503974] [NEW] no such option: consoleauth_topic
Public bug reported: [gongysh@fedora22 nova]$ /usr/bin/nova-consoleauth --config-file /etc/nova/nova.conf No handlers could be found for logger "oslo_config.cfg" 2015-10-08 14:25:50.996 31923 CRITICAL nova [-] NoSuchOptError: no such option: consoleauth_topic 2015-10-08 14:25:50.996 31923 ERROR nova Traceback (most recent call last): 2015-10-08 14:25:50.996 31923 ERROR nova File "/usr/bin/nova-consoleauth", line 10, in 2015-10-08 14:25:50.996 31923 ERROR nova sys.exit(main()) 2015-10-08 14:25:50.996 31923 ERROR nova File "/mnt/data3/opt/stack/nova/nova/cmd/consoleauth.py", line 40, in main 2015-10-08 14:25:50.996 31923 ERROR nova topic=CONF.consoleauth_topic) 2015-10-08 14:25:50.996 31923 ERROR nova File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 1902, in __getattr__ 2015-10-08 14:25:50.996 31923 ERROR nova raise NoSuchOptError(name) 2015-10-08 14:25:50.996 31923 ERROR nova NoSuchOptError: no such option: consoleauth_topic 2015-10-08 14:25:50.996 31923 ERROR nova ** 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/1503974 Title: no such option: consoleauth_topic Status in OpenStack Compute (nova): New Bug description: [gongysh@fedora22 nova]$ /usr/bin/nova-consoleauth --config-file /etc/nova/nova.conf No handlers could be found for logger "oslo_config.cfg" 2015-10-08 14:25:50.996 31923 CRITICAL nova [-] NoSuchOptError: no such option: consoleauth_topic 2015-10-08 14:25:50.996 31923 ERROR nova Traceback (most recent call last): 2015-10-08 14:25:50.996 31923 ERROR nova File "/usr/bin/nova-consoleauth", line 10, in 2015-10-08 14:25:50.996 31923 ERROR nova sys.exit(main()) 2015-10-08 14:25:50.996 31923 ERROR nova File "/mnt/data3/opt/stack/nova/nova/cmd/consoleauth.py", line 40, in main 2015-10-08 14:25:50.996 31923 ERROR nova topic=CONF.consoleauth_topic) 2015-10-08 14:25:50.996 31923 ERROR nova File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 1902, in __getattr__ 2015-10-08 14:25:50.996 31923 ERROR nova raise NoSuchOptError(name) 2015-10-08 14:25:50.996 31923 ERROR nova NoSuchOptError: no such option: consoleauth_topic 2015-10-08 14:25:50.996 31923 ERROR nova To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1503974/+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 1501672] Re: v2 image download returns 403 when 'get_image_locations' policy set
** Changed in: glance Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1501672 Title: v2 image download returns 403 when 'get_image_locations' policy set Status in Glance: Fix Released Status in Glance kilo series: In Progress Bug description: when get_image_location is set role:admin a regular users sees: $ glance --os-image-api-version 2 image-download 33fd3f1a-4924-4078-9d57-d7f6db4d015b 403 Forbidden: You are not authorized to complete this action. (HTTP 403) v1 works ok. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1501672/+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 1498370] Re: DHCP agent: interface unplug leads to exeception
** Changed in: neutron Status: Fix Committed => 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/1498370 Title: DHCP agent: interface unplug leads to exeception Status in neutron: Fix Released Bug description: 2015-09-22 01:23:42.612 ERROR neutron.agent.dhcp.agent [-] Unable to disable dhcp for c543db4d-e077-488f-b58c-5805f63f86b6. 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent Traceback (most recent call last): 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent File "/opt/stack/neutron/neutron/agent/dhcp/agent.py", line 115, in call_driver 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent getattr(driver, action)(**action_kwargs) 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent File "/opt/stack/neutron/neutron/agent/linux/dhcp.py", line 221, in disable 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent self._destroy_namespace_and_port() 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent File "/opt/stack/neutron/neutron/agent/linux/dhcp.py", line 226, in _destroy_namespace_and_port 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent self.device_manager.destroy(self.network, self.interface_name) 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent File "/opt/stack/neutron/neutron/agent/linux/dhcp.py", line 1223, in destroy 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent self.driver.unplug(device_name, namespace=network.namespace) 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent File "/opt/stack/neutron/neutron/agent/linux/interface.py", line 358, in unplug 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent tap_name = self._get_tap_name(device_name, prefix) 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent File "/opt/stack/neutron/neutron/agent/linux/interface.py", line 299, in _get_tap_name 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent dev_name = dev_name.replace(prefix or self.DEV_NAME_PREFIX, 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent AttributeError: 'NoneType' object has no attribute 'replace' 2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent 2015-09-22 01:23:42.616 INFO neutron.agent.dhcp.agent [-] Synchronizing state complete The reason is the device is None To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1498370/+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 1476770] Re: _translate_from_glance fails with "AttributeError: id" in grenade
** No longer affects: fuel -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1476770 Title: _translate_from_glance fails with "AttributeError: id" in grenade Status in Glance: Invalid Status in OpenStack-Gate: Fix Committed Status in oslo.vmware: Fix Released Status in python-glanceclient: New Bug description: http://logs.openstack.org/28/204128/2/check/gate-grenade- dsvm/80607dc/logs/old/screen-n-api.txt.gz?level=TRACE 2015-07-21 17:05:37.447 ERROR nova.api.openstack [req-9854210d-b9fc-47ff-9f00-1a0270266e2a tempest-ServersTestJSON-34270062 tempest-ServersTestJSON-745803609] Caught error: id 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack Traceback (most recent call last): 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/__init__.py", line 125, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return req.get_response(self.application) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1317, in send 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack application, catch_exc_info=False) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1281, in call_application 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack app_iter = application(self.environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 634, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return self._call_app(env, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 554, in _call_app 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return self._app(env, _fake_start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/routes/middleware.py", line 136, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack response = self.app(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack resp = self.call_func(req, *args, **self.kwargs) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return self.func(req, *args, **kwargs) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/wsgi.py", line 756, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack content_type, body, accept) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/wsgi.py", line 821, in _process_stack 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack action_result = self.dispatch(meth, request, action_args) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/wsgi.py", line 911, in dispatch 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return method(req=request, **action_args) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/compute/servers.py", line 636, in create 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack self._handle_create_exception(*sys.exc_info()) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/compute/servers.py", line 465, in
[Yahoo-eng-team] [Bug 1504053] [NEW] Fixtures 1.4.0 makes Py34 unit tests fail
Public bug reported: See the output of http://logs.openstack.org/97/231897/2/check/gate- neutron-python34/57063ea/console.html for complete tracebacks. This can be fixed by using fixtures 1.3.1. ** Affects: neutron Importance: Critical Assignee: Cyril Roelandt (cyril-roelandt) Status: In Progress ** Tags: gate-failure py34 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1504053 Title: Fixtures 1.4.0 makes Py34 unit tests fail Status in neutron: In Progress Bug description: See the output of http://logs.openstack.org/97/231897/2/check/gate- neutron-python34/57063ea/console.html for complete tracebacks. This can be fixed by using fixtures 1.3.1. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1504053/+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 1229820] Re: Code cleanup/refactoring in "router" dashboard
** Changed in: horizon Status: Confirmed => 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/1229820 Title: Code cleanup/refactoring in "router" dashboard Status in OpenStack Dashboard (Horizon): Invalid Bug description: Based on initial code review comments, there is scope for some code cleanup and refactoring of repeated methods in the new "router" dashboard. Additionally some redundant template files can be removed in this dashboard. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1229820/+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 1476770] Re: _translate_from_glance fails with "AttributeError: id" in grenade
** Also affects: fuel Importance: Undecided Status: New ** Changed in: fuel Milestone: None => 8.0 ** Changed in: fuel Assignee: (unassigned) => MOS Packaging Team (mos-packaging) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1476770 Title: _translate_from_glance fails with "AttributeError: id" in grenade Status in Fuel for OpenStack: New Status in Glance: Invalid Status in OpenStack-Gate: Fix Committed Status in oslo.vmware: Fix Released Status in python-glanceclient: New Bug description: http://logs.openstack.org/28/204128/2/check/gate-grenade- dsvm/80607dc/logs/old/screen-n-api.txt.gz?level=TRACE 2015-07-21 17:05:37.447 ERROR nova.api.openstack [req-9854210d-b9fc-47ff-9f00-1a0270266e2a tempest-ServersTestJSON-34270062 tempest-ServersTestJSON-745803609] Caught error: id 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack Traceback (most recent call last): 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/__init__.py", line 125, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return req.get_response(self.application) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1317, in send 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack application, catch_exc_info=False) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1281, in call_application 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack app_iter = application(self.environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 634, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return self._call_app(env, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 554, in _call_app 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return self._app(env, _fake_start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/routes/middleware.py", line 136, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack response = self.app(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return resp(environ, start_response) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack resp = self.call_func(req, *args, **self.kwargs) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return self.func(req, *args, **kwargs) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/wsgi.py", line 756, in __call__ 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack content_type, body, accept) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/wsgi.py", line 821, in _process_stack 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack action_result = self.dispatch(meth, request, action_args) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/wsgi.py", line 911, in dispatch 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return method(req=request, **action_args) 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack File "/opt/stack/old/nova/nova/api/openstack/compute/servers.py", line 636, in create 2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack
[Yahoo-eng-team] [Bug 1472999] Re: filter doesn't handle unicode charaters
** Changed in: horizon Status: In Progress => Invalid ** Changed in: nova Status: In Progress => Fix Committed ** Changed in: python-novaclient Status: In Progress => Fix Committed -- 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/1472999 Title: filter doesn't handle unicode charaters Status in OpenStack Dashboard (Horizon): Invalid Status in OpenStack Compute (nova): Fix Committed Status in python-glanceclient: In Progress Status in python-novaclient: Fix Committed Bug description: 1 go to project/instances 2. insert 'ölk' into filter field 3. enter filter 4. UnicodeEncodeError at /project/instances/ 'ascii' codec can't encode character u'\xf6' in position 0: ordinal not in range(128) Request Method: GET Request URL: http://localhost:8000/project/instances/ Django Version: 1.8.2 Exception Type: UnicodeEncodeError Exception Value: 'ascii' codec can't encode character u'\xf6' in position 0: ordinal not in range(128) Exception Location: /usr/lib64/python2.7/urllib.py in urlencode, line 1347 Python Executable:/usr/bin/python Python Version: 2.7.10 Python Path: ['/home/mrunge/work/horizon', '/usr/lib64/python27.zip', '/usr/lib64/python2.7', '/usr/lib64/python2.7/plat-linux2', '/usr/lib64/python2.7/lib-tk', '/usr/lib64/python2.7/lib-old', '/usr/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7/site-packages', '/usr/lib64/python2.7/site-packages/gtk-2.0', '/usr/lib/python2.7/site-packages', '/home/mrunge/work/horizon/openstack_dashboard'] To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1472999/+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 1321829] Re: horizon.less hard-coded sizes cleanup
Marking this as Invalid: it's being done as part of the wider Bootstrap/ SCSS cleanup, and it's more blueprint-scope then bug at this stage. ** Changed in: horizon Status: Triaged => Invalid ** Changed in: horizon Assignee: huyupeng (huyp) => (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/1321829 Title: horizon.less hard-coded sizes cleanup Status in OpenStack Dashboard (Horizon): Invalid Bug description: Right now, there are a lot of hard-coded pixel sizes. Bad for hi-def screens. Related issue: https://bugs.launchpad.net/horizon/+bug/1288402 with text overflow with translations. Since most sizes are hard-coded, it makes it difficult to restyle even one element. First step: We should move to .em units (We have some. It is currently a mix of px and em) Any other comments about how to make Horizon layout more dynamic are welcome. :) Also, we should avoid things like margin-left: -20px; because I don't think IE renders it properly. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1321829/+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 1156433] Re: network topology can not show up in some version of firefox browser
** Changed in: horizon Status: In Progress => 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/1156433 Title: network topology can not show up in some version of firefox browser Status in OpenStack Dashboard (Horizon): Invalid Bug description: The network topology can not show up in some version of Firefox brower such 17.04, 19.0.2. The canvas is empty. But it looks fine in chrome and IE browser. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1156433/+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 1504123] [NEW] non admin users not able to access network detail page from router detail page
Public bug reported: Non admin users not able to access network detail page from the router detail page since it is redirecting to admin's panel. steps to reproduce: --- 1. login to dashboard (any non admin user) 2. go to any router detail page 3. click on the network id link 4. it will redirect to login page expected behaviour: we should be able to view network detail page without admin access. ** Affects: horizon Importance: Undecided Assignee: Masco Kaliyamoorthy (masco) Status: New ** Changed in: horizon Assignee: (unassigned) => Masco Kaliyamoorthy (masco) -- 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/1504123 Title: non admin users not able to access network detail page from router detail page Status in OpenStack Dashboard (Horizon): New Bug description: Non admin users not able to access network detail page from the router detail page since it is redirecting to admin's panel. steps to reproduce: --- 1. login to dashboard (any non admin user) 2. go to any router detail page 3. click on the network id link 4. it will redirect to login page expected behaviour: we should be able to view network detail page without admin access. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1504123/+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 1312247] Re: not redirected to main page after a session expired
This isn't specific to the snapshot creation; as far as I'm aware, the session bugs have been ironed out now. Please feel free to change the status if the bug is still valid. ** Changed in: horizon Status: New => 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/1312247 Title: not redirected to main page after a session expired Status in OpenStack Dashboard (Horizon): Invalid Bug description: when creating a snapshot for an instance, if the session expires and than we press the "instances" link again to refresh the screen, we get an error in the webadmin instead of being redirected to the login page: This is from the log: //10.35.160.71:35357/v2.0/tenants/c3178ebef2c24d1b9a045bd67483a83c -H "User-Agent: python-keystoneclient" -H "Forwarded: for=10.64.245.229;by=python-keystoneclient" -H "X-Auth-Token: ff244a6dcae7573250e32652773ffb53" 2014-04-24 15:20:28,642 2351 INFO openstack_auth.views Logging out user "admin". 2014-04-24 15:20:30,523 2351 ERROR django.request Internal Server Error: /dashboard/auth/login/ Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/django/core/handlers/base.py", line 136, in get_response response = response.render() File "/usr/lib/python2.6/site-packages/django/template/response.py", line 104, in render self._set_content(self.rendered_content) File "/usr/lib/python2.6/site-packages/django/template/response.py", line 79, in rendered_content template = self.resolve_template(self.template_name) File "/usr/lib/python2.6/site-packages/django/template/response.py", line 57, in resolve_template return loader.get_template(template) File "/usr/lib/python2.6/site-packages/django/template/loader.py", line 145, in get_template File "/usr/lib/python2.6/site-packages/django/template/loader.py", line 138, in find_template TemplateDoesNotExist: auth/login.html (END) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1312247/+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 1194951] Re: Horizon Network Topology doesn't update in IE9
** Changed in: horizon Status: Confirmed => 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/1194951 Title: Horizon Network Topology doesn't update in IE9 Status in OpenStack Dashboard (Horizon): Invalid Bug description: Running the Horizon dashboard (v 1:2013.1.1-0ubuntu1~cloud0) on Grizzly the Network Topology diagram gets drawn once, and then only updates when the cached pages time out in IE. If I clear the IE cache and then go to the network topology for a project, I get the correct diagram. However, if I then go to a different project I get the same diagram for it too. Logging out and back in to the dashboard doesn't chance which diagram I get. Neither does logging in as a different user, or even rebooting the controller. The cached pages seem to time out over night and going to the Network Topology the next morning gives me a good diagram for the current project - but it doesn't automatically get updated again that day. Clearing the IE cache (deleting the Temporary Internet files in IE Tools->Delete...) gives a single valid updated snapshot of the topology. Firefox works correctly, automatically updating the topology diagram as elements come and go. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1194951/+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 1349609] Re: [Bootstrap] Project > Images fixed filter needs styling
This no longer occurs in master branch. ** Changed in: horizon Status: Confirmed => 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/1349609 Title: [Bootstrap] Project > Images fixed filter needs styling Status in OpenStack Dashboard (Horizon): Invalid Bug description: https://review.openstack.org/#/c/107042/ Bootstrap 3 has been updated. When you first load the page, the fixed filter buttons (Project/shared with me/public) all look enabled. If you click on each of them once, they all look disabled instead of only showing the selected one as 'enabled.' see image. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1349609/+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 1504165] [NEW] The Action Detach port/network from Qos-Policy is not working
You have been subscribed to a public bug: After Create Qos-Policy and Qos Rule to Port, I tried to detach the Policy. # neutron port-update --no-qos-policy. >From sriov-nic-agent.log neutron.plugins.ml2.drivers.mech_sriov.agent.eswitch_manager [req- b526991f-0632-4d9d-9b61-638414d7af1d - - - - -] VF with PCI slot :04:00.7 is already assigned; skipping reset maximum rate The BW on vf's didn't Changed. My Environment: - 2 Servers (All in one and Compute). - OS : CentOS Linux release 7.1.1503 (Core) - Kernel version : 3.10.0-123.el7.x86_64 - Openstack Version : Trunk ** Affects: neutron Importance: Undecided Status: New -- The Action Detach port/network from Qos-Policy is not working https://bugs.launchpad.net/bugs/1504165 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 1276722] Re: Upload horizon to pypi
** Changed in: horizon Status: Triaged => 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/1276722 Title: Upload horizon to pypi Status in OpenStack Dashboard (Horizon): Invalid Status in OpenStack Core Infrastructure: Triaged Bug description: Because horizon is not uploaded to pypi, you'll get the following error back from tox 1.6+ now: Some externally hosted files were ignored (use --allow-external horizon to allow). The work around is to use the flag, but ideal it should be hosted on pypi. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1276722/+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 1503712] Re: Error while deleting tenant in openstack Juno
We can use this ticket (I've added openstack-manuals to it), but I don't see anywhere on that page that it says to configure [trust] driver? [revoke] driver is mentioned, but it's value is correct. ** Also affects: openstack-manuals Importance: Undecided Status: New ** Changed in: openstack-manuals Status: New => Incomplete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1503712 Title: Error while deleting tenant in openstack Juno Status in Keystone: Invalid Status in openstack-manuals: Incomplete Bug description: Hi, When I'm trying to delete project with keystone: keystone tenant-delete radomirProject I get this error in keystone.log 2015-10-07 16:28:49.132 2465 INFO eventlet.wsgi.server [-] 10.0.2.60 - - [07/Oct/2015 16:28:49] "POST /v2.0/tokens HTTP/1.1" 200 2494 0.091314 2015-10-07 16:28:49.154 2455 INFO eventlet.wsgi.server [-] 10.0.2.60 - - [07/Oct/2015 16:28:49] "GET /v2.0/tenants/12a876bf668240de8bff9d9869bb4334 HTTP/1.1" 200 263 0.011250 2015-10-07 16:28:49.182 2455 ERROR keystone.common.wsgi [-] 'Revoke' object has no attribute 'list_trusts_for_trustee' 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi Traceback (most recent call last): 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi File "/usr/lib/python2.7/site-packages/keystone/common/wsgi.py", line 223, in __call__ 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi result = method(context, **params) 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi File "/usr/lib/python2.7/site-packages/keystone/assignment/controllers.py", line 135, in delete_project 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi self.assignment_api.delete_project(tenant_id) 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi File "/usr/lib/python2.7/site-packages/keystone/notifications.py", line 112, in wrapper 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi result = f(*args, **kwargs) 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi File "/usr/lib/python2.7/site-packages/keystone/assignment/core.py", line 150, in delete_project 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi self._emit_invalidate_user_project_tokens_notification(payload) 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi File "/usr/lib/python2.7/site-packages/keystone/notifications.py", line 124, in wrapper 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi public=self.public) 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi File "/usr/lib/python2.7/site-packages/keystone/notifications.py", line 254, in _send_notification 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi notify_event_callbacks(service, resource_type, operation, payload) 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi File "/usr/lib/python2.7/site-packages/keystone/notifications.py", line 204, in notify_event_callbacks 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi cb(service, resource_type, operation, payload) 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi File "/usr/lib/python2.7/site-packages/keystone/token/provider.py", line 516, in _delete_user_project_tokens_callback 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi project_id=project_id) 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi File "/usr/lib/python2.7/site-packages/keystone/token/persistence/core.py", line 167, in delete_tokens_for_user 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi for trust in self.trust_api.list_trusts_for_trustee(user_id): 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi File "/usr/lib/python2.7/site-packages/keystone/common/manager.py", line 74, in __getattr__ 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi f = getattr(self.driver, name) 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi AttributeError: 'Revoke' object has no attribute 'list_trusts_for_trustee' 2015-10-07 16:28:49.182 2455 TRACE keystone.common.wsgi To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1503712/+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 1502961] Re: libvirt spawn with configdrive failed with UnboundLocalError
** 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/1502961 Title: libvirt spawn with configdrive failed with UnboundLocalError Status in OpenStack Compute (nova): Fix Released Bug description: If we create a libvirt sever that requires configdrive, it will fail with follow error: 2015-10-05 09:02:50.714 30941 ERROR nova.compute.manager [instance: ada89410-3ce1-44bf-b1e5-f3a0a9dfd846] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2437, in spawn 2015-10-05 09:02:50.714 30941 ERROR nova.compute.manager [instance: ada89410-3ce1-44bf-b1e5-f3a0a9dfd846] admin_pass=admin_password) 2015-10-05 09:02:50.714 30941 ERROR nova.compute.manager [instance: ada89410-3ce1-44bf-b1e5-f3a0a9dfd846] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2958, in _create_image 2015-10-05 09:02:50.714 30941 ERROR nova.compute.manager [instance: ada89410-3ce1-44bf-b1e5-f3a0a9dfd846] config_drive_image.import_file_cleanup(configdrive_path) 2015-10-05 09:02:50.714 30941 ERROR nova.compute.manager [instance: ada89410-3ce1-44bf-b1e5-f3a0a9dfd846] UnboundLocalError: local variable 'config_drive_image' referenced before assignment This problem is seen with liberty 20150920 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1502961/+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 1504136] [NEW] Floating IP addresses sorting does not work
Public bug reported: Steps: 1. Navigate to Horizon: Project -> Compute -> Access & Security -> Floating IPs 2. Allocate IP to Project - several times 3. Try to Sort IP addresses by clicking on tablesorter-header "IP Address". Expected to sort IPs ascending and descending. Actual: sorting does not work at all. This bug was already filed and fiexd: https://bugs.launchpad.net/horizon/+bug/1428172, but now for current Horizon master it is valid (again?). ** Affects: horizon Importance: Undecided Status: New ** Description changed: Steps: 1. Navigate to Horizon: Project -> Compute -> Access & Security -> Floating IPs 2. Allocate IP to Project - several times 3. Try to Sort IP addresses by clicking on tablesorter-header "IP Address". Expected to sort IPs ascending and descending. Actual: sorting does not work at all. This bug was already filed and fiexd: https://bugs.launchpad.net/horizon/+bug/1428172, but now for current - Horizon upstream it is valid (again?). + Horizon master it is valid (again?). -- 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/1504136 Title: Floating IP addresses sorting does not work Status in OpenStack Dashboard (Horizon): New Bug description: Steps: 1. Navigate to Horizon: Project -> Compute -> Access & Security -> Floating IPs 2. Allocate IP to Project - several times 3. Try to Sort IP addresses by clicking on tablesorter-header "IP Address". Expected to sort IPs ascending and descending. Actual: sorting does not work at all. This bug was already filed and fiexd: https://bugs.launchpad.net/horizon/+bug/1428172, but now for current Horizon master it is valid (again?). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1504136/+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 1504165] [NEW] SR-IOV: The Action Detach port/network from Qos-Policy is not working
Public bug reported: After Create Qos-Policy and Qos Rule to Port, I tried to detach the Policy. # neutron port-update --no-qos-policy. >From sriov-nic-agent.log neutron.plugins.ml2.drivers.mech_sriov.agent.eswitch_manager [req- b526991f-0632-4d9d-9b61-638414d7af1d - - - - -] VF with PCI slot :04:00.7 is already assigned; skipping reset maximum rate The BW on vf's didn't Changed. My Environment: - 2 Servers (All in one and Compute). - OS : CentOS Linux release 7.1.1503 (Core) - Kernel version : 3.10.0-123.el7.x86_64 - Openstack Version : Trunk ** Affects: neutron Importance: Medium Status: Confirmed ** Tags: qos sriov-pci-pt ** Project changed: networking-qos => neutron ** Tags added: qos -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1504165 Title: SR-IOV: The Action Detach port/network from Qos-Policy is not working Status in neutron: Confirmed Bug description: After Create Qos-Policy and Qos Rule to Port, I tried to detach the Policy. # neutron port-update --no-qos-policy. From sriov-nic-agent.log neutron.plugins.ml2.drivers.mech_sriov.agent.eswitch_manager [req- b526991f-0632-4d9d-9b61-638414d7af1d - - - - -] VF with PCI slot :04:00.7 is already assigned; skipping reset maximum rate The BW on vf's didn't Changed. My Environment: - 2 Servers (All in one and Compute). - OS : CentOS Linux release 7.1.1503 (Core) - Kernel version : 3.10.0-123.el7.x86_64 - Openstack Version : Trunk To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1504165/+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 1504190] [NEW] Horizon revokes admin role from user if cannot get user_list
Public bug reported: 1) Deploy Horizon with users storing in LDAP 2) Create a lot of users in LDAP so Keystone couldn't return user_list 3) Go to identity/projects and try to update quotas for project where you have admin role Sometimes you get message 'You cannot revoke your administrative privileges from the project you are currently logged into.' and sometimes you will lose your admin role. MOS 6.1 ** Affects: horizon Importance: Undecided Status: New ** Description changed: 1) Deploy Horizon with users storing in LDAP 2) Create a lot of users in LDAP so Keystone couldn't return user_list - 3) Go to identity/projects and try to update quotas for project where you admin + 3) Go to identity/projects and try to update quotas for project where you have admin role - - Sometimes you get message 'You cannot revoke your administrative privileges ' - 'from the project you are currently logged into. ' - 'Please switch to another project with ' - 'administrative privileges or remove the ' - 'administrative role manually via the CLI.' - and sometimes you will lose your admin role. + Sometimes you get message 'You cannot revoke your administrative privileges from the project you are currently logged into.' and sometimes you will lose your admin role. + MOS 6.1 -- 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/1504190 Title: Horizon revokes admin role from user if cannot get user_list Status in OpenStack Dashboard (Horizon): New Bug description: 1) Deploy Horizon with users storing in LDAP 2) Create a lot of users in LDAP so Keystone couldn't return user_list 3) Go to identity/projects and try to update quotas for project where you have admin role Sometimes you get message 'You cannot revoke your administrative privileges from the project you are currently logged into.' and sometimes you will lose your admin role. MOS 6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1504190/+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 1337603] Re: css incorrect path to icons glyphicons-halflings.png
Bootstrap was upgraded a long time back, and we don't use glyphicons so
this should no longer be an issue.
** Changed in: horizon
Status: Confirmed => 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/1337603
Title:
css incorrect path to icons glyphicons-halflings.png
Status in OpenStack Dashboard (Horizon):
Invalid
Bug description:
With the recent merge from LESS to SCSS, it seems that the a url path
to the glyphicons is broken when I use an icon directly ().
Not sure if this will be fixed with bootstrap upgrade?
https://github.com/openstack/horizon/blob/master/openstack_dashboard/static/bootstrap/scss/bootstrap/_sprites.scss#L23
background-image: asset-url("glyphicons-halflings.png", image); ==>
page not found error @
/static/dashboard/scss/glyphicons-halflings.png. when it should have been:
/static/bootstrap/img/glyphicons-halflings.png
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1337603/+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 1175130] Re: Not possible to set a verbose_name for BatchAction
** Changed in: horizon Status: Triaged => 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/1175130 Title: Not possible to set a verbose_name for BatchAction Status in OpenStack Dashboard (Horizon): Invalid Bug description: At the moment, even if one sets a verbose_name for a BatchAction it gets overwritten by the conjugate() logic: https://github.com/openstack/horizon/blob/9cdee05678feb0ad623439a0efe2a43e915cb2b2/horizon/tables/actions.py#L539 It looks like this may have been added as a special case to handle the suspend/pause toggle type of action. Perhaps the toggling logic could be handle differently, e.g. via a special type of action? To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1175130/+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 1504196] [NEW] aggregate instance extra specs filter incorrectly filter out qualified host
Public bug reported:
With the below extra_specs in a flavor:
extra_specs| {"cpu_arch": "x86_64",
"aggregate_instance_extra_specs:bm": "true"} |
The filter doesn't qualify a host that satisfies
"aggregate_instance_extra_specs:bm": "true". This is because "cpu_arch":
"x86_64" doesn't match any aggregates since "cpu_arch" is not defined in
aggregates' metadata. This is wrong since the filter should only look at
keys with initial scope being "aggregate_instance_extra_specs", and
should not look at the key "cpu_arch" at all
** Affects: nova
Importance: Undecided
Assignee: Baodong (Robert) Li (baoli)
Status: New
** Changed in: nova
Assignee: (unassigned) => Baodong (Robert) Li (baoli)
--
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/1504196
Title:
aggregate instance extra specs filter incorrectly filter out
qualified host
Status in OpenStack Compute (nova):
New
Bug description:
With the below extra_specs in a flavor:
extra_specs| {"cpu_arch": "x86_64",
"aggregate_instance_extra_specs:bm": "true"} |
The filter doesn't qualify a host that satisfies
"aggregate_instance_extra_specs:bm": "true". This is because
"cpu_arch": "x86_64" doesn't match any aggregates since "cpu_arch" is
not defined in aggregates' metadata. This is wrong since the filter
should only look at keys with initial scope being
"aggregate_instance_extra_specs", and should not look at the key
"cpu_arch" at all
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1504196/+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 1503708] Re: InstanceV2 backports to V1 lack a context
** 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/1503708 Title: InstanceV2 backports to V1 lack a context Status in OpenStack Compute (nova): Fix Released Bug description: When we convert a V2 instance to a V1 instance, we don't provide it a context, which could, under some circumstances, cause a failure to lazy-load things we need to construct the older instance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1503708/+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 1504235] [NEW] Can't run instance with non-ascii symbols in user_data
Public bug reported:
Gating of ec2api project has a test that runs instance with user data that
contains non-ascii symbols under python 2.7.
And now it fails because of fix bug https://bugs.launchpad.net/nova/+bug/1502583
Version: master branch
stack trace from nova compute [1]:
2015-10-08 16:50:00.267 ERROR nova.compute.manager
[req-eb417914-b76f-42b3-a825-7e86785d2bbe user-9eea8ece project-e7ccb1a9]
[instance: 529a79f0-6707-4882-af0f-63a5af1fa111] Instance failed to spawn
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] Traceback (most recent call last):
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] File
"/opt/stack/new/nova/nova/compute/manager.py", line 2172, in _build_resources
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] yield resources
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] File
"/opt/stack/new/nova/nova/compute/manager.py", line 2019, in
_build_and_run_instance
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] block_device_info=block_device_info)
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] File
"/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 2437, in spawn
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] admin_pass=admin_password)
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] File
"/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 2942, in _create_image
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] cdb.make_drive(configdrive_path)
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] File
"/opt/stack/new/nova/nova/virt/configdrive.py", line 163, in make_drive
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] self._write_md_files(tmpdir)
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] File
"/opt/stack/new/nova/nova/virt/configdrive.py", line 98, in _write_md_files
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] self._add_file(basedir, data[0],
data[1])
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] File
"/opt/stack/new/nova/nova/virt/configdrive.py", line 90, in _add_file
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] f.write(data.encode('utf-8'))
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] UnicodeDecodeError: 'ascii' codec can't
decode byte 0xd0 in position 36: ordinal not in range(128)
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111]
[1] http://logs.openstack.org/50/232550/1/check/gate-functional-neutron-
dsvm-ec2api/2eda628/logs/screen-n-cpu.txt.gz#_2015-10-08_16_50_00_267
** 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/1504235
Title:
Can't run instance with non-ascii symbols in user_data
Status in OpenStack Compute (nova):
New
Bug description:
Gating of ec2api project has a test that runs instance with user data that
contains non-ascii symbols under python 2.7.
And now it fails because of fix bug
https://bugs.launchpad.net/nova/+bug/1502583
Version: master branch
stack trace from nova compute [1]:
2015-10-08 16:50:00.267 ERROR nova.compute.manager
[req-eb417914-b76f-42b3-a825-7e86785d2bbe user-9eea8ece project-e7ccb1a9]
[instance: 529a79f0-6707-4882-af0f-63a5af1fa111] Instance failed to spawn
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] Traceback (most recent call last):
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] File
"/opt/stack/new/nova/nova/compute/manager.py", line 2172, in _build_resources
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] yield resources
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager [instance:
529a79f0-6707-4882-af0f-63a5af1fa111] File
"/opt/stack/new/nova/nova/compute/manager.py", line 2019, in
_build_and_run_instance
2015-10-08 16:50:00.267 32724 ERROR nova.compute.manager
[Yahoo-eng-team] [Bug 1504234] [NEW] Checkmarks in project picker in the wrong place
Public bug reported: The checkmark showing the current project has changed positions in some cases and looks strange. I've seen cases where it's still in the right place, but other places where it looks like this: http://imgur.com/1oTPf9M ** 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/1504234 Title: Checkmarks in project picker in the wrong place Status in OpenStack Dashboard (Horizon): New Bug description: The checkmark showing the current project has changed positions in some cases and looks strange. I've seen cases where it's still in the right place, but other places where it looks like this: http://imgur.com/1oTPf9M To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1504234/+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 1504278] [NEW] Many of the details pages do not follow the same layout/style guide
Public bug reported: While looking at many of the details pages, it can be seen that almost none of them follow the same exact layout/style conventions. There are slight differences in the pages that make them look different. This is unacceptable. All details pages should have the same exact layout scheme. Not having this consistency could be confusing/misleading to the user. The one page that looks like it should is the instance details page. This page should be used as a template/model page for all others follow. The details' pages that need work are: - image details - network details - port details - router details - subnet details - volume details - VPN service details - firewall details - firewall policy details There may be more pages that need work that I just did not find... Please see the image links in the comment below for examples of good vs bad. You will easily be able to tell that the pages are slightly different in a few ways. The images include the current instance details page to be used as a model, the current (bad) port details page that should be fixed, and a fixed version of the port details page to show the proposed changes in affect. Also, I included a bad port details page image with box annotations to help indicate where there are errors, things are missing, or improvements should be made. ** 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/1504278 Title: Many of the details pages do not follow the same layout/style guide Status in OpenStack Dashboard (Horizon): New Bug description: While looking at many of the details pages, it can be seen that almost none of them follow the same exact layout/style conventions. There are slight differences in the pages that make them look different. This is unacceptable. All details pages should have the same exact layout scheme. Not having this consistency could be confusing/misleading to the user. The one page that looks like it should is the instance details page. This page should be used as a template/model page for all others follow. The details' pages that need work are: - image details - network details - port details - router details - subnet details - volume details - VPN service details - firewall details - firewall policy details There may be more pages that need work that I just did not find... Please see the image links in the comment below for examples of good vs bad. You will easily be able to tell that the pages are slightly different in a few ways. The images include the current instance details page to be used as a model, the current (bad) port details page that should be fixed, and a fixed version of the port details page to show the proposed changes in affect. Also, I included a bad port details page image with box annotations to help indicate where there are errors, things are missing, or improvements should be made. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1504278/+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 1504312] [NEW] bad deprecation warning for "Registering resources to apply quota limits"
Public bug reported: The following deprecation warning appears to be logged in all cases, regardless of neutron or other configuration. 2015-09-18 10:59:40.472 20552 WARNING neutron.quota [-] Deprecated: Registering resources to apply quota limits to using the quota_items option is deprecated as of Liberty.Resource REST controllers should take care of registering resources with the quota engine. That should only be printed when things are configured/working in a way that we now want to deprecate... not always. Found with Liberty. ** 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/1504312 Title: bad deprecation warning for "Registering resources to apply quota limits" Status in neutron: New Bug description: The following deprecation warning appears to be logged in all cases, regardless of neutron or other configuration. 2015-09-18 10:59:40.472 20552 WARNING neutron.quota [-] Deprecated: Registering resources to apply quota limits to using the quota_items option is deprecated as of Liberty.Resource REST controllers should take care of registering resources with the quota engine. That should only be printed when things are configured/working in a way that we now want to deprecate... not always. Found with Liberty. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1504312/+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 1504358] [NEW] Trace on nova net-delete for neutron network
Public bug reported: Created a neutron network "net3". By mistake executed nova "net-delete net3". The case was not gracefully handled. stack@osctrlr:~/devstack$ nova net-delete net3 ERROR (ClientException): 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-0780c222-cee5-4e1e-886d-4f0e893d9ca6) stack@osctrlr:~/devstack$ Attaching n-api logs. ** Affects: nova Importance: Undecided Status: New ** Attachment added: "n-api log" https://bugs.launchpad.net/bugs/1504358/+attachment/4489269/+files/n-api_crash.log -- 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/1504358 Title: Trace on nova net-delete for neutron network Status in OpenStack Compute (nova): New Bug description: Created a neutron network "net3". By mistake executed nova "net-delete net3". The case was not gracefully handled. stack@osctrlr:~/devstack$ nova net-delete net3 ERROR (ClientException): 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-0780c222-cee5-4e1e-886d-4f0e893d9ca6) stack@osctrlr:~/devstack$ Attaching n-api logs. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1504358/+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 1504370] [NEW] track_quota_usage conf variable is not in neutron.conf
Public bug reported: by default, neutron configurable items should be put in configure files for deployers to configure. track_quota_usage is missing there. ** Affects: neutron Importance: Undecided Assignee: yong sheng gong (gongysh) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => yong sheng gong (gongysh) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1504370 Title: track_quota_usage conf variable is not in neutron.conf Status in neutron: In Progress Bug description: by default, neutron configurable items should be put in configure files for deployers to configure. track_quota_usage is missing there. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1504370/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong
** Also affects: magnum Importance: Undecided Status: New ** Changed in: magnum Assignee: (unassigned) => lei zhang (zhang-lei) -- 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/1259292 Title: Some tests use assertEqual(observed, expected) , the argument order is wrong Status in Barbican: In Progress Status in Ceilometer: Invalid Status in Cinder: Fix Released Status in congress: In Progress Status in Designate: In Progress Status in Glance: Fix Committed Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): In Progress Status in Keystone: Fix Committed Status in Magnum: New Status in Manila: In Progress Status in Mistral: In Progress Status in murano: Fix Committed Status in OpenStack Compute (nova): Won't Fix Status in python-ceilometerclient: Invalid Status in python-cinderclient: Fix Released Status in python-designateclient: In Progress Status in python-mistralclient: In Progress Status in Python client library for Zaqar: In Progress Status in Sahara: Fix Released Status in zaqar: In Progress Bug description: The test cases will produce a confusing error message if the tests ever fail, so this is worth fixing. To manage notifications about this bug go to: https://bugs.launchpad.net/barbican/+bug/1259292/+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 1410067] Re: Add network to new dhcp agent cause the dhcp port status to be BUILD
*** This bug is a duplicate of bug 1411163 ***
https://bugs.launchpad.net/bugs/1411163
Isn't this the fix?
https://review.openstack.org/#/c/197937/
** This bug has been marked a duplicate of bug 1411163
No fdb entries added when failover dhcp and l3 agent together
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1410067
Title:
Add network to new dhcp agent cause the dhcp port status to be BUILD
Status in neutron:
Confirmed
Bug description:
SYMPTOM:
1.neutron dhcp-agent-network-remove [dhcp agent of network Node1] [network]
2.neutron dhcp-agent-network-add [dhcp agent of network Node2] [network]
3.neutron port-show [dhcp-port]
Then the status of dhcp port change to BUILD, and this may cause some problem
of the dhcp server and the metadata server .
CAUSE:
First I find the binding:host_id of dhcp port doesn't change to the new
host_id after dhcp-agent-network-add.
Then I check the code, I find it the status of port change to BUILD in the
devices_details_list = self.plugin_rpc.get_devices_details_list in
ovs_neutron_agent.py.
And it should change the status of port to ACTIVE in update_device_up,but in
the update_device_up we can see:
if (host and not plugin.port_bound_to_host(rpc_context,
port_id, host)):
LOG.debug(_("Device %(device)s not bound to the"
" agent host %(host)s"),
{'device': device, 'host': host})
return
We can see this,it return directly because the port didn't bind to the new
host, so cause the problem.
FIX:
I think we should update the binding:host_id of dhcp port to the new host.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1410067/+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 1504397] [NEW] truncate table size column cause the exception
Public bug reported: To reproduce: 1.edit openstack_dashboard/dashboards/project/images/images/tables.py 2.add 'truncate=40' to image size column 3.open the image page give the error Error while rendering table rows. Traceback (most recent call last): File "/home/openstack/horizon/horizon/tables/base.py", line 1774, in get_rows row = self._meta.row_class(self, datum) File "/home/openstack/horizon/horizon/tables/base.py", line 529, in __init__ self.load_cells() File "/home/openstack/horizon/openstack_dashboard/dashboards/project/images/images/tables.py", line 268, in load_cells super(UpdateRow, self).load_cells(image) File "/home/openstack/horizon/horizon/tables/base.py", line 555, in load_cells cell = table._meta.cell_class(datum, column, self) File "/home/openstack/horizon/horizon/tables/base.py", line 657, in __init__ if len(data) > column.truncate: TypeError: object of type 'int' has no len() Internal Server Error: /project/images/ ** Affects: horizon Importance: Undecided Assignee: zhu.rong (zhu-rong) Status: New ** Changed in: horizon Assignee: (unassigned) => zhu.rong (zhu-rong) -- 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/1504397 Title: truncate table size column cause the exception Status in OpenStack Dashboard (Horizon): New Bug description: To reproduce: 1.edit openstack_dashboard/dashboards/project/images/images/tables.py 2.add 'truncate=40' to image size column 3.open the image page give the error Error while rendering table rows. Traceback (most recent call last): File "/home/openstack/horizon/horizon/tables/base.py", line 1774, in get_rows row = self._meta.row_class(self, datum) File "/home/openstack/horizon/horizon/tables/base.py", line 529, in __init__ self.load_cells() File "/home/openstack/horizon/openstack_dashboard/dashboards/project/images/images/tables.py", line 268, in load_cells super(UpdateRow, self).load_cells(image) File "/home/openstack/horizon/horizon/tables/base.py", line 555, in load_cells cell = table._meta.cell_class(datum, column, self) File "/home/openstack/horizon/horizon/tables/base.py", line 657, in __init__ if len(data) > column.truncate: TypeError: object of type 'int' has no len() Internal Server Error: /project/images/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1504397/+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 1475091] Re: Missing name field for trusts
Morgan, Gilles and I spoke about this on IRC. I think we agreed that making the columns in the trust database have a unique constraint is the way to go. So if two requests came to create trusts with the same trustor/trustee/roles/expiration/scope/impersonation, then the second would bring up an exception saying there's a conflict. ** Changed in: keystone Status: Won't Fix => Triaged ** Changed in: keystone Importance: Wishlist => Medium ** Tags added: trusts -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1475091 Title: Missing name field for trusts Status in Keystone: Triaged Bug description: A name field in Keystone DB is needed for helping identifying trusts. Effectively , there could be multiple trusts for a same project/trustor/trustee including the same expiry date and same impersonate flag. And the same combination could have multiple trusts assigned with different roles or not. Having a name would help for implementing trust usage. A use case scenario is currently with Puppet Keystone module while creating the trust provider: When creating a resource, Puppet uses a name as a title for the resource, that name is unique in order to provide idem-potency. The trust ID (Keystone DB) doesn't exist until its creation and therefore cannot be used as a title for a Puppet resource. Without a name, puppet provider has to make up a name from the different fields, which doesn't guarantee uniqueness anyway. Worse when fetching resources, the provider would have to fetch all the fields to identify the resource and take the first one if many available. So far, most other Keystone DBMS objects (tables) have a name, which Puppet has been able to use to identify resources. The latter is why it made more sense to create this request as a bug instead of a blueprint, basically saying a name has been missing upfront rather than being a request for enhancement. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1475091/+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 1504264] [NEW] InvalidBDMEphemeralSize not handled during boot instance
Public bug reported: InvalidBDMEphemeralSize exception might be raised during boot process while we didn't catch this exception at API layer so 500 will be returned ** Affects: nova Importance: Low Assignee: jichenjc (jichenjc) Status: New ** Changed in: nova Assignee: (unassigned) => jichenjc (jichenjc) ** Changed in: nova Importance: Undecided => Low -- 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/1504264 Title: InvalidBDMEphemeralSize not handled during boot instance Status in OpenStack Compute (nova): New Bug description: InvalidBDMEphemeralSize exception might be raised during boot process while we didn't catch this exception at API layer so 500 will be returned To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1504264/+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 1504260] [NEW] locations not ‘deleted’ on delete-all image.locations
Public bug reported:
Problem:
When we try to delete all locations for an ‘active’ image, the locations are
not actually ‘deleted’ despite the image status being updated as ‘queued’.
Note: This behavior could be noticed only when we delete-all locations.
Scenario:
- Have an active image with its associated locations.
- Try updating the image to delete all locations with replace locations call
and ensure the response status code is 200 and with image status as ‘queued’.
eg., json: {‘op': 'replace', 'path': '/locations', 'value': []}; url:
/v2/images/%(image_id); http method: patch
- Make a call to get the image by ID.
Note: The obtained image details will still continue to have the list of
locations.
Reason:
- The update call to delete-all locations is ignored due to incorrect python
‘falsy’ conditional check (at glance.sqlalchemy.api layer) that
allows/disallows update of image locations.
Fix:
- Make the conditional check explicit so that the delete-all locations call
for the given image is allowed to update the image locations as 'deleted'.
** Affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1504260
Title:
locations not ‘deleted’ on delete-all image.locations
Status in Glance:
New
Bug description:
Problem:
When we try to delete all locations for an ‘active’ image, the locations are
not actually ‘deleted’ despite the image status being updated as ‘queued’.
Note: This behavior could be noticed only when we delete-all locations.
Scenario:
- Have an active image with its associated locations.
- Try updating the image to delete all locations with replace locations call
and ensure the response status code is 200 and with image status as ‘queued’.
eg., json: {‘op': 'replace', 'path': '/locations', 'value': []}; url:
/v2/images/%(image_id); http method: patch
- Make a call to get the image by ID.
Note: The obtained image details will still continue to have the list of
locations.
Reason:
- The update call to delete-all locations is ignored due to incorrect python
‘falsy’ conditional check (at glance.sqlalchemy.api layer) that
allows/disallows update of image locations.
Fix:
- Make the conditional check explicit so that the delete-all locations call
for the given image is allowed to update the image locations as 'deleted'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1504260/+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 1504265] [NEW] OpenStack SDN corrupts a few networking packets under load
Public bug reported: It appears that some combination of OpenStack SDN under load can silently corrupt exactly 50 bytes of TCP payload data. Only observed with VMs that run on the OpenStack control node which is apparently out of line with OpenStack best practices for production. Environment was RDO OpenStack Kilo, CentOS 7, Neutron/Openvswitch. Openvswitch Neutron plugin version is 2015.1.0-1.el7, linux is SLES11SP3 (kernel 3.0.76) 64 bit on VMware. Steps To Reproduce: Generate high network traffic. >From the sender: sender:~ $ dd if=/dev/zero count=100 bs=1000 | netcat 172.16.12.100 139 100+0 records in 100+0 records out 10 bytes (1.0 GB) copied, 12.5841 s, 79.5 MB/s ^C >From the receiver: Out of laziness using SMB port so shutdown Samba on the receiver before repro'ing. If OpenStack does not corrupt the networking stream: receiver:~ $ netcat -l -p 139 > out.bin; hexdump -C out.bin 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 1dcd6500 If OpenStack *does* corrupt the packets over the network, the corruption will be shown in the hexdump. Out of 10 tries, a few attempts yielded corruption so it is readily reproducable, but not that often. Two examples: receiver:~ $ netcat -l -p 139 > out.bin; hexdump -C out.bin 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0ac9db60 00 00 00 00 00 00 61 35 61 34 39 30 34 34 62 66 |..a5a49044bf| 0ac9db70 33 30 37 33 32 36 36 35 31 31 37 36 61 38 31 66 |307326651176a81f| 0ac9db80 32 35 32 61 33 35 35 39 31 34 30 31 39 63 33 33 |252a355914019c33| 0ac9db90 32 35 31 38 38 64 62 61 00 00 00 00 00 00 00 00 |25188dba| 0ac9dba0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 3b9aca00 receiver:~ $ netcat -l -p 139 > out.bin; hexdump -C out.bin 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 078cf070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70 ce |..p.| 078cf080 d0 31 40 0f 77 34 f7 23 02 75 10 77 d5 5b 2f 11 |.1@.w4.#.u.w.[/.| 078cf090 b8 61 c3 4f 15 30 7f 10 c0 39 96 b5 bb f1 bc 5c |.a.O.0...9.\| 078cf0a0 ea d7 2a de 69 80 9c d3 4a b3 24 60 67 03 8e a5 |..*.i...J.$`g...| 078cf0b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 07910130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 36 39 |..69| 07910140 34 65 37 35 37 65 39 39 63 35 61 63 64 65 36 64 |4e757e99c5acde6d| 07910150 63 34 33 35 34 33 37 66 62 39 39 35 38 63 38 61 |c435437fb9958c8a| 07910160 39 36 66 35 36 30 31 38 63 62 35 34 61 33 65 34 |96f56018cb54a3e4| 07910170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 32a57a20 00 00 00 00 00 00 32 31 33 31 39 61 36 64 33 33 |..21319a6d33| 32a57a30 38 66 34 63 37 35 64 39 63 65 34 39 33 63 32 61 |8f4c75d9ce493c2a| 32a57a40 62 33 35 61 61 33 31 64 61 35 31 31 35 61 30 34 |b35aa31da5115a04| 32a57a50 35 66 62 39 31 34 39 34 00 00 00 00 00 00 00 00 |5fb91494| 32a57a60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 3b9aca00 ** 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/1504265 Title: OpenStack SDN corrupts a few networking packets under load Status in neutron: New Bug description: It appears that some combination of OpenStack SDN under load can silently corrupt exactly 50 bytes of TCP payload data. Only observed with VMs that run on the OpenStack control node which is apparently out of line with OpenStack best practices for production. Environment was RDO OpenStack Kilo, CentOS 7, Neutron/Openvswitch. Openvswitch Neutron plugin version is 2015.1.0-1.el7, linux is SLES11SP3 (kernel 3.0.76) 64 bit on VMware. Steps To Reproduce: Generate high network traffic. From the sender: sender:~ $ dd if=/dev/zero count=100 bs=1000 | netcat 172.16.12.100 139 100+0 records in 100+0 records out 10 bytes (1.0 GB) copied, 12.5841 s, 79.5 MB/s ^C From the receiver: Out of laziness using SMB port so shutdown Samba on the receiver before repro'ing. If OpenStack does not corrupt the networking stream: receiver:~ $ netcat -l -p 139 > out.bin; hexdump -C out.bin 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 1dcd6500 If OpenStack *does* corrupt the packets over the network, the corruption will be shown in the hexdump. Out of 10 tries, a few attempts yielded corruption so it is readily reproducable, but not that often. Two examples: receiver:~ $ netcat -l -p 139 > out.bin; hexdump -C out.bin 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0ac9db60 00 00 00 00 00 00 61 35 61 34 39 30 34 34 62 66 |..a5a49044bf| 0ac9db70 33 30 37 33 32 36 36 35 31 31 37 36 61 38 31 66 |307326651176a81f| 0ac9db80 32 35 32 61
[Yahoo-eng-team] [Bug 1503890] Re: test_policy assumes oslo.policy internal implementationd details
** 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 neutron. https://bugs.launchpad.net/bugs/1503890 Title: test_policy assumes oslo.policy internal implementationd details Status in neutron: In Progress Status in oslo.policy: New Bug description: Neutron assumes that oslo.policy uses urlrequest.urlopen() http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/unit/test_policy.py#n108 http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/unit/test_policy.py#n121 Unfortunately this assumption is bad as oslo.policy is now using requests.post() https://review.openstack.org/#/c/226122/ So these 2 tests will fail when we release next oslo.policy version for Mitaka To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1503890/+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
