[Yahoo-eng-team] [Bug 1416475] [NEW] Image Details page has a different format to other Details pages
Public bug reported: The Image Details page still have overview tab which is not required as there are no other tabs. So we have to remove the redundant tab. ** Affects: horizon Importance: Undecided Assignee: Nikunj Aggarwal (nikunj2512) Status: New ** Changed in: horizon Assignee: (unassigned) = Nikunj Aggarwal (nikunj2512) -- 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/1416475 Title: Image Details page has a different format to other Details pages Status in OpenStack Dashboard (Horizon): New Bug description: The Image Details page still have overview tab which is not required as there are no other tabs. So we have to remove the redundant tab. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1416475/+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 1276207] Re: vmware driver does not validate server certificates
** Changed in: nova Status: Confirmed = 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/1276207 Title: vmware driver does not validate server certificates Status in Cinder: In Progress Status in OpenStack Compute (Nova): Fix Released Status in Oslo VMware library for OpenStack projects: Fix Committed Bug description: The VMware driver establishes connections to vCenter over HTTPS, yet the vCenter server certificate is not verified as part of the connection process. I know this because my vCenter server is using a self-signed certificate which always fails certification verification. As a result, someone could use a man-in-the-middle attack to spoof the vcenter host to nova. The vmware driver has a dependency on Suds, which I believe also does not validate certificates because hartsock and I noticed it uses urllib. For reference, here is a link on secure connections in OpenStack: https://wiki.openstack.org/wiki/SecureClientConnections Assuming Suds is fixed to provide an option for certificate verification, next step would be to modify the vmware driver to provide an option to override invalid certificates (such as self- signed). In other parts of OpenStack, there are options to bypass the certificate check with a insecure option set, or you could put the server's certificate in the CA store. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1276207/+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 1416459] [NEW] Disabling identity providers doesn't work
Public bug reported: During federated authentication we don't check if the identity provider is disabled or not. ** Affects: keystone Importance: Undecided Assignee: Marek Denis (marek-denis) Status: New ** Changed in: keystone Assignee: (unassigned) = Marek Denis (marek-denis) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1416459 Title: Disabling identity providers doesn't work Status in OpenStack Identity (Keystone): New Bug description: During federated authentication we don't check if the identity provider is disabled or not. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1416459/+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 1402917] Re: Error: You are not allowed to delete volume
Un-closing. As Trung noted, this change is dependent upon a change in cinder. This appears to be a change for Kilo rather than stable/juno (indicated in the description), correct? ** Changed in: horizon Status: Invalid = 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/1402917 Title: Error: You are not allowed to delete volume Status in OpenStack Dashboard (Horizon): New Bug description: Version: stable/juno Proposal: It should be allowed to delete the volume which is attached to an already-deleted VM. This scenario can occur when the associated VM is deleted but the auto-triggered volume-detaching process is failed accidentally. If so, it results in the case where the volume is attached to an already- deleted VM To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1402917/+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 1416435] [NEW] The publisher_id field is missing the service name sometimes
Public bug reported: In the notifications emitted by the Nova services, the 'publisher_id' fields is sometimes equal to 'None.node name' while it is 'service name.node name' (eg, 'conductor.node-1') otherwise. From what I can tell, the problem is located in nova/objects/instance.py (see [1] and [2]). This isn't a huge issue (eg instances can be created, deleted and so on) but it makes it problematic when trying to rely on this field for external processing/computation. [1] http://git.openstack.org/cgit/openstack/nova/tree/nova/objects/instance.py?id=d59dd36015dcf94cfa8eda64f480c43b18d63852#n834 [2] http://git.openstack.org/cgit/openstack/nova/tree/nova/objects/instance.py?id=d59dd36015dcf94cfa8eda64f480c43b18d63852#n1013 ** 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/1416435 Title: The publisher_id field is missing the service name sometimes Status in OpenStack Compute (Nova): New Bug description: In the notifications emitted by the Nova services, the 'publisher_id' fields is sometimes equal to 'None.node name' while it is 'service name.node name' (eg, 'conductor.node-1') otherwise. From what I can tell, the problem is located in nova/objects/instance.py (see [1] and [2]). This isn't a huge issue (eg instances can be created, deleted and so on) but it makes it problematic when trying to rely on this field for external processing/computation. [1] http://git.openstack.org/cgit/openstack/nova/tree/nova/objects/instance.py?id=d59dd36015dcf94cfa8eda64f480c43b18d63852#n834 [2] http://git.openstack.org/cgit/openstack/nova/tree/nova/objects/instance.py?id=d59dd36015dcf94cfa8eda64f480c43b18d63852#n1013 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1416435/+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 1416462] Re: Network is not showing in Create Instance Form
** 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/1416462 Title: Network is not showing in Create Instance Form Status in OpenStack Dashboard (Horizon): Invalid Bug description: In Horizon, Projects-Compute-instances, click on the create instances and go to the network tab. In that tab no network options are coming. Please see the attached screenshot below. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1416462/+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 1416462] [NEW] Network is not showing in Create Instance Form
Public bug reported: In Horizon, Projects-Compute-instances, click on the create instances and go to the network tab. In that tab no network options are coming. Please see the attached screenshot below. ** Affects: horizon Importance: Undecided Assignee: Nikunj Aggarwal (nikunj2512) Status: New ** Tags: horizon-core ** Changed in: horizon Assignee: (unassigned) = Nikunj Aggarwal (nikunj2512) -- 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/1416462 Title: Network is not showing in Create Instance Form Status in OpenStack Dashboard (Horizon): New Bug description: In Horizon, Projects-Compute-instances, click on the create instances and go to the network tab. In that tab no network options are coming. Please see the attached screenshot below. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1416462/+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 1416554] [NEW] l3 prevent port deletion doesn't handle missing ports
Public bug reported: The l3 code to check to see if a port can be deleted does not handle the case where the port id it is passed does not refer to a port that still exists. This throws an exception and makes the API behavior inconsistent when two concurrent requests come in to delete the same port.[1] This is inconsistent because if the port is concurrently deleted after the l3 check is done but before the delete attempt is made, no exception will be raised.[2] 1. This happens frequently when horizon deletes the subnet and immediately deletes the network afterwards. The dhcp agent will delete it's port on the subnet cleanup and may rip the port right before the delete_network call does it's auto port cleanup. The auto port cleanup will then hit a portnotfound exception which goes uncaught. 2. https://github.com/openstack/neutron/blob/6a797f354eb4ba936b80603f7cc01a2fe80446fd/neutron/plugins/ml2/plugin.py#L1113 ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1416554 Title: l3 prevent port deletion doesn't handle missing ports Status in OpenStack Neutron (virtual network service): In Progress Bug description: The l3 code to check to see if a port can be deleted does not handle the case where the port id it is passed does not refer to a port that still exists. This throws an exception and makes the API behavior inconsistent when two concurrent requests come in to delete the same port.[1] This is inconsistent because if the port is concurrently deleted after the l3 check is done but before the delete attempt is made, no exception will be raised.[2] 1. This happens frequently when horizon deletes the subnet and immediately deletes the network afterwards. The dhcp agent will delete it's port on the subnet cleanup and may rip the port right before the delete_network call does it's auto port cleanup. The auto port cleanup will then hit a portnotfound exception which goes uncaught. 2. https://github.com/openstack/neutron/blob/6a797f354eb4ba936b80603f7cc01a2fe80446fd/neutron/plugins/ml2/plugin.py#L1113 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1416554/+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 1416555] [NEW] Selenium integration tests need method for wait till element visible, wait till till element disappears and wait until text present in the element
Public bug reported: Selenium integration tests need method for wait till element visible, wait till till element disappears and wait until text present in the element As elements are dynamically identified based on page format, locator is no more used explicitly. Need methods for web driver to explicitly wait: a. for element to be present b. for element to disappear c. for text to be present in element ** Affects: horizon Importance: Undecided Assignee: Amogh (amogh-r-mavinagidad) Status: New ** Changed in: horizon Assignee: (unassigned) = Amogh (amogh-r-mavinagidad) -- 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/1416555 Title: Selenium integration tests need method for wait till element visible, wait till till element disappears and wait until text present in the element Status in OpenStack Dashboard (Horizon): New Bug description: Selenium integration tests need method for wait till element visible, wait till till element disappears and wait until text present in the element As elements are dynamically identified based on page format, locator is no more used explicitly. Need methods for web driver to explicitly wait: a. for element to be present b. for element to disappear c. for text to be present in element To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1416555/+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 1416516] [NEW] use of oslo config in code uses two different versions
Public bug reported: parts of the code do this: from oslo_config import cfg other parts do this: from oslo.config import cfg There should be one version we use and the usage should be the same / very similar. ** Affects: horizon Importance: Undecided Assignee: Nikunj Aggarwal (nikunj2512) 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/1416516 Title: use of oslo config in code uses two different versions Status in OpenStack Dashboard (Horizon): New Bug description: parts of the code do this: from oslo_config import cfg other parts do this: from oslo.config import cfg There should be one version we use and the usage should be the same / very similar. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1416516/+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 1416522] [NEW] Fix neutron-fwaas unit test failure due to router_info.RouterInfo().
Public bug reported: Due to recent updates to neutron/agents/l3/router_info.py, neutron-fwaas unit tests are failing with the following error. ft1.59: neutron_fwaas.tests.unit.services.firewall.agents.l3reference.test_firewall_l3_agent.TestFwaasL3AgentRpcCallback.test_get_router_info_list_for_tenant_for_namespaces_disabled_StringException: Traceback (most recent call last): _StringException: Empty attachments: pythonlogging:'' pythonlogging:'neutron.api.extensions' stderr stdout Traceback (most recent call last): File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 371, in test_get_router_info_list_for_tenant_for_namespaces_disabled self._get_router_info_list_helper(use_namespaces=False) File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 355, in _get_router_info_list_helper ri = self._prepare_router_data() File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 351, in _prepare_router_data router=router, ns_name=ns) TypeError: __init__() got multiple values for keyword argument 'router' Traceback (most recent call last): _StringException: Empty attachments: pythonlogging:'' pythonlogging:'neutron.api.extensions' stderr stdout Traceback (most recent call last): File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 371, in test_get_router_info_list_for_tenant_for_namespaces_disabled self._get_router_info_list_helper(use_namespaces=False) File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 355, in _get_router_info_list_helper ri = self._prepare_router_data() File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 351, in _prepare_router_data router=router, ns_name=ns) TypeError: __init__() got multiple values for keyword argument 'router' ** Affects: neutron Importance: Undecided Assignee: Trinath Somanchi (trinath-somanchi) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1416522 Title: Fix neutron-fwaas unit test failure due to router_info.RouterInfo(). Status in OpenStack Neutron (virtual network service): In Progress Bug description: Due to recent updates to neutron/agents/l3/router_info.py, neutron- fwaas unit tests are failing with the following error. ft1.59: neutron_fwaas.tests.unit.services.firewall.agents.l3reference.test_firewall_l3_agent.TestFwaasL3AgentRpcCallback.test_get_router_info_list_for_tenant_for_namespaces_disabled_StringException: Traceback (most recent call last): _StringException: Empty attachments: pythonlogging:'' pythonlogging:'neutron.api.extensions' stderr stdout Traceback (most recent call last): File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 371, in test_get_router_info_list_for_tenant_for_namespaces_disabled self._get_router_info_list_helper(use_namespaces=False) File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 355, in _get_router_info_list_helper ri = self._prepare_router_data() File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 351, in _prepare_router_data router=router, ns_name=ns) TypeError: __init__() got multiple values for keyword argument 'router' Traceback (most recent call last): _StringException: Empty attachments: pythonlogging:'' pythonlogging:'neutron.api.extensions' stderr stdout Traceback (most recent call last): File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 371, in test_get_router_info_list_for_tenant_for_namespaces_disabled self._get_router_info_list_helper(use_namespaces=False) File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 355, in _get_router_info_list_helper ri = self._prepare_router_data() File neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py, line 351, in _prepare_router_data router=router, ns_name=ns) TypeError: __init__() got multiple values for keyword argument 'router' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1416522/+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 1416583] [NEW] Policy check is missing outer parens
Public bug reported: The policy check call seems to be missing another set of parens and a comma resulting in incorrect parsing of the action in the policy.py https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/keystone.py#L147 user = request.user if admin: if not policy.check((identity, admin_required), request): raise exceptions.NotAuthorized endpoint_type = 'adminURL' ** Affects: horizon Importance: Undecided Assignee: Dan Nguyen (daniel-a-nguyen) Status: In Progress ** Changed in: horizon Assignee: (unassigned) = Dan Nguyen (daniel-a-nguyen) -- 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/1416583 Title: Policy check is missing outer parens Status in OpenStack Dashboard (Horizon): In Progress Bug description: The policy check call seems to be missing another set of parens and a comma resulting in incorrect parsing of the action in the policy.py https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/keystone.py#L147 user = request.user if admin: if not policy.check((identity, admin_required), request): raise exceptions.NotAuthorized endpoint_type = 'adminURL' To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1416583/+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 1416593] [NEW] vmware unit tests are still skipped in openstack/neutron
Public bug reported: Despite having fixed the problem that caused the skip during the adv services spin off, the vmware unit tests are still skipped because the __init__.py file is missing (they're just not a test package for testr) This has recently caused a regression which has been correctly caught in the repository where the decomposed plugin is being prepped up. Until the decomposition is complete however, it might be worth ensuring unit tests are executed as part of the py27 job on openstack/neutron ** Affects: neutron Importance: High Assignee: Salvatore Orlando (salvatore-orlando) 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/1416593 Title: vmware unit tests are still skipped in openstack/neutron Status in OpenStack Neutron (virtual network service): New Bug description: Despite having fixed the problem that caused the skip during the adv services spin off, the vmware unit tests are still skipped because the __init__.py file is missing (they're just not a test package for testr) This has recently caused a regression which has been correctly caught in the repository where the decomposed plugin is being prepped up. Until the decomposition is complete however, it might be worth ensuring unit tests are executed as part of the py27 job on openstack/neutron To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1416593/+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 1416596] [NEW] vmware unit tests broken
Public bug reported: commit 79c97120de9cff4d0992b5d41ff4bbf05e890f89 introduced a constraint which causes a vmware unit test to fail. This unit test indeed directly exercises the plugin - creating a context with get_admin_context. For such context, tenant_id is None, and the DB constraint on the default security group table fails. ** Affects: neutron Importance: Undecided Assignee: Salvatore Orlando (salvatore-orlando) Status: New ** Affects: vmware-nsx Importance: Undecided Status: New ** Also affects: vmware-nsx 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/1416596 Title: vmware unit tests broken Status in OpenStack Neutron (virtual network service): New Status in VMware NSX: New Bug description: commit 79c97120de9cff4d0992b5d41ff4bbf05e890f89 introduced a constraint which causes a vmware unit test to fail. This unit test indeed directly exercises the plugin - creating a context with get_admin_context. For such context, tenant_id is None, and the DB constraint on the default security group table fails. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1416596/+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 1416615] [NEW] add schema for some extension entities
Public bug reported: Entity like 'policy association' and 'project endpoint group' also need validation on the parameters for creating and updating API. ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1416615 Title: add schema for some extension entities Status in OpenStack Identity (Keystone): New Bug description: Entity like 'policy association' and 'project endpoint group' also need validation on the parameters for creating and updating API. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1416615/+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 1416612] [NEW] response of project_endpoint_group doesn't contain full url
Public bug reported:
Currently, the response of get_endpoint_group_in_project API doesn't
contain full url, it misses http://ip:port/v3.
An example of wrong response:
{project_endpoint_group: {endpoint_group_id:
1d3f23bbbf4148c9af6acc38a754b0c8, project_id:
9ca8a69c27274dc8bc0a979a9f8613a9, links: {self:
/OS-EP-FILTER/endpoint_groups/1d3f23bbbf4148c9af6acc38a754b0c8/projects/9ca8a69c27274dc8bc0a979a9f8613a9}}}
** Affects: keystone
Importance: Undecided
Assignee: wanghong (w-wanghong)
Status: New
** Changed in: keystone
Assignee: (unassigned) = wanghong (w-wanghong)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1416612
Title:
response of project_endpoint_group doesn't contain full url
Status in OpenStack Identity (Keystone):
New
Bug description:
Currently, the response of get_endpoint_group_in_project API doesn't
contain full url, it misses http://ip:port/v3.
An example of wrong response:
{project_endpoint_group: {endpoint_group_id:
1d3f23bbbf4148c9af6acc38a754b0c8, project_id:
9ca8a69c27274dc8bc0a979a9f8613a9, links: {self:
/OS-EP-FILTER/endpoint_groups/1d3f23bbbf4148c9af6acc38a754b0c8/projects/9ca8a69c27274dc8bc0a979a9f8613a9}}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1416612/+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 1397789] Re: No Error notifications are send in case the network creation fails.
[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/1397789 Title: No Error notifications are send in case the network creation fails. Status in OpenStack Neutron (virtual network service): Expired Bug description: In case the network creation fails(due to bad gateway details) through horizon, the notifications we receive are the following. network.create.start network.create.end subnet.create.start network.delete.start network.delete.end This gives the impression that network has created and then deleted instantaneously. There is no notifications.error messages generated in case the operations fails. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1397789/+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 1253896] Re: Attempts to verify guests are running via SSH fails. SSH connection to guest does not work.
** No longer affects: tempest/havana
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1253896
Title:
Attempts to verify guests are running via SSH fails. SSH connection to
guest does not work.
Status in OpenStack Neutron (virtual network service):
Fix Released
Status in neutron havana series:
Won't Fix
Status in OpenStack Compute (Nova):
Triaged
Status in Tempest:
Confirmed
Bug description:
An example of this can be found at
http://logs.openstack.org/74/57774/2/gate/gate-tempest-devstack-vm-
full/e592961/console.html. This test failing seems to cause the
tearDownClass failure and the process exit code failure.
Judging by the logs below, the VM is coming up, and the test is
connecting to the SSH server (dropbear) running in the VM, but the
authentication is failing. It appears that authentication is attempted
several times before paramiko gives up causing the test to fail. I
think this indicates there isn't a network or compute problem, instead
is possible the client doesn't have the correct key or the authorized
keys aren't configured properly on the server side. But these are just
guesses, I haven't been able to get any concrete data that would
support these theories.
2013-11-22 05:36:33.980 | 2013-11-22 05:32:17,029 Adding SecurityGroupRule
from_port=-1, group={}, id=14, ip_protocol=icmp, ip_range={u'cidr':
u'0.0.0.0/0'}, parent_group_id=105, to_port=-1 to shared resources of
TestMinimumBasicScenario
2013-11-22 05:36:33.980 | 2013-11-22 05:32:34,226 starting thread (client
mode): 0x52e7e50L
2013-11-22 05:36:33.980 | 2013-11-22 05:32:34,232 Connected (version 2.0,
client dropbear_2012.55)
2013-11-22 05:36:33.981 | 2013-11-22 05:32:34,237 kex
algos:['diffie-hellman-group1-sha1', 'diffie-hellman-group14-sha1'] server
key:['ssh-rsa', 'ssh-dss'] client encrypt:['aes128-ctr', '3des-ctr',
'aes256-ctr', 'aes128-cbc', '3des-cbc', 'aes256-cbc', 'twofish256-cbc',
'twofish-cbc', 'twofish128-cbc'] server encrypt:['aes128-ctr', '3des-ctr',
'aes256-ctr', 'aes128-cbc', '3des-cbc', 'aes256-cbc', 'twofish256-cbc',
'twofish-cbc', 'twofish128-cbc'] client mac:['hmac-sha1-96', 'hmac-sha1',
'hmac-md5'] server mac:['hmac-sha1-96', 'hmac-sha1', 'hmac-md5'] client
compress:['none'] server compress:['none'] client lang:[''] server lang:['']
kex follows?False
2013-11-22 05:36:33.981 | 2013-11-22 05:32:34,238 Ciphers agreed:
local=aes128-ctr, remote=aes128-ctr
2013-11-22 05:36:33.981 | 2013-11-22 05:32:34,238 using kex
diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local aes128-ctr,
remote aes128-ctr; mac: local hmac-sha1, remote hmac-sha1; compression: local
none, remote none
2013-11-22 05:36:33.981 | 2013-11-22 05:32:34,433 Switch to new keys ...
2013-11-22 05:36:33.982 | 2013-11-22 05:32:34,434 Adding ssh-rsa host key for
172.24.4.227: 189c16acb93fe44ae975e1c653f1856c
2013-11-22 05:36:33.982 | 2013-11-22 05:32:34,434 Trying SSH key
9a9afe52a9485c15495a59b94ebca6b6
2013-11-22 05:36:33.982 | 2013-11-22 05:32:34,437 userauth is OK
2013-11-22 05:36:33.982 | 2013-11-22 05:32:35,104 Authentication (publickey)
failed.
2013-11-22 05:36:33.982 | 2013-11-22 05:32:36,693 starting thread (client
mode): 0x52f9190L
2013-11-22 05:36:33.982 | 2013-11-22 05:32:36,697 Connected (version 2.0,
client dropbear_2012.55)
2013-11-22 05:36:33.983 | 2013-11-22 05:32:36,699 kex
algos:['diffie-hellman-group1-sha1', 'diffie-hellman-group14-sha1'] server
key:['ssh-rsa', 'ssh-dss'] client encrypt:['aes128-ctr', '3des-ctr',
'aes256-ctr', 'aes128-cbc', '3des-cbc', 'aes256-cbc', 'twofish256-cbc',
'twofish-cbc', 'twofish128-cbc'] server encrypt:['aes128-ctr', '3des-ctr',
'aes256-ctr', 'aes128-cbc', '3des-cbc', 'aes256-cbc', 'twofish256-cbc',
'twofish-cbc', 'twofish128-cbc'] client mac:['hmac-sha1-96', 'hmac-sha1',
'hmac-md5'] server mac:['hmac-sha1-96', 'hmac-sha1', 'hmac-md5'] client
compress:['none'] server compress:['none'] client lang:[''] server lang:['']
kex follows?False
2013-11-22 05:36:33.983 | 2013-11-22 05:32:36,699 Ciphers agreed:
local=aes128-ctr, remote=aes128-ctr
2013-11-22 05:36:33.983 | 2013-11-22 05:32:36,699 using kex
diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local aes128-ctr,
remote aes128-ctr; mac: local hmac-sha1, remote hmac-sha1; compression: local
none, remote none
2013-11-22 05:36:33.983 | 2013-11-22 05:32:36,903 Switch to new keys ...
2013-11-22 05:36:33.983 | 2013-11-22 05:32:36,904 Trying SSH key
9a9afe52a9485c15495a59b94ebca6b6
2013-11-22 05:36:33.984 | 2013-11-22 05:32:36,906 userauth is OK
2013-11-22 05:36:33.984 | 2013-11-22 05:32:37,438 Authentication (publickey)
failed.
2013-11-22 05:36:33.984 | 2013-11-22 05:32:39,035 starting thread (client
mode): 0x24c62d0L
2013-11-22 05:36:33.984 | 2013-11-22 05:32:39,043 Connected (version 2.0,
client dropbear_2012.55)
[Yahoo-eng-team] [Bug 1415935] Re: encode_headers which has NoneType value would raise exception
What version of glanceclient are you using?
** Project changed: glance = python-glanceclient
** Changed in: python-glanceclient
Status: New = Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1415935
Title:
encode_headers which has NoneType value would raise exception
Status in Python client library for Glance:
Incomplete
Bug description:
refer to https://review.openstack.org/#/c/129289/
if you're using Nova but don't have Nova configured with
auth_strategy='keystone' (see nova.image.glance._create_glance_client for
details),
and when you resize(or other operation need call glance) an VM, it may call
glanceclient, and code may go to the logic like:
/usr/lib/python2.7/site-packages/glanceclient/v1/client.py(36)__init__()
- self.http_client = http.HTTPClient(endpoint, *args, **kwargs)
/usr/lib/python2.7/site-packages/glanceclient/common/http.py(57)__init__()
and in
/usr/lib/python2.7/site-packages/glanceclient/common/http.py(57)__init__()
self.identity_headers = kwargs.get('identity_headers')
self.auth_token = kwargs.get('token')
and the self.identity_headers may be like:
{'X-Service-Catalog': '[]', 'X-Auth-Token': None, 'X-Roles': u'admin',
'X-Tenant-Id': None, 'X-User-Id': None, 'X-Identity-Status': 'Confirmed'}
and for https://review.openstack.org/#/c/136326/,
for the code:
if self.identity_headers:
for k, v in six.iteritems(self.identity_headers):
headers.setdefault(k, v)
headers would be like: {'X-Service-Catalog': '[]', 'X-Auth-Token':
None, 'X-Roles': u'admin', 'X-Tenant-Id': None, 'X-User-Id': None, 'X
-Identity-Status': 'Confirmed', }
so headers = self.encode_headers(headers) in
/usr/lib/python2.7/site-packages/glanceclient/common/http.py(1957)__request()
would raise TypeError(NoneType can't be encoded), thus resize(or other
operation need call glance) would fail.
To manage notifications about this bug go to:
https://bugs.launchpad.net/python-glanceclient/+bug/1415935/+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 1416427] [NEW] VPNaaS: Create functional tests for OpenSwan implementation
Public bug reported: Currently, there are no functional tests for OpenSwan reference implementation of VPNaaS. Should develop tests to exercise this implementation. ** Affects: neutron Importance: Undecided Assignee: Paul Michali (pcm) Status: New ** Tags: vpnaas ** Changed in: neutron Assignee: (unassigned) = Paul Michali (pcm) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1416427 Title: VPNaaS: Create functional tests for OpenSwan implementation Status in OpenStack Neutron (virtual network service): New Bug description: Currently, there are no functional tests for OpenSwan reference implementation of VPNaaS. Should develop tests to exercise this implementation. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1416427/+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 1416286] [NEW] In launch instance page, the select network page's layout is not as others
Public bug reported: In launch instance page, other page layout: left is col-sm-6,right is col-sm-6. but in select network page the layout is not as that, and I look the page has css td class=actions, td class=help_text, there is no code about .actions .help_text in https://github.com/openstack/horizon/blob/master/openstack_dashboard/static/dashboard/scss/components/_workflow.scss. In juno it has those css(https://github.com/openstack/horizon/blob/stable/juno/openstack_dashboard/static/dashboard/scss/horizon_workflow.scss#L9). ** Affects: nova Importance: Undecided Assignee: tinytmy (tangmeiyan77) 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/1416286 Title: In launch instance page, the select network page's layout is not as others Status in OpenStack Compute (Nova): New Bug description: In launch instance page, other page layout: left is col-sm-6,right is col-sm-6. but in select network page the layout is not as that, and I look the page has css td class=actions, td class=help_text, there is no code about .actions .help_text in https://github.com/openstack/horizon/blob/master/openstack_dashboard/static/dashboard/scss/components/_workflow.scss. In juno it has those css(https://github.com/openstack/horizon/blob/stable/juno/openstack_dashboard/static/dashboard/scss/horizon_workflow.scss#L9). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1416286/+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 1416000] Re: VMware: write error lost while transferring volume
** Also affects: oslo.vmware 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/1416000 Title: VMware: write error lost while transferring volume Status in Cinder: New Status in OpenStack Compute (Nova): New Status in Oslo VMware library for OpenStack projects: New Bug description: I'm running the following command: cinder create --image-id a24f216f-9746-418e-97f9-aebd7fa0e25f 1 The write side of the data transfer (a VMwareHTTPWriteFile object) returns an error in write() which I haven't debugged, yet. However, this error is never reported to the user, although it does show up in the logs. The effect is that the transfer sits in the 'downloading' state until the 7200 second timeout, when it reports the timeout. The reason is that the code which waits on transfer completion (in start_transfer) does: try: # Wait on the read and write events to signal their end read_event.wait() write_event.wait() except (timeout.Timeout, Exception) as exc: ... That is, it waits for the read thread to signal completion via read_event before checking write_event. However, because write_thread has died, read_thread is blocking and will never signal completion. You can demonstrate this by swapping the order. If you want for write first it will die immediately, which is what you want. However, that's not right either because now you're missing read errors. Ideally this code needs to be able to notice an error at either end and stop immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1416000/+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 1416326] [NEW] Add l3 agent to Ha router failed
Public bug reported: reproduce progress: 1. create a Ha router(min_l3_agents_per_router=2) 2. use 'l3-agent-router-remove' remove a agent from router 3. use 'l3-agent-router-add' add the deleted agent to router you will find the error in neutron-server: 2015-01-30 09:38:47.126 26402 INFO neutron.api.v2.resource [req-23ade291-165e-4c24-899f-40062005b216 None] create failed (client error): The router a081ae1d-ad5b-41b5-a60a-6c129ba3efa b has been already hosted by the L3 Agent 3b61ea90-8373-4609-adda-c10118401f4a. ** Affects: neutron Importance: Undecided Assignee: shihanzhang (shihanzhang) Status: New ** Changed in: neutron Assignee: (unassigned) = shihanzhang (shihanzhang) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1416326 Title: Add l3 agent to Ha router failed Status in OpenStack Neutron (virtual network service): New Bug description: reproduce progress: 1. create a Ha router(min_l3_agents_per_router=2) 2. use 'l3-agent-router-remove' remove a agent from router 3. use 'l3-agent-router-add' add the deleted agent to router you will find the error in neutron-server: 2015-01-30 09:38:47.126 26402 INFO neutron.api.v2.resource [req-23ade291-165e-4c24-899f-40062005b216 None] create failed (client error): The router a081ae1d-ad5b-41b5-a60a-6c129ba3efa b has been already hosted by the L3 Agent 3b61ea90-8373-4609-adda-c10118401f4a. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1416326/+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 1416308] [NEW] remove_router_interface need to improve its validate to avoid 500 DBError
Public bug reported:
500 DBError should not be returned in a user operation.
[User operation]
curl -i -X PUT -H X-Auth-Token: $TOKEN -H Content-Type: application/json
http://192.168.122.201:9696/v2.0/routers/edff6799-7f1b-4d9e-bc8e-115cd22afd82/remove_router_interface
-d '{id:edff6799-7f1b-4d9e-remove_router_interface}'
HTTP/1.1 500 Internal Server Error
Content-Type: application/json; charset=UTF-8
Content-Length: 150
X-Openstack-Request-Id: req-31c11f44-73c4-47bf-bbc3-a3b0eb41148d
Date: Fri, 30 Jan 2015 06:30:26 GMT
{NeutronError: {message: Request Failed: internal server error while
processing your request., type: HTTPInternalServerError, detail: }}
When subnet_id or port_id is not defined in the body of the above RESR API
request, 400 Error should be returned.
However, the varidate for this is not enough and cause a 500 DB Error.
[TraceLog]
2015-01-28 21:37:16.956 2589 ERROR neutron.api.v2.resource
[req-c65b69cd-9a1b-4083-b85f-ea98030f5022 None] add_router_interface failed
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource Traceback (most
recent call last):
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource File
/usr/lib/python2.6/site-packages/neutron/api/v2/resource.py, line 87, in
resource
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource result =
method(request=request, **args)
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource File
/usr/lib/python2.6/site-packages/neutron/api/v2/base.py, line 194, in
_handle_action
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource return
getattr(self._plugin, name)(*arg_list, **kwargs)
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource File
/usr/lib/python2.6/site-packages/neutron/db/l3_db.py, line 367, in
add_router_interface
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource 'tenant_id':
subnet['tenant_id'],
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource UnboundLocalError:
local variable 'subnet' referenced before assignment
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource
[About fix]
A varidate like in add_router_interface should be good enough.
See add_router_interface is returning 400 correctly.
curl -i -X PUT -H X-Auth-Token: $TOKEN -H Content-Type: application/json
http://192.168.122.201:9696/v2.0/routers/139d6962-0919-444a-8ee4-8e47e35f054b/add_router_interface
-d '{router:{name:test_router}}'
HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=UTF-8
Content-Length: 134
X-Openstack-Request-Id: req-bca4b0ca-9e3a-4171-b783-ccc9a8c1cb80
Date: Thu, 29 Jan 2015 02:20:39 GMT
{NeutronError: {message: Bad router request: Either subnet_id or port_id
must be specified, type: BadRequest, detail: }}
** Affects: neutron
Importance: Undecided
Assignee: watanabe.isao (watanabe.isao)
Status: New
** Changed in: neutron
Assignee: (unassigned) = watanabe.isao (watanabe.isao)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1416308
Title:
remove_router_interface need to improve its validate to avoid 500
DBError
Status in OpenStack Neutron (virtual network service):
New
Bug description:
500 DBError should not be returned in a user operation.
[User operation]
curl -i -X PUT -H X-Auth-Token: $TOKEN -H Content-Type: application/json
http://192.168.122.201:9696/v2.0/routers/edff6799-7f1b-4d9e-bc8e-115cd22afd82/remove_router_interface
-d '{id:edff6799-7f1b-4d9e-remove_router_interface}'
HTTP/1.1 500 Internal Server Error
Content-Type: application/json; charset=UTF-8
Content-Length: 150
X-Openstack-Request-Id: req-31c11f44-73c4-47bf-bbc3-a3b0eb41148d
Date: Fri, 30 Jan 2015 06:30:26 GMT
{NeutronError: {message: Request Failed: internal server error while
processing your request., type: HTTPInternalServerError, detail: }}
When subnet_id or port_id is not defined in the body of the above RESR API
request, 400 Error should be returned.
However, the varidate for this is not enough and cause a 500 DB Error.
[TraceLog]
2015-01-28 21:37:16.956 2589 ERROR neutron.api.v2.resource
[req-c65b69cd-9a1b-4083-b85f-ea98030f5022 None] add_router_interface failed
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource Traceback (most
recent call last):
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource File
/usr/lib/python2.6/site-packages/neutron/api/v2/resource.py, line 87, in
resource
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource result =
method(request=request, **args)
2015-01-28 21:37:16.956 2589 TRACE neutron.api.v2.resource File
/usr/lib/python2.6/site-packages/neutron/api/v2/base.py, line 194, in
_handle_action
[Yahoo-eng-team] [Bug 1416315] [NEW] delete ip rule in dvr agent failed
Public bug reported: when I create a dvr router, I find the error log in l3 agent: 2015-01-30 09:04:41.979 26426 DEBUG neutron.agent.linux.utils [-] Running command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'qr outer-bd7efd9a-88bb-4d19-bfe9-d5d24ec16eda', 'ip', 'rule', 'del', 'priority', 'None'] create_process /opt/stack/neutron/neutron/agent/linux/utils.py:46 2015-01-30 09:04:42.238 26426 ERROR neutron.agent.linux.utils [-] Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'qrouter-bd7efd9a-88bb-4d19-bfe9-d5d24ec16eda', 'ip', 'rule', 'del', 'priorit y', 'None'] Exit code: 255 Stdout: '' Stderr: 'Error: argument None is wrong: preference value is invalid\n\n' ** 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/1416315 Title: delete ip rule in dvr agent failed Status in OpenStack Neutron (virtual network service): New Bug description: when I create a dvr router, I find the error log in l3 agent: 2015-01-30 09:04:41.979 26426 DEBUG neutron.agent.linux.utils [-] Running command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'qr outer-bd7efd9a-88bb-4d19-bfe9-d5d24ec16eda', 'ip', 'rule', 'del', 'priority', 'None'] create_process /opt/stack/neutron/neutron/agent/linux/utils.py:46 2015-01-30 09:04:42.238 26426 ERROR neutron.agent.linux.utils [-] Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'qrouter-bd7efd9a-88bb-4d19-bfe9-d5d24ec16eda', 'ip', 'rule', 'del', 'priorit y', 'None'] Exit code: 255 Stdout: '' Stderr: 'Error: argument None is wrong: preference value is invalid\n\n' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1416315/+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 1416303] [NEW] response of v3 OS-EC2 API doesn't contain links field
Public bug reported:
An example of create API:
{credential: {access: 1d3c23ddf17b4a2dbb1702fda6f70fff,
tenant_id: af893e3fa7e94f380103e3a0777b, secret:
e27ca17c32534c18a5d695f26bd766db, user_id:
ea8e8e91c7404f9db859730df4374137, trust_id: null}}
This is because we don't apply wrap_member or wrap_collection on the response
of v3 OS-EC2 API.
https://github.com/openstack/keystone/blob/master/keystone/contrib/ec2/controllers.py#L387
https://github.com/openstack/keystone/blob/master/keystone/contrib/ec2/controllers.py#L174
** Affects: keystone
Importance: Undecided
Assignee: wanghong (w-wanghong)
Status: New
** Changed in: keystone
Assignee: (unassigned) = wanghong (w-wanghong)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1416303
Title:
response of v3 OS-EC2 API doesn't contain links field
Status in OpenStack Identity (Keystone):
New
Bug description:
An example of create API:
{credential: {access: 1d3c23ddf17b4a2dbb1702fda6f70fff,
tenant_id: af893e3fa7e94f380103e3a0777b, secret:
e27ca17c32534c18a5d695f26bd766db, user_id:
ea8e8e91c7404f9db859730df4374137, trust_id: null}}
This is because we don't apply wrap_member or wrap_collection on the response
of v3 OS-EC2 API.
https://github.com/openstack/keystone/blob/master/keystone/contrib/ec2/controllers.py#L387
https://github.com/openstack/keystone/blob/master/keystone/contrib/ec2/controllers.py#L174
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1416303/+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 1416306] [NEW] duplicate routes in the namespace of dvr router agent
Public bug reported: when I create a dvr router, I found there are duplicate routes in router namespace: root@devstack:~# ip netns exec qrouter-bd7efd9a-88bb-4d19-bfe9-d5d24ec16eda ip rule 0: from all lookup local 32766: from all lookup main 32767: from all lookup default 32768: from 10.0.0.3 lookup 16 32769: from 20.20.20.5 lookup 16 167772161: from 10.0.0.1/24 lookup 167772161 167772161: from 10.0.0.1/24 lookup 167772161 167772161: from 10.0.0.1/24 lookup 167772161 167772161: from 10.0.0.1/24 lookup 167772161 167772161: from 10.0.0.1/24 lookup 167772161 336860161: from 20.20.20.1/24 lookup 336860161 336860161: from 20.20.20.1/24 lookup 336860161 336860161: from 20.20.20.1/24 lookup 336860161 336860161: from 20.20.20.1/24 lookup 336860161 336860161: from 20.20.20.1/24 lookup 336860161 ** 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/1416306 Title: duplicate routes in the namespace of dvr router agent Status in OpenStack Neutron (virtual network service): New Bug description: when I create a dvr router, I found there are duplicate routes in router namespace: root@devstack:~# ip netns exec qrouter-bd7efd9a-88bb-4d19-bfe9-d5d24ec16eda ip rule 0: from all lookup local 32766: from all lookup main 32767: from all lookup default 32768: from 10.0.0.3 lookup 16 32769: from 20.20.20.5 lookup 16 167772161: from 10.0.0.1/24 lookup 167772161 167772161: from 10.0.0.1/24 lookup 167772161 167772161: from 10.0.0.1/24 lookup 167772161 167772161: from 10.0.0.1/24 lookup 167772161 167772161: from 10.0.0.1/24 lookup 167772161 336860161: from 20.20.20.1/24 lookup 336860161 336860161: from 20.20.20.1/24 lookup 336860161 336860161: from 20.20.20.1/24 lookup 336860161 336860161: from 20.20.20.1/24 lookup 336860161 336860161: from 20.20.20.1/24 lookup 336860161 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1416306/+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 1416321] Re: Attempt to boot from volume - no image supplied
A revert of this nova commit seems to fix the problem
https://review.openstack.org/#/c/143054/
** Also 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/1416321
Title:
Attempt to boot from volume - no image supplied
Status in OpenStack Compute (Nova):
New
Status in tripleo - openstack on openstack:
Triaged
Bug description:
About 12 UTC 29/1/2015 all tripleo overcloud jobs started failing with
2015-01-29 17:32:21.475 | + wait_for -w 50 --delay 5 -- neutron port-list -f
csv -c id --quote none '|' grep id
2015-01-29 17:33:11.364 | Timing out after 50 seconds:
2015-01-29 17:33:11.364 | COMMAND=neutron port-list -f csv -c id --quote none
| grep id
2015-01-29 17:33:11.364 | OUTPUT=
2015-01-29 17:33:11.364 | + cleanup
reproducing this localy shows a failure in getting the block device
| created | 2015-01-30T02:43:05Z
|
| fault| {message: Build of instance
4c958085-7a95-4825-af04-cf574c3614c7 aborted: Failure prepping block device.,
code: 500, details: File \/opt/stack/venvs/nova/lib/
python2.7/site-packages/nova/compute/manager.py\, line 2077, in
_do_build_and_run_instance |
| | filter_properties)
|
| | File
\/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/compute/manager.py\,
line 2192, in _build_and_run_instance
|
| | 'create.error', fault=e)
|
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1416321/+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 1416278] Re: Ha router should not schedule to 'dvr_snat' agent
** Changed in: neutron
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1416278
Title:
Ha router should not schedule to 'dvr_snat' agent
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
Ha router should not schedule to 'dvr_snat' agent, but in
'get_l3_agent_candidates', it allow a Ha router to 'dvr-snat' agent,
def get_l3_agent_candidates(self, context, sync_router, l3_agents):
Get the valid l3 agents for the router from a list of l3_agents.
candidates = []
for l3_agent in l3_agents:
if not l3_agent.admin_state_up:
continue
agent_conf = self.get_configuration_dict(l3_agent)
router_id = agent_conf.get('router_id', None)
use_namespaces = agent_conf.get('use_namespaces', True)
handle_internal_only_routers = agent_conf.get(
'handle_internal_only_routers', True)
gateway_external_network_id = agent_conf.get(
'gateway_external_network_id', None)
agent_mode = agent_conf.get('agent_mode', 'legacy')
if not use_namespaces and router_id != sync_router['id']:
continue
ex_net_id = (sync_router['external_gateway_info'] or {}).get(
'network_id')
if ((not ex_net_id and not handle_internal_only_routers) or
(ex_net_id and gateway_external_network_id and
ex_net_id != gateway_external_network_id)):
continue
is_router_distributed = sync_router.get('distributed', False)
if agent_mode in ('legacy', 'dvr_snat') and (
not is_router_distributed):
candidates.append(l3_agent)
so 'if agent_mode in ('legacy', 'dvr_snat') ' should be 'if
agent_mode == 'legacy''
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1416278/+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 1416412] [NEW] DHCP agent should be more proactive in fetching active networks
Public bug reported: Currently DHCP agent resyncs its state quite often but it's only happening if there is a reason to resync: either some issues on agent side or update command received from neutron server. That could lead to a case when new active networks exist but agent doesn't know anything about them and doesn't try to host them. The need for this feature becomes more important after dhcp rescheduling has been merged. ** Affects: neutron Importance: Medium Assignee: Eugene Nikanorov (enikanorov) Status: New ** Tags: l3-ipam-dhcp -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1416412 Title: DHCP agent should be more proactive in fetching active networks Status in OpenStack Neutron (virtual network service): New Bug description: Currently DHCP agent resyncs its state quite often but it's only happening if there is a reason to resync: either some issues on agent side or update command received from neutron server. That could lead to a case when new active networks exist but agent doesn't know anything about them and doesn't try to host them. The need for this feature becomes more important after dhcp rescheduling has been merged. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1416412/+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 1086189] Re: User is not logged out once his token is revoked by keystone
Paul, please investigate this bug in close contact with our Keystone team. According to what Vlad has told me, there are some weirdness in Keystone behavior - the user is being logged out not on the next immediate request after his set of roles has been shrunk, but several minutes later. Need to find out whether we could eliminate this lag. ** Changed in: django-openstack-auth Status: In Progress = Invalid ** Changed in: django-openstack-auth Importance: Low = Undecided ** Changed in: django-openstack-auth Assignee: Vlad Okhrimenko (vokhrimenko) = (unassigned) ** Changed in: horizon Assignee: Vlad Okhrimenko (vokhrimenko) = Paul Karikh (pkarikh) -- 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/1086189 Title: User is not logged out once his token is revoked by keystone Status in Django OpenStack Auth: Invalid Status in OpenStack Dashboard (Horizon): In Progress Bug description: Once user's token is revoked (due to, for example reducing user's set of roles in current tenant), on the next request he is not logged out, but instead gets a bunch of 'Unauthorized' errors. Not redirecting user in that case to log-in page does not make sense because he can't do anything useful without valid token. To manage notifications about this bug go to: https://bugs.launchpad.net/django-openstack-auth/+bug/1086189/+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 1416361] [NEW] Nova doesn't allow to resize down an instance booted from a volume
Public bug reported: If instance is booted from a volume, Nova won't allow to resize the instance down, despite the fact root disk (ephemeral) is not even used: http://paste.openstack.org/show/164108/ malor@ubuntu:~/devstack$ nova resize --poll demo m1.tiny Server resizing... 100% complete Finished but in nova-compute.log: 2015-01-30 11:06:14.535 ERROR oslo.messaging.rpc.dispatcher [req-c788c8b2-d953-4f7f-962c-afca7ad41ff7 demo demo] Exception during message handling: Resize error: Unable to resize disk down. 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 137, in _dispatch_and_reply 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 180, in _dispatch 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 126, in _do_dispatch 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/exception.py, line 88, in wrapped 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher payload) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py, line 82, in __exit__ 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/exception.py, line 71, in wrapped 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher return f(self, context, *args, **kw) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 296, in decorated_function 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher pass 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py, line 82, in __exit__ 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 281, in decorated_function 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher return function(self, context, *args, **kwargs) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 346, in decorated_function 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher return function(self, context, *args, **kwargs) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 269, in decorated_function 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher migration.instance_uuid, exc_info=True) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py, line 82, in __exit__ 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 255, in decorated_function 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher return function(self, context, *args, **kwargs) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 324, in decorated_function 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher kwargs['instance'], e, sys.exc_info()) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py, line 82, in __exit__ 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 312, in decorated_function 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher return function(self, context, *args, **kwargs) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 3851, in resize_instance 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher self.instance_events.clear_events_for_instance(instance) 2015-01-30 11:06:14.535 TRACE oslo.messaging.rpc.dispatcher File
