[Yahoo-eng-team] [Bug 1752499] [NEW] Container object download doesn't work in MSEdge

2018-02-28 Thread Robin Cernin 
Public bug reported:

Steps:

Log in to the dashboard.

Select the appropriate project from the drop down menu at the top left.

On the Project tab, open the Object Store tab and click Containers
category.

Select the container that you want to download the object from.

Download file.

Expected: File will be downloaded

Actual: Nothing happens

Environment: Pike

Browsers: MS Edge

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

Title:
  Container object download doesn't work in MSEdge

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Steps:

  Log in to the dashboard.

  Select the appropriate project from the drop down menu at the top
  left.

  On the Project tab, open the Object Store tab and click Containers
  category.

  Select the container that you want to download the object from.

  Download file.

  Expected: File will be downloaded

  Actual: Nothing happens

  Environment: Pike

  Browsers: MS Edge

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1752499/+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 1752463] [NEW] Attaching virtual GPU devices to guests in nova

2018-02-28 Thread John G. Fanelli 
Public bug reported:


This bug tracker is for errors with the documentation, use the following
as a template and remove or add fields as you see fit. Convert [ ] into
[x] to check boxes:


- [X] This is a doc addition request.
- [X] I have a fix to the document that I can paste below including example: 
input and output. 

Hi -- Fantastic news that NVIDIA vGPU is supported in OpenStack.  In
order for vGPU to work, it requires a vGPU driver that normally sits
behind a license portal. If an OpenStack user trys to use the non-vGPU
driver, it will not work and cause them to lose time debugging.

FREE evaluation drivers are available here: http://www.nvidia.com/object
/grid-evaluation.html

I would suggest adding wording to this effect to the page to same time
and frustration.

thank you

john fanelli
jfane...@nvidia.com


---
Release: 17.0.1.dev1 on 2018-02-28 15:54
SHA: 5039511840bd64151f3111d9c8d7d8a01344193b
Source: 
https://git.openstack.org/cgit/openstack/nova/tree/doc/source/admin/virtual-gpu.rst
URL: https://docs.openstack.org/nova/queens/admin/virtual-gpu.html

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

Title:
  Attaching virtual GPU devices to guests in nova

Status in OpenStack Compute (nova):
  New

Bug description:

  This bug tracker is for errors with the documentation, use the
  following as a template and remove or add fields as you see fit.
  Convert [ ] into [x] to check boxes:

  
  - [X] This is a doc addition request.
  - [X] I have a fix to the document that I can paste below including example: 
input and output. 

  Hi -- Fantastic news that NVIDIA vGPU is supported in OpenStack.  In
  order for vGPU to work, it requires a vGPU driver that normally sits
  behind a license portal. If an OpenStack user trys to use the non-vGPU
  driver, it will not work and cause them to lose time debugging.

  FREE evaluation drivers are available here:
  http://www.nvidia.com/object/grid-evaluation.html

  I would suggest adding wording to this effect to the page to same time
  and frustration.

  thank you

  john fanelli
  jfane...@nvidia.com

  
  ---
  Release: 17.0.1.dev1 on 2018-02-28 15:54
  SHA: 5039511840bd64151f3111d9c8d7d8a01344193b
  Source: 
https://git.openstack.org/cgit/openstack/nova/tree/doc/source/admin/virtual-gpu.rst
  URL: https://docs.openstack.org/nova/queens/admin/virtual-gpu.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1752463/+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 1468366] Re: [RFE] (Operator-only) Logging API for security group rules

2018-02-28 Thread Akihiro Motoki 
** Changed in: neutron
Milestone: queens-1 => queens-3

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

Title:
  [RFE] (Operator-only) Logging API for security group rules

Status in neutron:
  Fix Released

Bug description:
  Learning what happened on traffic flows is necessary for cloud
  administrator to tackle a problem related to network.

  Problem Description
  ===
  - When *operator* (including cloud administrator and developer) has an issue 
related to network (e.g network security issue). Gathering all events related 
to security groups is necessary for troubleshooting process.

  - When tenant or operator deploys a security groups for number of VMs.
  They want to make sure security group rules work as expected and to
  assess what kinds of packets went through their security-groups or
  were dropped.

  Currently, we don't have a way to perform that. In other word, logging
  is a missing feature in security groups.

  Proposed Change
  ===
  - To improve the situation, we'd like to propose a logging API [1]_ to 
collect all events related to security group rules when they occurred.

  - Only *operator* will be allowed to execute logging API.

  - Layout the logging API model can extend to other resource such as
  firewall.

  [1] https://review.openstack.org/#/c/203509/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1468366/+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 1752360] Re: Launching instance with volume created from snapshot doesn't honor original image min_disk

2018-02-28 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/548629
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=3233de8f0d13ad9e0223da9f1cf895aa30a6177e
Submitter: Zuul
Branch:master

commit 3233de8f0d13ad9e0223da9f1cf895aa30a6177e
Author: Beth Elwell 
Date:   Wed Feb 28 15:52:06 2018 +

Add same launch instance error handling as image to instance

Previously, when launching an instance with an instance snapshot rather
than with an image, the error handling was not as pleasant. I.e. the
volume size was not automatically set to the minimum size and the error
message would only appear after attempting to launch an instance. This
is a small patch that addresses this and makes the user experience more
friendly.

Change-Id: Ib694f66c74e90ee2e15201673de953c08cf10122
Closes-bug: #1752360


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

Title:
  Launching instance with volume created from snapshot doesn't honor
  original image min_disk

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  When launching from Horizon an instance with volume creation from an
  image with a min-disk parameter :

  * the volume size (GB) is automatically set to the minimum size
  * if I choose a volume size inferior to this minimum size I get an error 
message: "The Volume size must be at least xxGB).

  However, when trying to launch an instance with instance snapshot, the
  behaviour is much less user friendly:

  * the Volume Size (GB) field is not automatically filled in with the minimum 
size
  * the error message is not displayed before you click on the Launch Instance 
button

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1752360/+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 1752418] [NEW] fs017: failure to delete IP causing tempest failures

2018-02-28 Thread Matt Young 
Public bug reported:

master promotion is being blocked by a failure in periodic-multinode-
1ctlr-featureset017

master: 66b3734b4a57941c2d66dfc7d7961b2925c46b92_e4e594a6

---

http://38.145.34.55/master.log

2018-02-28 20:21:26,221 2381 INFO promoter Skipping promotion of
tripleo-ci-testing to current-tripleo, missing successful jobs:
['periodic-multinode-1ctlr-featureset016', 'periodic-multinode-1ctlr-
featureset017', 'periodic-multinode-1ctlr-featureset019']

---

It appears that tempest is failing telemetry tests:

- https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-
centos-7-multinode-1ctlr-featureset017-master/45442f0/tempest.html.gz

(hypothesis from mwhahaha) a failure to delete an IP, or failing to
delete it fast enough is causing this

- https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-
centos-7-multinode-1ctlr-
featureset017-master/45442f0/subnode-2/var/log/containers/neutron/server.log.txt.gz#_2018-02-28_19_13_39_116

---

2018-02-28 19:13:38.980 27 INFO neutron.wsgi 
[req-8500f497-a51a-45b6-9713-5d4fd8bcb500 c090e652604f44a08d3498250ad90595 
f0f25c526c484052ab6b4af65d114e51 - default default] 192.168.24.3 "DELETE 
/v2.0/routers/c8260734-ffe9-4450-a3c7-a4cff0fdc42e HTTP/1.1" status: 204  len: 
168 time: 1.3387601
2018-02-28 19:13:38.982 27 DEBUG neutron.wsgi [-] (27) accepted 
('192.168.24.3', 53010) server 
/usr/lib/python2.7/site-packages/eventlet/wsgi.py:883
2018-02-28 19:13:39.041 27 DEBUG neutron.db.db_base_plugin_v2 
[req-eef89b52-7b20-497b-af68-f575151fed76 c090e652604f44a08d3498250ad90595 
f0f25c526c484052ab6b4af65d114e51 - default default] Deleting subnet 
87f0f9b4-edab-454d-a7d9-0144816b54b5 delete_subnet 
/usr/lib/python2.7/site-packages/neutron/db/db_base_plugin_v2.py:999
2018-02-28 19:13:39.042 27 DEBUG neutron_lib.callbacks.manager 
[req-eef89b52-7b20-497b-af68-f575151fed76 c090e652604f44a08d3498250ad90595 
f0f25c526c484052ab6b4af65d114e51 - default default] Notify callbacks [] for 
subnet, before_delete _notify_loop 
/usr/lib/python2.7/site-packages/neutron_lib/callbacks/manager.py:167
2018-02-28 19:13:39.116 27 INFO neutron.db.db_base_plugin_v2 
[req-eef89b52-7b20-497b-af68-f575151fed76 c090e652604f44a08d3498250ad90595 
f0f25c526c484052ab6b4af65d114e51 - default default] Found port 
(48798d40-cdc3-415a-9244-2dfaac84f134, 10.100.0.6) having IP allocation on 
subnet 87f0f9b4-edab-454d-a7d9-0144816b54b5, cannot delete
2018-02-28 19:13:39.118 27 INFO neutron.pecan_wsgi.hooks.translation 
[req-eef89b52-7b20-497b-af68-f575151fed76 c090e652604f44a08d3498250ad90595 
f0f25c526c484052ab6b4af65d114e51 - default default] DELETE failed (client 
error): There was a conflict when trying to complete your request.
2018-02-28 19:13:39.118 27 DEBUG neutron.pecan_wsgi.hooks.notifier 
[req-eef89b52-7b20-497b-af68-f575151fed76 c090e652604f44a08d3498250ad90595 
f0f25c526c484052ab6b4af65d114e51 - default default] No notification will be 
sent due to unsuccessful status code: 409 after 
/usr/lib/python2.7/site-packages/neutron/pecan_wsgi/hooks/notifier.py:79

** Affects: neutron
 Importance: Undecided
 Status: Invalid

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

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

Title:
  fs017: failure to delete IP causing tempest failures

Status in neutron:
  Invalid

Bug description:
  master promotion is being blocked by a failure in periodic-multinode-
  1ctlr-featureset017

  master: 66b3734b4a57941c2d66dfc7d7961b2925c46b92_e4e594a6

  ---

  http://38.145.34.55/master.log

  2018-02-28 20:21:26,221 2381 INFO promoter Skipping promotion of
  tripleo-ci-testing to current-tripleo, missing successful jobs:
  ['periodic-multinode-1ctlr-featureset016', 'periodic-multinode-1ctlr-
  featureset017', 'periodic-multinode-1ctlr-featureset019']

  ---

  It appears that tempest is failing telemetry tests:

  - https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-
  centos-7-multinode-1ctlr-featureset017-master/45442f0/tempest.html.gz

  (hypothesis from mwhahaha) a failure to delete an IP, or failing to
  delete it fast enough is causing this

  - https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-
  centos-7-multinode-1ctlr-
  
featureset017-master/45442f0/subnode-2/var/log/containers/neutron/server.log.txt.gz#_2018-02-28_19_13_39_116

  ---

  2018-02-28 19:13:38.980 27 INFO neutron.wsgi 
[req-8500f497-a51a-45b6-9713-5d4fd8bcb500 c090e652604f44a08d3498250ad90595 
f0f25c526c484052ab6b4af65d114e51 - default default] 192.168.24.3 "DELETE 
/v2.0/routers/c8260734-ffe9-4450-a3c7-a4cff0fdc42e HTTP/1.1" status: 204  len: 
168 time: 1.3387601
  2018-02-28 19:13:38.982 27 DEBUG neutron.wsgi [-] (27) accepted 
('192.168.24.3', 53010) server 
/usr/lib/python2.7/site-packages/eventlet/wsgi.py:883
  2018-02-28 19:13:39.041 27 DEBUG neutron.db.db_base_plugin_v2

[Yahoo-eng-team] [Bug 1752391] Re: cloud-init does not recognize initramfs provided network config in all cases

2018-02-28 Thread Scott Moser 
** Also affects: cloud-init
   Importance: Undecided
   Status: New

** Changed in: cloud-init
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu)
   Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  cloud-init does not recognize initramfs provided network config in all
  cases

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed

Bug description:
  Cloud-init relies on the 'ip=' or 'ip6=' parameter to be present in the
  kernel command line in order to consider /run/net-*.conf files.  Those files
  are written by the initramfs indicating that network is was configured.

  When 'ip=' or 'ip6=' is found on the command line, cloud-init will consider
  that to be "kernel command line provided" network, and renders a network
  configuration like:
# control-manual ens3
iface ens3 inet dhcp
broadcast 10.0.3.255
dns-nameservers 169.254.169.254
gateway 10.0.3.1

  The key there being that it is not marked 'auto'.  If cloud-init does
  not recognize this, it will render:
auto ens3
iface ens3 inet dhcp

  There are some iscsi-root where initramfs configures networking
  but the ip= parameter is not present.  2 such cases are:
   a.) static config in /etc/iscsi/iscsi.initramfs (copied into the initramfs)
   b.) iBft

  If the devices are marked 'auto', then 'networking.service' takes
  the device down during shutdown.  That causes any filesystem activity
  to hang and block shutdown/reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cloud-init 17.1-46-g7acc9e68-0ubuntu1~16.04.1 [modified: 
usr/lib/python3/dist-packages/cloudinit/net/cmdline.py 
usr/lib/python3/dist-packages/cloudinit/sources/helpers/openstack.py]
  ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98
  Uname: Linux 4.4.0-108-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CloudName: OpenStack
  Date: Wed Feb 28 18:35:50 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1752391/+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 1752382] [NEW] Install and configure in keystone

2018-02-28 Thread Alain Edwards 
Public bug reported:


This bug tracker is for errors with the documentation, use the following
as a template and remove or add fields as you see fit. Convert [ ] into
[x] to check boxes:

- [X ] This doc is inaccurate in this way: Keystone Endpoints
- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: 
input and output. 

In the keystone install and configure guide Openstack (Ostack) specifies
to bootstrap the keystone server with the command below; which specifies
the endpoints to be http://controller:5000/v3/ (ending with a slash). On
the other hand, in the OStack Dashboard (i.e. Horizon)install and
configure guide (https://docs.openstack.org/horizon/pike/install
/install-ubuntu.html) under the `Enable the Identity API version 3`
setting there is no forward slash (OPENSTACK_KEYSTONE_URL =
"http://%s:5000/v3; % OPENSTACK_HOST); thus resulting in the dashboard
failing to authenticate.

One last thing, when I installed the OStack dashboard package using apt
the `/etc/openstack-dashboard/local_settings.py` file had
`OPENSTACK_KEYSTONE_URL = "http://%s:5000/v2.0; % OPENSTACK_HOST`
instead of `OPENSTACK_KEYSTONE_URL = "http://%s:5000/v3; %
OPENSTACK_HOST`. The Git repo has the correct endpoint though, so I
figure a new release is coming with a fix.

Keystone Bootstrap Command:
keystone-manage bootstrap --bootstrap-password ADMIN_PASS \
  --bootstrap-admin-url http://controller:35357/v3/ \
  --bootstrap-internal-url http://controller:5000/v3/ \
  --bootstrap-public-url http://controller:5000/v3/ \
  --bootstrap-region-id RegionOne

---
Release: 12.0.1.dev17 on 2018-02-20 08:16
SHA: 6de0a147d68042af79ddc6d700cec3fd71b9d03c
Source: 
https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/install/keystone-install-ubuntu.rst
URL: 
https://docs.openstack.org/keystone/pike/install/keystone-install-ubuntu.html

** Affects: keystone
 Importance: Undecided
 Status: New


** Tags: dashboard doc enpoint horizon keyston openstack

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

Title:
  Install and configure in keystone

Status in OpenStack Identity (keystone):
  New

Bug description:

  This bug tracker is for errors with the documentation, use the
  following as a template and remove or add fields as you see fit.
  Convert [ ] into [x] to check boxes:

  - [X ] This doc is inaccurate in this way: Keystone Endpoints
  - [ ] This is a doc addition request.
  - [ ] I have a fix to the document that I can paste below including example: 
input and output. 

  In the keystone install and configure guide Openstack (Ostack)
  specifies to bootstrap the keystone server with the command below;
  which specifies the endpoints to be http://controller:5000/v3/ (ending
  with a slash). On the other hand, in the OStack Dashboard (i.e.
  Horizon)install and configure guide
  (https://docs.openstack.org/horizon/pike/install/install-ubuntu.html)
  under the `Enable the Identity API version 3` setting there is no
  forward slash (OPENSTACK_KEYSTONE_URL = "http://%s:5000/v3; %
  OPENSTACK_HOST); thus resulting in the dashboard failing to
  authenticate.

  One last thing, when I installed the OStack dashboard package using
  apt the `/etc/openstack-dashboard/local_settings.py` file had
  `OPENSTACK_KEYSTONE_URL = "http://%s:5000/v2.0; % OPENSTACK_HOST`
  instead of `OPENSTACK_KEYSTONE_URL = "http://%s:5000/v3; %
  OPENSTACK_HOST`. The Git repo has the correct endpoint though, so I
  figure a new release is coming with a fix.

  Keystone Bootstrap Command:
  keystone-manage bootstrap --bootstrap-password ADMIN_PASS \
--bootstrap-admin-url http://controller:35357/v3/ \
--bootstrap-internal-url http://controller:5000/v3/ \
--bootstrap-public-url http://controller:5000/v3/ \
--bootstrap-region-id RegionOne

  ---
  Release: 12.0.1.dev17 on 2018-02-20 08:16
  SHA: 6de0a147d68042af79ddc6d700cec3fd71b9d03c
  Source: 
https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/install/keystone-install-ubuntu.rst
  URL: 
https://docs.openstack.org/keystone/pike/install/keystone-install-ubuntu.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1752382/+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 1737207] Re: Guest admin password and network information is logged at debug if libvirt.inject_partition != -2

2018-02-28 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/526772
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=6839630e86d958dcda8585664586754d419363a7
Submitter: Zuul
Branch:master

commit 6839630e86d958dcda8585664586754d419363a7
Author: Matt Riedemann 
Date:   Fri Dec 8 16:02:44 2017 -0500

libvirt: mask InjectionInfo.admin_pass

Logging network information and the admin password
for guest instances is not ideal, so let's not do it.

Change-Id: I328ba88b128c6c125e65d850ed7a6e57049dc7e2
Closes-Bug: #1737207


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

Title:
  Guest admin password and network information is logged at debug if
  libvirt.inject_partition != -2

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  In Progress
Status in OpenStack Compute (nova) pike series:
  In Progress
Status in OpenStack Compute (nova) queens series:
  In Progress

Bug description:
  When using the libvirt driver and the inject_partition config option
  is != -2 (disabled), the driver will log the network information and
  admin password about the guest during disk injection:

  http://logs.openstack.org/50/524750/1/check/legacy-tempest-dsvm-
  neutron-full-
  centos-7/a7f051e/logs/screen-n-cpu.txt.gz#_Dec_04_13_42_41_311316

  Dec 04 13:42:41.311316 centos-7-rax-dfw-0001196569 nova-compute[7962]: DEBUG 
nova.virt.libvirt.driver [None req-80dab566-372b-43d7-88f9-d807cc9cb673 service 
nova] [instance: 941f8290-5e14-4b53-85c9-c5045de9a067] Checking root disk 
injection InjectionInfo(network_info=[{"profile": {}, "ovs_interfaceid": 
"56e5a50e-d30e-4814-aee3-fcc9525d12ca", "preserve_on_delete": false, "network": 
{"bridge": "br-int", "subnets": [{"ips": [{"meta": {}, "version": 4, "type": 
"fixed", "floating_ips": [], "address": "10.1.0.6"}], "version": 4, "meta": 
{"dhcp_server": "10.1.0.2"}, "dns": [], "routes": [], "cidr": "10.1.0.0/28", 
"gateway": {"meta": {}, "version": 4, "type": "gateway", "address": 
"10.1.0.1"}}], "meta": {"injected": false, "tenant_id": 
"77504d716f9d4f38a021cbfa4f0e28ee", "mtu": 1450}, "id": 
"766bb2bf-e1c0-43b8-8800-5737351e9a03", "label": 
"tempest-ServersTestJSON-518988576-network"}, "devname": "tap56e5a50e-d3", 
"vnic_type": "normal", "qbh_params": null, "meta": {}, "details": 
{"port_filter": true, "datapath_type": "system", "ovs_hybrid_plug": true}, 
"address": "fa:16:3e:d3:8e:f8", "active": false, "type": "ovs", "id": 
"56e5a50e-d30e-4814-aee3-fcc9525d12ca", "qbg_params": null}], files=[], 
admin_pass=u'V2^cP#tYp*=UD&7') {{(pid=7962) _inject_data 
/opt/stack/new/nova/nova/virt/libvirt/driver.py:3115}}
  Dec 04 13:42:41.314687 centos-7-rax-dfw-0001196569 nova-compute[7962]: DEBUG 
nova.virt.libvirt.driver [None req-80dab566-372b-43d7-88f9-d807cc9cb673 service 
nova] [instance: 941f8290-5e14-4b53-85c9-c5045de9a067] Injecting 
InjectionInfo(network_info=[{"profile": {}, "ovs_interfaceid": 
"56e5a50e-d30e-4814-aee3-fcc9525d12ca", "preserve_on_delete": false, "network": 
{"bridge": "br-int", "subnets": [{"ips": [{"meta": {}, "version": 4, "type": 
"fixed", "floating_ips": [], "address": "10.1.0.6"}], "version": 4, "meta": 
{"dhcp_server": "10.1.0.2"}, "dns": [], "routes": [], "cidr": "10.1.0.0/28", 
"gateway": {"meta": {}, "version": 4, "type": "gateway", "address": 
"10.1.0.1"}}], "meta": {"injected": false, "tenant_id": 
"77504d716f9d4f38a021cbfa4f0e28ee", "mtu": 1450}, "id": 
"766bb2bf-e1c0-43b8-8800-5737351e9a03", "label": 
"tempest-ServersTestJSON-518988576-network"}, "devname": "tap56e5a50e-d3", 
"vnic_type": "normal", "qbh_params": null, "meta": {}, "details": 
{"port_filter": true, "datapath_type": "system", "ovs_hybrid_plug": true}, 
"address": "fa:16:3e:d3:8e:f8", "active": false, "type": "ovs", "id": 
"56e5a50e-d30e-4814-aee3-fcc9525d12ca", "qbg_params": null}], files=[], 
admin_pass=u'V2^cP#tYp*=UD&7') {{(pid=7962) _inject_data 
/opt/stack/new/nova/nova/virt/libvirt/driver.py:3146}}

  This was introduced in Ocata (15.0.0):
  https://review.openstack.org/#/c/337790/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1737207/+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 1751349] Re: Keystone auth parameters cannot be configured in [keystone] section

2018-02-28 Thread Tony Breeds 
** Changed in: nova/pike
   Status: New => Invalid

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

Title:
  Keystone auth parameters cannot be configured in [keystone] section

Status in OpenStack Compute (nova):
  Invalid
Status in OpenStack Compute (nova) pike series:
  Invalid

Bug description:
  I am seeing nova-api attempting to use the keystone public endpoint
  when /v2.1/os-quota-sets is called on my Pike deployment. This is not
  valid in my environment; the API must use the internal endpoint to
  reach keystone. When the public endpoint is used, the connection sits
  in SYN_SENT state in netstat until it times out after a minute or two.

  Hacking the endpoint_filter at
  
https://github.com/openstack/nova/blob/d536bec9fc098c9db8d46f39aab30feb0783e428/nova/api/openstack/identity.py#L43-L46
  to include interface=internal fixes the issue.

  Unless I am mistaken this issue still exists in master:
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/api/openstack/identity.py#L33-L35

  Something similar to the [placement] section should be implemented
  allowing os_interface to be configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1751349/+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 1752360] [NEW] Launching instance with volume created from snapshot doesn't honor original image min_disk

2018-02-28 Thread Beth Elwell 
Public bug reported:

When launching from Horizon an instance with volume creation from an
image with a min-disk parameter :

* the volume size (GB) is automatically set to the minimum size
* if I choose a volume size inferior to this minimum size I get an error 
message: "The Volume size must be at least xxGB).

However, when trying to launch an instance with instance snapshot, the
behaviour is much less user friendly:

* the Volume Size (GB) field is not automatically filled in with the minimum 
size
* the error message is not displayed before you click on the Launch Instance 
button

** Affects: horizon
 Importance: Undecided
 Assignee: Beth Elwell (bethelwell)
 Status: In Progress

** Changed in: horizon
 Assignee: (unassigned) => Beth Elwell (bethelwell)

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

Title:
  Launching instance with volume created from snapshot doesn't honor
  original image min_disk

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  When launching from Horizon an instance with volume creation from an
  image with a min-disk parameter :

  * the volume size (GB) is automatically set to the minimum size
  * if I choose a volume size inferior to this minimum size I get an error 
message: "The Volume size must be at least xxGB).

  However, when trying to launch an instance with instance snapshot, the
  behaviour is much less user friendly:

  * the Volume Size (GB) field is not automatically filled in with the minimum 
size
  * the error message is not displayed before you click on the Launch Instance 
button

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1752360/+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 1737201] Re: TypeError when sending notification during attach_interface

2018-02-28 Thread Tony Breeds 
** Also affects: nova/pike
   Importance: Undecided
   Status: New

** Also affects: nova/ocata
   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/1737201

Title:
  TypeError when sending notification during attach_interface

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  New
Status in OpenStack Compute (nova) pike series:
  New

Bug description:
  http://logs.openstack.org/50/524750/1/check/legacy-tempest-dsvm-
  neutron-
  full/eb8d805/logs/screen-n-api.txt.gz?level=TRACE#_Dec_04_13_34_20_635874

  Dec 04 13:34:20.635874 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: ERROR nova.api.openstack.extensions [None 
req-2d1b063f-1324-4498-af68-ce48c6d8e5a3 
tempest-AttachInterfacesTestJSON-149718191 
tempest-AttachInterfacesTestJSON-149718191] Unexpected exception in API method: 
TypeError: 'NoneType' object has no attribute '__getitem__'
  Dec 04 13:34:20.636066 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: Traceback (most recent call last):
  Dec 04 13:34:20.636202 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 
163, in _process_incoming
  Dec 04 13:34:20.636336 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: res = self.dispatcher.dispatch(message)
  Dec 04 13:34:20.636474 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
220, in dispatch
  Dec 04 13:34:20.636614 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: return self._do_dispatch(endpoint, method, 
ctxt, args)
  Dec 04 13:34:20.636745 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
190, in _do_dispatch
  Dec 04 13:34:20.636892 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: result = func(ctxt, **new_args)
  Dec 04 13:34:20.637049 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 76, in wrapped
  Dec 04 13:34:20.637187 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: function_name, call_dict, binary)
  Dec 04 13:34:20.637317 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  Dec 04 13:34:20.637442 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: self.force_reraise()
  Dec 04 13:34:20.637607 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  Dec 04 13:34:20.637761 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: six.reraise(self.type_, self.value, self.tb)
  Dec 04 13:34:20.637895 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 67, in wrapped
  Dec 04 13:34:20.638044 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: return f(self, context, *args, **kw)
  Dec 04 13:34:20.638183 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/opt/stack/new/nova/nova/compute/utils.py", line 930, in decorated_function
  Dec 04 13:34:20.638306 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: return function(self, context, *args, 
**kwargs)
  Dec 04 13:34:20.638433 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/opt/stack/new/nova/nova/compute/manager.py", line 215, in decorated_function
  Dec 04 13:34:20.638566 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: kwargs['instance'], e, sys.exc_info())
  Dec 04 13:34:20.638696 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  Dec 04 13:34:20.638820 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: self.force_reraise()
  Dec 04 13:34:20.638953 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  Dec 04 13:34:20.639076 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]: six.reraise(self.type_, self.value, self.tb)
  Dec 04 13:34:20.639200 ubuntu-xenial-inap-mtl01-0001196572 
devstack@n-api.service[6808]:   File 
"/opt/stack/new/nova/nova/compute/manager.py", line 203, in decorated_function
  Dec 04 13:34:20.639325 ubuntu-xenial-inap-mtl01-0001196572

[Yahoo-eng-team] [Bug 1752340] [NEW] inconsistent use of units like GiB and GB in the documentation

2018-02-28 Thread Balazs Gibizer 
Public bug reported:

In the nova documentation the power of 2 (GiB, MiB) and the power of 10
(GB, MB) units are used inconsistently.

Examples:

ebalgib@elxa95hld12:~/upstream/git/nova/doc$ egrep -n -e '(GB)|(GiB)' -R 
../api-ref/
../api-ref/source/parameters.yaml:910:Filters the response by a minimum 
disk space, in GiB. For example, ``100``.
../api-ref/source/parameters.yaml:1557:Amount of disk in GiB the node has.
../api-ref/source/parameters.yaml:2075:The actual free disk on this 
hypervisor(in GB).
../api-ref/source/parameters.yaml:2492:The size of the root disk that will 
be created in GiB. If 0 the
../api-ref/source/parameters.yaml:2504:The size of the root disk that was 
created in GiB.
../api-ref/source/parameters.yaml:2511:GiB. Ephemeral disks may be written 
over on server state
../api-ref/source/parameters.yaml:2520:The size of the ephemeral disk that 
was created, in GiB.
../api-ref/source/parameters.yaml:2527:GiB. Ephemeral disks may be written 
over on server state
../api-ref/source/parameters.yaml:2941:The disk size on the host (in GB).
../api-ref/source/parameters.yaml:3158:The free disk remaining on this 
hypervisor(in GB).
../api-ref/source/parameters.yaml:3855:The disk in this hypervisor(in GB).
../api-ref/source/parameters.yaml:3862:the ephemeral disk size of it (in 
GiB).
../api-ref/source/parameters.yaml:3869:the ephemeral disk size of it (in 
GiB).
../api-ref/source/parameters.yaml:3875:The disk used in this hypervisor(in 
GB).
../api-ref/source/parameters.yaml:4169:The minimum amount of disk space an 
image requires to boot, in GiB. For example, ``100``.
../api-ref/source/parameters.yaml:5553:The size of the volume, in gibibytes 
(GiB).
../api-ref/source/parameters.yaml:5794:Multiplying the server disk size (in 
GiB) by hours the server exists,

ebalgib@elxa95hld12:~/upstream/git/nova/doc$ egrep -n -e '(MB)|(MiB)' -R 
../api-ref/
../api-ref/source/parameters.yaml:916:Filters the response by a minimum 
RAM, in MB. For example, ``512``.
../api-ref/source/parameters.yaml:1590:Amount of memory in MiB the node has.
../api-ref/source/parameters.yaml:2627:The amount of RAM a flavor has, in 
MiB.
../api-ref/source/parameters.yaml:2633:The amount of RAM a flavor has, in 
MiB.
../api-ref/source/parameters.yaml:2669:MiB. If 0 (the default), no 
dedicated swap disk will be created.
../api-ref/source/parameters.yaml:2676:The size of a dedicated swap disk 
that was allocated, in MiB.
../api-ref/source/parameters.yaml:2684:MiB. If 0 (the default), no 
dedicated swap disk will be created.
../api-ref/source/parameters.yaml:2888:The free RAM in this hypervisor(in 
MB).
../api-ref/source/parameters.yaml:2972:The memory size on the host (in MB).
../api-ref/source/parameters.yaml:3933:- ``maximum`` - Amount of memory 
provisioned for the VM in MB (Integer)
../api-ref/source/parameters.yaml:3936:  system and its applications in MB 
(Integer)
../api-ref/source/parameters.yaml:3943:The memory of this hypervisor(in MB).
../api-ref/source/parameters.yaml:3949:The memory size of the server (in 
MB).
../api-ref/source/parameters.yaml:3955:The memory size of the server (in 
MB).
../api-ref/source/parameters.yaml:3961:The memory used in this 
hypervisor(in MB).
../api-ref/source/parameters.yaml:4175:The minimum amount of RAM an image 
requires to function, in MB. For example, ``512``.
../api-ref/source/parameters.yaml:4886:The amount of allowed server RAM, in 
MB, for each tenant.
../api-ref/source/parameters.yaml:4893:The amount of allowed instance RAM, 
in MB, for the quota class.
../api-ref/source/parameters.yaml:4906:The amount of allowed server RAM, in 
MB, for each tenant.
../api-ref/source/parameters.yaml:5801:Multiplying the server memory size 
(in MB) by hours the server exists,

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: api-ref doc docs

** Tags added: doc docs

** Tags added: api-ref

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

Title:
  inconsistent use of units like GiB and GB in the documentation

Status in OpenStack Compute (nova):
  New

Bug description:
  In the nova documentation the power of 2 (GiB, MiB) and the power of
  10 (GB, MB) units are used inconsistently.

  Examples:

  ebalgib@elxa95hld12:~/upstream/git/nova/doc$ egrep -n -e '(GB)|(GiB)' -R 
../api-ref/
  ../api-ref/source/parameters.yaml:910:Filters the response by a minimum 
disk space, in GiB. For example, ``100``.
  ../api-ref/source/parameters.yaml:1557:Amount of disk in GiB the node has.
  ../api-ref/source/parameters.yaml:2075:The actual free disk on this 
hypervisor(in GB).
  ../api-ref/source/parameters.yaml:2492:The size of the root disk that 
will be created in GiB. If 0 the

[Yahoo-eng-team] [Bug 1752289] Re: ServiceCatalog does not contain "network" service

2018-02-28 Thread Matt Riedemann 
This is likely related to
https://github.com/openstack/nova/commit/6cde77ebbab85bc8ccd2ab7ad977b1d4af4a13fa
if it's a regression in Queens.

** Tags added: queens-backport-potential

** Also affects: nova/queens
   Importance: Undecided
   Status: New

** Changed in: nova/queens
   Status: New => Confirmed

** Changed in: nova
   Importance: Undecided => High

** Changed in: nova/queens
   Importance: Undecided => High

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

Title:
  ServiceCatalog does not contain "network" service

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) queens series:
  Confirmed

Bug description:
  On SLE12SP3, openstack-nova 17.0.0.0~xrc2~dev160-1.1, I try to boot an
  cirros instance and get:

  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager 
[req-53fa6935-f60d-4e07-bc75-14b6a5336330 f80483de8573468b869e64262780a903 
d9685d1130d74a73af6ee213c421d9de - default default] [instance: 
0ae671f6-5241-486f-9054-1100b124f704] Instance failed to spawn: 
EndpointNotFound: ['internal', 'public'] endpoint for network service not found
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] Traceback (most recent call last):
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2236, in 
_build_resources
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] yield resources
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2019, in 
_build_and_run_instance
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] block_device_info=block_device_info)
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3011, in 
spawn
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] mdevs=mdevs)
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 5256, in 
_get_guest_xml
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] network_info_str = str(network_info)
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/network/model.py", line 568, in __str__
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] return self._sync_wrapper(fn, *args, 
**kwargs)
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/network/model.py", line 551, in 
_sync_wrapper
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] self.wait()
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/network/model.py", line 583, in wait
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] self[:] = self._gt.wait()
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 175, in wait
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] return self._exit_event.wait()
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/eventlet/event.py", line 125, in wait
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] current.throw(*self._exc)
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 214, in main
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] result = function(*args, **kwargs)
  2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/utils.py", line 906, in

[Yahoo-eng-team] [Bug 1752312] Re: Cannot include custom js in tacker-horizon

2018-02-28 Thread Trinh Nguyen 
** Summary changed:

- Cannot include custom js from tacker-horizon
+ Cannot include custom js in tacker-horizon

** Changed in: horizon
   Status: New => Invalid

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

Title:
  Cannot include custom js in tacker-horizon

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Hello,

  I'm trying to update the Tacker Horizon UI with some custom js in this
  directory:

  tacker-
  horizon/tacker_horizon/openstack_dashboard/dashboards/nfv/static/nfv/js/nfv.js

  But I got this error logs:

  OfflineGenerationError: You have offline compression enabled but key
  "7d4e238898d4d476fa5b96bb1f88b45077496f67923c28950054d4747083740a" is
  missing from offline manifest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1752312/+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 1596829] Re: String interpolation should be delayed at logging calls

2018-02-28 Thread Akihiro Motoki 
** No longer affects: horizon

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

Title:
  String interpolation should be delayed at logging calls

Status in congress:
  Fix Released
Status in ec2-api:
  Confirmed
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in Glare:
  Fix Released
Status in Ironic:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in masakari:
  Fix Released
Status in networking-vsphere:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in os-brick:
  Fix Released
Status in os-vif:
  Fix Released
Status in Glance Client:
  Fix Released
Status in python-manilaclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in python-troveclient:
  Fix Released
Status in senlin:
  Invalid
Status in watcher:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  String interpolation should be delayed to be handled by the logging
  code, rather than being done at the point of the logging call.

  Wrong: LOG.debug('Example: %s' % 'bad')
  Right: LOG.debug('Example: %s', 'good')

  See the following guideline.

  * http://docs.openstack.org/developer/oslo.i18n/guidelines.html
  #adding-variables-to-log-messages

  The rule for it should be added to hacking checks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/congress/+bug/1596829/+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 1752312] [NEW] Cannot include custom js from tacker-horizon

2018-02-28 Thread Trinh Nguyen 
Public bug reported:

Hello,

I'm trying to update the Tacker Horizon UI with some custom js in this
directory:

tacker-
horizon/tacker_horizon/openstack_dashboard/dashboards/nfv/static/nfv/js/nfv.js

But I got this error logs:

OfflineGenerationError: You have offline compression enabled but key
"7d4e238898d4d476fa5b96bb1f88b45077496f67923c28950054d4747083740a" is
missing from offline manifest.

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

Title:
  Cannot include custom js from tacker-horizon

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Hello,

  I'm trying to update the Tacker Horizon UI with some custom js in this
  directory:

  tacker-
  horizon/tacker_horizon/openstack_dashboard/dashboards/nfv/static/nfv/js/nfv.js

  But I got this error logs:

  OfflineGenerationError: You have offline compression enabled but key
  "7d4e238898d4d476fa5b96bb1f88b45077496f67923c28950054d4747083740a" is
  missing from offline manifest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1752312/+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 1699060] Re: Impossible to define policy rule based on domain ID

2018-02-28 Thread Alexander Chadin 
** Changed in: watcher
   Importance: Undecided => Wishlist

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

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

Title:
  Impossible to define policy rule based on domain ID

Status in Glance:
  New
Status in OpenStack Heat:
  Triaged
Status in Manila:
  Opinion
Status in neutron:
  Opinion
Status in OpenStack Compute (nova):
  Opinion
Status in oslo.policy:
  New
Status in watcher:
  Opinion

Bug description:
  We have common approach to set rules for each API using policy.json file.
  And for the moment, it is not possible to use "domain_id" in policy rules,
  only "project_id" and "user_id". It becomes very important because Keystone 
API v3 is used more and more.
  The only service that supports rules with "domain_id" is Keystone itself.

  As a result we should be able to use following rules:
  "admin_or_domain_owner": "is_admin:True or domain_id:%(domain_id)s",
  "domain_owner": "domain_id:%(domain_id)s",

  like this:

  "volume:get": "rule:domain_owner",

  or

  "volume:get": "rule:admin_or_domain_owner",

  Right now, we always get 403 error having such rules.

  Related mail-list thread: https://openstack.nimeyo.com/115438
  /openstack-dev-all-policy-rules-for-apis-based-on-domain_id

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1699060/+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 1596829] Re: String interpolation should be delayed at logging calls

2018-02-28 Thread Alexander Chadin 
** Changed in: watcher
   Status: Fix Committed => Fix Released

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

Title:
  String interpolation should be delayed at logging calls

Status in congress:
  Fix Released
Status in ec2-api:
  Confirmed
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in Glare:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in masakari:
  Fix Released
Status in networking-vsphere:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in os-brick:
  Fix Released
Status in os-vif:
  Fix Released
Status in Glance Client:
  Fix Released
Status in python-manilaclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in python-troveclient:
  Fix Released
Status in senlin:
  Invalid
Status in watcher:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  String interpolation should be delayed to be handled by the logging
  code, rather than being done at the point of the logging call.

  Wrong: LOG.debug('Example: %s' % 'bad')
  Right: LOG.debug('Example: %s', 'good')

  See the following guideline.

  * http://docs.openstack.org/developer/oslo.i18n/guidelines.html
  #adding-variables-to-log-messages

  The rule for it should be added to hacking checks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/congress/+bug/1596829/+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 1752301] [NEW] Project tags treats entire collection as a single tag

2018-02-28 Thread Gage Hugo 
Public bug reported:

When backporting Debian stable/queens from release Sid to Stretch, an
issue where 3 unit tests were failing due to the entire project tags
collection being treated as a single tag was encountered[0].

It was later determined that the hybrid_property.expression
implementation was causing this issue[1]. When a quick change was pushed
up and tested, the issue appeared to be fixed[2].

The fix for this issue is to drop @hybrid_property usage for @property,
which removes the use of tags.expression. Project should always have
tags instantiated, so there is not a behavior difference, which is a
better fit for @property.


[0] 
http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2018-02-27.log.html#t2018-02-27T11:23:30

[1] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone
/%23openstack-keystone.2018-02-27.log.html#t2018-02-27T19:32:42

[2] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone
/%23openstack-keystone.2018-02-27.log.html#t2018-02-27T21:24:34

** Affects: keystone
 Importance: High
 Assignee: Gage Hugo (gagehugo)
 Status: In Progress

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

Title:
  Project tags treats entire collection as a single tag

Status in OpenStack Identity (keystone):
  In Progress

Bug description:
  When backporting Debian stable/queens from release Sid to Stretch, an
  issue where 3 unit tests were failing due to the entire project tags
  collection being treated as a single tag was encountered[0].

  It was later determined that the hybrid_property.expression
  implementation was causing this issue[1]. When a quick change was
  pushed up and tested, the issue appeared to be fixed[2].

  The fix for this issue is to drop @hybrid_property usage for
  @property, which removes the use of tags.expression. Project should
  always have tags instantiated, so there is not a behavior difference,
  which is a better fit for @property.

  
  [0] 
http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2018-02-27.log.html#t2018-02-27T11:23:30

  [1] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone
  /%23openstack-keystone.2018-02-27.log.html#t2018-02-27T19:32:42

  [2] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone
  /%23openstack-keystone.2018-02-27.log.html#t2018-02-27T21:24:34

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1752301/+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 1752290] [NEW] [RFE] (Operator-only) Add support 'snat' for loggable resource type

2018-02-28 Thread Yushiro FURUKAWA 
Public bug reported:

This RFE adds support SNAT for loggable resource type. The purpose is to
collect following logs for audit for cloud providers:

  *  What did VM instance(local IP) use SNAT IP address ?
  *  When used?

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: rfe

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

Title:
  [RFE] (Operator-only) Add support 'snat' for loggable resource type

Status in neutron:
  New

Bug description:
  This RFE adds support SNAT for loggable resource type. The purpose is
  to collect following logs for audit for cloud providers:

*  What did VM instance(local IP) use SNAT IP address ?
*  When used?

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1752290/+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 1752289] [NEW] ServiceCatalog does not contain "network" service

2018-02-28 Thread Thomas Bechtold 
Public bug reported:

On SLE12SP3, openstack-nova 17.0.0.0~xrc2~dev160-1.1, I try to boot an
cirros instance and get:

2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager 
[req-53fa6935-f60d-4e07-bc75-14b6a5336330 f80483de8573468b869e64262780a903 
d9685d1130d74a73af6ee213c421d9de - default default] [instance: 
0ae671f6-5241-486f-9054-1100b124f704] Instance failed to spawn: 
EndpointNotFound: ['internal', 'public'] endpoint for network service not found
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] Traceback (most recent call last):
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2236, in 
_build_resources
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] yield resources
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2019, in 
_build_and_run_instance
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] block_device_info=block_device_info)
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3011, in 
spawn
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] mdevs=mdevs)
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 5256, in 
_get_guest_xml
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] network_info_str = str(network_info)
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/network/model.py", line 568, in __str__
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] return self._sync_wrapper(fn, *args, 
**kwargs)
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/network/model.py", line 551, in 
_sync_wrapper
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] self.wait()
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/network/model.py", line 583, in wait
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] self[:] = self._gt.wait()
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 175, in wait
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] return self._exit_event.wait()
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/eventlet/event.py", line 125, in wait
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] current.throw(*self._exc)
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 214, in main
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] result = function(*args, **kwargs)
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/utils.py", line 906, in context_wrapper
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] return func(*args, **kwargs)
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1414, in 
_allocate_network_async
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704] six.reraise(*exc_info)
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1397, in 
_allocate_network_async
2018-02-28 10:24:07.553 10768 ERROR nova.compute.manager [instance: 
0ae671f6-5241-486f-9054-1100b124f704]

[Yahoo-eng-team] [Bug 1752275] [NEW] Write a document on API reference guideline

2018-02-28 Thread Akihiro Motoki 
Public bug reported:

There is no guideline on the neutron API reference so far in the neutron-lib 
repository.
Only thing we have is in 
https://etherpad.openstack.org/p/neutron-api-ref-sprint and I believe the 
content would be ncie.
It is better to have some guideline in-tree.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: api-ref

** Tags added: api-ref

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

Title:
  Write a document on API reference guideline

Status in neutron:
  New

Bug description:
  There is no guideline on the neutron API reference so far in the neutron-lib 
repository.
  Only thing we have is in 
https://etherpad.openstack.org/p/neutron-api-ref-sprint and I believe the 
content would be ncie.
  It is better to have some guideline in-tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1752275/+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 1752274] [NEW] Merge all API references in wiki, neutron-specs and neutron-lib into neutron-lib

2018-02-28 Thread Akihiro Motoki 
Public bug reported:

Neutron API reference is maintained under neutron-lib repo, but there
are also resources in OpenStack wiki and neutron-specs repository. The
contents are a bit older but they still have useful contents, so this
bug is used to merge them into neutron-lib API reference.

OpenStack wiki : https://wiki.openstack.org/wiki/Neutron/APIv2-specification
neutron-specs: 
http://git.openstack.org/cgit/openstack/neutron-specs/tree/misc/api

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: api-ref

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

Title:
  Merge all API references in wiki, neutron-specs and neutron-lib into
  neutron-lib

Status in neutron:
  New

Bug description:
  Neutron API reference is maintained under neutron-lib repo, but there
  are also resources in OpenStack wiki and neutron-specs repository. The
  contents are a bit older but they still have useful contents, so this
  bug is used to merge them into neutron-lib API reference.

  OpenStack wiki : https://wiki.openstack.org/wiki/Neutron/APIv2-specification
  neutron-specs: 
http://git.openstack.org/cgit/openstack/neutron-specs/tree/misc/api

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1752274/+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 1752265] [NEW] invalid "default_notification_exchange" config in keystone.conf of O version

2018-02-28 Thread andy wang 
Public bug reported:

[environment]: openstack ocata version.

[description]: I test event notifications in my devstack and find that 
'default_notification_exchange' in [oslo_messaging_rabbit] section seemed 
invalid. The valid config is 'control_exchange' in [DEFAULT] section.
I don't know if anyone else encount this problem? and I don't konw whether 
other version has this problem. If it is invalid, It should be removed.  

the below link is keystone.conf
https://github.com/openstack/keystone/blob/stable/ocata/etc/keystone.conf.sample

** Affects: keystone
 Importance: Undecided
 Status: New

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

Title:
  invalid "default_notification_exchange" config in keystone.conf  of O
  version

Status in OpenStack Identity (keystone):
  New

Bug description:
  [environment]: openstack ocata version.

  [description]: I test event notifications in my devstack and find that 
'default_notification_exchange' in [oslo_messaging_rabbit] section seemed 
invalid. The valid config is 'control_exchange' in [DEFAULT] section.
  I don't know if anyone else encount this problem? and I don't konw whether 
other version has this problem. If it is invalid, It should be removed.  

  the below link is keystone.conf
  
https://github.com/openstack/keystone/blob/stable/ocata/etc/keystone.conf.sample

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