[Yahoo-eng-team] [Bug 1759743] [NEW] Multiple same query parameters are not reflected on "servers_link" value in the response

2018-03-28 Thread Takashi NATSUME 
Public bug reported:

Description
===

In "List Servers Detailed" API, when specifying multiple same query parameters 
(e.g. status=error=active),
only one pair of parameter and value (status=error) is included in the 
"servers_links"("href") of the response.

The 'collections.OrderedDict' eliminate duplications of query parameters.
So the issue occurrs.

https://github.com/openstack/nova/blob/3f08521d33c60e4bfe04bc236bb8761f654004df/nova/api/openstack/common.py#L390

Steps to reproduce
==

Execute "List Servers Detailed" API with multiple same query parameters
(status=error=active) and 'limit' query parameter.

curl -g -i -X GET
"http://10.0.2.15/compute/v2.1/servers/detail?limit=1=error=active;
-H "OpenStack-API-Version: compute 2.60" -H "User-Agent: python-
novaclient" -H "Accept: application/json" -H "X-OpenStack-Nova-API-
Version: 2.60" -H "X-Auth-Token: $TOKEN"

Expected result
===

All pairs of query parameter and value (status=error=active)
should be included in "servers_links".

{
   "servers_links":[
  {
 
"href":"http://10.0.2.15/compute/v2.1/servers/detail?limit=1=error=active=e8c1d40e-2be7-4c8e-9283-88be8562bc5a;,
 "rel":"next"
  }
   ],
   "servers":[
(snipped...)
   ]
}

Actual result
=

only one pair of parameter and value (status=error) is included.

{
   "servers_links":[
  {
 
"href":"http://10.0.2.15/compute/v2.1/servers/detail?limit=1=error=e8c1d40e-2be7-4c8e-9283-88be8562bc5a;,
 "rel":"next"
  }
   ],
   "servers":[
(snipped...)
   ]
}

Environment
===

OS: Ubuntu 16.04.2 LTS
nova master (commit 3f08521d33c60e4bfe04bc236bb8761f654004df)

** Affects: nova
 Importance: Undecided
 Assignee: Takashi NATSUME (natsume-takashi)
 Status: In Progress


** Tags: api

** Tags added: api

** Changed in: nova
   Status: New => In Progress

** Description changed:

  Description
  ===
  
- In "List Servers" API, when specifying multiple same query parameters (e.g. 
status=error=active),
+ In "List Servers Detailed" API, when specifying multiple same query 
parameters (e.g. status=error=active),
  only one pair of parameter and value (status=error) is included in the 
"servers_links"("href") of the response.
  
  The 'collections.OrderedDict' eliminate duplications of query parameters.
  So the issue occurrs.
  
  
https://github.com/openstack/nova/blob/3f08521d33c60e4bfe04bc236bb8761f654004df/nova/api/openstack/common.py#L390
  
  Steps to reproduce
  ==
  
- Execute "List Servers" API with multiple same query parameters
+ Execute "List Servers Detailed" API with multiple same query parameters
  (status=error=active) and 'limit' query parameter.
  
  curl -g -i -X GET
  
"http://10.0.2.15/compute/v2.1/servers/detail?limit=1=error=active;
  -H "OpenStack-API-Version: compute 2.60" -H "User-Agent: python-
  novaclient" -H "Accept: application/json" -H "X-OpenStack-Nova-API-
  Version: 2.60" -H "X-Auth-Token: $TOKEN"
  
- 
  Expected result
  ===
  
  All pairs of query parameter and value (status=error=active)
  should be included in "servers_links".
  
  {
-"servers_links":[
-   {
-  
"href":"http://10.0.2.15/compute/v2.1/servers/detail?limit=1=error=active=e8c1d40e-2be7-4c8e-9283-88be8562bc5a;,
-  "rel":"next"
-   }
-],
-"servers":[
+    "servers_links":[
+   {
+  
"href":"http://10.0.2.15/compute/v2.1/servers/detail?limit=1=error=active=e8c1d40e-2be7-4c8e-9283-88be8562bc5a;,
+  "rel":"next"
+   }
+    ],
+    "servers":[
  (snipped...)
-]
+    ]
  }
  
  Actual result
  =
  
  only one pair of parameter and value (status=error) is included.
  
  {
-"servers_links":[
-   {
-  
"href":"http://10.0.2.15/compute/v2.1/servers/detail?limit=1=error=e8c1d40e-2be7-4c8e-9283-88be8562bc5a;,
-  "rel":"next"
-   }
-],
-"servers":[
+    "servers_links":[
+   {
+  
"href":"http://10.0.2.15/compute/v2.1/servers/detail?limit=1=error=e8c1d40e-2be7-4c8e-9283-88be8562bc5a;,
+  "rel":"next"
+   }
+    ],
+    "servers":[
  (snipped...)
-]
+    ]
  }
  
  Environment
  ===
  
  OS: Ubuntu 16.04.2 LTS
  nova master (commit 3f08521d33c60e4bfe04bc236bb8761f654004df)

-- 
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/1759743

Title:
  Multiple same query parameters are not reflected on "servers_link"
  value in the response

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Description
  ===

  In "List Servers Detailed" API, when specifying multiple same query 
parameters (e.g. status=error=active),
  only one pair of parameter and value (status=error) is included in the 
"servers_links"("href") of the response.

  The 'collections.OrderedDict' eliminate duplications of

[Yahoo-eng-team] [Bug 1759546] Re: Unable to retrieve nested resource list from horizon

2018-03-28 Thread Akihiro Motoki 
This seems about heat panel.

** Project changed: horizon => heat-dashboard

-- 
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/1759546

Title:
  Unable to retrieve nested resource list from horizon

Status in heat-dashboard:
  New

Bug description:
  From Openstack horizon we cannot retrieve nested resource list.

  When even stack is created using nested templates then from horizon we
  can only get resource list of main template. But from CLI we can
  retrieve all the resources information even the ones that are defined
  in nested templates using depth attribute available..

  I think the same option should be available from horizon and CLI. So
  user should be able to get nested resource list, get the information
  about nested resource.

To manage notifications about this bug go to:
https://bugs.launchpad.net/heat-dashboard/+bug/1759546/+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 1759694] Re: DHCP agent doesn't respawn metadata when enable_isolated_metadata and gateway removed

2018-03-28 Thread Swaminathan Vasudevan 
*** This bug is a duplicate of bug 1753540 ***
https://bugs.launchpad.net/bugs/1753540

Cherry-picked to stable/pike
https://review.openstack.org/#/c/557536/

** This bug has been marked a duplicate of bug 1753540
   When isolated metadata is enabled, metadata proxy doesn't get automatically 
started/stopped when needed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1759694

Title:
  DHCP agent doesn't respawn metadata when enable_isolated_metadata and
  gateway removed

Status in neutron:
  New

Bug description:
  Hi,

  We are running Neutron Pike with OVS and DVR.

  When enable_isolated_metadata is True and we remove the gateway port
  for a network from a router, a metadata process is not respawned to
  start serving metadata.

  How to replicate :

  [root@5c1fced0888e /]# openstack network create test_nw
  +---+--+
  | Field | Value|
  +---+--+
  | admin_state_up| UP   |
  | availability_zone_hints   |  |
  | availability_zones|  |
  | created_at| 2018-03-28T21:18:29Z |
  | description   |  |
  | dns_domain|  |
  | id| d19dabb2-f8c8-4608-8387-1f356a9f0f14 |
  | ipv4_address_scope| None |
  | ipv6_address_scope| None |
  | is_default| False|
  | is_vlan_transparent   | None |
  | mtu   | 1500 |
  | name  | test_nw  |
  | port_security_enabled | True |
  | project_id| c053ae2460e741008fa0ea908ae7da8c |
  | provider:network_type | vxlan|
  | provider:physical_network | None |
  | provider:segmentation_id  | 65035|
  | qos_policy_id | None |
  | revision_number   | 2|
  | router:external   | Internal |
  | segments  | None |
  | shared| False|
  | status| ACTIVE   |
  | subnets   |  |
  | tags  |  |
  | updated_at| 2018-03-28T21:18:30Z |
  +---+--+
  [root@5c1fced0888e /]# openstack subnet create --network 
d19dabb2-f8c8-4608-8387-1f356a9f0f14 --subnet-range 10.10.10.0/24 --gateway 
10.10.10.254 test_sn
  +-+--+
  | Field   | Value|
  +-+--+
  | allocation_pools| 10.10.10.1-10.10.10.253  |
  | cidr| 10.10.10.0/24|
  | created_at  | 2018-03-28T21:20:03Z |
  | description |  |
  | dns_nameservers |  |
  | enable_dhcp | True |
  | gateway_ip  | 10.10.10.254 |
  | host_routes |  |
  | id  | 1cd9d1f4-8c43-411b-85db-9514fe7b5e06 |
  | ip_version  | 4|
  | ipv6_address_mode   | None |
  | ipv6_ra_mode| None |
  | name| test_sn  |
  | network_id  | d19dabb2-f8c8-4608-8387-1f356a9f0f14 |
  | project_id  | c053ae2460e741008fa0ea908ae7da8c |
  | revision_number | 0|
  | segment_id  | None |
  | service_types   |  |
  | subnetpool_id   | None |
  | tags|  |
  | updated_at  | 2018-03-28T21:20:03Z |
  | use_default_subnet_pool | None

[Yahoo-eng-team] [Bug 1759345] Re: -with-oslo-master job fails with DuplicateOptError: duplicate option: polling_interval

2018-03-28 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/557003
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=a1b49c796e44df35318fc35327b132aae22dce48
Submitter: Zuul
Branch:master

commit a1b49c796e44df35318fc35327b132aae22dce48
Author: Ihar Hrachyshka 
Date:   Tue Mar 27 11:32:37 2018 -0700

Don't define polling_interval option in two places

The option is currently defined in two places - as a generic agent
option and as a sriov agent specific one. This is a problem now that
oslo.config tracks location where options are defined
(I6dec1e09dcab203c6287f9c56c866f220a42f850) because when unit test
runner imports all modules, it registers the option from those two
separate locations, and since locations are different, it's considered
the options are duplicate, which results in the following error:

DuplicateOptError: duplicate option: polling_interval

To fix the issue, I removed the definition of the option from sriov
module and made sure the common agent options are registered whenever
the sriov module is imported.

Change-Id: I485532692f4b3a5804885e0325a8352fe6b1aa65
Closes-Bug: #1759345


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1759345

Title:
  -with-oslo-master job fails with DuplicateOptError: duplicate option:
  polling_interval

Status in neutron:
  Fix Released

Bug description:
  http://logs.openstack.org/periodic/git.openstack.org/openstack/neutron/master
  /openstack-tox-py27-with-oslo-master/f65fec8/job-output.txt.gz

  2018-03-27 06:16:32.984356 | ubuntu-xenial | --- import errors ---
  2018-03-27 06:16:32.984599 | ubuntu-xenial | Failed to import test module: 
neutron.tests.unit.plugins.ml2.drivers.mech_sriov.agent.common.test_config
  2018-03-27 06:16:32.984708 | ubuntu-xenial | Traceback (most recent call 
last):
  2018-03-27 06:16:32.985036 | ubuntu-xenial |   File 
"/home/zuul/src/git.openstack.org/openstack/neutron/.tox/py27/local/lib/python2.7/site-packages/unittest2/loader.py",
 line 456, in _find_test_path
  2018-03-27 06:16:32.985174 | ubuntu-xenial | module = 
self._get_module_from_name(name)
  2018-03-27 06:16:32.985496 | ubuntu-xenial |   File 
"/home/zuul/src/git.openstack.org/openstack/neutron/.tox/py27/local/lib/python2.7/site-packages/unittest2/loader.py",
 line 395, in _get_module_from_name
  2018-03-27 06:16:32.985563 | ubuntu-xenial | __import__(name)
  2018-03-27 06:16:32.985804 | ubuntu-xenial |   File 
"neutron/tests/unit/plugins/ml2/drivers/mech_sriov/agent/common/test_config.py",
 line 21, in 
  2018-03-27 06:16:32.985993 | ubuntu-xenial | from 
neutron.plugins.ml2.drivers.mech_sriov.agent.common import config
  2018-03-27 06:16:32.986193 | ubuntu-xenial |   File 
"neutron/plugins/ml2/drivers/mech_sriov/agent/common/config.py", line 57, in 

  2018-03-27 06:16:32.986351 | ubuntu-xenial | 
agent_common_config.register_agent_sriov_nic_opts()
  2018-03-27 06:16:32.986588 | ubuntu-xenial |   File 
"neutron/conf/plugins/ml2/drivers/mech_sriov/agent_common.py", line 56, in 
register_agent_sriov_nic_opts
  2018-03-27 06:16:32.986717 | ubuntu-xenial | 
cfg.register_opts(agent_opts, 'AGENT')
  2018-03-27 06:16:32.987017 | ubuntu-xenial |   File 
"/home/zuul/src/git.openstack.org/openstack/neutron/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 2416, in __inner
  2018-03-27 06:16:32.987129 | ubuntu-xenial | result = f(self, *args, 
**kwargs)
  2018-03-27 06:16:32.987458 | ubuntu-xenial |   File 
"/home/zuul/src/git.openstack.org/openstack/neutron/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 2614, in register_opts
  2018-03-27 06:16:32.987604 | ubuntu-xenial | self.register_opt(opt, 
group, clear_cache=False)
  2018-03-27 06:16:32.987969 | ubuntu-xenial |   File 
"/home/zuul/src/git.openstack.org/openstack/neutron/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 2420, in __inner
  2018-03-27 06:16:32.988101 | ubuntu-xenial | return f(self, *args, 
**kwargs)
  2018-03-27 06:16:32.988437 | ubuntu-xenial |   File 
"/home/zuul/src/git.openstack.org/openstack/neutron/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 2590, in register_opt
  2018-03-27 06:16:32.988546 | ubuntu-xenial | return 
group._register_opt(opt, cli)
  2018-03-27 06:16:32.988847 | ubuntu-xenial |   File 
"/home/zuul/src/git.openstack.org/openstack/neutron/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 1886, in _register_opt
  2018-03-27 06:16:32.988952 | ubuntu-xenial | if 
_is_opt_registered(self._opts, opt):
  2018-03-27 06:16:32.989257 | ubuntu-xenial |   File

[Yahoo-eng-team] [Bug 1744611] Re: operation_log: QUERY_STRING is not logged

2018-03-28 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/536180
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=61039b0a29df04f8f353fcfc0361604407d39894
Submitter: Zuul
Branch:master

commit 61039b0a29df04f8f353fcfc0361604407d39894
Author: Akihiro Motoki 
Date:   Mon Jan 22 09:36:17 2018 +0900

operation_log: add QUERY_STRING to request_url

Change-Id: Iaa2690c0c98e5925d4a6f3de43402c66b1ca0dc1
Closes-Bug: #1744611


** Changed in: horizon
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1744611

Title:
  operation_log: QUERY_STRING is not logged

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Some operations use QUERY_STRING but QUERY_STRINGs are not logged in
  the operation log. It would be nice if they are logged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1744611/+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 1750843] Re: pysaml2 version in global requirements must be updated to 4.5.0

2018-03-28 Thread Matthew Thode 
keystone, you can test by depending on this patch
https://review.openstack.org/557434

** Also affects: keystone
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1750843

Title:
  pysaml2 version in global requirements must be updated to 4.5.0

Status in OpenStack Identity (keystone):
  New
Status in OpenStack Global Requirements:
  New

Bug description:
  As per security vulnerability CVE-2016-10149, XML External Entity
  (XXE) vulnerability in PySAML2 4.4.0 and earlier allows remote
  attackers to read arbitrary files via a crafted SAML XML request or
  response and it has a CVSS v3 Base Score of 7.5.

  The above vulnerability has been fixed in version 4.5.0 as per
  https://github.com/rohe/pysaml2/issues/366. The latest version of
  pysaml2 (https://pypi.python.org/pypi/pysaml2/4.5.0) has this fix.
  However, the global requirements has the version set to < 4.0.3

  
https://github.com/openstack/requirements/blob/master/global-requirements.txt#L230
  pysaml2>=4.0.2,<4.0.3

  
https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L347
  pysaml2===4.0.2

  The version of pysaml2 supported for OpenStack should be updated such
  that OpenStack deployments are not vulnerable to the above mentioned
  CVE.

  pysaml2 is used by OpenStack Keystone for identity Federation. This
  bug in itself is not a security vulnerability but not fixing this bug
  causes OpenStack deployments to be vulnerable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1750843/+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 1420370] Re: Subnet Network Address is missing asterisk

2018-03-28 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/555096
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=f8196331ea139f52b303eb87d0280152f06d9475
Submitter: Zuul
Branch:master

commit f8196331ea139f52b303eb87d0280152f06d9475
Author: Akihiro Motoki 
Date:   Thu Mar 22 08:32:00 2018 +0900

Add asterisk to conditionally required fields

https://review.openstack.org/#/c/552247/ introduced a way to
add asterisk mark to conditionally required fields.

This commit covers several known forms:
- Create Network / Create Subnet
- Create Port
- Attach Interface to Instance
- Add Security Group Rule

Change-Id: I809c23fd64dc2f379c3fdb585741c6b266ec5b1b
Closes-Bug: #1420370
Closes-Bug: #1292165
Closes-Bug: #1755131


** Changed in: horizon
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1420370

Title:
  Subnet Network Address is missing asterisk

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The Network Address field in the Create Subnet workflow (Subnet tab)
  is missing an asterisk.

  Steps to reproduce:

  1. Go to Admin -> Networks
  2. Click on a Network
  3. Click Create Subnet
  4. Attempt to create the subnet without filling in the Network Address field.

  The error message is at the top of the form, when it should be by the
  field, and the Network Address field itself is missing an asterisk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1420370/+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 1755131] Re: Form fields with 'switched' can't be set required=True

2018-03-28 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/555096
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=f8196331ea139f52b303eb87d0280152f06d9475
Submitter: Zuul
Branch:master

commit f8196331ea139f52b303eb87d0280152f06d9475
Author: Akihiro Motoki 
Date:   Thu Mar 22 08:32:00 2018 +0900

Add asterisk to conditionally required fields

https://review.openstack.org/#/c/552247/ introduced a way to
add asterisk mark to conditionally required fields.

This commit covers several known forms:
- Create Network / Create Subnet
- Create Port
- Attach Interface to Instance
- Add Security Group Rule

Change-Id: I809c23fd64dc2f379c3fdb585741c6b266ec5b1b
Closes-Bug: #1420370
Closes-Bug: #1292165
Closes-Bug: #1755131


** Changed in: horizon
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1755131

Title:
  Form fields with 'switched' can't be set required=True

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Some form fields like class AttachInterface in
  dashboards/project/instances/forms.py:

  class AttachInterface(forms.SelfHandlingForm):
  specification_method = forms.ThemableChoiceField(
  label=_("The way to specify an interface"),
  initial=False,
  widget=forms.ThemableSelectWidget(attrs={
  'class': 'switchable',
  'data-slug': 'specification_method',
  }))
  network = forms.ThemableChoiceField(
  label=_("Network"),
  required=False,
  widget=forms.ThemableSelectWidget(attrs={
  'class': 'switched',
  'data-switch-on': 'specification_method',
  'data-specification_method-network': _('Network'),
  }))

  When the value of specification_method field is selected as network,the 
network filed is necessary and should
  set required=True.But when the value is selected as port, the network field 
is not necessary and the network
  field is also be checked and return an error.Now, we need the star when the 
network is necessary and ignore the
  check when it is not necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1755131/+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 1759616] Re: [2.x] CentOS networking adds weird route

2018-03-28 Thread Andres Rodriguez 
This is definitely not a MAAS bug, as the config sent is exactly as the
one send for Ubuntu.

** Also affects: cloud-init
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1759616

Title:
  [2.x] CentOS networking adds weird route

Status in cloud-init:
  New
Status in MAAS:
  Incomplete

Bug description:
  MAAS CentOS deployed machine has a weird route:

  169.254.0.0/16 dev ens3 scope link metric 1002

  [centos@precise ~]$ ip route sh
  default via 192.168.122.1 dev ens3
  169.254.0.0/16 dev ens3 scope link metric 1002
  192.168.122.0/24 dev ens3 proto kernel scope link src 192.168.122.6
  192.168.133.0/24 via 192.168.122.1 dev ens3

  Deploying Ubuntu doesn't yield the same config.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1759616/+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 1584647] Re: [SRU] "Interface monitor is not active" can be observed at ovs-agent start

2018-03-28 Thread Corey Bryant 
** Changed in: neutron (Ubuntu)
   Status: New => Invalid

** Changed in: cloud-archive
   Status: New => Invalid

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

** Changed in: cloud-archive/mitaka
   Importance: Undecided => High

** Changed in: neutron (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: neutron (Ubuntu Xenial)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1584647

Title:
  [SRU] "Interface monitor is not active" can be observed at ovs-agent
  start

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Invalid
Status in neutron source package in Xenial:
  Triaged

Bug description:
  [Impact]

  Requesting to backport to Mitaka since we are seeing this issue in
  Mitaka clouds (and fix landed in Newton) whereby some compute nodes
  fail to have their flows added to br-tun following restart of
  openvswitch-switch.

  [Test Case]

  * Deploy Openstack Mitaka with one compute host
  * Create an instance with overlay network (gre)
  * Make a note of flows added to br-tun (ovs-vsctl dump-flows br-tun)
  * systemctl restart openvswitch-switch
  * Check that flows are re-added to br-tun (compare with previous output)
  * Ensure you do not see "Interface monitor is not active" in 
/var/log/neutron/neutron-openvswitch-agent

  NOTE: the root cause of this issue is that ovsdb monitor async process
  that neutron-openvswitch-agent starts takes too long to start and is
  not active by the time the rpc_loop tries to poll for updates. It is
  hard to simulate this scenario and as such it is difficult to know
  whether it has happened and resolved by this patch. Nevertheless this
  patch is small and known to have resolved the issue for newer versions
  of Openstack.

  [Regression Potential]

  I can't think how this patch could cause a regression. The only
  possible difference could be that the rpc_loop might take longer to
  update flows on ovs restart but that in itself would indicate a wider
  system issue beyond the neutron service that would not constitute a
  regression.

  ---

  I noticed this error message in neutron-ovs-agent log when start
  neutron-openvswitch-agent

  ERROR neutron.agent.linux.ovsdb_monitor [req-a7c7a398-a13b-490e-
  adf8-c5afb24b4b9c None None] Interface monitor is not active.

  ovs-agent will start ovsdb_monitor at [1], and first use it at [2].
  There is no guarantee that ovsdb_monitor is ready at [2]. So, I can
  see the error when start neutron-openvswitch-agent.

  We should block the start to wait for the process to be active, and
  then use it. Or else, the use of ovsdb_monitor will be meaningless.

  [1]
  
https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/agent/linux/polling.py#L35

  [2]
  
https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1994

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1584647/+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 1759609] [NEW] VMware: _detach_instance_volumes method fails due to wrong detach_volume call

2018-03-28 Thread Claudiu Belu 
Public bug reported:

The method _detach_instance_volumes [1] calls self.detach_volume [2]
with an invalid number of arguments (context argument is missing),
causing it to fail.

[1] 
https://github.com/openstack/nova/blob/master/nova/virt/vmwareapi/driver.py#L426
[2] 
https://github.com/openstack/nova/blob/master/nova/virt/vmwareapi/driver.py#L438

** Affects: nova
 Importance: Undecided
 Assignee: Claudiu Belu (cbelu)
 Status: 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/1759609

Title:
  VMware:  _detach_instance_volumes method fails due to wrong
  detach_volume call

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  The method _detach_instance_volumes [1] calls self.detach_volume [2]
  with an invalid number of arguments (context argument is missing),
  causing it to fail.

  [1] 
https://github.com/openstack/nova/blob/master/nova/virt/vmwareapi/driver.py#L426
  [2] 
https://github.com/openstack/nova/blob/master/nova/virt/vmwareapi/driver.py#L438

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1759609/+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 1584647] Re: [SRU] "Interface monitor is not active" can be observed at ovs-agent start

2018-03-28 Thread Corey Bryant 
** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

** Also affects: neutron (Ubuntu Xenial)
   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/1584647

Title:
  [SRU] "Interface monitor is not active" can be observed at ovs-agent
  start

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Invalid
Status in neutron source package in Xenial:
  Triaged

Bug description:
  [Impact]

  Requesting to backport to Mitaka since we are seeing this issue in
  Mitaka clouds (and fix landed in Newton) whereby some compute nodes
  fail to have their flows added to br-tun following restart of
  openvswitch-switch.

  [Test Case]

  * Deploy Openstack Mitaka with one compute host
  * Create an instance with overlay network (gre)
  * Make a note of flows added to br-tun (ovs-vsctl dump-flows br-tun)
  * systemctl restart openvswitch-switch
  * Check that flows are re-added to br-tun (compare with previous output)
  * Ensure you do not see "Interface monitor is not active" in 
/var/log/neutron/neutron-openvswitch-agent

  NOTE: the root cause of this issue is that ovsdb monitor async process
  that neutron-openvswitch-agent starts takes too long to start and is
  not active by the time the rpc_loop tries to poll for updates. It is
  hard to simulate this scenario and as such it is difficult to know
  whether it has happened and resolved by this patch. Nevertheless this
  patch is small and known to have resolved the issue for newer versions
  of Openstack.

  [Regression Potential]

  I can't think how this patch could cause a regression. The only
  possible difference could be that the rpc_loop might take longer to
  update flows on ovs restart but that in itself would indicate a wider
  system issue beyond the neutron service that would not constitute a
  regression.

  ---

  I noticed this error message in neutron-ovs-agent log when start
  neutron-openvswitch-agent

  ERROR neutron.agent.linux.ovsdb_monitor [req-a7c7a398-a13b-490e-
  adf8-c5afb24b4b9c None None] Interface monitor is not active.

  ovs-agent will start ovsdb_monitor at [1], and first use it at [2].
  There is no guarantee that ovsdb_monitor is ready at [2]. So, I can
  see the error when start neutron-openvswitch-agent.

  We should block the start to wait for the process to be active, and
  then use it. Or else, the use of ovsdb_monitor will be meaningless.

  [1]
  
https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/agent/linux/polling.py#L35

  [2]
  
https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1994

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1584647/+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 1715270] Re: Remove usage of kwarg retry_on_request in API

2018-03-28 Thread Sergii Golovatiuk 
** Also affects: tripleo
   Importance: Undecided
   Status: New

** Changed in: tripleo
   Status: New => Confirmed

** Changed in: tripleo
   Status: Confirmed => 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/1715270

Title:
  Remove usage of kwarg retry_on_request in API

Status in OpenStack Compute (nova):
  Fix Released
Status in tripleo:
  In Progress

Bug description:
  As Retry on request is always enabled in oslo.db, so kwarg
  retry_on_request is deprecated for removal in new release Queens.

  https://bugs.launchpad.net/oslo.db/+bug/1714440
  http://git.openstack.org/cgit/openstack/oslo.db/tree/oslo_db/api.py#n109

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1715270/+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 1584647] Re: "Interface monitor is not active" can be observed at ovs-agent start

2018-03-28 Thread Edward Hope-Morley 
** Also affects: neutron (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: cloud-archive
   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/1584647

Title:
  "Interface monitor is not active" can be observed at ovs-agent start

Status in Ubuntu Cloud Archive:
  New
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  New

Bug description:
  I noticed this error message in neutron-ovs-agent log when start
  neutron-openvswitch-agent

  ERROR neutron.agent.linux.ovsdb_monitor [req-a7c7a398-a13b-490e-
  adf8-c5afb24b4b9c None None] Interface monitor is not active.

  ovs-agent will start ovsdb_monitor at [1], and first use it at [2].
  There is no guarantee that ovsdb_monitor is ready at [2]. So, I can
  see the error when start neutron-openvswitch-agent.

  We should block the start to wait for the process to be active, and
  then use it. Or else, the use of ovsdb_monitor will be meaningless.


  [1]
  
https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/agent/linux/polling.py#L35

  [2]
  
https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1994

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1584647/+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 1759582] [NEW] (HTTP 500)

2018-03-28 Thread wangthes 
Public bug reported:

错误：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-77e487f6-0b89-4460-b4b5-f3d6d9801cc8)

** 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/1759582

Title:
   (HTTP 500)

Status in OpenStack Compute (nova):
  New

Bug description:
  错误：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-77e487f6-0b89-4460-b4b5-f3d6d9801cc8)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1759582/+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 1759546] [NEW] Unable to retrieve nested resource list from horizon

2018-03-28 Thread Sudheer Kalla 
Public bug reported:

>From Openstack horizon we cannot retrieve nested resource list.

When even stack is created using nested templates then from horizon we
can only get resource list of main template. But from CLI we can
retrieve all the resources information even the ones that are defined in
nested templates using depth attribute available..

I think the same option should be available from horizon and CLI. So
user should be able to get nested resource list, get the information
about nested resource.

** 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/1759546

Title:
  Unable to retrieve nested resource list from horizon

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  From Openstack horizon we cannot retrieve nested resource list.

  When even stack is created using nested templates then from horizon we
  can only get resource list of main template. But from CLI we can
  retrieve all the resources information even the ones that are defined
  in nested templates using depth attribute available..

  I think the same option should be available from horizon and CLI. So
  user should be able to get nested resource list, get the information
  about nested resource.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1759546/+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 1759510] [NEW] Image import fails with python 3.5, image stuck in uploading state

2018-03-28 Thread Abhishek Kekane 
Public bug reported:

New image import api with glance-direct or web-download fails to import
image if cloud is using python3.5. Image stuck in uploading state
forever.

Steps:
1. Ensure you are running glance on python 3.5
   Add below lines in your devstack/local.conf
   WSGI_MODE=mod_wsgi
   USE_PYTHON3=True
   PYTHON3_VERSION=3.5

2. Source devstack/openrc using "$ source devstack/openrc admin admin"

3. Create image using new import api
   $ glance image-create-via-import --container-format ami --disk-format ami 
--name cirros_image --file 

g-api logs:

Mar 28 08:36:01 ubuntu-3 glance-api[23449]:  |__Flow 'api_image_import': 
TypeError: Unicode-objects must be encoded before hashing
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor Traceback (most recent call last):
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File 
"/usr/local/lib/python3.5/dist-packages/taskflow/engines/action_engine/executor.py",
 line 53, in _execute_task
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor result = task.execute(**arguments)
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File 
"/opt/stack/glance/glance/async/flows/api_image_import.py", line 218, in execute
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor image_import.set_image_data(image, file_path 
or self.uri, self.task_id)
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File 
"/opt/stack/glance/glance/common/scripts/image_import/main.py", line 154, in 
set_image_data
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor "task_id": task_id})
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File 
"/usr/local/lib/python3.5/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor self.force_reraise()
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File 
"/usr/local/lib/python3.5/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor six.reraise(self.type_, self.value, self.tb)
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File 
"/usr/local/lib/python3.5/dist-packages/six.py", line 693, in reraise
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor raise value
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File 
"/opt/stack/glance/glance/common/scripts/image_import/main.py", line 146, in 
set_image_data
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor image.set_data(data_iter)
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File 
"/opt/stack/glance/glance/domain/proxy.py", line 195, in set_data
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor self.base.set_data(data, size)
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File "/opt/stack/glance/glance/notifier.py", 
line 480, in set_data
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor _send_notification(notify_error, 
'image.upload', msg)
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File 
"/usr/local/lib/python3.5/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor self.force_reraise()
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File 
"/usr/local/lib/python3.5/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor six.reraise(self.type_, self.value, self.tb)
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File 
"/usr/local/lib/python3.5/dist-packages/six.py", line 693, in reraise
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor raise value
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File "/opt/stack/glance/glance/notifier.py", 
line 427, in set_data
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor self.repo.set_data(data, size)
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File "/opt/stack/glance/glance/api/policy.py", 
line 193, in set_data
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor return self.image.set_data(*args, **kwargs)
Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR 
glance.async.taskflow_executor   File

[Yahoo-eng-team] [Bug 1756064] Re: neutron agent doesn't remove trunk bridge after nova-compute restart

2018-03-28 Thread Ivan Dyukov 
** No longer affects: nova

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1756064

Title:
  neutron agent doesn't remove trunk bridge after nova-compute restart

Status in neutron:
  Invalid
Status in os-vif:
  New

Bug description:
  env:
  backend is openvswitch with DPDK
  Version is Ocata

  Steps:
  Create two networks.
  Create two ports for each network
  Create trunk port
  boot virtual machine with trunk port
  Restart nova-compute on compute node: #  openstack-service restart 
openstack-nova-compute
  Remove the virtual machine
  Check ovs configuration on compute node: ovs-vsctl show

  Expected result: there is no trunk bridge e.g. tbr-c4ce71ea-7
  Actual result: trunk bridge and services ports are still in ovs 
configuration. e.g.

  Bridge "tbr-c4ce71ea-7"
  Port "spt-63eb23e7-af"
  tag: 102
  Interface "spt-63eb23e7-af"
  type: patch
  options: {peer="spi-63eb23e7-af"}
  Port "tbr-c4ce71ea-7"
  Interface "tbr-c4ce71ea-7"
  type: internal
  Port "tpt-d6c0e47e-ed"
  Interface "tpt-d6c0e47e-ed"
  type: patch
  options: {peer="tpi-d6c0e47e-ed"}

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1756064/+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