[Yahoo-eng-team] [Bug 1640319] Re: AttributeError: 'module' object has no attribute 'convert_to_boolean'

2016-11-21 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/395450
Committed: 
https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=3dfc497daf26f5b8ebce6569e72e40371138b0cc
Submitter: Jenkins
Branch:master

commit 3dfc497daf26f5b8ebce6569e72e40371138b0cc
Author: YAMAMOTO Takashi 
Date:   Wed Nov 9 16:51:22 2016 +0900

Use some definitions from neutron-lib

The following two unrelated changes are combined
into this single commit to pass the gate.

---

Use some definitions from neutron-lib

Including:
- convert_to_boolean
- PORT_STATUS_ACTIVE
- TAP_DEVICE_PREFIX
- db_api.get_engine

Closes-Bug: #1640319
Closes-Bug: #1641481
Closes-Bug: #1641494
Partial-Bug: #1581361

---

l3_db_midonet: Update after the recent Neutron change. [1]

[1] I93e4d847f96707b17c4a7dfdb3bbf81d062fe3fb

Closes-Bug: #1643747
Related-Bug: #1540844

---

Change-Id: Ide96124c12c993a3ee0f2353c8201da9a6b5890c


** Changed in: networking-midonet
   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/1640319

Title:
  AttributeError: 'module' object has no attribute 'convert_to_boolean'

Status in networking-midonet:
  Fix Released
Status in neutron:
  Fix Committed
Status in openstack-ansible:
  Fix Released
Status in vmware-nsx:
  Fix Committed

Bug description:
  With latest neutron master code, neutron service q-svc could start due to the 
following error:
  2016-11-08 21:54:39.435 DEBUG oslo_concurrency.lockutils [-] Lock "manager" 
released by "neutron.manager._create_instance" :: held 1.467s from (pid=18534) 
inner /usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:282
  2016-11-08 21:54:39.435 ERROR neutron.service [-] Unrecoverable error: please 
check log for details.
  2016-11-08 21:54:39.435 TRACE neutron.service Traceback (most recent call 
last):
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/opt/stack/neutron/neutron/service.py", line 87, in serve_wsgi
  2016-11-08 21:54:39.435 TRACE neutron.service service.start()
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/opt/stack/neutron/neutron/service.py", line 63, in start
  2016-11-08 21:54:39.435 TRACE neutron.service self.wsgi_app = 
_run_wsgi(self.app_name)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/opt/stack/neutron/neutron/service.py", line 289, in _run_wsgi
  2016-11-08 21:54:39.435 TRACE neutron.service app = 
config.load_paste_app(app_name)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/opt/stack/neutron/neutron/common/config.py", line 125, in load_paste_app
  2016-11-08 21:54:39.435 TRACE neutron.service app = 
loader.load_app(app_name)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/oslo_service/wsgi.py", line 353, in 
load_app
  2016-11-08 21:54:39.435 TRACE neutron.service return 
deploy.loadapp("config:%s" % self.config_path, name=name)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 247, in 
loadapp
  2016-11-08 21:54:39.435 TRACE neutron.service return loadobj(APP, uri, 
name=name, **kw)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 272, in 
loadobj
  2016-11-08 21:54:39.435 TRACE neutron.service return context.create()
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710, in 
create
  2016-11-08 21:54:39.435 TRACE neutron.service return 
self.object_type.invoke(self)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 144, in 
invoke
  2016-11-08 21:54:39.435 TRACE neutron.service **context.local_conf)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/util.py", line 55, in 
fix_call
  2016-11-08 21:54:39.435 TRACE neutron.service val = callable(*args, **kw)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/urlmap.py", line 31, in 
urlmap_factory
  2016-11-08 21:54:39.435 TRACE neutron.service app = 
loader.get_app(app_name, global_conf=global_conf)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 350, in 
get_app
  2016-11-08 21:54:39.435 TRACE neutron.service name=name, 
global_conf=global_conf).create()
  2016-11-08 21:54:39.435 TRACE neutron.service   File

[Yahoo-eng-team] [Bug 1548190] Re: dhcp-agent performance issue

2016-11-21 Thread Kevin Benton 
Fixed with this patch:
http://docs.openstack.org/developer/neutron/devref/provisioning_blocks.html

** Changed in: neutron
   Status: Confirmed => Fix Released

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

** Changed in: neutron
 Assignee: Soumiyajit (soumiyajit-v) => Kevin Benton (kevinbenton)

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

Title:
  dhcp-agent performance issue

Status in neutron:
  Fix Released

Bug description:
  Single controller[48 GB RAM, 16vCPU, 120GB Disk]
  1 Network Node
  100 ESX hypervisors distributed in 10 nova-compute nodes
  100 KVM hypervisors

  Test:

  1. Create /16 network
  2. Template to spawn 500 instances on network created in step 1

  Observation:

  1. Tried spinning 500 instances on KVM and 500 instances on ESX hypervisor 
using CirrOS qemu & vmdk image respectively
  2. Stack creation went through fine, but randomly  few VM's missed dhcp IP on 
first boot
  3. After forcing sudo udhcpc from guest OS, VM's was able to receive IP
  4. Tried tcpdump on network dhcp port on network node, I could able to see 
only dhcp request coming from guest VM but there was no dhcp offer or ack from 
dhcp agent.

  Assume this issue is due to scale test on this setup.

  Please let me know if you need any particular logs or details to debug
  this issue, I can work and re-create issue and collect logs.

  Logs:

  Network node:

  stack@network:/opt/stack/neutron$ git log -1
  commit 171351d5fb55f96e9ed9e56eab755f2717ee67b0
  Merge: 0a5a3cf 8f15d72
  Author: Jenkins 
  Date:   Fri Feb 19 07:25:52 2016 +

  Merge "Adopt Grafana to plot Neutron Failure Rates"
  stack@network:/opt/stack/neutron$ 

  stack@network:/opt/stack/neutron$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu 14.04.3 LTS"
  stack@network:/opt/stack/neutron$ 

  stack@network:/opt/stack/neutron$ dpkg -l | grep dhcp
  ii  isc-dhcp-client 4.2.4-7ubuntu12.3
amd64ISC DHCP client
  ii  isc-dhcp-common 4.2.4-7ubuntu12.3
amd64common files used by all the isc-dhcp* packages
  stack@network:/opt/stack/neutron$ 

  nobody   32359  0.0  0.0  28212  2324 ?SFeb19   0:00
  dnsmasq --no-hosts --no-resolv --strict-order --except-interface=lo
  --pid-file=/opt/stack/data/neutron/dhcp/dba9d787-d145-4b2b-8c5d-
  d1b3375935ba/pid --dhcp-
  hostsfile=/opt/stack/data/neutron/dhcp/dba9d787-d145-4b2b-8c5d-
  d1b3375935ba/host --addn-
  hosts=/opt/stack/data/neutron/dhcp/dba9d787-d145-4b2b-8c5d-
  d1b3375935ba/addn_hosts --dhcp-
  optsfile=/opt/stack/data/neutron/dhcp/dba9d787-d145-4b2b-8c5d-
  d1b3375935ba/opts --dhcp-
  leasefile=/opt/stack/data/neutron/dhcp/dba9d787-d145-4b2b-8c5d-
  d1b3375935ba/leases --dhcp-match=set:ipxe,175 --bind-interfaces
  --interface=ns-460a72e9-8f --dhcp-
  range=set:tag0,169.254.169.252,static,86400s --dhcp-lease-max=4
  --conf-file= --domain=openstacklocal


  === sshd host keys ===
  -BEGIN SSH HOST KEY KEYS-
  ssh-rsa 
B3NzaC1yc2EDAQABgmNQGIVf2P+n6U3yYkWwv/V598atmu3ZCHN8XRHIgujUkKKJ5IaurmDFH9XqSJhB2B+90ZP/z0bTqkI0to7QuoFw0GzyV2og59cZZrjntimdoAdo7RZKuwtyQZoIOHILBE2On/y1F3ixhVeE5j78GuiDN+yCNiIBhAnm0V9d0QxGtqc=
 root@kvm-218-admin-3
  ssh-dss 
B3NzaC1kc3MAAACBAJNHiG1dQxMG+vmlJEWY1xgak5xHGFzm+QFEkFXOaRzdzPw8y9DX/O+bxnrcaSKwKHBJcKaJZJ+SHnVEpX2QgQQA+uSSMCMKQFISjdTCtTQ/0tUiLculV/ISrXDCm9cHG6DWqplVoc/LmXJObh1NZrjPunW2NrUCoI2qXtFMbdiVFQC4GI/n1hxNcGEjkzJ2GRRcenU+hwAAAIAjJ09CspilFn7DintV3Sh7lCs1I5+m+mQcI/AJeLSE+Ee04Nw47KWgrFyoaCQNYyHt1wgONlTmcKYyDxUGwjbRTyZYEwdaxgd+klxt7NP6fR2kmuzCLiyFP+W2WNJcqRr6xxlRif4TOwbOd/Qlt0JeM1LufaxyuogSBgWS/kys6IAIPMlAPi41qCGhUnUkbx23OrzqkP+xZEj7cGnxa/HxpnIkZ+qMhRIhBMFADEt4MKKmdZyTPYDiSaiBR298ic6ywekA1YxAqwCEtKlA+7Cdl9q7REIPVh1CSWZdJEKi9qKBMYaMzuw7cbkdh5ZbOMHWALS8JgndYGD77xWQwKamCA==
 root@kvm-218-admin-3
  -END SSH HOST KEY KEYS-
  === network info ===
  if-info: lo,up,127.0.0.1,8,::1
  if-info: eth0,up,,8,fe80::f816:3eff:feec:77dc
  === datasource: configdrive local ===
  instance-id: 11a83228-beef-4c0e-a7a3-15748de381e9
  name: kvm-218-admin-3
  availability-zone: nova
  local-hostname: kvm-218-admin-3.novalocal
  launch-index: 0
  === cirros: current=0.3.4 uptime=191.83 ===
  route: fscanf
  === pinging gateway failed, debugging connection ===
   debug start ##
  ### /etc/init.d/sshd start
  Starting dropbear sshd: OK
  route: fscanf
  ### ifconfig -a
  eth0 Link encap:Ethernet HWaddr FA:16:3E:EC:77:DC
inet6 addr: fe80::f816:3eff:feec:77dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:84 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0

[Yahoo-eng-team] [Bug 1643710] [NEW] Incorrect order of container objects and folders by size

2016-11-21 Thread Eddie Ramirez 
Public bug reported:

How to reproduce:
1. Go to Project->Object Storage->Containers
2. Create a few objects with different size also some folders with or without 
objects in it.
3. Sort by "Size"

Actual result:
Objects are sorted by their size but folders are sorted in an expected way, 
they could appear between objects.

Expected result:
Folders should appear at the beginning (sort ASC) or end of the table (sort 
DESC). We should assume  the size of folders as "0".

** Affects: horizon
 Importance: Undecided
 Status: New


** Tags: swift

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1643710/+attachment/4781237/+files/Containers%20%20%20OpenStack%20Dashboard.png

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

Title:
  Incorrect order of container objects and folders by size

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  How to reproduce:
  1. Go to Project->Object Storage->Containers
  2. Create a few objects with different size also some folders with or without 
objects in it.
  3. Sort by "Size"

  Actual result:
  Objects are sorted by their size but folders are sorted in an expected way, 
they could appear between objects.

  Expected result:
  Folders should appear at the beginning (sort ASC) or end of the table (sort 
DESC). We should assume  the size of folders as "0".

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1643710/+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 1606462] Re: OVS firewall should make use of security_group_updated

2016-11-21 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/395956
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=7db68e32023162d843d287a121fec64a6786e87c
Submitter: Jenkins
Branch:master

commit 7db68e32023162d843d287a121fec64a6786e87c
Author: IWAMOTO Toshihiro 
Date:   Thu Nov 10 14:27:18 2016 +0900

ovsfw: small cleanups to improve readability

security_group_updated is actually called but of no use for ovsfw.
Fix the comment to reflect the reality.  In iptables_firewall, the
method is used to clear obsolete conntrack entries, but ovsfw implements
that differently.  Also, remove empty definition of apply_port_filter,
which is never called.

Change-Id: I26b402e0fa5ac19022e022bf7c51e171d0f5d333
Closes-Bug: #1606462


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

Title:
  OVS firewall should make use of security_group_updated

Status in neutron:
  Fix Released

Bug description:
  Look at this:

  class OVSFirewallDriver(firewall.FirewallDriver):
  ...
  def security_group_updated(self, action_type, sec_group_ids,
 device_ids=None):
  """This method is obsolete

  The current driver only supports enhanced rpc calls into security 
group
  agent. This method is never called from that place.
  """

  but this is used by the enhanced rpc. See
  SecurityGroupAgentRpc._security_group_updated.

  Also this can be checked by inserting a test raise statement into the
  above method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1606462/+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 1639312] Re: Nova does not validate graphics console addresses

2016-11-21 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/373264
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=f84ae10c66aeda223581b26c134b5c44c15d9e6e
Submitter: Jenkins
Branch:master

commit f84ae10c66aeda223581b26c134b5c44c15d9e6e
Author: Pawel Koniszewski 
Date:   Wed Nov 16 11:05:10 2016 +0100

Refactor console checks in live migration process

_check_graphics_addresses_can_live_migrate was added to check
whether we can live migrate a VM with VNC/SPICE enabled when:

* libvirt did not allow to change and migrate guest XML with
  updated graphics listen addresses. Right now we always can update
  VNC/SPICE listen address.
* Destination node was running old-code that does not set the fields.
  Currently when live migrating between two versions of OpenStack
  (N and N-1) the fields are always set.

Therefore this check is redundant and can be removed.

Going deeper in this code - graphics_listen_addr_vnc and
graphics_listen_addr_spice in libvirt migrate data object are of
type IPAddressField. It means that both need to contain valid IP address.
By default in nova.conf it is 127.0.0.1. It can't be set to None because
IP address is taken from nova.conf and even if set to None it will be
passed as a string 'None' and will fail IPAddressField validation.

graphics_listen_addrs in migration.py currently always returns a dict
which contains IP addresses of both VNC and spice graphics consoles.

This means that:
* check 'if listen_addrs' is always True
* check 'if not listen_addrs' is always False

So we really never passed through 'if not listen_addrs' since
migrate_data is objectified as those addresses are always there.

However, serial_listen_addr is handled different way. The type of
this field in libvirt migrate data object is StringField that might
be set to None or empty string through nova.conf. So we still need
to validate whether serial console can be migrated so that we will
be sure that particular live migration will not break serial console
in case when serial listen address is not configured at destination.

Change-Id: I73f7bfafa4554bf1c2dfc980289be88154170282
Closes-Bug: #1639312


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

Title:
  Nova does not validate graphics console addresses

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Due to all changes in nova live migration code path there is condition
  that is always evaluated to False:

  
https://github.com/openstack/nova/blob/5a81b00e6b2adba2a380b90e402ff391d64ea6a5/nova/virt/libvirt/driver.py#L5888

  Even when using the lowest RPC microversion (4.0) migrata_data will
  always be populated with graphics console addresses. This data will
  not be there only when doing live migration, e.g., from Kilo to
  Newton, which is not supported anyway. Even though both options,
  graphics_listen_addr_vnc and graphics_listen_addr_spice are nullable:

  
https://github.com/openstack/nova/blob/4eb89c206e68a7172ebad897ad24769036c7bdd6/nova/objects/migrate_data.py#L125

  there is no way to pass None through nova.conf, instead it is always
  passed as string (e.g. "None"). Therefore values of both options will
  be validated whether they are valid IP addresses. Also by default
  vncserver_listen and server_listen are not set to None, but to
  127.0.0.1

  
https://github.com/openstack/nova/blob/cd3b57d0c0cb867ef48a6e9721d9b3e28cb08e84/nova/conf/vnc.py#L58
  
https://github.com/openstack/nova/blob/cd3b57d0c0cb867ef48a6e9721d9b3e28cb08e84/nova/conf/spice.py#L65

  Because of all this stuff nova never reaches code that should validate
  graphics console addresses and we might allow live migration that
  breaks graphics console on instance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1639312/+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 1643688] [NEW] Azure should set hostname during init-local

2016-11-21 Thread Bastian Blank 
Public bug reported:

The Azure data-source currently considers itself a networked one, as at
least part of the information is read via network. In consequence the
hostname is only known after network is already setup and a ifdown/ifup
cycle is initiated to update the network view of the hostname. This
cycle leads to a massive delay in boot time, at least if ipv6 setup is
requested.

Please split hostname setup out of the normal networked init run. The
information via the ovf file is known pretty early and without network.

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

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

Title:
  Azure should set hostname during init-local

Status in cloud-init:
  New

Bug description:
  The Azure data-source currently considers itself a networked one, as
  at least part of the information is read via network. In consequence
  the hostname is only known after network is already setup and a
  ifdown/ifup cycle is initiated to update the network view of the
  hostname. This cycle leads to a massive delay in boot time, at least
  if ipv6 setup is requested.

  Please split hostname setup out of the normal networked init run. The
  information via the ovf file is known pretty early and without
  network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643688/+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 1643689] [NEW] Error running manage.py compress after https://review.openstack.org/#/c/399771/

2016-11-21 Thread Alfredo Moralejo 
Public bug reported:

After https://review.openstack.org/#/c/399771/, we are getting following
error when running "python manage.py compress":

CommandError: An error occurred during rendering 
/tmp/horizon/openstack_dashboard/templates/_stylesheets.html: Couldn't find 
anything to import: ../../mixins
Extensions: , , 
Search path:
  
on line 21 of 
horizon/lib/roboto_fontface/css/roboto/sass/roboto-fontface-regular.scss
imported from line 21 of 
horizon/lib/roboto_fontface/css/roboto/sass/roboto-fontface.scss
imported from line 16 of themes/material/bootstrap/_styles.scss
imported from line 16 of themes/material/_styles.scss
imported from line 1 of u'string:c61b5d22d54bf56c:\n// My Themes\n@import 
"/themes/material/variables";\n\n// Horizon\n@import "/dashboard/scss/horizon'
 
and exits. 

Note that this issue is making horizon packaging to fail.

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

Title:
  Error running manage.py compress after
  https://review.openstack.org/#/c/399771/

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  After https://review.openstack.org/#/c/399771/, we are getting
  following error when running "python manage.py compress":

  CommandError: An error occurred during rendering 
/tmp/horizon/openstack_dashboard/templates/_stylesheets.html: Couldn't find 
anything to import: ../../mixins
  Extensions: , , 
  Search path:

  on line 21 of 
horizon/lib/roboto_fontface/css/roboto/sass/roboto-fontface-regular.scss
  imported from line 21 of 
horizon/lib/roboto_fontface/css/roboto/sass/roboto-fontface.scss
  imported from line 16 of themes/material/bootstrap/_styles.scss
  imported from line 16 of themes/material/_styles.scss
  imported from line 1 of u'string:c61b5d22d54bf56c:\n// My Themes\n@import 
"/themes/material/variables";\n\n// Horizon\n@import "/dashboard/scss/horizon'
   
  and exits. 

  Note that this issue is making horizon packaging to fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1643689/+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 1526715] Re: disallow non-admin search for soft-delete instance

2016-11-21 Thread jichenjc 
ok, this is a valid point ,even though I think the softdelete/restore might be 
admin only thing
it's not related to bug itself

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

Title:
  disallow non-admin search for soft-delete instance

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  search deleted instance is only for admin.
  So we should disallow non-admin search for deleted and soft_deleted instances

  $ curl -g -i -X GET 
http://192.168.122.239:8774/v2.1/d1c5aa58af6c426492c642eb649017be/servers/detail?status=soft_deleted
 -H "User-Agent: python-novaclient" -H "Accept: application/json" -H 
"X-OpenStack-Nova-API-Version: 2.6" -H "X-Auth-Token: 
4414496776a3486ba96a6702f13ed5ce"
  HTTP/1.1 200 OK
  Content-Type: application/json
  Content-Length: 15
  X-Openstack-Nova-Api-Version: 2.6
  Vary: X-OpenStack-Nova-API-Version
  X-Compute-Request-Id: req-15a68220-093c-4688-b9ac-9dc89215140d
  Date: Tue, 15 Dec 2015 16:34:36 GMT

  {"servers": []}
  $

  2015-12-15 11:34:35.991 DEBUG nova.compute.api [req-15a68220-093c-4688
  -b9ac-9dc89215140d demo demo] Searching by: {'deleted': False,
  'vm_state': ['soft-delete'], 'project_id':
  u'd1c5aa58af6c426492c642eb649017be'} from (pid=26588) get_all
  /opt/stack/nova/nova/compute/api.py:2055

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1526715/+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 1643684] [NEW] _check_requested_image uses incorrect bdm info to validate target volume when booting from boot from volume instance snapshot image

2016-11-21 Thread Jesse Keating 
Public bug reported:

This is a complicated one.

Start with a boot from volume instance. Instance uses a 1G volume, and a
tiny image. Make a snapshot of this, which results in a volume snapshot
plus a image in glance. Image details:

# openstack image show a9a2a4af-0383-47a0-85e6-c3211f11459e
+--+---+
| Field| Value |
+--+---+
| checksum | d41d8cd98f00b204e9800998ecf8427e  |
| container_format | bare  |
| created_at   | 2016-11-21T18:13:23Z  |
| disk_format  | qcow2 |
| file | /v2/images/a9a2a4af-0383-47a0-85e6-c3211f11459e/file  |
| id   | a9a2a4af-0383-47a0-85e6-c3211f11459e  |
| min_disk | 10|
| min_ram  | 0 |
| name | testsnap  |
| owner| 6fe9193745c64a44ab30d6bd1c5cb8bb  |
| properties   | base_image_ref='', bdm_v2='True', |
|  | block_device_mapping='[{"guest_format": null, |
|  | "boot_index": 0, "delete_on_termination": false,  |
|  | "no_device": null, "snapshot_id": "5186f403-bf91-49d4 |
|  | -b3db-c273e087fcfa", "device_name": "/dev/vda",   |
|  | "disk_bus": "virtio", "image_id": null, "source_type":|
|  | "snapshot", "tag": null, "device_type": "disk",   |
|  | "volume_id": null, "destination_type": "volume",  |
|  | "volume_size": 1}]', owner_specified.shade.md5='133eae9fb |
|  | 1c98f45894a4e60d8736619', |
|  | owner_specified.shade.object='images/cirros', owner_speci |
|  | fied.shade.sha256='f11286e2bd317ee1a1d0469a6b182b33bda4af |
|  | 6f35ba224ca49d75752c81e20a', root_device_name='/dev/vda'  |
| protected| False |
| schema   | /v2/schemas/image |
| size | 0 |
| status   | active|
| tags |   |
| updated_at   | 2016-11-21T18:13:24Z  |
| virtual_size | None  |
| visibility   | private   |
+--+---+

First, try booting just using the image:

# openstack server create --image a9a2a4af-0383-47a0-85e6-c3211f11459e --flavor 
2 --nic net-id=832c3099-a589-4f05-8f70-c5af5b2f852b lolwhut
Volume is smaller than the minimum size specified in image metadata. Volume 
size is 1073741824 bytes, minimum size is 10737418240 bytes. (HTTP 400) 
(Request-ID: req-97cc0a55-7d5b-4e14-8f4b-e8a501f96f11)

Nova is saying that the minimum size is 10G, but the requested bdm size
is 1. I'm assuming that's coming from the instance data's
block_device_mapping key, which has volume_size of 1.

Now, try doing this where you're also requesting to boot from volume, of
size 15 (this was done via horizon):

2016-11-21 19:50:28.398 12516 DEBUG nova.api.openstack.wsgi [req-
4481446f-e026-4e83-b07a-1acdfa08194f 4921001dd4944f1396f7e6d64717f044
6fe9193745c64a44ab30d6bd1c5cb8bb - default default] Action: 'create',
calling method: >, body: {"server": {"name": "jlkwhat", "imageRef": "",
"availability_zone": "ci", "key_name": "turtle-key", "flavorRef": "2",
"OS-DCF:diskConfig": "AUTO", "max_count": 1, "block_device_mapping_v2":
[{"boot_index": "0", "uuid": "a9a2a4af-0383-47a0-85e6-c3211f11459e",
"volume_size": 15, "device_name": "vda", "source_type": "image",
"destination_type": "volume", "delete_on_termination": false}],
"min_count": 1, "networks": [{"uuid":
"832c3099-a589-4f05-8f70-c5af5b2f852b"}], "security_groups": [{"name":
"f8cb8d50-698a-48b0-9a83-1201e89834e0"}]}} _process_stack
/opt/bbc/openstack-2016.2-newton/nova/local/lib/python2.7/site-
packages/nova/api/openstack/wsgi.py:633


See that it has a source_type of image, and a destination_type of volume, and 
block_device_mapping_v2 shows volume_size of 15 (but references that image UUID 
from above).

Nova STILL spits out the same warning:

2016-11-21 19:50:29.004 12516 DEBUG nova.api.openstack.wsgi [req-

[Yahoo-eng-team] [Bug 1641822] Re: admin guide: create a PCI section

2016-11-21 Thread Steve Martinelli 
https://review.openstack.org/#/c/399337/ merged

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

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

Title:
  admin guide: create a PCI section

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  A section dedicated to PCI should be created in the admin guide [1].
  The content can largely come from our developer docs [2], but should
  be modified for a deployer in mind.

  [1] 
https://github.com/openstack/openstack-manuals/tree/master/doc/admin-guide/source
  [2] http://docs.openstack.org/developer/keystone/security_compliance.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1641822/+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 1643623] [NEW] Not able to abort live migration

2016-11-21 Thread Sivasathurappan Radhakrishnan 
Public bug reported:

Tried to live migrate instance to destination host which was an invalid
one. Got a error message saying host was not available . Did a nova list and found status
and task state was stuck in migrating status forever. Couldn't see the
instance in 'nova migration-list' and not able to abort the migration
using 'nova live-migration-abort'.

Steps to reproduce:
1) Create an instance test_1
2) live migrate instance using 'nova live-migration test_1 '
3) Check status of the instance using 'nova show test_1' or 'nova list'.

Expected Result:
Status of the instance should have been in Active status as live migration 
failed with invalid host name

Actual Result:
Instance is stuck in 'migrating' status forever.

Environment:
Multinode devstack environment with 2 compute nodes
1)Current master
2)Networking-neutron
3)Hypervisor Libvirt-KVM

** Affects: nova
 Importance: Undecided
 Assignee: Sivasathurappan Radhakrishnan (siva-radhakrishnan)
 Status: New


** Tags: live-migration

** Tags added: live-migration

** Changed in: nova
 Assignee: (unassigned) => Sivasathurappan Radhakrishnan 
(siva-radhakrishnan)

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

Title:
  Not able to abort live migration

Status in OpenStack Compute (nova):
  New

Bug description:
  Tried to live migrate instance to destination host which was an
  invalid one. Got a error message saying host was not available . Did a nova list and found
  status and task state was stuck in migrating status forever. Couldn't
  see the instance in 'nova migration-list' and not able to abort the
  migration using 'nova live-migration-abort'.

  Steps to reproduce:
  1) Create an instance test_1
  2) live migrate instance using 'nova live-migration test_1 '
  3) Check status of the instance using 'nova show test_1' or 'nova list'.

  Expected Result:
  Status of the instance should have been in Active status as live migration 
failed with invalid host name

  Actual Result:
  Instance is stuck in 'migrating' status forever.

  Environment:
  Multinode devstack environment with 2 compute nodes
  1)Current master
  2)Networking-neutron
  3)Hypervisor Libvirt-KVM

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1643623/+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 1374663] Re: [SRU] agent/linux/ip_lib.py does not correctly handle output from 'iproute2' command

2016-11-21 Thread Launchpad Bug Tracker 
This bug was fixed in the package neutron - 1:2014.1.5-0ubuntu7

---
neutron (1:2014.1.5-0ubuntu7) trusty; urgency=medium

  * agent/linux/ip_lib.py does not correctly handle output from 'iproute2'
command. (LP: #1374663):
- d/p/neutron-ns-iface-enum.patch: Searches /sys/class/net for the correct
  interface name instead of scraping iproute2 output.

 -- Shane Peters (Shaner)   Thu, 03 Nov 2016
16:53:31 -0400

** Changed in: neutron (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] agent/linux/ip_lib.py does not correctly handle output from
  'iproute2' command

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive icehouse series:
  In Progress
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * The get_devices() method in neutron/agent/linux/ip_lib.py chokes if 
'iproute2' presents interface names containing '@', such as ipip tunnels and 
macvlan devices:

tunl0@NONE:  mtu 1480 qdisc noop state DOWN mode DEFAULT 
group default
clone@eth0:  mtu 1454 qdisc noop state 
DOWN mode DEFAULT
  
* The mere presence of one of the above interface names will cause the
  code to fail with:

RuntimeError:
Command: ['ip', 'addr', 'show', 'tunl0@NONE']
Exit code: 1
Stdout: ''
Stderr: 'Device "tunl0@NONE" does not exist.\n'

  
  [Test Case]

   * This has been seen in the vpn_agent.log after upgrading to a xenial kernel 
(4.4.0-45-generic) in a trusty/icehouse environment.
 
  /var/log/neutron/vpn_agent.log:
  ERROR neutron.agent.linux.interface [-] Failed unplugging interface   
'qg-e75da35-63@if10' 

  
  [Regression Potential]

* iproute2 is still used, however, a search path was added
  (/sys/class/net) which returns the interfaces without the '@'.

* This has been fixed since Kilo so there is minimal regression
  potential.

  
  [ Other Info ]

*

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1374663/+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 1643597] [NEW] Q_PLUGIN_EXTRA_CONF_FILES issue in vpnaas

2016-11-21 Thread YAMAMOTO Takashi 
Public bug reported:

the way neutron-vpnaas devstack plugin configures Q_PLUGIN_EXTRA_CONF_FILES
causes errors like the following if there are multiple devstack plugins using
the variable.

/usr/local/bin/neutron-server --config-file /etc/neutron/neutron.conf 
--config-file /etc/neutron/plugins/midonet/midonet.ini --config-file 
/etc/neutron/neutron_lbaas.confneutron_vpnaas.conf --config-file 
/etc/neutron/services_lbaas.conf
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
Traceback (most recent call last):
  File "/usr/local/bin/neutron-server", line 10, in 
sys.exit(main())
  File "/opt/stack/neutron/neutron/cmd/eventlet/server/__init__.py", line 22, 
in main
server.boot_server(_main_neutron_server)
  File "/opt/stack/neutron/neutron/server/__init__.py", line 29, in boot_server
config.init(sys.argv[1:])
  File "/opt/stack/neutron/neutron/common/config.py", line 81, in init
**kwargs)
  File "/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2297, 
in __call__
raise ConfigFilesNotFoundError(self._namespace._files_not_found)
oslo_config.cfg.ConfigFilesNotFoundError: Failed to find some config files: 
/etc/neutron/neutron_lbaas.confneutron_vpnaas.conf
q-svc failed to start

** Affects: neutron
 Importance: Undecided
 Assignee: YAMAMOTO Takashi (yamamoto)
 Status: In Progress


** Tags: vpnaas

** Tags added: vpnaas

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

Title:
  Q_PLUGIN_EXTRA_CONF_FILES issue in vpnaas

Status in neutron:
  In Progress

Bug description:
  the way neutron-vpnaas devstack plugin configures Q_PLUGIN_EXTRA_CONF_FILES
  causes errors like the following if there are multiple devstack plugins using
  the variable.

  /usr/local/bin/neutron-server --config-file /etc/neutron/neutron.conf 
--config-file /etc/neutron/plugins/midonet/midonet.ini --config-file 
/etc/neutron/neutron_lbaas.confneutron_vpnaas.conf --config-file 
/etc/neutron/services_lbaas.conf
  Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
  Traceback (most recent call last):
File "/usr/local/bin/neutron-server", line 10, in 
  sys.exit(main())
File "/opt/stack/neutron/neutron/cmd/eventlet/server/__init__.py", line 22, 
in main
  server.boot_server(_main_neutron_server)
File "/opt/stack/neutron/neutron/server/__init__.py", line 29, in 
boot_server
  config.init(sys.argv[1:])
File "/opt/stack/neutron/neutron/common/config.py", line 81, in init
  **kwargs)
File "/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py", line 
2297, in __call__
  raise ConfigFilesNotFoundError(self._namespace._files_not_found)
  oslo_config.cfg.ConfigFilesNotFoundError: Failed to find some config files: 
/etc/neutron/neutron_lbaas.confneutron_vpnaas.conf
  q-svc failed to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1643597/+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 1643581] Re: mtu size - auto setting for wifi not loads some webpages initially

2016-11-21 Thread Assaf Muller 
You reported a bug on the OpenStack Neutron component, pretty clear the
bug report is not relevant for OpenStack.

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

Title:
  mtu size - auto setting for wifi not loads some webpages initially

Status in neutron:
  Invalid

Bug description:
  Webpages like economictimes.indiatimes.com , opening of inner links in
  ndtv.com , at times dinamalar.com etc.,. did not open and mostly
  resulted in request time out. It opened after 10 or 15 minutes gap
  when refreshed. Changing the dns in netgear wifi modem to google dns,
  verisign dns, open dns or auto obtain dns did not solve the problem.

  Atlast found out that Wifi Network MTU size Auto as default was
  causing this request time out.

  Now after putting a MTU size value manually for wifi network lower
  than the MTU size value configured in wifi modem, all the above
  webpages opens.

  Presently using Ubuntu 16.10

  Kindly make auto MTU size setting for wifi network  to first probe mtu
  size of wifi modem and set a slightly lower value thant that as MTU.

  Reporting this to make Ubuntu user friendly even for newbies.

  I am using Ubuntu for more than 6 years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1643581/+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 1643581] [NEW] mtu size - auto setting for wifi not loads some webpages initially

2016-11-21 Thread Oppili 
Public bug reported:

Webpages like economictimes.indiatimes.com , opening of inner links in
ndtv.com , at times dinamalar.com etc.,. did not open and mostly
resulted in request time out. It opened after 10 or 15 minutes gap when
refreshed. Changing the dns in netgear wifi modem to google dns,
verisign dns, open dns or auto obtain dns did not solve the problem.

Atlast found out that Wifi Network MTU size Auto as default was causing
this request time out.

Now after putting a MTU size value manually for wifi network lower than
the MTU size value configured in wifi modem, all the above webpages
opens.

Presently using Ubuntu 16.10

Kindly make auto MTU size setting for wifi network  to first probe mtu
size of wifi modem and set a slightly lower value thant that as MTU.

Reporting this to make Ubuntu user friendly even for newbies.

I am using Ubuntu for more than 6 years.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: load mtu network not webpage wifi

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

Title:
  mtu size - auto setting for wifi not loads some webpages initially

Status in neutron:
  New

Bug description:
  Webpages like economictimes.indiatimes.com , opening of inner links in
  ndtv.com , at times dinamalar.com etc.,. did not open and mostly
  resulted in request time out. It opened after 10 or 15 minutes gap
  when refreshed. Changing the dns in netgear wifi modem to google dns,
  verisign dns, open dns or auto obtain dns did not solve the problem.

  Atlast found out that Wifi Network MTU size Auto as default was
  causing this request time out.

  Now after putting a MTU size value manually for wifi network lower
  than the MTU size value configured in wifi modem, all the above
  webpages opens.

  Presently using Ubuntu 16.10

  Kindly make auto MTU size setting for wifi network  to first probe mtu
  size of wifi modem and set a slightly lower value thant that as MTU.

  Reporting this to make Ubuntu user friendly even for newbies.

  I am using Ubuntu for more than 6 years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1643581/+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 1642399] Re: dhcp agent should be more responsive to resync requests

2016-11-21 Thread Kevin Benton 
I'm not sure why this is a process we need to speed up. Resync requests
are not normal.

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

Title:
  dhcp agent should be more responsive to resync requests

Status in neutron:
  Opinion

Bug description:
  The dhcp agent currently uses sleep between sync events. If a schedule
  resync is explicitly called, it needs to wait til sleep times out.

  Rather than sleep, this can be replaced with threading.Event (wait),
  in this way, the agent can be more responsive to resync requests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1642399/+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 1082248] Re: Use uuidutils instead of uuid.uuid4()

2016-11-21 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/394821
Committed: 
https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=88c64a8d7b6182439153fee7c0ab06912ce89e39
Submitter: Jenkins
Branch:master

commit 88c64a8d7b6182439153fee7c0ab06912ce89e39
Author: bailinzhang 
Date:   Tue Nov 8 16:41:04 2016 +0800

Replaces uuid.uuid4 with uuidutils.generate_uuid()

Change-Id: I1b1e265fefdf7b09b4b4807e0134a053390ec8f6
Closes-Bug: #1082248


** Changed in: kuryr-libnetwork
   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/1082248

Title:
  Use uuidutils instead of uuid.uuid4()

Status in Cinder:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  Fix Released
Status in Karbor:
  In Progress
Status in kolla:
  In Progress
Status in kuryr:
  In Progress
Status in kuryr-libnetwork:
  Fix Released
Status in Magnum:
  In Progress
Status in Mistral:
  Fix Released
Status in Murano:
  In Progress
Status in networking-calico:
  In Progress
Status in networking-ovn:
  Fix Released
Status in networking-sfc:
  In Progress
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  In Progress
Status in python-muranoclient:
  In Progress
Status in Sahara:
  Fix Released
Status in senlin:
  Fix Released
Status in tacker:
  In Progress
Status in watcher:
  Fix Released

Bug description:
  Openstack common has a wrapper for generating uuids.

  We should only use that function when generating uuids for
  consistency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1082248/+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 1643577] [NEW] cannot launch an instance in dashboard

2016-11-21 Thread Emmanuel Zhao 
Public bug reported:

Hi,
I ran devstack(master branch)to do an all in one installation in ubuntu 14.04. 
When I try to launch an instance in Horizon. I clicked the button "Launch" in 
"Instance" panel. There was nothing appeared. When I try to launch an instance 
with CLI, it's OK.
Looks like there are some JavaScript errors in Horizon.

** Affects: horizon
 Importance: Undecided
 Status: New

** Description changed:

  Hi,
  I ran devstack(master branch)to do an all in one installation in ubuntu 
14.04. When I try to launch an instance in Horizon. I clicked the button 
"Launch" in "Instance" panel. There was nothing appeared. When I try to launch 
an instance with CLI, it's OK.
+ Looks like there are some JavaScript errors in Horizon.

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

Title:
  cannot launch an instance in dashboard

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Hi,
  I ran devstack(master branch)to do an all in one installation in ubuntu 
14.04. When I try to launch an instance in Horizon. I clicked the button 
"Launch" in "Instance" panel. There was nothing appeared. When I try to launch 
an instance with CLI, it's OK.
  Looks like there are some JavaScript errors in Horizon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1643577/+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 1643569] [NEW] Choose VMware datastore in dependence of the provisioned space

2016-11-21 Thread Christian Berendt 
Public bug reported:

At the moment the _select_datastore method in the VMware driver chooses
the in dependence of the free space. The datastore with the most free
space will be chosen for a new instance.

On of our customers want to place new instances on the datastore with
the less provisioned space and not the one with the most free space.

The amount of provisioned space is not directly provided by the VMware
API and has to be calculated by using the capacity, the free space and
the uncommitted bytes of the datastore. provisionedSpace = Capacity -
freeSpace - uncommitted.

Following changes are necessary to support the selection of a datastore
in dependence of the provisioned space:

* The uncommitted property is not requested by the get_datastore method.
The get_datastore method hast to request the uncommitted property.

* The Datastore class does not provide a keyword argument for the amount
of provisioned space. A provisioned space keyword argument has to be
added to the Datastore class.

* The _select_datastore method has to calculate the provisioned space of
a datastore.

* A new configuration parameter datastore_allocation_type with
'provisionedSpace' and 'freeSpace' as choices has to be introduced. The
default value should be 'freeSpace' to not change the default behaviour
of the _select_datastore method.

* When  datastore_allocation_type is set to 'provisionedSpace' then the
provisionedSpace will be compared instead of the freeSpace and the
datastore with the lowest value for provisionedSpace will be chosen.

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

Title:
  Choose VMware datastore in dependence of the provisioned space

Status in OpenStack Compute (nova):
  New

Bug description:
  At the moment the _select_datastore method in the VMware driver
  chooses the in dependence of the free space. The datastore with the
  most free space will be chosen for a new instance.

  On of our customers want to place new instances on the datastore with
  the less provisioned space and not the one with the most free space.

  The amount of provisioned space is not directly provided by the VMware
  API and has to be calculated by using the capacity, the free space and
  the uncommitted bytes of the datastore. provisionedSpace = Capacity -
  freeSpace - uncommitted.

  Following changes are necessary to support the selection of a
  datastore in dependence of the provisioned space:

  * The uncommitted property is not requested by the get_datastore
  method. The get_datastore method hast to request the uncommitted
  property.

  * The Datastore class does not provide a keyword argument for the
  amount of provisioned space. A provisioned space keyword argument has
  to be added to the Datastore class.

  * The _select_datastore method has to calculate the provisioned space
  of a datastore.

  * A new configuration parameter datastore_allocation_type with
  'provisionedSpace' and 'freeSpace' as choices has to be introduced.
  The default value should be 'freeSpace' to not change the default
  behaviour of the _select_datastore method.

  * When  datastore_allocation_type is set to 'provisionedSpace' then
  the provisionedSpace will be compared instead of the freeSpace and the
  datastore with the lowest value for provisionedSpace will be chosen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1643569/+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 1643571] [NEW] lbaas data model is too recursive

2016-11-21 Thread YAMAMOTO Takashi 
Public bug reported:

this is an example of pool to_api_dict().
http://paste.openstack.org/show/589872/
as you can see, it has too many copies of same objects.
note: there are only 3 objects in the dict.

while from_sqlalchemy_model has some recursion protection,
it's better to make it shallower.

especially, to_dict/to_api_dict should not do much recursion.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: lbaas

** Tags added: lbaas

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

Title:
  lbaas data model is too recursive

Status in neutron:
  New

Bug description:
  this is an example of pool to_api_dict().
  http://paste.openstack.org/show/589872/
  as you can see, it has too many copies of same objects.
  note: there are only 3 objects in the dict.

  while from_sqlalchemy_model has some recursion protection,
  it's better to make it shallower.

  especially, to_dict/to_api_dict should not do much recursion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1643571/+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 1643532] Re: 'other_config' information is not written in ovs agent

2016-11-21 Thread Rodolfo Alonso 
Filled by Iafa6be3749b1ee863f5fa71150c708fc46951510

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

Title:
  'other_config' information is not written in ovs agent

Status in neutron:
  Invalid

Bug description:
  'other_config' information is not written in ovs agent.

  During the creation of a port, OVS databse is updated. 'other_config'
  key in Port database is not written correctly.

  This transaction is executed in 'port_bound' function.
  other_config:segmentation_id value is set as an integer; however
  values in 'other_config' dict must be strings.

  Info: http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf, pages 1 and
  14-15.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1643532/+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 1082248] Re: Use uuidutils instead of uuid.uuid4()

2016-11-21 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/398943
Committed: 
https://git.openstack.org/cgit/openstack/watcher/commit/?id=876f3adb221271ece06cc1d6a893c81d7d4e0f45
Submitter: Jenkins
Branch:master

commit 876f3adb221271ece06cc1d6a893c81d7d4e0f45
Author: qinchunhua 
Date:   Thu Nov 17 19:27:54 2016 +0800

Replaces uuid.uuid4 with uuidutils.generate_uuid()

Change-Id: I38740842402841ae446603faacbbe969854f2396
Closes-Bug: #1082248


** Changed in: watcher
   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/1082248

Title:
  Use uuidutils instead of uuid.uuid4()

Status in Cinder:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  Fix Released
Status in Karbor:
  In Progress
Status in kolla:
  In Progress
Status in kuryr:
  In Progress
Status in kuryr-libnetwork:
  In Progress
Status in Magnum:
  In Progress
Status in Mistral:
  Fix Released
Status in Murano:
  In Progress
Status in networking-calico:
  In Progress
Status in networking-ovn:
  Fix Released
Status in networking-sfc:
  In Progress
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  In Progress
Status in python-muranoclient:
  In Progress
Status in Sahara:
  Fix Released
Status in senlin:
  Fix Released
Status in tacker:
  In Progress
Status in watcher:
  Fix Released

Bug description:
  Openstack common has a wrapper for generating uuids.

  We should only use that function when generating uuids for
  consistency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1082248/+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 1643532] [NEW] 'other_config' information is not written in ovs agent

2016-11-21 Thread Rodolfo Alonso 
Public bug reported:

'other_config' information is not written in ovs agent.

During the creation of a port, OVS databse is updated. 'other_config'
key in Port database is not written correctly.

This transaction is executed in 'port_bound' function.
other_config:segmentation_id value is set as an integer; however values
in 'other_config' dict must be strings.

Info: http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf, pages 1 and
14-15.

** Affects: neutron
 Importance: Undecided
 Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)

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

Title:
  'other_config' information is not written in ovs agent

Status in neutron:
  New

Bug description:
  'other_config' information is not written in ovs agent.

  During the creation of a port, OVS databse is updated. 'other_config'
  key in Port database is not written correctly.

  This transaction is executed in 'port_bound' function.
  other_config:segmentation_id value is set as an integer; however
  values in 'other_config' dict must be strings.

  Info: http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf, pages 1 and
  14-15.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1643532/+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 1643511] Re: nova-api commands fail when running behind httpd

2016-11-21 Thread Gabriele Cerami 
** Also affects: tripleo
   Importance: Undecided
   Status: New

** Changed in: tripleo
Milestone: None => ocata-2

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

Title:
  nova-api commands fail when running behind httpd

Status in OpenStack Compute (nova):
  In Progress
Status in tripleo:
  Confirmed

Bug description:
  After https://review.openstack.org/#/c/333212 when running some
  openstack nova commands we are getting errors like [1]:

  Execution of '/usr/bin/openstack flavor create --format shell m1.micro
  --public --id 84 --ram 128 --disk 0 --vcpus 1' returned 1: Unknown
  Error (HTTP 500)

  Following error is found in apache logs:

  [Sat Nov 19 10:39:12.366389 2016] [:error] [pid 21326] [remote ::1:80] 
mod_wsgi (pid=21326): Exception occurred processing WSGI script 
'/var/www/cgi-bin/nova/nova-api'.
  [Sat Nov 19 10:39:12.366458 2016] [:error] [pid 21326] [remote ::1:80] 
TypeError: expected byte string object for header value, value of type unicode 
found

  We are hitting this bug both in puppet-openstack-integration and
  tripleo jobs.

  
  [1] 
https://ci.centos.org/artifacts/rdo/weirdo-master-promote-puppet-openstack-scenario003/689/weirdo-project/puppet.txt.gz
  [2] 
https://ci.centos.org/artifacts/rdo/weirdo-master-promote-puppet-openstack-scenario003/689/weirdo-project/logs/apache/nova_api_wsgi_error_ssl.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1643511/+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 1643511] [NEW] nova-api commands fail when running behind httpd

2016-11-21 Thread Alfredo Moralejo 
Public bug reported:

After https://review.openstack.org/#/c/333212 when running some
openstack nova commands we are getting errors like [1]:

Execution of '/usr/bin/openstack flavor create --format shell m1.micro
--public --id 84 --ram 128 --disk 0 --vcpus 1' returned 1: Unknown Error
(HTTP 500)

Following error is found in apache logs:

[Sat Nov 19 10:39:12.366389 2016] [:error] [pid 21326] [remote ::1:80] mod_wsgi 
(pid=21326): Exception occurred processing WSGI script 
'/var/www/cgi-bin/nova/nova-api'.
[Sat Nov 19 10:39:12.366458 2016] [:error] [pid 21326] [remote ::1:80] 
TypeError: expected byte string object for header value, value of type unicode 
found

We are hitting this bug both in puppet-openstack-integration and tripleo
jobs.


[1] 
https://ci.centos.org/artifacts/rdo/weirdo-master-promote-puppet-openstack-scenario003/689/weirdo-project/puppet.txt.gz
[2] 
https://ci.centos.org/artifacts/rdo/weirdo-master-promote-puppet-openstack-scenario003/689/weirdo-project/logs/apache/nova_api_wsgi_error_ssl.txt.gz

** Affects: nova
 Importance: Undecided
 Status: New

** Affects: tripleo
 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/1643511

Title:
  nova-api commands fail when running behind httpd

Status in OpenStack Compute (nova):
  New
Status in tripleo:
  New

Bug description:
  After https://review.openstack.org/#/c/333212 when running some
  openstack nova commands we are getting errors like [1]:

  Execution of '/usr/bin/openstack flavor create --format shell m1.micro
  --public --id 84 --ram 128 --disk 0 --vcpus 1' returned 1: Unknown
  Error (HTTP 500)

  Following error is found in apache logs:

  [Sat Nov 19 10:39:12.366389 2016] [:error] [pid 21326] [remote ::1:80] 
mod_wsgi (pid=21326): Exception occurred processing WSGI script 
'/var/www/cgi-bin/nova/nova-api'.
  [Sat Nov 19 10:39:12.366458 2016] [:error] [pid 21326] [remote ::1:80] 
TypeError: expected byte string object for header value, value of type unicode 
found

  We are hitting this bug both in puppet-openstack-integration and
  tripleo jobs.

  
  [1] 
https://ci.centos.org/artifacts/rdo/weirdo-master-promote-puppet-openstack-scenario003/689/weirdo-project/puppet.txt.gz
  [2] 
https://ci.centos.org/artifacts/rdo/weirdo-master-promote-puppet-openstack-scenario003/689/weirdo-project/logs/apache/nova_api_wsgi_error_ssl.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1643511/+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 1643485] [NEW] Stable Newton grenade multinode jobs fail with "Failed to connect to the host via ssh: Host key verification failed."

2016-11-21 Thread Jakub Libosvar 
Public bug reported:

post-stack part of grenade fails: e.g.
http://logs.openstack.org/42/399142/1/gate/gate-grenade-dsvm-
multinode/a25f646/logs/grenade.sh.txt.gz#_2016-11-20_10_18_52_797

** Affects: neutron
 Importance: Critical
 Status: New

** Changed in: neutron
   Importance: Undecided => Critical

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

Title:
  Stable Newton grenade multinode jobs fail with "Failed to connect to
  the host via ssh: Host key verification failed."

Status in neutron:
  New

Bug description:
  post-stack part of grenade fails: e.g.
  http://logs.openstack.org/42/399142/1/gate/gate-grenade-dsvm-
  multinode/a25f646/logs/grenade.sh.txt.gz#_2016-11-20_10_18_52_797

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1643485/+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 1643484] [NEW] Functional jobs pass int values to ovsdb other_config

2016-11-21 Thread Jakub Libosvar 
Public bug reported:

other_config is a map that expects {"string": "string", ... } values
while sometimes int is passed instead of string which leads to error log
message: attempting to write bad value to column other_config (ovsdb
error: expected string, got )

** Affects: neutron
 Importance: Low
 Assignee: Jakub Libosvar (libosvar)
 Status: In Progress

** Changed in: neutron
   Importance: Undecided => Low

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

Title:
  Functional jobs pass int values to ovsdb other_config

Status in neutron:
  In Progress

Bug description:
  other_config is a map that expects {"string": "string", ... } values
  while sometimes int is passed instead of string which leads to error
  log message: attempting to write bad value to column other_config
  (ovsdb error: expected string, got )

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1643484/+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 1643477] [NEW] TRACE keystone ValueError: Empty module name

2016-11-21 Thread shaoliangliang 
Public bug reported:

2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone 
driver = importutils.import_object(driver_name, *args)
2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 44, in 
import_object
2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone 
return import_class(import_str)(*args, **kwargs)
2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 30, in 
import_class
2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone 
__import__(mod_str)
2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone 
ValueError: Empty module name
2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone 
2016-11-21 08:42:41.793 | +lib/keystone:bootstrap_keystone:1 exit_trap
2016-11-21 08:42:41.799 | +./stack.sh:exit_trap:487  local r=1
2016-11-21 08:42:41.809 | ++./stack.sh:exit_trap:488  jobs -p
2016-11-21 08:42:41.817 | +./stack.sh:exit_trap:488  jobs=
2016-11-21 08:42:41.822 | +./stack.sh:exit_trap:491  [[ -n '' ]]
2016-11-21 08:42:41.831 | +./stack.sh:exit_trap:497  
kill_spinner
2016-11-21 08:42:41.839 | +./stack.sh:kill_spinner:383   '[' '!' -z 
'' ']'
2016-11-21 08:42:41.847 | +./stack.sh:exit_trap:499  [[ 1 -ne 0 
]]
2016-11-21 08:42:41.856 | +./stack.sh:exit_trap:500  echo 
'Error on exit'
2016-11-21 08:42:41.856 | Error on exit
2016-11-21 08:42:41.862 | +./stack.sh:exit_trap:501  
generate-subunit 1479717436 325 fail
2016-11-21 08:42:42.231 | +./stack.sh:exit_trap:502  [[ -z 
/opt/stack/logs ]]
2016-11-21 08:42:42.235 | +./stack.sh:exit_trap:505  
/home/devstack/tools/worlddump.py -d /opt/stack/logs
2016-11-21 08:42:42.568 | +./stack.sh:exit_trap:511  exit 1

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

Title:
  TRACE keystone ValueError: Empty module name

Status in OpenStack Identity (keystone):
  New

Bug description:
  2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone 
driver = importutils.import_object(driver_name, *args)
  2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 44, in 
import_object
  2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone 
return import_class(import_str)(*args, **kwargs)
  2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 30, in 
import_class
  2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone 
__import__(mod_str)
  2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone 
ValueError: Empty module name
  2016-11-21 08:42:41.728 | 2016-11-21 16:42:41.725 21346 TRACE keystone 
  2016-11-21 08:42:41.793 | +lib/keystone:bootstrap_keystone:1 exit_trap
  2016-11-21 08:42:41.799 | +./stack.sh:exit_trap:487  local r=1
  2016-11-21 08:42:41.809 | ++./stack.sh:exit_trap:488  jobs -p
  2016-11-21 08:42:41.817 | +./stack.sh:exit_trap:488  jobs=
  2016-11-21 08:42:41.822 | +./stack.sh:exit_trap:491  [[ -n '' 
]]
  2016-11-21 08:42:41.831 | +./stack.sh:exit_trap:497  
kill_spinner
  2016-11-21 08:42:41.839 | +./stack.sh:kill_spinner:383   '[' '!' 
-z '' ']'
  2016-11-21 08:42:41.847 | +./stack.sh:exit_trap:499  [[ 1 -ne 
0 ]]
  2016-11-21 08:42:41.856 | +./stack.sh:exit_trap:500  echo 
'Error on exit'
  2016-11-21 08:42:41.856 | Error on exit
  2016-11-21 08:42:41.862 | +./stack.sh:exit_trap:501  
generate-subunit 1479717436 325 fail
  2016-11-21 08:42:42.231 | +./stack.sh:exit_trap:502  [[ -z 
/opt/stack/logs ]]
  2016-11-21 08:42:42.235 | +./stack.sh:exit_trap:505  
/home/devstack/tools/worlddump.py -d /opt/stack/logs
  2016-11-21 08:42:42.568 | +./stack.sh:exit_trap:511  exit 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1643477/+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 1613542] Re: tempest.conf doesn't contain $project in [service_available] section

2016-11-21 Thread Yanyan Hu 
** Changed in: senlin
   Status: In Progress => Invalid

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

Title:
  tempest.conf doesn't contain $project in [service_available] section

Status in Aodh:
  Fix Released
Status in Ceilometer:
  Fix Released
Status in ec2-api:
  Fix Released
Status in Gnocchi:
  Fix Released
Status in Ironic:
  In Progress
Status in Ironic Inspector:
  Fix Released
Status in OpenStack Identity (keystone):
  Invalid
Status in Magnum:
  Fix Released
Status in neutron:
  New
Status in OpenStack Data Processing ("Sahara") sahara-tests:
  Fix Released
Status in senlin:
  Invalid
Status in Vitrage:
  In Progress
Status in vmware-nsx:
  Fix Released

Bug description:
  When generating the tempest conf, the tempest plugins need to register the 
config options.
  But for the [service_available] section, ceilometer (and the other mentioned 
projects) doesn't register any value so it's missng in the tempest sample 
config.

  Steps to reproduce:

  $ tox -egenconfig
  $ source .tox/genconfig/bin/activate
  $ oslo-config-generator --config-file 
.tox/genconfig/lib/python2.7/site-packages/tempest/cmd/config-generator.tempest.conf
 --output-file tempest.conf.sample

  Now check the [service_available] section from tempest.conf.sample

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1613542/+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 1082248] Re: Use uuidutils instead of uuid.uuid4()

2016-11-21 Thread bailin.zhang 
** Also affects: gnocchi
   Importance: Undecided
   Status: New

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

** Changed in: gnocchi
 Assignee: (unassigned) => bailin.zhang (bailin-zhang)

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

Title:
  Use uuidutils instead of uuid.uuid4()

Status in Cinder:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  Fix Released
Status in Karbor:
  In Progress
Status in kolla:
  In Progress
Status in kuryr:
  In Progress
Status in kuryr-libnetwork:
  In Progress
Status in Magnum:
  In Progress
Status in Mistral:
  Fix Released
Status in Murano:
  In Progress
Status in networking-calico:
  In Progress
Status in networking-ovn:
  Fix Released
Status in networking-sfc:
  In Progress
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  In Progress
Status in python-muranoclient:
  In Progress
Status in Sahara:
  Fix Released
Status in senlin:
  Fix Released
Status in tacker:
  In Progress
Status in watcher:
  In Progress

Bug description:
  Openstack common has a wrapper for generating uuids.

  We should only use that function when generating uuids for
  consistency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1082248/+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 1643451] [NEW] neutron devstack plugin enables q-trunk depending on rally

2016-11-21 Thread YAMAMOTO Takashi 
Public bug reported:

it enables q-trunk if rally devstack plugin is enabled.

i wanted to use neutron devstack plugin to configure qos plugin. [1]
i was surprised that it enables q-trunk.

[1] https://github.com/openstack/networking-
midonet/blob/691f8490317f36ec2c629c9a397c09eebf7638bd/devstack/README.rst#qos

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  neutron devstack plugin enables q-trunk depending on rally

Status in neutron:
  New

Bug description:
  it enables q-trunk if rally devstack plugin is enabled.

  i wanted to use neutron devstack plugin to configure qos plugin. [1]
  i was surprised that it enables q-trunk.

  [1] https://github.com/openstack/networking-
  midonet/blob/691f8490317f36ec2c629c9a397c09eebf7638bd/devstack/README.rst#qos

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