[Yahoo-eng-team] [Bug 1507456] Re: default setting of certificate for SAML signing doesn't work

[Dave Chen]

This is not an issue anymore with the latest code base, and the patch
intends to fix that has been abandoned, so mark it as won't fix.

** Changed in: keystone
   Status: In Progress => Won't Fix

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

Title:
  default setting of certificate for SAML signing doesn't work

Status in OpenStack Identity (keystone):
  Won't Fix

Bug description:
  Currently, the default setting is
  '/etc/keystone/ssl/certs/signing_cert.pem' which is the public key
  certificate which contains,

  - Signature Algorithm
  - Public Key
  - Signature Algorithm
  - Subject

  etc.

  But sigver.read_cert_from_file expects the certificate's content
  holds plain certificate information, which means it 's start from
  -BEGIN CERTIFICATE-
  or
  -BEGIN PUBLIC KEY-

  and end with

  -END CERTIFICATE-
  or
  -END PUBLIC KEY-

  So, the default setting will not work for SAML signing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1507456/+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 1625334] Re: Update port with subnet_id in fixed_ips allocates a new IP when existing one could be used.

[OpenStack Infra]

Reviewed:  https://review.openstack.org/372794
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=14fee9cfcc816128606fc11d33800af90a0b1859
Submitter: Jenkins
Branch:master

commit 14fee9cfcc816128606fc11d33800af90a0b1859
Author: Carl Baldwin 
Date:   Mon Sep 12 15:31:08 2016 -0600

Try to reuse existing IPs when a port update specifies subnet

If a port update specifies only a subnet_id for a fixed_ip then we
want to look at existing fixed_ips to see if that subnet_id is already
there. This avoids allocating a new IP address on the subnet and
deallocating the old one.

Without some special care, this breaks the code path for prefix
delegation. One could argue that PD needs reworking. However, as a
stop-gap measure, we still run the old code path if the address is an
EUI-64 address. This allows PD to continue to work as it was
originally written and it doesn't do any harm because allocating
EUI-64 addresses is repeatable.

This commit removes a test case from the DNS integration tests. The
test was specifically testing that DNS records we updated in the case
where a subnet id was passed to re-allocate a fixed_ip. Since the use
case no longer works, the test doesn't make sense.

This commit also preserves the ability to add an additional IP from a
subnet for which the port already has IPs.

Change-Id: Iba5d54efa7f99ed82275ffc8e5be975b373c29d3
Related-Bug: #1622616
Closes-Bug: #1625334


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

Title:
  Update port with subnet_id in fixed_ips allocates a new IP when
  existing one could be used.

Status in neutron:
  Fix Released

Bug description:
  This issue has been seen twice causing this related bug [1]. What
  happens is the DHCP agent updates the port using the subnet_id but not
  the actual ip_address that the port already has. So, the server
  allocates a new IP address and throws out the old one.

  What it should do is recognize that there is already an IP address on
  the port that satisfies the request and avoid the churn.

  A previous attempt was made [1] to address this bug but was reverted
  because it had a side effect [3].  Need a fix that addresses this
  issue without the side-effect.

  [1] https://bugs.launchpad.net/neutron/+bug/1622616/
  [2] https://review.openstack.org/#/c/369051/
  [3] https://bugs.launchpad.net/neutron/+bug/1623800

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1625334/+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 1615676] Re: os-vif log messages corrupt and pollute test output

[OpenStack Infra]

Reviewed:  https://review.openstack.org/374233
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=735f710ae0c0e0037970796beacd3527e2a8ca8a
Submitter: Jenkins
Branch:master

commit 735f710ae0c0e0037970796beacd3527e2a8ca8a
Author: Sean Dague 
Date:   Wed Sep 21 11:11:21 2016 -0400

move os_vif.initialize() to nova-compute start

os_vif.initialize() was previously executed during module load. This
means it was entirely possible that it was run before things like
logging were actually set up in the expected way. Move this back into
execution time instead of load time to ensure that logging is actually
setup.

Changes need to be made to tests which make assumptions about os_vif
objects to manually initialize os_vif when it will be used. os_vif
objects can't be created until it is initialized, so some delayed
object creation is also done in test_vif.py.

Closes-Bug: #1615676

Change-Id: I89fe5c5b3d762f3a3238b587685df85d15ee56c4


** Changed in: nova
   Status: In Progress => 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/1615676

Title:
  os-vif log messages corrupt and pollute test output

Status in OpenStack Compute (nova):
  Fix Released
Status in os-vif:
  In Progress

Bug description:
  When running unit tests with tox, os-vif logging pollutes the output
  of the testr runner and on multi-core machines, nearly always corrupts
  the output stream like so:

  http://paste.openstack.org/show/562213/

  os-vif logging setup should be examined to ensure it is being
  processed like all other modules that behave properly with testr.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1615676/+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 1608475] Re: Live Migration Error on Mitaka release

[Surya Rudra]

** Changed in: horizon
 Assignee: (unassigned) => Surya Rudra (rudrasurya)

** Project changed: horizon => neutron

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

Title:
  Live Migration Error on Mitaka release

Status in neutron:
  New

Bug description:
  While Live Migrating from one compute node to another compute node in
  Mitaka release, the operation returns SUCCESS but the host system
  remains same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1608475/+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 1625220] Re: get_function_by_ifname does not return true for physical function

[OpenStack Infra]

Reviewed:  https://review.openstack.org/372558
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=859de9c9971a3dd13f245d2245686fb3d19a832d
Submitter: Jenkins
Branch:master

commit 859de9c9971a3dd13f245d2245686fb3d19a832d
Author: Edan David 
Date:   Mon Sep 19 10:48:55 2016 -0400

Add missing slash to dir path

When validating a PF in the method 'get_function_by_ifname'
the number of VFs are read from a file,
the path to that file was missing a slash ('/').

Change-Id: I7bf4bb96f1f769bff247f5af2c81dd96b08e2f04
Closes-Bug: #1625220


** Changed in: nova
   Status: In Progress => 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/1625220

Title:
  get_function_by_ifname does not return true for physical function

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Due to a missing slash ('/') in the 'get_function_by_ifname' method 
(pci/utils),
  an incorrect path was passed to read the number of VFs and determine if the 
device is a PF or not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1625220/+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 1626489] [NEW] placement api 404 errors are logged poorly

[Chris Dent]

Public bug reported:

In version 1.0 of the placement API, 404 errors are logged at level
ERROR with a traceback:

```
2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
[req-8da084c1-467d-488c-941b-af73e18e086d admin admin] Uncaught exception
2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
Traceback (most recent call last):
2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler   File 
"/opt/stack/nova/nova/api/openstack/placement/handler.py", line 171, in __call__
2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
return dispatch(environ, start_response, self._map)
2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler   File 
"/opt/stack/nova/nova/api/openstack/placement/handler.py", line 94, in dispatch
2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
json_formatter=util.json_error_formatter)
2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
HTTPNotFound: The resource could not be found.
2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
```

This is then immediately followed by an INFO which provides most of
what's needed to analyse why a 404 is a 404:

```
2016-09-22 10:37:20.034 22918 INFO nova.api.openstack.placement.requestlog 
[req-8da084c1-467d-488c-941b-af73e18e086d admin admin] 10.0.2.15 " GET 
/placement" status: 404 len: 52
```

(note this particular 404 represents a bug in the service ('' and '/'
path info should be treated the same), which will be reported in another
bug)

First off, a 404 should probably not be logged as an error if we are
assuming this is an api that people will be making diverse queries
against. However, if we are choosing to log a traceback the not found
message should include more information. The reason, at the moment, that
there's not much there is that the placement handlers allow a NotFound
from the objects in nova/objects/resource_providers.py to rise without
being modified (until an outer layer), and those NotFound are bare: they
include no messages about what was NotFound as it was assumed the
calling context would know.

What should probably happen here is that in the api handler code those
places where a NotFound could happen, they should be caught, a debug log
message made, and the NotFound transformed into more verbose
webob.exc.HTTPNotFound at that layer, not the higher layer.

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: api placement scheduler

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

Title:
  placement api 404 errors are logged poorly

Status in OpenStack Compute (nova):
  New

Bug description:
  In version 1.0 of the placement API, 404 errors are logged at level
  ERROR with a traceback:

  ```
  2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
[req-8da084c1-467d-488c-941b-af73e18e086d admin admin] Uncaught exception
  2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
Traceback (most recent call last):
  2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler   
File "/opt/stack/nova/nova/api/openstack/placement/handler.py", line 171, in 
__call__
  2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
return dispatch(environ, start_response, self._map)
  2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler   
File "/opt/stack/nova/nova/api/openstack/placement/handler.py", line 94, in 
dispatch
  2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
json_formatter=util.json_error_formatter)
  2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
HTTPNotFound: The resource could not be found.
  2016-09-22 10:37:20.033 22918 ERROR nova.api.openstack.placement.handler 
  ```

  This is then immediately followed by an INFO which provides most of
  what's needed to analyse why a 404 is a 404:

  ```
  2016-09-22 10:37:20.034 22918 INFO nova.api.openstack.placement.requestlog 
[req-8da084c1-467d-488c-941b-af73e18e086d admin admin] 10.0.2.15 " GET 
/placement" status: 404 len: 52
  ```

  (note this particular 404 represents a bug in the service ('' and '/'
  path info should be treated the same), which will be reported in
  another bug)

  First off, a 404 should probably not be logged as an error if we are
  assuming this is an api that people will be making diverse queries
  against. However, if we are choosing to log a traceback the not found
  message should include more information. The reason, at the moment,
  that there's not much there is that the placement handlers allow a
  NotFound from the objects in nova/objects/resource_providers.py to
  rise without being modified (until an outer layer), and those NotFound
  are bare: they include no messa

[Yahoo-eng-team] [Bug 1626490] [NEW] placement api root resource is only '/' not '' which can lead to unexpected 404s

[Chris Dent]

Public bug reported:

The placement api handler for root is defined as matching '/'. This
works fine in those situations where the requested URL actually includes
the '/' but in some situations it can be easy to not include it. If, for
example, the API is mounted under a prefix like '/placement' (as in the
default devstack setup) then it is possible to make a request to
http://example.com/placement and get a 404 whereas
http://example.com/placement/ will get the expected microversion
information.

This ought to be easy to fix and was basically an oversight.

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: api placement scheduler

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

Title:
  placement api root resource is only '/' not '' which can lead to
  unexpected 404s

Status in OpenStack Compute (nova):
  New

Bug description:
  The placement api handler for root is defined as matching '/'. This
  works fine in those situations where the requested URL actually
  includes the '/' but in some situations it can be easy to not include
  it. If, for example, the API is mounted under a prefix like
  '/placement' (as in the default devstack setup) then it is possible to
  make a request to http://example.com/placement and get a 404 whereas
  http://example.com/placement/ will get the expected microversion
  information.

  This ought to be easy to fix and was basically an oversight.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1626490/+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 1626493] [NEW] placement api log entries have mismatched request ids

[Chris Dent]

Public bug reported:

The placement (v 1.0) API's service logs get confused about request id.
The following is one request:

```
2016-09-22 10:54:54.372 22919 DEBUG nova.api.openstack.placement.requestlog 
[req-93669abf-57c5-4415-a734-1affc816a9ae admin admin] Starting request: 
10.0.2.15 "GET /placement/resource_providers/fastidious" __call__ 
/opt/stack/nova/nova/api/openstack/placement/requestlog.py:36
2016-09-22 10:54:54.414 22919 INFO nova.api.openstack.placement.requestlog 
[req-7312f440-2c66-4483-a514-eaf3602b50e6 admin admin] 10.0.2.15 "GET 
/placement/resource_providers/fastidious" status: 404 len: 80
```

This is probably because the request id middleware is not being called
first.

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

Title:
  placement api log entries have mismatched request ids

Status in OpenStack Compute (nova):
  New

Bug description:
  The placement (v 1.0) API's service logs get confused about request
  id. The following is one request:

  ```
  2016-09-22 10:54:54.372 22919 DEBUG nova.api.openstack.placement.requestlog 
[req-93669abf-57c5-4415-a734-1affc816a9ae admin admin] Starting request: 
10.0.2.15 "GET /placement/resource_providers/fastidious" __call__ 
/opt/stack/nova/nova/api/openstack/placement/requestlog.py:36
  2016-09-22 10:54:54.414 22919 INFO nova.api.openstack.placement.requestlog 
[req-7312f440-2c66-4483-a514-eaf3602b50e6 admin admin] 10.0.2.15 "GET 
/placement/resource_providers/fastidious" status: 404 len: 80
  ```

  This is probably because the request id middleware is not being called
  first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1626493/+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 1626496] [NEW] when placement API sends a 405 the header value is in the incorrect format

[Chris Dent]

Public bug reported:

When the placement handlers raise an HTTPMethodNotAllowed response, the
headers are set with those methods that are allowed. These need to be
not unicode (it's not clear how they get to be unicode (in 2.7) in the
first place, but something is doing it, and that's not right) otherwise
we get:

```
2016-09-22 11:03:01.875 22919 ERROR nova.api.openstack.placement.handler 
HTTPMethodNotAllowed: The method specified is not allowed for this resource.
2016-09-22 11:03:01.875 22919 ERROR nova.api.openstack.placement.handler 
2016-09-22 11:03:01.877 22919 INFO nova.api.openstack.placement.requestlog 
[req-524fdd42-0f19-4eb3-827f-99ae22fc6dd9 admin admin] 10.0.2.15 "DELETE 
/placement/resource_providers" status: 405 len: 133
mod_wsgi (pid=22919): Exception occurred processing WSGI script 
'/usr/local/bin/nova-placement-api'.
TypeError: expected byte string object for header value, value of type unicode 
found
```

wherein the service correctly tries to send a 405 but then the mod_wsgi
server blows up on the data it is getting.

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: api placement scheduler

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

Title:
  when placement API sends a 405 the header value is in the incorrect
  format

Status in OpenStack Compute (nova):
  New

Bug description:
  When the placement handlers raise an HTTPMethodNotAllowed response,
  the headers are set with those methods that are allowed. These need to
  be not unicode (it's not clear how they get to be unicode (in 2.7) in
  the first place, but something is doing it, and that's not right)
  otherwise we get:

  ```
  2016-09-22 11:03:01.875 22919 ERROR nova.api.openstack.placement.handler 
HTTPMethodNotAllowed: The method specified is not allowed for this resource.
  2016-09-22 11:03:01.875 22919 ERROR nova.api.openstack.placement.handler 
  2016-09-22 11:03:01.877 22919 INFO nova.api.openstack.placement.requestlog 
[req-524fdd42-0f19-4eb3-827f-99ae22fc6dd9 admin admin] 10.0.2.15 "DELETE 
/placement/resource_providers" status: 405 len: 133
  mod_wsgi (pid=22919): Exception occurred processing WSGI script 
'/usr/local/bin/nova-placement-api'.
  TypeError: expected byte string object for header value, value of type 
unicode found
  ```

  wherein the service correctly tries to send a 405 but then the
  mod_wsgi server blows up on the data it is getting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1626496/+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 1625135] Re: removing all subports from trunk leaves trunk in DOWN status with openvswitch driver

[OpenStack Infra]

Reviewed:  https://review.openstack.org/372750
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=4371ae010a7888220bb67ca9bd423e54c0239fd4
Submitter: Jenkins
Branch:master

commit 4371ae010a7888220bb67ca9bd423e54c0239fd4
Author: Armando Migliaccio 
Date:   Mon Sep 19 13:27:30 2016 -0700

Ensure trunk status is acknowledged during OVS subport operations

Before this patch, change to trunk status was reported only when
subports were being added, but not when being removed. This patch
tweak things to make sure the same happens on subports removal.

This patch also improves unit coverage for the parts of the code
affected. In particular the import of oslo_context has been aliased
to catch errors where context as variable is shadowed by the homonym
module.

Closes-bug: #1625135

Change-Id: I73127d7829c31ca66578eb8f7d76409b36c9dc6d


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

Title:
  removing all subports from trunk leaves trunk in DOWN status with
  openvswitch driver

Status in neutron:
  Fix Released

Bug description:
  Removing all of the subports from a trunk leaves it in the DOWN status
  rather than it transitioning back to ACTIVE after finishing the wiring
  as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1625135/+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 1625875] Re: OVS metadata for trunk ports are not handled correctly

[OpenStack Infra]

Reviewed:  https://review.openstack.org/373600
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=29457631ad0b77b06dee40cb5114f5f4aced129a
Submitter: Jenkins
Branch:master

commit 29457631ad0b77b06dee40cb5114f5f4aced129a
Author: Armando Migliaccio 
Date:   Tue Sep 20 19:34:32 2016 -0700

Update trunk metadata during wire/unwire operations

Before this patch metadata on the OVS trunk bridge were
not updated during unwiring operations and upon subsequent
wire operations old subports were getting wiped from the
external_ids field of the OVS parent port. This could lead
to OVS ports left behind on the host on trunk removal.

This patch ensures that the subports stored as metadata
reflect the logical state of the trunk.

Closes-bug: #1625875

Change-Id: I9d885b10d84fad43c527d3ca7bc9a37439197fc9


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

Title:
  OVS metadata for trunk ports are not handled correctly

Status in neutron:
  Fix Released

Bug description:
  Caught during code review, there's issue when we add/remove subports. This 
makes the use of metadata totally unreliable. The error may lead to stale
  OVS ports on the host when the trunk is removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1625875/+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 1490984] Re: instance binded floating ip cannot ping external gateway, bug i can ping the other pc in external network

[greatbsky]

mitaka has no problems, so fixed

** Changed in: neutron
   Status: Incomplete => 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/1490984

Title:
  instance binded floating ip cannot ping external gateway, bug i can
  ping the other pc in external network

Status in neutron:
  Fix Released

Bug description:
  
  instance(192.168.100.0/24) binded floating ip cannot ping external 
gateway(192.168.1.1), if I disassociate floating ip I can ping the 
gateway(192.168.1.1).

  I deploy openstack all in one physical compute following the guide:
  http://docs.openstack.org/kilo/install-
  guide/install/yum/content/ch_networking.html

  nova install in compute1 and compute1 as the hypervisor.
  [root@compute1 ~]# virsh list
   IdName   State
  
   5 IaaS_openstack_controller_centos7.0 running
   6 IaaS_openstack_network_centos7.0 running
   7 IaaS_openstack_block1_centos7.0 running
   38instance-000f  running
   39instance-000e  running

  neutron has been installed in IaaS_openstack_network_centos7.0

  
  --init the neutron network:
  [root@controller keystone]# neutron net-create ext-net --router:external 
--provider:physical_network external --provider:network_type flat
  [root@controller keystone]# neutron subnet-create ext-net 192.168.1.0/24 
--name ext-subnet --allocation-pool start=192.168.1.240,end=192.168.1.250 
--disable-dhcp --gateway 192.168.1.1
  [root@controller keystone]# neutron net-create demo-net
  [root@controller keystone]# neutron subnet-create demo-net 192.168.100.0/24 
--name demo-subnet --gateway 192.168.100.1
  [root@controller keystone]# neutron router-create demo-router
  [root@controller keystone]# neutron router-interface-add demo-router 
demo-subnetc
  [root@controller keystone]# neutron router-gateway-set demo-router ext-net

  
  --@network
  [root@network ~]# neutron agent-list
  
+--+++---++---+
  | id   | agent_type | host   | 
alive | admin_state_up | binary|
  
+--+++---++---+
  | 0923f4c3-8f0a-4468-b239-07942c32 | L3 agent   | compute1   | 
xxx   | True   | neutron-l3-agent  |
  | 1ce168ed-4d96-4c41-8bbd-6a9da22b3d24 | DHCP agent | controller | 
xxx   | True   | neutron-dhcp-agent|
  | 276d38c8-d2b7-4799-b1ee-849738a1dd44 | Metadata agent | compute1   | 
xxx   | True   | neutron-metadata-agent|
  | 565ed14a-bfde-4258-9df3-9a7819394410 | Metadata agent | network| 
:-)   | True   | neutron-metadata-agent|
  | a8cfbb25-7323-4e6a-b29f-8c16c0e6e5ef | DHCP agent | compute1   | 
xxx   | True   | neutron-dhcp-agent|
  | bd81321b-888c-42ca-bf40-fe921f19a23c | DHCP agent | network| 
:-)   | True   | neutron-dhcp-agent|
  | c7313ecd-0715-4a62-9b4c-19f1c4f364fc | Open vSwitch agent | compute1   | 
:-)   | True   | neutron-openvswitch-agent |
  | cdf31fd6-143d-4104-8b75-e378da2b11fd | L3 agent   | network| 
:-)   | True   | neutron-l3-agent  |
  | ee2821f0-57f7-4cb0-85d4-a34a203ddb57 | Metadata agent | controller | 
xxx   | True   | neutron-metadata-agent|
  | f47e9e85-b7ee-4dcf-979a-7353c1e5b4b5 | Open vSwitch agent | network| 
:-)   | True   | neutron-openvswitch-agent |
  
+--+++---++---+
  [root@network ~]# ip netns list
  qrouter-f40f72af-a964-4fc4-9d6e-2912d3666870
  qdhcp-c2ba1db5-1ce2-4e35-8ac5-31691b930156
  [root@network ~]# ip net exec qrouter-f40f72af-a964-4fc4-9d6e-2912d3666870 ip 
a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  10: qr-346be01a-09:  mtu 1500 qdisc 
noqueue state UNKNOWN
  link/ether fa:16:3e:f8:d1:e7 brd ff:ff:ff:ff:ff:ff
  inet 192.168.100.1/24 brd 192.168.100.255 scope global qr-346be01a-09
 valid_lft forever preferred_lft forever
  inet6 fe80::f816:3eff:fef8:d1e7/64 scope link
 valid_lft forever preferred_lft forever
  11: qg-46e0fef7-b7:  mtu 1500 qdisc 
noqueue state UNKNOWN
  link/ether fa:16:3e:4a:87:c3 brd ff:ff:ff:ff:ff:ff
  inet 192.168.1.240/24 brd 192.168.1.255 scope global qg-46e0fef7-b7
 valid_lft fore

[Yahoo-eng-team] [Bug 1625639] Re: Wrong message on LB floating IP disassociation

[OpenStack Infra]

Reviewed:  https://review.openstack.org/373351
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=d99444b87bbc5af2e842bce03f513374ebfe2621
Submitter: Jenkins
Branch:master

commit d99444b87bbc5af2e842bce03f513374ebfe2621
Author: Guillaume Espanel 
Date:   Tue Sep 20 15:58:11 2016 +0200

Display the right floating ip on LB disassociation

The RemoveVIPFloatingIP.single method was deleting a floating IP and
then displayed a message about another floating IP.

Change-Id: Ic6078299ddb34550c002218aad28d05907827b01
Closes-bug: #1625639


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

Title:
  Wrong message on LB floating IP disassociation

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Issue
  =

  When disassociating a floating IP from a load balancer VIP,
  the displayed message indicates that another floating IP
  has been disassociated.

  Steps to reproduce
  ==

   - Create 2 LB
   - Create 2 VIP
   - Associate a floating IP to both the VIPs
   - Disassociate one of the floating IP from the VIPs

  Expected behavior
  =

  The message displayed that the selected floating IP has been
  disassociated.

  Actual behavior
  ===

  The displayed message indicates that another floating IP has been
  disassociated.

  Version
  ===

  mitaka/stable

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1625639/+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 1596692] Re: NUMATopologyFilter filters out a compute from candidates for booting a VM with 'hw:cpu_thread_policy=require' unless cores from all NUMA nodes are enabled in vcpu_pi

[OpenStack Infra]

Reviewed:  https://review.openstack.org/334659
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=1c04e18ec922b6a6f6de6734fbceb0eed336f2ee
Submitter: Jenkins
Branch:master

commit 1c04e18ec922b6a6f6de6734fbceb0eed336f2ee
Author: Mikhail Chernik 
Date:   Mon Jun 27 22:04:46 2016 +0200

Fix require thread policy for multi-NUMA computes

CPU thread policy "require" demands that instances are created on hosts
with hardware threads, e.g HyperThreading. It is possible that a compute
has several NUMA nodes, but only some of them contribute to the list of
pinned CPUs. In this case NUMATopologyFiler will exclude the compute
from candidates even if hardware threads are enabled and cores from
other NUMA nodes are available for CPU pinning.

This commit allows a compute with enabled HyperThreading to pass
NUMATopologyFilter if at least one NUMA node contributes to the list of
cores allowed for CPU pinning.

Change-Id: I3235cc6bf1a2a9e29a17acc43472e2a6bd4c26ec
Closes-Bug: 1596692


** Changed in: nova
   Status: In Progress => 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/1596692

Title:
  NUMATopologyFilter filters out a compute from candidates for booting a
  VM with  'hw:cpu_thread_policy=require' unless cores from all NUMA
  nodes are enabled in vcpu_pin_set on the compute

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  The 'require' CPU thread policy allows booting instances on hardware
  threads siblings only. However, if a compute host has several NUMA
  nodes and at least one NUMA node does not contribute to a list of
  pinned CPU cores, NUMATopologyFilter excludes such node from possible
  targets to an instance.

  Steps to reproduce:

  1) On a compute with several NUMA nodes vcpu_pin_set key of nova.conf
  does not contain sibling thread cores from one NUMA node (e.g. they
  are allocated for OVS with DPDK support)

  ex: vcpu_pin_set=0,1,20,21

  List of cores on a NUMA node can be obtained with lstopo or numactl -H 
command: 
  # numactl -H
  available: 4 nodes (0-3)
  node 0 cpus: 0 1 2 3 4 20 21 22 23 24
  node 0 size: 64328 MB
  node 0 free: 21952 MB
  node 1 cpus: 5 6 7 8 9 25 26 27 28 29
  node 1 size: 64510 MB
  node 1 free: 30091 MB

  Sibling cores can be found with # cat
  /sys/bus/cpu/devices/cpu*/topology/thread_siblings_list command

  # cat /sys/bus/cpu/devices/cpu{0,1}/topology/thread_siblings_list 
  0,20
  1,21

  2) Create corresponding flavor

  # openstack flavor create pinned.threads_require --ram 2048 --disk 0 --vcpus 2
  # openstack flavor set pinned.threads_require --property 
"hw:cpu_thread_policy=require" --property "hw:cpu_policy=dedicated"

  3) Boot an instance with created flavor
  # openstack server create --flavor pinned.threads_require --image cirros vm1

  4) List instances:
  # openstack server list

  Expected result: 
  Instance vm1 is booted

  Actiual result:
  Instance vm1 is in ERROR state with message 'No valid host was found. There 
are not enough hosts available.' (assuming there are no other computes with 
sibling thread cores available)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1596692/+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 1620748] Re: In placement when an attempt is made to write to missing inventory the error message is ugly

[OpenStack Infra]

Reviewed:  https://review.openstack.org/373380
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=995d283e4f9a6a0cbf44f840c643d7dd99212f82
Submitter: Jenkins
Branch:master

commit 995d283e4f9a6a0cbf44f840c643d7dd99212f82
Author: Chris Dent 
Date:   Tue Sep 20 14:36:37 2016 +

[placement] Stringify class and provider uuid in error

When attempting to make an allocation of a particular class of
resource against a resource provider which has no inventory for that
class, an InvalidInventory exception is raised. This was workign
okay but the associated message was displaying stringified sets
of resource class ids, and not the resource classes names.

This changes joins the sets into strings for both resource classes
and provider uuids and turns the class indexes into their names.
A functional test which was checking for the exception has been
updated to also check the exception's message.

Change-Id: Ife38220da1069ffb6da26a4f8e3b954f0dc12f13
Closes-Bug: #1620748


** Changed in: nova
   Status: In Progress => 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/1620748

Title:
  In placement when an attempt is made to write to missing inventory the
  error message is ugly

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  The error message from the exception is:

  Inventory for 'set([0, 2])' on resource provider 'set(['a7774b97
  -838c-4b36-9cda-cfe6cbba0f0f'])' invalid

  This is because the data given to the exception has not been
  stringified from sets nor turned from resource class ids to resource
  class strings. Change needed near here:

  
https://github.com/openstack/nova/blob/985c7ca4dc15176dc9cccf0ebcabaa18ea98ca2a/nova/objects/resource_provider.py#L715

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1620748/+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 1626521] [NEW] Host aggregate name is not displaying in success message while creating it

[SREELAKSHMI PENTA]

Public bug reported:


Reproduced in master.
Steps to reproduce
1. Go to Admin/System/Host Aggregates
2. Create Host aggregate.

Actual result:
Displaying host aggregate name as Success: Created new host aggregate "Create 
Host Aggregate".

Expected Result:
Success: Created new host aggregate "".

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

Title:
  Host aggregate name is not displaying in success message while
  creating it

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  
  Reproduced in master.
  Steps to reproduce
  1. Go to Admin/System/Host Aggregates
  2. Create Host aggregate.

  Actual result:
  Displaying host aggregate name as Success: Created new host aggregate "Create 
Host Aggregate".

  Expected Result:
  Success: Created new host aggregate "".

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1626521/+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 1625818] Re: FWaaS v2 does not handle _interfaces not present in updated router gracefully

[Armando Migliaccio]

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

Title:
  FWaaS v2 does not handle _interfaces not present in updated router
  gracefully

Status in neutron:
  Fix Released

Bug description:
  When updated router info comes in to firewall_l3_agent_v2.py without
  the _interfaces field set, the code does not gracefully detect this
  and skip the update.  This was picked up in tempest testing after the
  RC cutoff.  The fix for master is under review; the fix needs to be
  backported to stable/neutron.  Fix in master is:
  https://review.openstack.org/#/c/371611

  I found an example of an updated router that does not have _interfaces as an 
attribute at [1]:
  2016-09-15 19:37:08.356 21040 ERROR 
neutron_fwaas.services.firewall.agents.l3reference.firewall_l3_agent_v2 
[req-b3e3ccbc-92ea-4c8e-8196-2987ecdd0195 - -] FWaaS router update RPC info 
call failed for {u'enable_snat': True, u'gw_port': {u'allowed_address_pairs': 
[], u'extra_dhcp_opts': [], u'updated_at': u'2016-09-15T19:36:31', 
u'device_owner': u'network:router_gateway', u'revision_number': 7, 
u'port_security_enabled': False, u'binding:profile': {}, u'binding:vnic_type': 
u'normal', u'fixed_ips': [{u'subnet_id': 
u'b27366c2-987c-4f6c-85a6-4fa329392ade', u'prefixlen': 24, u'ip_address': 
u'172.24.5.11'}, {u'subnet_id': u'71583438-8240-4bc1-a12f-3fc28087dff3', 
u'prefixlen': 64, u'ip_address': u'2001:db8::6'}], u'id': 
u'38a74555-f603-4287-9667-c13a7bcb8779', u'security_groups': [], 
u'binding:vif_details': {u'port_filter': True, u'ovs_hybrid_plug': True}, 
u'address_scopes': {u'4': None, u'6': None}, u'binding:vif_type': u'ovs', 
u'mac_address': u'fa:16:3e:5f:69:e7', u'project_id': u'', u'st
 atus': u'ACTIVE', u'subnets': [{u'dns_nameservers': [], u'ipv6_ra_mode': None, 
u'gateway_ip': u'2001:db8::2', u'cidr': u'2001:db8::/64', u'id': 
u'71583438-8240-4bc1-a12f-3fc28087dff3', u'subnetpool_id': None}, 
{u'dns_nameservers': [], u'ipv6_ra_mode': None, u'gateway_ip': u'172.24.5.1', 
u'cidr': u'172.24.5.0/24', u'id': u'b27366c2-987c-4f6c-85a6-4fa329392ade', 
u'subnetpool_id': None}], u'binding:host_id': u'ubuntu-trusty-rax-ord-4320605', 
u'description': u'', u'device_id': u'bcb45377-b7b2-4186-98dd-58e77a9b75e3', 
u'name': u'', u'admin_state_up': True, u'network_id': 
u'16004da0-37c9-4481-b769-0706b581d9e9', u'tenant_id': u'', u'created_at': 
u'2016-09-15T19:36:29', u'mtu': 1500, u'extra_subnets': []}, u'updated_at': 
u'2016-09-15T19:37:07', u'revision_number': 7, u'id': 
u'bcb45377-b7b2-4186-98dd-58e77a9b75e3', u'availability_zone_hints': [], 
u'availability_zones': [u'nova'], u'distributed': False, u'project_id': 
u'750d1d0452334b93815857b6b9bc9190', u'status': u'ACTIVE', u'ha_vr_id': 0,
  u'description': u'', u'ha': False, u'gw_port_host': 
u'ubuntu-trusty-rax-ord-4320605', u'external_gateway_info': {u'network_id': 
u'16004da0-37c9-4481-b769-0706b581d9e9', u'enable_snat': True, 
u'external_fixed_ips': [{u'subnet_id': u'b27366c2-987c-4f6c-85a6-4fa329392ade', 
u'ip_address': u'172.24.5.11'}, {u'subnet_id': 
u'71583438-8240-4bc1-a12f-3fc28087dff3', u'ip_address': u'2001:db8::6'}]}, 
u'name': u'tempest-router-smoke-1843134667', u'gw_port_id': 
u'38a74555-f603-4287-9667-c13a7bcb8779', u'admin_state_up': True, u'tenant_id': 
u'750d1d0452334b93815857b6b9bc9190', u'created_at': u'2016-09-15T19:36:28', 
u'flavor_id': None, u'routes': []}
  [1] 
http://logs.openstack.org/74/370274/11/check/gate-neutron-fwaas-dsvm-tempest/0768c92/logs/screen-q-l3.txt.gz#_2016-09-15_19_37_08_356

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1625818/+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 1626277] Re: DB migration tests are timing out

[OpenStack Infra]

Reviewed:  https://review.openstack.org/374390
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=97301049958522cf91527d48172f4af9c2645c2d
Submitter: Jenkins
Branch:master

commit 97301049958522cf91527d48172f4af9c2645c2d
Author: Henry Gessau 
Date:   Wed Sep 21 16:57:21 2016 -0400

Allow more time for DB migration tests

Adopt the timeout override fixture from nova.

Borrowed from I591f3c270804dfb01eab7c8c5d43b87a7abcdeda
Co-Authored-By: Sean Dague 

Closes-Bug: #1626277

Change-Id: I0b40ce97ba42d55f048e9728d9f032ada5c85100


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

Title:
  DB migration tests are timing out

Status in neutron:
  Fix Released

Bug description:
  Tests involving database migrations are timing out.
  This may be related to 
http://lists.openstack.org/pipermail/openstack-dev/2016-September/103664.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1626277/+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 1626534] [NEW] request unsupport method to Placement API 500 returned

[Alex Xu]

Public bug reported:

I get 500 return as below:

curl -g -i -X DELETE http://hp-pc:8778/placement/resource_providers -H
"User-Agent: python-novaclient" -H "Accept: application/json" -H "X
-Auth-Token: 79768b74827c40aebbcbf8c91e89e6cf"


HTTP/1.1 500 Internal Server Error
Date: Thu, 22 Sep 2016 12:54:10 GMT
Server: Apache/2.4.18 (Ubuntu)
Content-Length: 604
Connection: close
Content-Type: text/html; charset=iso-8859-1



500 Internal Server Error

Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator at
 [no address given] to inform them of the time this error occurred,
 and the actions you performed just before this error.
More information about this error may be available
in the server error log.

Apache/2.4.18 (Ubuntu) Server at hp-pc Port 8778



The error message get from server side:

2016-09-22 20:54:10.453 DEBUG nova.api.openstack.placement.requestlog 
[req-a70ddef7-745c-4fe6-84b6-e33f28b34af2 placement service] Starting request: 
127.0.0.1 "DELETE /placement/resource_providers" from (pid=23252) __call__ 
/opt/stack/nova/nova/api/openstack/placement/requestlog.py:36
2016-09-22 20:54:10.638 ERROR nova.api.openstack.placement.handler 
[req-dbf43944-b6b6-4931-8754-b5d11bfe3974 admin admin] Uncaught exception
2016-09-22 20:54:10.638 TRACE nova.api.openstack.placement.handler Traceback 
(most recent call last):
2016-09-22 20:54:10.638 TRACE nova.api.openstack.placement.handler   File 
"/opt/stack/nova/nova/api/openstack/placement/handler.py", line 171, in __call__
2016-09-22 20:54:10.638 TRACE nova.api.openstack.placement.handler try:
2016-09-22 20:54:10.638 TRACE nova.api.openstack.placement.handler   File 
"/opt/stack/nova/nova/api/openstack/placement/handler.py", line 98, in dispatch
2016-09-22 20:54:10.638 TRACE nova.api.openstack.placement.handler return 
handler(environ, start_response)
2016-09-22 20:54:10.638 TRACE nova.api.openstack.placement.handler   File 
"/opt/stack/nova/nova/api/openstack/placement/handler.py", line 113, in 
handle_405
2016-09-22 20:54:10.638 TRACE nova.api.openstack.placement.handler _('The 
method specified is not allowed for this resource.'),
2016-09-22 20:54:10.638 TRACE nova.api.openstack.placement.handler 
HTTPMethodNotAllowed: The method specified is not allowed for this resource.
2016-09-22 20:54:10.638 TRACE nova.api.openstack.placement.handler
2016-09-22 20:54:10.639 INFO nova.api.openstack.placement.requestlog 
[req-dbf43944-b6b6-4931-8754-b5d11bfe3974 admin admin] 127.0.0.1 "DELETE 
/placement/resource_providers" status: 405 len: 243
mod_wsgi (pid=23252): Exception occurred processing WSGI script 
'/usr/local/bin/nova-placement-api'.
Traceback (most recent call last):
  File "/opt/stack/nova/nova/api/openstack/placement/requestlog.py", line 38, 
in __call__
return self._log_app(environ, start_response)
  File "/opt/stack/nova/nova/api/openstack/placement/requestlog.py", line 64, 
in _log_app
return self.application(environ, replacement_start_response)
  File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in 
__call__
return resp(environ, start_response)
  File "/usr/local/lib/python2.7/dist-packages/webob/response.py", line 1037, 
in __call__
start_response(self.status, headerlist)
  File "/opt/stack/nova/nova/api/openstack/placement/requestlog.py", line 62, 
in replacement_start_response
return start_response(status, headers, exc_info)
TypeError: expected byte string object, value of type unicode found


This is due to the we have unicode in the response headers, in this case
the allow headers is unicode.

This is same as
https://groups.google.com/forum/?fromgroups=#!topic/modwsgi/HvD3TJbUkTc

** Affects: nova
 Importance: Undecided
 Assignee: Alex Xu (xuhj)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Alex Xu (xuhj)

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

Title:
  request unsupport method to Placement API 500 returned

Status in OpenStack Compute (nova):
  New

Bug description:
  I get 500 return as below:

  curl -g -i -X DELETE http://hp-pc:8778/placement/resource_providers -H
  "User-Agent: python-novaclient" -H "Accept: application/json" -H "X
  -Auth-Token: 79768b74827c40aebbcbf8c91e89e6cf"

  
  HTTP/1.1 500 Internal Server Error
  Date: Thu, 22 Sep 2016 12:54:10 GMT
  Server: Apache/2.4.18 (Ubuntu)
  Content-Length: 604
  Connection: close
  Content-Type: text/html; charset=iso-8859-1

  
  
  500 Internal Server Error
  
  Internal Server Error
  The server encountered an internal error or
  misconfiguration and was unable to complete
  your request.
  Please contact the server administrator at
   [no address given] to inform them of the time this error occurred,
   and the actions you performed just before this error.

[Yahoo-eng-team] [Bug 1626536] [NEW] test_floatingip_associate_disassociate fails too frequently

[Akihiro Motoki]

Public bug reported:

Recently test_floatingip_associate_disassociate fails frequently in our
integration tests.

gate-horizon-dsvm-integration-deprecated-ubuntu-xenial
gate-horizon-dsvm-integration-current-ubuntu-xenial

http://logs.openstack.org/55/374055/2/check/gate-horizon-dsvm-
integration-deprecated-ubuntu-xenial/ac0ba5c/

logstash query:

message:"FAIL:
openstack_dashboard.test.integration_tests.tests.test_floatingips.TestFloatingipAssociateDisassociate.test_floatingip_associate_disassociate"

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

Title:
  test_floatingip_associate_disassociate fails too frequently

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Recently test_floatingip_associate_disassociate fails frequently in
  our integration tests.

  gate-horizon-dsvm-integration-deprecated-ubuntu-xenial
  gate-horizon-dsvm-integration-current-ubuntu-xenial

  http://logs.openstack.org/55/374055/2/check/gate-horizon-dsvm-
  integration-deprecated-ubuntu-xenial/ac0ba5c/

  logstash query:

  message:"FAIL:
  
openstack_dashboard.test.integration_tests.tests.test_floatingips.TestFloatingipAssociateDisassociate.test_floatingip_associate_disassociate"

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1626536/+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 1626123] Re: Functional tests result depends on way test running

[Sean Dague]

Honestly this is probably just a bug in this test case in particular.
Please look at why this fails in some runnings and not in others.

** Changed in: nova
   Status: New => Opinion

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

Title:
  Functional tests result depends on way test running

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  Description
  ===
  testtools.run and testtools.run --load-list work differently with nova tests.

  Steps to reproduce
  ==
  amadev@pilgrim:~/m/nova$ source .tox/functional/bin/activate
  (functional) amadev@pilgrim:~/m/nova$ python -m testtools.run 
nova.tests.functional.notification_sample_tests.test_instance.TestInstanceNotificationSample.test_create_delete_server_with_instance_update
  ...
  Ran 1 test in 5.806s
  OK
  (functional) amadev@pilgrim:~/m/nova$ testr list-tests 
test_create_delete_server_with_instance_update > /tmp/nova-tests
  (functional) amadev@pilgrim:~/m/nova$ python -m testtools.run discover 
--load-list /tmp/nova-tests
  ...
  Ran 1 test in 4.689s
  FAILED (failures=1)

  Expected result
  ===
  Tests shouldn't depent on the method of running.

  Environment
  ===
  upstream master

  Logs & Configs
  ==
  http://xsnippet.org/361996/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1626123/+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 1626566] [NEW] some 'url' in "images/urls.py" are repeated and redundant

[qiaomin032]

Public bug reported:

The 'image_urls' and 'snapshot_urls' in 'images/urls.py' are repeated,
we can refactor the code and remove some redundant code.

** Affects: horizon
 Importance: Undecided
 Assignee: qiaomin032 (chen-qiaomin)
 Status: In Progress

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

Title:
  some 'url' in "images/urls.py" are repeated and redundant

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  The 'image_urls' and 'snapshot_urls' in 'images/urls.py' are repeated,
  we can refactor the code and remove some redundant code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1626566/+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 1623573] Re: placement API functional test fixtures do not do appropriate stdout and stderr handling

[OpenStack Infra]

Reviewed:  https://review.openstack.org/374256
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=687984bcb4a259dcc8e88e9d9b902b103bb396a1
Submitter: Jenkins
Branch:master

commit 687984bcb4a259dcc8e88e9d9b902b103bb396a1
Author: Chris Dent 
Date:   Wed Sep 21 15:41:58 2016 +

[placement] Manage log and other output in gabbi fixure

Recent changes to the placement API added more verbose logging and
output across both stdout and stderr. In test runs this resulted in
a combination of far too much output as well as output that was
impossible to read because it was interleaved.

This change uses fixtures from nova.tests.fixtures to capture
stray output streams and logs.

It also adds a specific logger for the ERROR level that overrides
the fixture log handling to send that level to the default stderr.
This is required in order to effectively see error messages on both
side of the wsgi-intercept used when running gabbi. Without this,
the errors are swallowed and test development and debugging,
especially locally for TDD, is hamstrung.

Closes-Bug: #1623573
Change-Id: I300456b0261dfc0ae46c799e5a03cbeab25106c2


** Changed in: nova
   Status: In Progress => 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/1623573

Title:
  placement API functional test fixtures do not do appropriate stdout
  and stderr handling

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  In a multi-process environment the logging that is done in the
  placement API when it is running under functional tests with gabbi
  interleaves, resulting in illegible output in test runs. Makes it
  pretty hard to do anything when a failure happens.

  There are fixtures that other nova tests use that ought to be reusable
  here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1623573/+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 1625604] Re: The timeout is not honored in NeutronOVSDBTransaction

[OpenStack Infra]

Reviewed:  https://review.openstack.org/373231
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=a01ca102500cb4705c6c4d8e10180931aa7d5056
Submitter: Jenkins
Branch:master

commit a01ca102500cb4705c6c4d8e10180931aa7d5056
Author: Hong Hui Xiao 
Date:   Tue Sep 20 20:15:21 2016 +0800

Fix wrong use of six.moves.queue.get()

timeout is not the first positional argument.

Change-Id: Icd745514adc14730b9179fa7a6dd5c115f5e87a5
Closes-Bug: #1625604


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

Title:
  The timeout is not honored  in NeutronOVSDBTransaction

Status in neutron:
  Fix Released

Bug description:
  According to [1], the usage of [2] is not appropriate. If timeout > 0,
  the commit will wait forever.

  
  [1] https://docs.python.org/2/library/queue.html#module-Queue
  [2] 
https://github.com/openstack/neutron/blob/be29217d82cc633bda1a66c2e50612de1e3f7e15/neutron/agent/ovsdb/impl_idl.py#L67

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1625604/+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 1626643] [NEW] integration tests: socket.error: Connection refused frequently happens in selenium remote driver

[Akihiro Motoki]

Public bug reported:

socket.error: [Errno 111] Connection refused frequently occurs recently in 
selenium remote_connection.
This is seen in various tests. It seems selenium fails to connect a browser.

For example, http://logs.openstack.org/14/303514/55/check/gate-horizon-
dsvm-integration-current-ubuntu-
xenial/af1bef2/console.html#_2016-09-21_10_56_45_019822

66 hits in last 7 days in 311 integration test run (dsvm-integration-current 
and dsvm-integration-deprecated)
The failure rate is 21%. The rate is high enough.

logstash query:
message:"socket.error: [Errno 111] Connection refused"
AND filename:"console.html"
AND (build_name:"gate-horizon-dsvm-integration-deprecated-ubuntu-xenial" OR 
build_name:"gate-horizon-dsvm-integration-current-ubuntu-xenial")

** Affects: horizon
 Importance: High
 Status: New


** Tags: integration-tests

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

Title:
  integration tests: socket.error: Connection refused frequently happens
  in selenium remote driver

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  socket.error: [Errno 111] Connection refused frequently occurs recently in 
selenium remote_connection.
  This is seen in various tests. It seems selenium fails to connect a browser.

  For example, http://logs.openstack.org/14/303514/55/check/gate-
  horizon-dsvm-integration-current-ubuntu-
  xenial/af1bef2/console.html#_2016-09-21_10_56_45_019822

  66 hits in last 7 days in 311 integration test run (dsvm-integration-current 
and dsvm-integration-deprecated)
  The failure rate is 21%. The rate is high enough.

  logstash query:
  message:"socket.error: [Errno 111] Connection refused"
  AND filename:"console.html"
  AND (build_name:"gate-horizon-dsvm-integration-deprecated-ubuntu-xenial" OR 
build_name:"gate-horizon-dsvm-integration-current-ubuntu-xenial")

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1626643/+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 1626642] [NEW] Cleanup and add more UT for FWaaS v2 plugin

[Sridar Kandaswamy]

Public bug reported:

Add more UT without overlap to the db UT. Add a helper function or add
to setUp a lot of the common code around creating a router, subnet and
attach etc so eliminates redundant code.

** Affects: neutron
 Importance: Undecided
 Assignee: Sridar Kandaswamy (skandasw)
 Status: New


** Tags: fwaas

** Changed in: neutron
 Assignee: (unassigned) => Sridar Kandaswamy (skandasw)

** Tags added: fwaas

** Description changed:

- Add more UT without overlap to the db UT. Also on the plugin, add a
- helper function or add to setUp a lot of the common code around creating
- a router, subnet and attach etc so eliminates redundant code.
+ Add more UT without overlap to the db UT. Add a helper function or add
+ to setUp a lot of the common code around creating a router, subnet and
+ attach etc so eliminates redundant code.

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

Title:
  Cleanup and add more UT for FWaaS v2 plugin

Status in neutron:
  New

Bug description:
  Add more UT without overlap to the db UT. Add a helper function or add
  to setUp a lot of the common code around creating a router, subnet and
  attach etc so eliminates redundant code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1626642/+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 1621180] Re: specifying apt_mirror of '' renders empty entries in /etc/apt/sources.list for uri

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  specifying apt_mirror of '' renders empty entries in
  /etc/apt/sources.list for uri

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in juju-core package in Ubuntu:
  New
Status in cloud-init source package in Xenial:
  Fix Released
Status in juju-core source package in Xenial:
  New

Bug description:
   Begin SRU Template 
  [Impact]
  This is a bug that existed only in development time in cloud-init and was 
exposed during uploads to yakkety.  It has never existed in xenial, but we do 
need to make sure that the function is still present.

  The impact was that if a user (juju) started an instance with:
    apt_mirror: ''

  that was taken as the apt mirror a

[Yahoo-eng-team] [Bug 1619394] Re: base64 user-data broken in OVF datasource

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  base64 user-data broken in OVF datasource

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact] 
  Users of the OVF datasource can not provide user-data that is base64 encoded.

  [Test Case]
  $ rel=xenial
  $ burl="http://cloud-images.ubuntu.com/daily/server/$rel/current/";
  $ disk="$rel-server-cloudimg-amd64-disk1.img"
  $ wget "$burl/$disk" -O "$disk"

  # prepare the ovftransport.iso
  $ git clone http://git.launchpad.net/cloud-init
  $ ( cd cloud-init/doc/sources/ovf && ./make-iso ovf-env.xml.tmpl user-data 
--output - ) > ovftransport.iso

  # create a t

[Yahoo-eng-team] [Bug 1610784] Re: cloud-init openstack.py code does not recognize network type 'tap'

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  cloud-init openstack.py code does not recognize network type 'tap'

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact]
  Certain versions and configurations of Openstack produce a config
  drive that has network devices described as 'type: tap'.  Previously
  cloud-init would require those to be 'type: ethernet' or other.

  The fix was to allow 'tap' to be considered a "physical" type from the
  guest VM's perspective.

  [Test Case]
   * Boot a VM in the reporters environment,
   * add proposed,
   * rm -Rf /var/lib/cloud /var/log/cloud-init*
   * reboot
   

[Yahoo-eng-team] [Bug 1616831] Re: cloud-init doesn't prefer new APT config format when old and new are provided

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  cloud-init doesn't prefer new APT config format when old and new are
  provided

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact]
  New apt configuration was enabled, but if the user provided both new
  configuration format and old configuration format, then then cloud-init
  would error.

  The fixed behavior is to allow new and old and warn if they differ.

  This allows a user to provide the same data for older releases and
  newer release.

  [Test Case]
  # Recreate failure (this would recreate on intermediate versions of
  # cloud-init that were in tru

[Yahoo-eng-team] [Bug 1612313] Re: maas datasource needs support for vendor-data

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  maas datasource needs support for vendor-data

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact] 
  This is a new feature adding 'vendor data' support to MAAS.
  MAAS in 2.X will make use of this feature in cloud-init.

  [Test Case]
  There are unit tests to test this, actual integration test is not easily
  done outside of MAAS.

  [Regression Potential] 
  Very low chance of regression.  Cloud-init will try once to retrive
  vendor-data and if it is present use it.  If not, it will go on.

  The regression possibility would then be in cases when interactin

[Yahoo-eng-team] [Bug 1609899] Re: salt minion module writes minion keys to the wrong directory

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  salt minion module writes minion keys to the wrong directory

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact] 
  Salt minion config module of cloud-init would not work by default
  if 'public_key' and 'private_key' were provided.

  [Test Case]
  ## Recreate failure
  $ cat >user-data  "$p" &&
  apt-get update -q && apt-get -qy install cloud-init'
  $ lxc exec x1 -- sh -c 'apt-get -qy --purge remove salt-minion && rm -Rf 
/etc/salt'
  $ lxc exec x1 -- sh -c '
  cd /var/lib/cloud && for d in *; 

[Yahoo-eng-team] [Bug 1607810] Re: Wrong default key 'fdqn' in POST_LIST_ALL / cc_phone_home.py

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Wrong default key 'fdqn' in POST_LIST_ALL / cc_phone_home.py

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact] 
  A feature of cloud-init to post its fully qualified domain name
  to a web service was broken.

  [Test Case]
  ## Recreate failure

  $ cat >user-data 

[Yahoo-eng-team] [Bug 1576692] Re: fully support package installation in systemd

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  fully support package installation in systemd

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in init-system-helpers source package in Xenial:
  Fix Committed

Bug description:
  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]

  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.

  We'd like to

[Yahoo-eng-team] [Bug 1605749] Re: ConfigDrive: cloud-init fails to configure bond from network_data.json

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  ConfigDrive: cloud-init fails to configure bond from network_data.json

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
  cloud-init fails to configure bond interfaces from network_data.json

  There is a couple of reasons:

  Bond links found in network_data.json do not have a name attribute.
  cloud-init doesn't require the name attribute to exist in links. [1]
  However cloud-init later expects the links to have a name attribute
  and crashes when it doesn't have any. [2] The name attribute is not
  part of the OpenStack network_data.json specification and will
  therefore never be provided.

  

[Yahoo-eng-team] [Bug 1612875] Re: FixedIPsTestJson fails server build with "was re-scheduled: operation failed: filter 'nova-no-nd-reflection' already exists with uuid"

[Matt Riedemann]

** Also affects: nova/newton
   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/1612875

Title:
  FixedIPsTestJson fails server build with "was re-scheduled: operation
  failed: filter 'nova-no-nd-reflection' already exists with uuid"

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) newton series:
  New

Bug description:
  Seen here:

  http://logs.openstack.org/98/355098/1/check/gate-tempest-dsvm-full-
  ubuntu-
  xenial/3c301f3/logs/screen-n-cond.txt.gz?level=TRACE#_2016-08-13_00_53_27_621

  2016-08-13 00:53:27.621 15971 ERROR nova.scheduler.utils 
[req-e7b83619-01ae-43f2-b293-af02c5cb35a8 tempest-FixedIPsTestJson-2017152444 
tempest-FixedIPsTestJson-2017152444] [instance: 
ac2c9a4a-1b07-43e1-8f4c-b75541331307] Error from last host: 
ubuntu-xenial-rax-ord-3453779 (node ubuntu-xenial-rax-ord-3453779): 
[u'Traceback (most recent call last):\n', u'  File 
"/opt/stack/new/nova/nova/compute/manager.py", line 1778, in 
_do_build_and_run_instance\nfilter_properties)\n', u'  File 
"/opt/stack/new/nova/nova/compute/manager.py", line 1973, in 
_build_and_run_instance\ninstance_uuid=instance.uuid, 
reason=six.text_type(e))\n', u"RescheduledException: Build of instance 
ac2c9a4a-1b07-43e1-8f4c-b75541331307 was re-scheduled: operation failed: filter 
'nova-no-nd-reflection' already exists with uuid 
1f47eeb2-d473-481e-998a-c4d64a44ac5e\n"]
  2016-08-13 00:53:27.676 15971 WARNING nova.scheduler.utils 
[req-e7b83619-01ae-43f2-b293-af02c5cb35a8 tempest-FixedIPsTestJson-2017152444 
tempest-FixedIPsTestJson-2017152444] Failed to compute_task_build_instances: No 
valid host was found. There are not enough hosts available.
  Traceback (most recent call last):

File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", 
line 199, in inner
  return func(*args, **kwargs)

File "/opt/stack/new/nova/nova/scheduler/manager.py", line 104, in 
select_destinations
  dests = self.driver.select_destinations(ctxt, spec_obj)

File "/opt/stack/new/nova/nova/scheduler/filter_scheduler.py", line 74, in 
select_destinations
  raise exception.NoValidHost(reason=reason)

  NoValidHost: No valid host was found. There are not enough hosts
  available.

  2016-08-13 00:53:27.676 15971 WARNING nova.scheduler.utils [req-
  e7b83619-01ae-43f2-b293-af02c5cb35a8 tempest-
  FixedIPsTestJson-2017152444 tempest-FixedIPsTestJson-2017152444]
  [instance: ac2c9a4a-1b07-43e1-8f4c-b75541331307] Setting instance to
  ERROR state.

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22was
  %20re-scheduled%3A%20operation%20failed%3A%20filter%20'nova-no-nd-
  
reflection'%20already%20exists%20with%20uuid%5C%22%20AND%20tags%3A%5C%22screen-n-cond.txt%5C%22&from=7d

  5 hits in 7 days, check queue only, but multiple changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1612875/+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 1626702] [NEW] Instances deletes should be asynchronous with host availability

[Darren Carpenter]

Public bug reported:

Description: When a host goes down and instances on that host are
deleted while the host is down, this request should be tracked in the
database so that when the host comes back up it can scrub the delete
request against the status of the active instance and delete it if
necessary. The overall goal is for the delete to be processed so that
any attached volumes return to an available state instead of being left
in an in-use state. (attached to a non-existent instance)

This is being experienced while using Cloud Foundry. When the host goes
down, Bosh attempts to re-create the instance along with associating any
previous known volumes.

This has been tested on the following tag:
10.1.18

If this was not an issue, I would expect the delete request to go
through while the host was down and the system itself would clean up the
mess once the host comes back online freeing up the volume for use
immediately.

(This is going to be tested in Liberty as well and further notes will be
attached to the bug report)

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: 10.1.18

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

Title:
  Instances deletes should be asynchronous with host availability

Status in OpenStack Compute (nova):
  New

Bug description:
  Description: When a host goes down and instances on that host are
  deleted while the host is down, this request should be tracked in the
  database so that when the host comes back up it can scrub the delete
  request against the status of the active instance and delete it if
  necessary. The overall goal is for the delete to be processed so that
  any attached volumes return to an available state instead of being
  left in an in-use state. (attached to a non-existent instance)

  This is being experienced while using Cloud Foundry. When the host
  goes down, Bosh attempts to re-create the instance along with
  associating any previous known volumes.

  This has been tested on the following tag:
  10.1.18

  If this was not an issue, I would expect the delete request to go
  through while the host was down and the system itself would clean up
  the mess once the host comes back online freeing up the volume for use
  immediately.

  (This is going to be tested in Liberty as well and further notes will
  be attached to the bug report)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1626702/+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 1626720] [NEW] integration tests: test_download_rc_v2_file fails with selenium.common.exceptions.NoSuchElementException

[Akihiro Motoki]

Public bug reported:

openstack_dashboard.test.integration_tests.tests.test_credentials.TestDownloadRCFile.test_download_rc_v2_file
failed several times. This test is executed first, so most time might be
needed.

There are two failure patterns observed.
The one is 'AssertionError: False is not true' and the other is 
selenium.common.exceptions.NoSuchElementException.

In both patterns, "root: INFO: X11 isn't installed. Should use xvfb to run 
tests" message was observed.
I think this is always output and is not related to this failure directly, but 
it looks useful when using logstash.
the following query looks fine.
message:"root: INFO: X11 isn't installed. Should use xvfb to run tests."
AND (build_name:"gate-horizon-dsvm-integration-current-ubuntu-xenial" OR 
build_name:"gate-horizon-dsvm-integration-deprecated-ubuntu-xenial")

(a) AssertionError: False is not true
==
FAIL: 
openstack_dashboard.test.integration_tests.tests.test_credentials.TestDownloadRCFile.test_download_rc_v2_file
--
_StringException: Traceback (most recent call last):
   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_credentials.py",
 line 56, in test_download_rc_v2_file
self.assertTrue(False)
   File 
"/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/unittest2/case.py",
 line 702, in assertTrue
raise self.failureException(msg)
AssertionError: False is not true

 >> begin captured logging << 
root: INFO: X11 isn't installed. Should use xvfb to run tests.
- >> end captured logging << -

(b) selenium.common.exceptions.NoSuchElementException
==
ERROR: 
openstack_dashboard.test.integration_tests.tests.test_credentials.TestDownloadRCFile.test_download_rc_v2_file
--
_StringException: Traceback (most recent call last):
  File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_credentials.py",
 line 28, in setUp
super(TestDownloadRCFile, self).setUp()
  File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/helpers.py", 
line 307, in setUp
self.home_pg.change_project(self.HOME_PROJECT)
  File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/basepage.py",
 line 66, in change_project
self.topbar.user_dropdown_project.click_on_project(name)
  File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/regions/bars.py",
 line 59, in user_dropdown_project
src_elem = self._get_element(*self._user_dropdown_project_locator)
  File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/regions/baseregion.py",
 line 61, in _get_element
return self.src_elem.find_element(*locator)
  File "/opt/stack/new/horizon/horizon/test/webdriver.py", line 40, in 
find_element
web_el = super(WrapperFindOverride, self).find_element(by, value)
  File 
"/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py",
 line 752, in find_element
'value': value})['value']
  File 
"/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py",
 line 236, in execute
self.error_handler.check_response(response)
  File 
"/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/remote/errorhandler.py",
 line 192, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: Unable to locate 
element: {"method":"css selector","selector":".navbar-collapse > 
ul.navbar-nav:first-child"}
Stacktrace:
at FirefoxDriver.prototype.findElementInternal_ 
(file:///tmp/tmpFRqPcW/extensions/fxdri...@googlecode.com/components/driver-component.js:10770)
at fxdriver.Timer.prototype.setTimeout/<.notify 
(file:///tmp/tmpFRqPcW/extensions/fxdri...@googlecode.com/components/driver-component.js:625)

 >> begin captured logging << 
root: INFO: X11 isn't installed. Should use xvfb to run tests.
- >> end captured logging << -

** Affects: horizon
 Importance: High
 Status: New


** Tags: integration-tests

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

Title:
  integration tests: test_download_rc_v2_file fails with
  selenium.common.exceptions.NoSuchElementException

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  
openstack_dashboard.test.integration_tests.tests.test_credentials.TestDow

[Yahoo-eng-team] [Bug 1588041] [NEW] [2.0 rc1] juju can't access vSphere VM deployed with Xenial, cloud-init fails to set SSH keys

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I tried to do a bootstrap with vsphere as a provider using vsphere 6.0 and juju 
1.25.5.
-
  vsphere:
type: vsphere
host: '**.***.*.***'
user: 'administra...@vsphere.oil'
password: '**'
datacenter: 'dc0'
bootstrap-timeout: 1800
logging-config: 
"=DEBUG;juju=DEBUG;golxc=TRACE;juju.container.lxc=TRACE"
agent-stream: released
-

Initially, I did not specify the default series and bootstrap VM
deployed with Xenial, however, juju  could not connect to it after
getting the address and seems stuck trying to connect and I had to
CTRL-C:

-
$ juju bootstrap -e vsphere
ERROR the "vsphere" provider is provisional in this version of Juju. To use it 
anyway, set JUJU_DEV_FEATURE_FLAGS="vsphere-provider" in your shell environment
$ export JUJU_DEV_FEATURE_FLAGS="vsphere-provider"
$ juju bootstrap -e vsphere
Bootstrapping environment "vsphere"
Starting new instance for initial state server
Launching instance
 - juju-e33e5800-edd9-4af7-8654-6d59b1e98eb9-machine-0
Installing Juju agent on bootstrap instance
Waiting for address
Attempting to connect to 10.245.39.94:22
Attempting to connect to fe80::250:56ff:fead:1b03:22
^CInterrupt signalled: waiting for bootstrap to exit
ERROR failed to bootstrap environment: interrupted
-

When I specified the default series to be trusty, it worked:
-
  vsphere:
type: vsphere
host: '**.***.*.***'
user: 'administra...@vsphere.oil'
password: '**'
datacenter: 'dc0'
default-series: trusty
bootstrap-timeout: 1800
logging-config: 
"=DEBUG;juju=DEBUG;golxc=TRACE;juju.container.lxc=TRACE"
agent-stream: released
-

This was the output:

-
$ juju bootstrap -e vsphere
Bootstrapping environment "vsphere"
Starting new instance for initial state server
Launching instance
 - juju-b157863b-3ed4-4ae5-8c3c-82ae7629bff7-machine-0
Installing Juju agent on bootstrap instance
Waiting for address
Attempting to connect to 10.245.45.153:22
Attempting to connect to fe80::250:56ff:fead:3fa2:22
Warning: Permanently added '10.245.45.153' (ECDSA) to the list of known hosts.
sudo: unable to resolve host ubuntuguest
Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Running apt-get upgrade
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: cloud-utils
Installing package: cloud-image-utils
Installing package: tmux
Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP 
%{http_code}; time %{time_total}s; size %{size_download} bytes; speed 
%{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz 
<[https://streams.canonical.com/juju/tools/agent/1.25.5/juju-1.25.5-trusty-amd64.tgz]>
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
Bootstrap agent installed
vsphere -> vsphere
Waiting for API to become available
Waiting for API to become available
Waiting for API to become available
Waiting for API to become available
Bootstrap complete
-

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Affects: juju
 Importance: High
 Status: Triaged


** Tags: ci jujuqa landscape oil oil-2.0 vsphere
-- 
[2.0 rc1] juju can't access vSphere VM deployed with Xenial,  cloud-init fails 
to set SSH keys
https://bugs.launchpad.net/bugs/1588041
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to cloud-init.

-- 
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 1449062] Re: qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

[Sean McGinnis]

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

** Changed in: cinder
   Importance: Undecided => Medium

** Changed in: cinder
 Assignee: (unassigned) => Sean McGinnis (sean-mcginnis)

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

Title:
  qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

Status in Cinder:
  New
Status in Cinder mitaka series:
  New
Status in Cinder newton series:
  New
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive liberty series:
  Fix Committed
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Security Advisory:
  In Progress
Status in python-oslo.concurrency package in Ubuntu:
  Fix Released
Status in python-oslo.concurrency source package in Wily:
  Fix Committed
Status in python-oslo.concurrency source package in Xenial:
  Fix Released
Status in python-oslo.concurrency source package in Yakkety:
  Fix Released

Bug description:
  Reported via private E-mail from Richard W.M. Jones.

  Turns out qemu image parser is not hardened against malicious input
  and can be abused to allocated an arbitrary amount of memory and/or
  dump a lot of information when used with "--output=json".

  The solution seems to be: limit qemu-img ressource using ulimit.

  Example of abuse:

  -- afl1.img --

  $ /usr/bin/time qemu-img info afl1.img
  image: afl1.img
  [...]
  0.13user 0.19system 0:00.36elapsed 92%CPU (0avgtext+0avgdata 
642416maxresident)k
  0inputs+0outputs (0major+156927minor)pagefaults 0swaps

  The original image is 516 bytes, but it causes qemu-img to allocate
  640 MB.

  -- afl2.img --

  $ qemu-img info --output=json afl2.img | wc -l
  589843

  This is a 200K image which causes qemu-img info to output half a
  million lines of JSON (14 MB of JSON).

  Glance runs the --output=json variant of the command.

  -- afl3.img --

  $ /usr/bin/time qemu-img info afl3.img
  image: afl3.img
  [...]
  0.09user 0.35system 0:00.47elapsed 94%CPU (0avgtext+0avgdata 
1262388maxresident)k
  0inputs+0outputs (0major+311994minor)pagefaults 0swaps

  qemu-img allocates 1.3 GB (actually, a bit more if you play with
  ulimit -v).  It appears that you could change it to allocate
  arbitrarily large amounts of RAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1449062/+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 1588041] Re: [2.0 rc1] juju can't access vSphere VM deployed with Xenial, cloud-init fails to set SSH keys

[Robert C Jennings]

I have downloaded a drive image of a xenial VM that Juju attempted to
boot and found that cloud-init could not parse the user-data attached to
the instance.  Here is the relevant error from /var/log/cloud-init.log.
Attaching /var/lib/cloud, /var/log, and /etc/cloud to this bug for
further research.

Sep 22 18:47:54 ubuntu [CLOUDINIT] __init__.py[DEBUG]: {'Content-Type': 
'text/x-not-multipart', 'Content-Disposition': 'attachment; 
filename="part-001"', 'MIME-Version': '1.0'}
Sep 22 18:47:54 ubuntu [CLOUDINIT] __init__.py[WARNING]: Unhandled 
non-multipart (text/x-not-multipart) userdata: 'b'I2Nsb3VkLWNvbmZpZwphcHRf'...'


** Attachment added: "xenial-juju-vsphere-userdata-20160921.tar.gz"
   
https://bugs.launchpad.net/juju/+bug/1588041/+attachment/4746458/+files/xenial-juju-vsphere-userdata-20160921.tar.gz

** Project changed: cloud-images => cloud-init

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

Title:
  [2.0 rc1] juju can't access vSphere VM deployed with Xenial,  cloud-
  init fails to set SSH keys

Status in cloud-init:
  New
Status in juju:
  Triaged

Bug description:
  I tried to do a bootstrap with vsphere as a provider using vsphere 6.0 and 
juju 1.25.5.
  -
    vsphere:
  type: vsphere
  host: '**.***.*.***'
  user: 'administra...@vsphere.oil'
  password: '**'
  datacenter: 'dc0'
  bootstrap-timeout: 1800
  logging-config: 
"=DEBUG;juju=DEBUG;golxc=TRACE;juju.container.lxc=TRACE"
  agent-stream: released
  -

  Initially, I did not specify the default series and bootstrap VM
  deployed with Xenial, however, juju  could not connect to it after
  getting the address and seems stuck trying to connect and I had to
  CTRL-C:

  -
  $ juju bootstrap -e vsphere
  ERROR the "vsphere" provider is provisional in this version of Juju. To use 
it anyway, set JUJU_DEV_FEATURE_FLAGS="vsphere-provider" in your shell 
environment
  $ export JUJU_DEV_FEATURE_FLAGS="vsphere-provider"
  $ juju bootstrap -e vsphere
  Bootstrapping environment "vsphere"
  Starting new instance for initial state server
  Launching instance
   - juju-e33e5800-edd9-4af7-8654-6d59b1e98eb9-machine-0
  Installing Juju agent on bootstrap instance
  Waiting for address
  Attempting to connect to 10.245.39.94:22
  Attempting to connect to fe80::250:56ff:fead:1b03:22
  ^CInterrupt signalled: waiting for bootstrap to exit
  ERROR failed to bootstrap environment: interrupted
  -

  When I specified the default series to be trusty, it worked:
  -
    vsphere:
  type: vsphere
  host: '**.***.*.***'
  user: 'administra...@vsphere.oil'
  password: '**'
  datacenter: 'dc0'
  default-series: trusty
  bootstrap-timeout: 1800
  logging-config: 
"=DEBUG;juju=DEBUG;golxc=TRACE;juju.container.lxc=TRACE"
  agent-stream: released
  -

  This was the output:

  -
  $ juju bootstrap -e vsphere
  Bootstrapping environment "vsphere"
  Starting new instance for initial state server
  Launching instance
   - juju-b157863b-3ed4-4ae5-8c3c-82ae7629bff7-machine-0
  Installing Juju agent on bootstrap instance
  Waiting for address
  Attempting to connect to 10.245.45.153:22
  Attempting to connect to fe80::250:56ff:fead:3fa2:22
  Warning: Permanently added '10.245.45.153' (ECDSA) to the list of known hosts.
  sudo: unable to resolve host ubuntuguest
  Logging to /var/log/cloud-init-output.log on remote host
  Running apt-get update
  Running apt-get upgrade
  Installing package: curl
  Installing package: cpu-checker
  Installing package: bridge-utils
  Installing package: rsyslog-gnutls
  Installing package: cloud-utils
  Installing package: cloud-image-utils
  Installing package: tmux
  Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP 
%{http_code}; time %{time_total}s; size %{size_download} bytes; speed 
%{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz 
<[https://streams.canonical.com/juju/tools/agent/1.25.5/juju-1.25.5-trusty-amd64.tgz]>
  Bootstrapping Juju machine agent
  Starting Juju machine agent (jujud-machine-0)
  Bootstrap agent installed
  vsphere -> vsphere
  Waiting for API to become available
  Waiting for API to become available
  Waiting for API to become available
  Waiting for API to become available
  Bootstrap complete
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init

[Yahoo-eng-team] [Bug 1449062] Re: qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

[Sean McGinnis]

** Also affects: cinder/mitaka
   Importance: Undecided
   Status: New

** Also affects: cinder/newton
   Importance: Medium
 Assignee: Sean McGinnis (sean-mcginnis)
   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/1449062

Title:
  qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

Status in Cinder:
  In Progress
Status in Cinder mitaka series:
  New
Status in Cinder newton series:
  In Progress
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive liberty series:
  Fix Committed
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Security Advisory:
  In Progress
Status in python-oslo.concurrency package in Ubuntu:
  Fix Released
Status in python-oslo.concurrency source package in Wily:
  Fix Committed
Status in python-oslo.concurrency source package in Xenial:
  Fix Released
Status in python-oslo.concurrency source package in Yakkety:
  Fix Released

Bug description:
  Reported via private E-mail from Richard W.M. Jones.

  Turns out qemu image parser is not hardened against malicious input
  and can be abused to allocated an arbitrary amount of memory and/or
  dump a lot of information when used with "--output=json".

  The solution seems to be: limit qemu-img ressource using ulimit.

  Example of abuse:

  -- afl1.img --

  $ /usr/bin/time qemu-img info afl1.img
  image: afl1.img
  [...]
  0.13user 0.19system 0:00.36elapsed 92%CPU (0avgtext+0avgdata 
642416maxresident)k
  0inputs+0outputs (0major+156927minor)pagefaults 0swaps

  The original image is 516 bytes, but it causes qemu-img to allocate
  640 MB.

  -- afl2.img --

  $ qemu-img info --output=json afl2.img | wc -l
  589843

  This is a 200K image which causes qemu-img info to output half a
  million lines of JSON (14 MB of JSON).

  Glance runs the --output=json variant of the command.

  -- afl3.img --

  $ /usr/bin/time qemu-img info afl3.img
  image: afl3.img
  [...]
  0.09user 0.35system 0:00.47elapsed 94%CPU (0avgtext+0avgdata 
1262388maxresident)k
  0inputs+0outputs (0major+311994minor)pagefaults 0swaps

  qemu-img allocates 1.3 GB (actually, a bit more if you play with
  ulimit -v).  It appears that you could change it to allocate
  arbitrarily large amounts of RAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1449062/+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 1622644] Re: OVS agent ryu/native implementation breaks non-OF1.3 uses

[Thomas Morin]

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

Title:
  OVS agent ryu/native implementation breaks non-OF1.3 uses

Status in networking-bgpvpn:
  Fix Released
Status in BaGPipe:
  New
Status in neutron:
  Fix Released

Bug description:
  The ryu-based OVS agent variant forces the bridge Openflow version to 1.3 
only [1], which breaks a few things:
  - troubleshooting tools relying on ovs-ofctl, unless they specify "-O 
Openflow13", will break:
version negotiation failed (we support version 0x01, peer supports version 
0x04)
ovs-ofctl: br-tun: failed to connect to socket (Broken pipe)

  - calling add_flow on an OVSCookieBridge derived from a bridge that is
  an native.ovs_bridge.OVSAgentBridge, will fail with the same error,
  because add_flow will call ovs-ofctl without specifying "-O
  Openflow13"  (this issue is currently hitting networking-bgpvpn: [2])

  It seems like a possible fix would be to not restrict the set of
  Openflow versions supported by the bridge to Openflow13, but to just
  *add* Openflow13 to the set of supported versions.

  [1] 
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/ovs_bridge.py#L78
  [2] 
https://github.com/openstack/networking-bagpipe/blob/master/networking_bagpipe/agent/bagpipe_bgp_agent.py#L512

To manage notifications about this bug go to:
https://bugs.launchpad.net/bgpvpn/+bug/1622644/+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 1449062] Re: qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

[Hemanth Makkapati]

** Also affects: glance
   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/1449062

Title:
  qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

Status in Cinder:
  In Progress
Status in Cinder mitaka series:
  New
Status in Cinder newton series:
  In Progress
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive liberty series:
  Fix Committed
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in Glance:
  New
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Security Advisory:
  In Progress
Status in python-oslo.concurrency package in Ubuntu:
  Fix Released
Status in python-oslo.concurrency source package in Wily:
  Fix Committed
Status in python-oslo.concurrency source package in Xenial:
  Fix Released
Status in python-oslo.concurrency source package in Yakkety:
  Fix Released

Bug description:
  Reported via private E-mail from Richard W.M. Jones.

  Turns out qemu image parser is not hardened against malicious input
  and can be abused to allocated an arbitrary amount of memory and/or
  dump a lot of information when used with "--output=json".

  The solution seems to be: limit qemu-img ressource using ulimit.

  Example of abuse:

  -- afl1.img --

  $ /usr/bin/time qemu-img info afl1.img
  image: afl1.img
  [...]
  0.13user 0.19system 0:00.36elapsed 92%CPU (0avgtext+0avgdata 
642416maxresident)k
  0inputs+0outputs (0major+156927minor)pagefaults 0swaps

  The original image is 516 bytes, but it causes qemu-img to allocate
  640 MB.

  -- afl2.img --

  $ qemu-img info --output=json afl2.img | wc -l
  589843

  This is a 200K image which causes qemu-img info to output half a
  million lines of JSON (14 MB of JSON).

  Glance runs the --output=json variant of the command.

  -- afl3.img --

  $ /usr/bin/time qemu-img info afl3.img
  image: afl3.img
  [...]
  0.09user 0.35system 0:00.47elapsed 94%CPU (0avgtext+0avgdata 
1262388maxresident)k
  0inputs+0outputs (0major+311994minor)pagefaults 0swaps

  qemu-img allocates 1.3 GB (actually, a bit more if you play with
  ulimit -v).  It appears that you could change it to allocate
  arbitrarily large amounts of RAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1449062/+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 1626751] [NEW] Shelve and unshelve actions should not be available for a locked instance

[Ying Zuo]

Public bug reported:

There will be an error when the user tries to shelve/unshelve a locked
instance so it shouldn't be listed in the action dropdown for a locked
instance.

** Affects: horizon
 Importance: Undecided
 Assignee: Ying Zuo (yingzuo)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => Ying Zuo (yingzuo)

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

Title:
  Shelve and unshelve actions should not be available for a  locked
  instance

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  There will be an error when the user tries to shelve/unshelve a locked
  instance so it shouldn't be listed in the action dropdown for a locked
  instance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1626751/+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 1623327] Re: openstack orchestration service list fails to return endpoint

[Steve Baker]

The openstack deployment tool you used is not setting up the endpoints
correctly for endpoints which require tenants in the path - if you used
a particular deployment tool this bug should be raised there.

** Changed in: python-heatclient
   Status: New => Invalid

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

Title:
  openstack orchestration service list fails to return endpoint

Status in OpenStack Identity (keystone):
  New
Status in python-heatclient:
  Invalid
Status in python-openstackclient:
  New

Bug description:
  OpenStack service endpoints are created for the heat service, but the
  openstack client cannot find the endpoints to issue the query against.
  I suspect this is due to the domain auth tokens included in the
  initial authentication doesn't include any endpoints with the
  $(tenant_id)s in the output there.

  I'm not sure whether this should be a bug against the openstack client
  or against keystone. I believe its intentional to exclude the
  endpoints with a tenant_id substitution in the endpoint, but it
  doesn't make any sense to me as it seems the openstack catalog list
  command uses this catalog query in order to list endpoints and
  services, which it only gets the service but not the endpoints.

  Here's some output collected:

  > openstack catalog list
  +--+-++
  | Name | Type| Endpoints  |
  +--+-++
  | heat | orchestration   ||
  | heat-cfn | cloudformation  | RegionOne  |
  |  | |   public: http://10.5.20.176:8000/v1   |
  |  | | RegionOne  |
  |  | |   admin: http://10.5.20.176:8000/v1|
  |  | | RegionOne  |
  |  | |   internal: http://10.5.20.176:8000/v1 |
  |  | ||

  ...

  > openstack endpoint list | grep heat
  | 85ee6b6e8f814856a3a547982f6b2835 | RegionOne  | heat | 
orchestration   | True| internal  | 
http://10.5.20.176:8004/v1/$(tenant_id)s  |
  | 895cb2e4e5d1492e9e40c205f6b0c508 | RegionOne  | heat | 
orchestration   | True| public| 
http://10.5.20.176:8004/v1/$(tenant_id)s  |
  | ad63a139c90749ff9d98a704200d2e49 | RegionOne  | heat | 
orchestration   | True| admin | 
http://10.5.20.176:8004/v1/$(tenant_id)s  |


  > openstack orchestration service list
  public endpoint for orchestration service not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1623327/+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 1626778] [NEW] [api] document /auth/tokens/OS-PKI/revoked

[Steve Martinelli]

Public bug reported:

The /auth/tokens/OS-PKI/revoked API is undocumented:
https://github.com/openstack/keystone/blob/8a56c161ee29e34e70c6334b048881e8fbbd7514/keystone/auth/routers.py#L36

Likewise, for v2, the /tokens/revoked API is undocumented too:
https://github.com/openstack/keystone/blob/8a56c161ee29e34e70c6334b048881e8fbbd7514/keystone/token/routers.py#L25

** Affects: keystone
 Importance: Medium
 Status: Confirmed


** Tags: api-ref

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

Title:
  [api] document /auth/tokens/OS-PKI/revoked

Status in OpenStack Identity (keystone):
  Confirmed

Bug description:
  The /auth/tokens/OS-PKI/revoked API is undocumented:
  
https://github.com/openstack/keystone/blob/8a56c161ee29e34e70c6334b048881e8fbbd7514/keystone/auth/routers.py#L36

  Likewise, for v2, the /tokens/revoked API is undocumented too:
  
https://github.com/openstack/keystone/blob/8a56c161ee29e34e70c6334b048881e8fbbd7514/keystone/token/routers.py#L25

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1626778/+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 1302831] Re: hacking/flake8 skips most xenapi plugins

[OpenStack Infra]

Reviewed:  https://review.openstack.org/289431
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=6bb1fd776feb7efd36a8c622ded37b67a21754cc
Submitter: Jenkins
Branch:master

commit 6bb1fd776feb7efd36a8c622ded37b67a21754cc
Author: Stephen Finucane 
Date:   Mon Mar 7 16:12:17 2016 +

plugins/xenserver: Add '.py' extension

All Python files, except executables, should have a '.py' extension.
This wasn't being done for files in the 'plugins/xenserver' folder,
likely because it seems unnatural to call a "plugin" with a file
extension.

Begin working towards a resolution for this by renaming all files to
include a '.py' extension. To avoid forcing operators to upgrade the
Nova service and per-host plugins at the same time, continue to
reference the old, non-'.py' filenames, using symlinks to ensure the
references continue to work. Once Ocata has been released, these
symlinks can be removed, the API version updated and the reference
updated to include the '.py' extension.

Change-Id: Icf4cf2424c15276a6c01778fb92f76bbdc9b2068
Closes-bug: #1302831


** Changed in: nova
   Status: In Progress => 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/1302831

Title:
  hacking/flake8 skips most xenapi plugins

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  It appears to be because the plugins themselves don't have a filename
  that ends in .py so they get skipped. Only the few files in there that
  end .py are being checked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1302831/+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 1626779] [NEW] [api] document OS-SIMPLE-CERT routes

[Steve Martinelli]

Public bug reported:

The /certificates/ca and /certificates/signing routes are not
documented:
https://github.com/openstack/keystone/blob/8a56c161ee29e34e70c6334b048881e8fbbd7514/keystone/token/routers.py#L51-L59

The /OS-SIMPLE-CERT/list_certificates and /OS-SIMPLE-
CERT/get_ca_certificate routes are not documented:
https://github.com/openstack/keystone/blob/d9c6b50a3ae514e640fa13a344e59fe3649ee0ef/keystone/token/_simple_cert.py#L52-L69

** Affects: keystone
 Importance: Medium
 Status: Confirmed


** Tags: api-ref

** Changed in: keystone
Milestone: None => ocata-1

** Summary changed:

- [api] document cert routes
+ [api] document OS-SIMPLE-CERT routes

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

Title:
  [api] document OS-SIMPLE-CERT routes

Status in OpenStack Identity (keystone):
  Confirmed

Bug description:
  The /certificates/ca and /certificates/signing routes are not
  documented:
  
https://github.com/openstack/keystone/blob/8a56c161ee29e34e70c6334b048881e8fbbd7514/keystone/token/routers.py#L51-L59

  The /OS-SIMPLE-CERT/list_certificates and /OS-SIMPLE-
  CERT/get_ca_certificate routes are not documented:
  
https://github.com/openstack/keystone/blob/d9c6b50a3ae514e640fa13a344e59fe3649ee0ef/keystone/token/_simple_cert.py#L52-L69

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1626779/+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 1626794] [NEW] [api] document "belongsTo" query for HEAD/GET tokens on v2

[Steve Martinelli]

Public bug reported:

Apparently there is a query parameter -- belongsTo -- that can be used
on GET/HEAD requests to /v2.0/tokens/{token_id} -- it's not documented
in the API reference at all.

Here's what it does:

 def _token_belongs_to(self, token, belongs_to):
"""Check if the token belongs to the right tenant.

This is only used on v2 tokens.  The structural validity of the token
will have already been checked before this method is called.

"""
if belongs_to:
token_data = token['access']['token']
if ('tenant' not in token_data or
token_data['tenant']['id'] != belongs_to):
raise exception.Unauthorized()


https://github.com/openstack/keystone/blob/0340cd0150af04f950e2b868c932dfee2dbf8530/keystone/token/provider.py#L354-L365

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: api-ref

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

Title:
  [api] document "belongsTo" query for HEAD/GET tokens on v2

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  Apparently there is a query parameter -- belongsTo -- that can be used
  on GET/HEAD requests to /v2.0/tokens/{token_id} -- it's not documented
  in the API reference at all.

  Here's what it does:

   def _token_belongs_to(self, token, belongs_to):
  """Check if the token belongs to the right tenant.

  This is only used on v2 tokens.  The structural validity of the token
  will have already been checked before this method is called.

  """
  if belongs_to:
  token_data = token['access']['token']
  if ('tenant' not in token_data or
  token_data['tenant']['id'] != belongs_to):
  raise exception.Unauthorized()

  
  
https://github.com/openstack/keystone/blob/0340cd0150af04f950e2b868c932dfee2dbf8530/keystone/token/provider.py#L354-L365

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1626794/+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 1626796] [NEW] There should show project name to make more sense

[qiaomin032]

Public bug reported:

1 Open Admin/SYSTEM/Floating IPs panel. 
2 Click into the floating ip detail page.
3 There only show the project ID in the detail page. 
There should also show the project name will make more sense.
Other detail page, such as Router, Network also have this issue.

** Affects: horizon
 Importance: Undecided
 Assignee: qiaomin032 (chen-qiaomin)
 Status: In Progress

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

Title:
  There should show project name to make more sense

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  1 Open Admin/SYSTEM/Floating IPs panel. 
  2 Click into the floating ip detail page.
  3 There only show the project ID in the detail page. 
  There should also show the project name will make more sense.
  Other detail page, such as Router, Network also have this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1626796/+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 1589821] Re: cleanup_incomplete_migrations periodic task regression with commit 099cf53 (CVE-2016-7498)

[Tristan Cacqueray]

** Changed in: ossa
   Status: In Progress => 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/1589821

Title:
  cleanup_incomplete_migrations periodic task regression with commit
  099cf53 (CVE-2016-7498)

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) mitaka series:
  Fix Committed
Status in OpenStack Security Advisory:
  Fix Released

Bug description:
  Patch [1] changes the instance filtering condition in periodic task
  "cleanup_incomplete_migrations" introduced in [2], in such a way that
  it generates new issue, [3]

  After change [1] lands,  the condition changes filtering logic, so now
  all instances on current host are filtered, which is not expected.

  We should filter all instances where instance uuids are associated
  with migration records and those migration status is set to 'error'
  and instance is marked as deleted.

  [1] https://review.openstack.org/#/c/256102/
  [2] https://review.openstack.org/#/c/219299/
  [2] https://bugs.launchpad.net/nova/+bug/1586309

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1589821/+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 1606056] [NEW] nova-api did not start

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

 Im doing a cloud-init install of a fresh ubuntu 14.04 image, straight
from the 'all in one VM' instructions and keep getting :

   
[ERROR] /home/stack/devstack/lib/nova:800 nova-api did not start
Error on exit
2016-07-24 19:28:12,017 - util.py[WARNING]: Failed running 
/var/lib/cloud/instance/scripts/runcmd [1]
2016-07-24 19:28:12,023 - cc_scripts_user.py[WARNING]: Failed to run module 
scripts-user (scripts in /var/lib/cloud/instance/scripts)
2016-07-24 19:28:12,023 - util.py[WARNING]: Running scripts-user () failed
ci-info: no authorized ssh keys fingerprints found for user stack.

What keys is it wanting? Ive tried adding various ssh keys to the stack
user, but nothing changes.


I would be asking on the forum, but the spam filter is not allowing any 
questions at all.

** Affects: nova
 Importance: Undecided
 Status: New

-- 
nova-api did not start
https://bugs.launchpad.net/bugs/1606056
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to OpenStack Compute (nova).

-- 
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 1606056] Re: nova-api did not start

[Tom Fifield]

** Project changed: openstack-community => nova

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

Title:
  nova-api did not start

Status in OpenStack Compute (nova):
  New

Bug description:
   Im doing a cloud-init install of a fresh ubuntu 14.04 image, straight
  from the 'all in one VM' instructions and keep getting :

 
  [ERROR] /home/stack/devstack/lib/nova:800 nova-api did not start
  Error on exit
  2016-07-24 19:28:12,017 - util.py[WARNING]: Failed running 
/var/lib/cloud/instance/scripts/runcmd [1]
  2016-07-24 19:28:12,023 - cc_scripts_user.py[WARNING]: Failed to run 
module scripts-user (scripts in /var/lib/cloud/instance/scripts)
  2016-07-24 19:28:12,023 - util.py[WARNING]: Running scripts-user () failed
  ci-info: no authorized ssh keys fingerprints found for user stack.

  What keys is it wanting? Ive tried adding various ssh keys to the
  stack user, but nothing changes.

  
  I would be asking on the forum, but the spam filter is not allowing any 
questions at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1606056/+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 1626827] [NEW] Fix pep8 E501 line too long

[Tony Xu]

Public bug reported:

Wrap line to under 79 characters

** Affects: nova
 Importance: Undecided
 Assignee: Tony Xu (hhktony)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Tony Xu (hhktony)

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

Title:
  Fix pep8 E501 line too long

Status in OpenStack Compute (nova):
  New

Bug description:
  Wrap line to under 79 characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1626827/+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 1626830] [NEW] Integration tests do not handle StaleElementReferenceException well

[Richard Jones]

Public bug reported:

The attached is an example of a test run that failed, I believe because
it is testing for text in a cell that is updated as the test is run.
Therefore the StaleElementReferenceException race condition

1. element is fetched,
2. element is removed from DOM
3. element is tested (specifically text content) -> 
StaleElementReferenceException

is triggered. The code in integration_tests/basewebobject.py
_wait_until() could be made more robust by handling the
StaleElementReferenceException and returning False (ie. no match).

An alternative is to have the test in question wait until the data being
updated is stable, but the specific test failure I see
(integration_tests/tests/test_instances:TestInstances.test_filter_instances)
will not be able to do this reliably, there is still a race condition
between the cell indicating instability and the cell indicating status.
I believe the most reliable solution here is to add robustness against
the StaleElementReferenceException race condition in the _wait_until
method.

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

Title:
  Integration tests do not handle StaleElementReferenceException well

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The attached is an example of a test run that failed, I believe
  because it is testing for text in a cell that is updated as the test
  is run. Therefore the StaleElementReferenceException race condition

  1. element is fetched,
  2. element is removed from DOM
  3. element is tested (specifically text content) -> 
StaleElementReferenceException

  is triggered. The code in integration_tests/basewebobject.py
  _wait_until() could be made more robust by handling the
  StaleElementReferenceException and returning False (ie. no match).

  An alternative is to have the test in question wait until the data
  being updated is stable, but the specific test failure I see
  (integration_tests/tests/test_instances:TestInstances.test_filter_instances)
  will not be able to do this reliably, there is still a race condition
  between the cell indicating instability and the cell indicating
  status. I believe the most reliable solution here is to add robustness
  against the StaleElementReferenceException race condition in the
  _wait_until method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1626830/+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 1626832] [NEW] Fix pep8 E501 line too long

[Tony Xu]

Public bug reported:

Wrap line to under 79 characters

** Affects: neutron
 Importance: Undecided
 Assignee: Tony Xu (hhktony)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => Tony Xu (hhktony)

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

Title:
  Fix pep8 E501 line too long

Status in neutron:
  New

Bug description:
  Wrap line to under 79 characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1626832/+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 1626832] Re: Fix pep8 E501 line too long

[Armando Migliaccio]

** Changed in: neutron
   Status: New => Opinion

** Changed in: neutron
   Status: Opinion => Invalid

** Changed in: neutron
 Assignee: Tony Xu (hhktony) => (unassigned)

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

Title:
  Fix pep8 E501 line too long

Status in neutron:
  Invalid

Bug description:
  Wrap line to under 79 characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1626832/+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 1626858] [NEW] The explanation of how to use the customization_module may confuse users.

[Kenji Ishii]

Public bug reported:

The explanation of how to use costomization_module is writtend by
http://docs.openstack.org/developer/horizon/topics/customizing.html
#horizon-customization-module-overrides.

And this sample code is below.

HORIZON_CONFIG = {
"customization_module": "my_project.overrides"
}

However, if a user do so, other attributes that HORIZON_CONFIG have are 
eliminated.
In latest horizon, it would caues circular redirect loop.
So, Avoiding confusing users, we should indicate more safe way like below.

HORIZON_CONFIG["customization_module"] = "my_project.overrides"

** Affects: horizon
 Importance: Undecided
 Assignee: Kenji Ishii (ken-ishii)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => Kenji Ishii (ken-ishii)

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

Title:
  The explanation of how to use the customization_module may confuse
  users.

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The explanation of how to use costomization_module is writtend by
  http://docs.openstack.org/developer/horizon/topics/customizing.html
  #horizon-customization-module-overrides.

  And this sample code is below.

  HORIZON_CONFIG = {
  "customization_module": "my_project.overrides"
  }

  However, if a user do so, other attributes that HORIZON_CONFIG have are 
eliminated.
  In latest horizon, it would caues circular redirect loop.
  So, Avoiding confusing users, we should indicate more safe way like below.

  HORIZON_CONFIG["customization_module"] = "my_project.overrides"

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