date:20160320

[Yahoo-eng-team] [Bug 1521815] Re: DVR functional tests failing intermittently

2016-03-20 Thread Launchpad Bug Tracker

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
   Status: Incomplete => Expired

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

Title:
  DVR functional tests failing intermittently

Status in neutron:
  Expired

Bug description:
  Some console logs:

  
http://logs.openstack.org/18/248418/3/check/gate-neutron-dsvm-functional/8a6dfcf/console.html
  
http://logs.openstack.org/00/189500/23/check/gate-neutron-dsvm-functional/d949ce0/console.html
  
http://logs.openstack.org/72/252072/1/check/gate-neutron-dsvm-functional/aafcd9a/console.html
  
http://logs.openstack.org/32/192032/26/check/gate-neutron-dsvm-functional/b267f83/console.html
  
http://logs.openstack.org/02/251502/3/check/gate-neutron-dsvm-functional/b074a96/console.html

  Tests seen failing so far (May not be comprehensive):
  
neutron.tests.functional.agent.l3.test_dvr_router.TestDvrRouter.test_dvr_router_add_fips_on_restarted_agent
  
neutron.tests.functional.agent.l3.test_dvr_router.TestDvrRouter.test_dvr_router_lifecycle_without_ha_with_snat_with_fips
  
neutron.tests.functional.agent.l3.test_dvr_router.TestDvrRouter.test_dvr_router_lifecycle_ha_with_snat_with_fips
  
neutron.tests.functional.agent.l3.test_dvr_router.TestDvrRouter.test_dvr_router_lifecycle_without_ha_without_snat_with_fips

  The commonality is:
  1) DVR tests (With and without HA, with and without SNAT)
  2) The tests are taking thousands of seconds to fail, causing the job to time 
out, this is even though we're supposed to have a per-test timeout of 180 
seconds defined in tox.ini. This means (I suspect) that we're not getting the 
functional tests logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1521815/+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 1533984] Re: Unexpected API Error, Unable to launch instance

2016-03-20 Thread Launchpad Bug Tracker

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
   Status: Incomplete => Expired

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

Title:
   Unexpected API Error, Unable to launch instance

Status in OpenStack Compute (nova):
  Expired

Bug description:
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions 
[req-8301ca11-42d5-4fb8-8945-58d743dd5613 6082754577a84cae9230d97f8215a7e4 
c9e30dd215b84199b8f3ff0303fde797 - - -] Unexpected exception in API method
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, 
in wrapped
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in 
wrapper
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in 
wrapper
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 
611, in create
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions 
**create_kwargs)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/hooks.py", line 149, in inner
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions rv = 
f(*args, **kwargs)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/compute/api.py", line 1581, in create
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions 
check_server_group_quota=check_server_group_quota)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/compute/api.py", line 1181, in 
_create_instance
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions 
auto_disk_config, reservation_id, max_count)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/compute/api.py", line 923, in 
_validate_and_build_base_options
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions 
requested_networks, max_count)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/compute/api.py", line 533, in 
_check_requested_networks
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions 
max_count)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/network/api.py", line 49, in wrapped
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions return 
func(self, context, *args, **kwargs)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/network/api.py", line 396, in 
validate_networks
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions 
requested_networks)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/network/rpcapi.py", line 204, in 
validate_networks
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions return 
self.client.call(ctxt, 'validate_networks', networks=networks)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 403, in 
call
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions return 
self.prepare().call(ctxt, method, **kwargs)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 158, in 
call
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions 
retry=self.retry)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 90, in 
_send
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions 
timeout=timeout, retry=retry)
  2016-01-14 11:44:10.056 2737 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 
431, in send
  2016-01-14 11:44:10.056 2737 ERROR

[Yahoo-eng-team] [Bug 1536470] Re: Fixing test cases

2016-03-20 Thread OpenStack Infra

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

commit b6b685ab9855951cbc123cd44110244ca2ff7d20
Author: sanjana 
Date:   Thu Jan 21 15:45:57 2016 +0530

Fixing test cases

The tests in ceilometer_tests.py for fetching the meter list,
alarm list, sample list, statistic list and the resource list
are incomplete.It verifies the API call, but the API could fail
completely and an empty list would still pass the assertion.
This patch fixes it.

Change-Id: I532992a9a7ad150c83e7f18721d885721070b029
Closes-bug:#1536470


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

Title:
  Fixing test cases

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The tests in ceilometer_tests.py file for fetching the meter list,
  sample list, statistic list and the resource list are incomplete. It
  verifies the API call, but the API could fail completely and an empty
  list would pass the assertion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1536470/+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 1558807] Re: Volume attached at different path than reported by nova/cinder when using config drive

2016-03-20 Thread Sean McGinnis

Appears to be an issue on the Nova side, but marking Cinder as Invalid
for now instead of removing it in case there are any changes required on
the Cinder side to address this.

** Changed in: cinder
   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/1558807

Title:
  Volume attached at different path than reported by nova/cinder when
  using config drive

Status in Cinder:
  Invalid
Status in OpenStack Compute (nova):
  New

Bug description:
  When booting a node with config drive then attaching a cinder volume
  we see conflicting information about where the cinder volume is
  attached. In this case the config drive is at /dev/vdb, the cinder
  volume is at /dev/vdc but volume show reports the cinder volume to be
  at /dev/vdb.

  This shows how one can get nova/cinder in this state using
  openstackclient (assuming that config drives attach to /dev/vdb):

  $ OS_CLIENT_CONFIG_FILE=../vexxhost/vexx.yaml venv/bin/openstack --os-cloud 
openstackci-vexxhost server create --config-drive True --key-name clarkb-work 
--image ubuntu-trusty --flavor v1-standard-2 clarkb-test
  
+--+--+
  | Field| Value
|
  
+--+--+
  | OS-DCF:diskConfig| MANUAL   
|
  | OS-EXT-AZ:availability_zone  |  
|
  | OS-EXT-STS:power_state   | 0
|
  | OS-EXT-STS:task_state| scheduling   
|
  | OS-EXT-STS:vm_state  | building 
|
  | OS-SRV-USG:launched_at   | None 
|
  | OS-SRV-USG:terminated_at | None 
|
  | accessIPv4   |  
|
  | accessIPv6   |  
|
  | addresses|  
|
  | adminPass| redacted 
|
  | config_drive | True 
|
  | created  | 2016-03-17T21:12:38Z 
|
  | flavor   | v1-standard-2 
(ca2a6e9c-2236-4107-8905-7ae9427132ff) |
  | hostId   |  
|
  | id   | cdaf7671-5a5c-4118-a422-d8aae096bd1e 
|
  | image| ubuntu-trusty 
(d42c4ce4-3fa0-4dcb-877e-1d66a05a4f8d) |
  | key_name | clarkb-work  
|
  | name | clarkb-test  
|
  | os-extended-volumes:volumes_attached | []   
|
  | progress | 0
|
  | project_id   | projectid
|
  | properties   |  
|
  | security_groups  | [{u'name': u'default'}]  
|
  | status   | BUILD
|
  | updated  | 2016-03-17T21:12:38Z 
|
  | user_id  | userid   
|
  
+--+--+
  $ OS_CLIENT_CONFIG_FILE=../vexxhost/vexx.yaml venv/bin/openstack --os-cloud 
openstackci-vexxhost volume create --size 100 clarkb-test
  +-+--+
  | Field   | Value|
  +-+--+
  | attachments | []   |
  | availability_zone   | ca-ymq-2 |
  | bootable| false|
  | consistencygroup_id | None |
  | created_at  | 2016-03-17T21:13:13.683882   |
  | description | None

[Yahoo-eng-team] [Bug 1538620] Re: Attach with host and instance_uuid not backwards compatible

2016-03-20 Thread Sean McGinnis

** No longer affects: cinder

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

Title:
  Attach with host and instance_uuid not backwards compatible

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Patch https://review.openstack.org/#/c/266006/ added the ability for
  Cinder to accept both host and instance_uuid when doing an attach.
  This is not backwards compatible to earlier API versions, so when Nova
  calls attach with versions prior to this change with both arguments it
  causes a failure.

  This information is needed for the multiattach work, but we should
  revert that change and try to find a cleaner way to do this that will
  not break backwards compatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538620/+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 1557255] Re: keystone crashes after installing networking-odl in Liberty

2016-03-20 Thread Morgan Fainberg

Marked as invalid. This was an issue with OpenDaylight installing a
version of PBR that was not compatible with keystone - version conflict
outside the scope of keystone project.

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

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

Title:
  keystone crashes after installing networking-odl in Liberty

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  Hi there! i am trying to integrate OpenDaylight Be and OpenStack
  Liberty on Ubuntu 14.04.4 Server. Keystone was working fine before
  integrating. After installing python-pip and networking_odl (apt-get
  install python-pip and pip install networking_odl) keystone throws 505
  internal server error. (No handlers could be found for logger
  “keystoneclient.auth.identity.generic.base” ERROR
  (InternalServerError): Internal Server Error (HTTP 500)).Installing
  again from scratch didn't solve the issue.Keystone log in apace2
  showed the following error.

  2016-03-14 19:24:01.930398 No handlers could be found for logger 
"oslo_config.cfg"
  2016-03-14 19:24:02.248054 mod_wsgi (pid=4579): Target WSGI script 
'/usr/bin/keystone-wsgi-admin' cannot be loaded as Python module.
  2016-03-14 19:24:02.248133 mod_wsgi (pid=4579): Exception occurred processing 
WSGI script '/usr/bin/keystone-wsgi-admin'.
  2016-03-14 19:24:02.248208 Traceback (most recent call last):
  2016-03-14 19:24:02.248264 File "/usr/bin/keystone-wsgi-admin", line 36, in 

  2016-03-14 19:24:02.248328 application = initialize_admin_application()
  2016-03-14 19:24:02.248355 File 
"/usr/lib/python2.7/dist-packages/keystone/server/wsgi.py", line 78, in 
initialize_admin_application
  2016-03-14 19:24:02.248386 return initialize_application('admin')
  2016-03-14 19:24:02.248404 File 
"/usr/lib/python2.7/dist-packages/keystone/server/wsgi.py", line 64, in 
initialize_application
  2016-03-14 19:24:02.248437 startup_application_fn=loadapp)
  2016-03-14 19:24:02.248457 File 
"/usr/lib/python2.7/dist-packages/keystone/server/common.py", line 51, in 
setup_backends
  2016-03-14 19:24:02.248479 res = startup_application_fn()
  2016-03-14 19:24:02.248501 File 
"/usr/lib/python2.7/dist-packages/keystone/server/wsgi.py", line 61, in loadapp
  2016-03-14 19:24:02.248525 'config:%s' % config.find_paste_config(), name)
  2016-03-14 19:24:02.248537 File 
"/usr/lib/python2.7/dist-packages/keystone/service.py", line 46, in loadapp
  2016-03-14 19:24:02.248641 controllers.latest_app = deploy.loadapp(conf, 
name=name)
  2016-03-14 19:24:02.248658 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 247, in 
loadapp
  2016-03-14 19:24:02.248922 return loadobj(APP, uri, name=name, **kw)
  2016-03-14 19:24:02.248943 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 272, in 
loadobj
  2016-03-14 19:24:02.248967 return context.create()
  2016-03-14 19:24:02.248979 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710, in create
  2016-03-14 19:24:02.248995 return self.object_type.invoke(self)
  2016-03-14 19:24:02.249006 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 144, in invoke
  2016-03-14 19:24:02.249021 **context.local_conf)
  2016-03-14 19:24:02.249032 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/util.py", line 55, in fix_call
  2016-03-14 19:24:02.249103 val = callable(*args, **kw)
  2016-03-14 19:24:02.249121 File 
"/usr/lib/python2.7/dist-packages/paste/urlmap.py", line 28, in urlmap_factory
  2016-03-14 19:24:02.249228 app = loader.get_app(app_name, 
global_conf=global_conf)
  2016-03-14 19:24:02.249245 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 350, in 
get_app
  2016-03-14 19:24:02.249266 name=name, global_conf=global_conf).create()
  2016-03-14 19:24:02.249278 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 362, in 
app_context
  2016-03-14 19:24:02.249294 APP, name=name, global_conf=global_conf)
  2016-03-14 19:24:02.249304 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 450, in 
get_context
  2016-03-14 19:24:02.249319 global_additions=global_additions)
  2016-03-14 19:24:02.249330 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 559, in 
_pipeline_app_context
  2016-03-14 19:24:02.249345 APP, pipeline[-1], global_conf)
  2016-03-14 19:24:02.249356 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 454, in 
get_context
  2016-03-14 19:24:02.249371 section)
  2016-03-14 19:24:02.249381 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 476, in 
_context_from_use
  2016-03-14 19:24:02.249396 object_type, name=use, global_conf=global_conf)
  2016-03-14 19:24:02.249406 File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 406, in 
get_context

[Yahoo-eng-team] [Bug 1558690] Re: project set works for invalid properties

2016-03-20 Thread Morgan Fainberg

This is a "feature" (i use that term loosely) in keystone (the extras
field), changing behavior at this point is not in scope. Fixing things
at the CLI to be more friendly might be doable.

Marked as wont fix because this is not something we can change behavior
on.

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

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

Title:
  project set works for invalid properties

Status in OpenStack Identity (keystone):
  Won't Fix
Status in python-openstackclient:
  New

Bug description:
  openstack project set accepts invalid properties, and even somehow
  sets their values

  # openstack project set ABC --property xyz=pqr
  # openstack project show ABC
  +-+--+
  | Field   | Value|
  +-+--+
  | description |  |
  | domain_id   | ef8acb82bebd4c4abdc6b2056440b596 |
  | enabled | True |
  | id  | 315700c2a1384b1ca21543504e3513bb |
  | is_domain   | False|
  | name| ABC  |
  | xyz | pqr  |
  +-+--+

  As seen above, the new "xyz" field was created with the specified
  value. This is not a valid property and should not have been created.

  Also, specifying an invalid property without a value did not return an
  error:

  # openstack project set ABC --property QQQ
  # openstack project show ABC
  +-+--+
  | Field   | Value|
  +-+--+
  | description |  |
  | domain_id   | ef8acb82bebd4c4abdc6b2056440b596 |
  | enabled | True |
  | id  | 315700c2a1384b1ca21543504e3513bb |
  | is_domain   | False|
  | name| ABC  |
  | xyz | pqr  |
  +-+--+

  openstackclient version = 1.5.0
  keystone version = mitaka

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1558690/+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 1558343] Re: configdrive is lost after resize.(libvirt driver)

2016-03-20 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/294560
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=29fb0aca1623eb0c4a565d728501667a4c5e8136
Submitter: Jenkins
Branch:master

commit 29fb0aca1623eb0c4a565d728501667a4c5e8136
Author: Matthew Booth 
Date:   Fri Mar 18 12:12:51 2016 +

Fix conversion of config disks to qcow2 during resize/migration

finish_migration contains some code which converts raw disks to qcow2
when moving from a host which uses raw disks to a host which uses
qcow2 disks. This was erroneously also converted config disks, which
are hard-coded to be raw even when other disks are qcow2.

This has always been broken, but it wasn't previously exposed because
a subsequent bug unconditionally overwrote the qcow2 config disk with
a new, raw one. Change I03e08fae97416ebe5cdedcf238a06d1b90203c5d
changed the order of these 2 events, so that the erroneously-converted
config drive was no longer overwritten, resulting in a qcow2 file
being presented to the instance as raw.

This change explicitly filters out config disks from conversion.

Change-Id: I6bf3cd4f9e0e152bf69732d9a17f93c86dedbd40
Closes-Bug: #1558343


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

Title:
  configdrive is lost after resize.(libvirt driver)

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) kilo series:
  Confirmed
Status in OpenStack Compute (nova) liberty series:
  Confirmed

Bug description:
  Used the trunk code as of 2016/03/16
  my environment disabled metadata agent and forced the use of config drive.

  
  console log before resize: http://paste.openstack.org/show/490825/
  console log after resize: http://paste.openstack.org/show/490824/

  
  qemu 18683 1  4 18:40 ?00:00:32 /usr/bin/qemu-system-x86_64 
-name instance-0002 -S -machine pc-i440fx-2.0,accel=tcg,usb=off -m 128 
-realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 
018892c7-8144-49c0-93d2-79ee83efd6a9 -smbios type=1,manufacturer=OpenStack 
Foundation,product=OpenStack 
Nova,version=13.0.0,serial=16c127e2-6369-4e19-a646-251a416a8dcd,uuid=018892c7-8144-49c0-93d2-79ee83efd6a9,family=Virtual
 Machine -no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-instance-0002/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive 
file=/opt/stack/data/nova/instances/018892c7-8144-49c0-93d2-79ee83efd6a9/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -drive file=/opt/stack/da
 
ta/nova/instances/018892c7-8144-49c0-93d2-79ee83efd6a9/disk.config,if=none,id=drive-ide0-1-1,readonly=on,format=raw,cache=none
 -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1 -netdev 
tap,fd=23,id=hostnet0 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:34:d6:f3,bus=pci.0,addr=0x3 
-chardev 
file,id=charserial0,path=/opt/stack/data/nova/instances/018892c7-8144-49c0-93d2-79ee83efd6a9/console.log
 -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 
-device isa-serial,chardev=charserial1,id=serial1 -vnc 127.0.0.1:1 -k en-us 
-device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on

  
  $ blkid
  /dev/vda1: LABEL="cirros-rootfs" UUID="d42bb4a4-04bb-49b0-8821-5b813116b17b" 
TYPE="ext3" 
  $ 

  
  another vm without resize:
  $ blkid 
  /dev/vda1: LABEL="cirros-rootfs" UUID="d42bb4a4-04bb-49b0-8821-5b813116b17b" 
TYPE="ext3" 
  /dev/sr0: LABEL="config-2" TYPE="iso9660" 
  $

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1558343/+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 1559026] [NEW] nova-novncproxy doesn't start when 'record' is specified

2016-03-20 Thread Radoslav Gerganov

Public bug reported:

$ /usr/local/bin/nova-novncproxy --record --config-file
/etc/nova/nova.conf --web /opt/stack/noVNC

2016-03-18 12:34:01.940 CRITICAL nova [-] AttributeError: 'bool' object
has no attribute 'startswith'

2016-03-18 12:34:01.940 TRACE nova Traceback (most recent call last):
2016-03-18 12:34:01.940 TRACE nova   File "/usr/local/bin/nova-novncproxy", 
line 10, in 
2016-03-18 12:34:01.940 TRACE nova sys.exit(main())
2016-03-18 12:34:01.940 TRACE nova   File 
"/opt/stack/nova/nova/cmd/novncproxy.py", line 39, in main
2016-03-18 12:34:01.940 TRACE nova port=CONF.vnc.novncproxy_port)
2016-03-18 12:34:01.940 TRACE nova   File 
"/opt/stack/nova/nova/cmd/baseproxy.py", line 73, in proxy
2016-03-18 12:34:01.940 TRACE nova 
RequestHandlerClass=websocketproxy.NovaProxyRequestHandler
2016-03-18 12:34:01.940 TRACE nova   File 
"/usr/local/lib/python2.7/dist-packages/websockify/websocketproxy.py", line 
265, in __init__
2016-03-18 12:34:01.940 TRACE nova websocket.WebSocketServer.__init__(self, 
RequestHandlerClass, *args, **kwargs)
2016-03-18 12:34:01.940 TRACE nova   File 
"/usr/local/lib/python2.7/dist-packages/websockify/websocket.py", line 647, in 
__init__
2016-03-18 12:34:01.940 TRACE nova self.record = os.path.abspath(record)
2016-03-18 12:34:01.940 TRACE nova   File "/usr/lib/python2.7/posixpath.py", 
line 367, in abspath
2016-03-18 12:34:01.940 TRACE nova if not isabs(path):
2016-03-18 12:34:01.940 TRACE nova   File "/usr/lib/python2.7/posixpath.py", 
line 61, in isabs
2016-03-18 12:34:01.940 TRACE nova return s.startswith('/')
2016-03-18 12:34:01.940 TRACE nova AttributeError: 'bool' object has no 
attribute 'startswith'
2016-03-18 12:34:01.940 TRACE nova 


The 'record' argument should be string, not boolean.

** Affects: nova
 Importance: Low
 Assignee: Radoslav Gerganov (rgerganov)
 Status: In Progress

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

Title:
  nova-novncproxy doesn't start when 'record' is specified

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  $ /usr/local/bin/nova-novncproxy --record --config-file
  /etc/nova/nova.conf --web /opt/stack/noVNC

  2016-03-18 12:34:01.940 CRITICAL nova [-] AttributeError: 'bool'
  object has no attribute 'startswith'

  2016-03-18 12:34:01.940 TRACE nova Traceback (most recent call last):
  2016-03-18 12:34:01.940 TRACE nova   File "/usr/local/bin/nova-novncproxy", 
line 10, in 
  2016-03-18 12:34:01.940 TRACE nova sys.exit(main())
  2016-03-18 12:34:01.940 TRACE nova   File 
"/opt/stack/nova/nova/cmd/novncproxy.py", line 39, in main
  2016-03-18 12:34:01.940 TRACE nova port=CONF.vnc.novncproxy_port)
  2016-03-18 12:34:01.940 TRACE nova   File 
"/opt/stack/nova/nova/cmd/baseproxy.py", line 73, in proxy
  2016-03-18 12:34:01.940 TRACE nova 
RequestHandlerClass=websocketproxy.NovaProxyRequestHandler
  2016-03-18 12:34:01.940 TRACE nova   File 
"/usr/local/lib/python2.7/dist-packages/websockify/websocketproxy.py", line 
265, in __init__
  2016-03-18 12:34:01.940 TRACE nova 
websocket.WebSocketServer.__init__(self, RequestHandlerClass, *args, **kwargs)
  2016-03-18 12:34:01.940 TRACE nova   File 
"/usr/local/lib/python2.7/dist-packages/websockify/websocket.py", line 647, in 
__init__
  2016-03-18 12:34:01.940 TRACE nova self.record = os.path.abspath(record)
  2016-03-18 12:34:01.940 TRACE nova   File "/usr/lib/python2.7/posixpath.py", 
line 367, in abspath
  2016-03-18 12:34:01.940 TRACE nova if not isabs(path):
  2016-03-18 12:34:01.940 TRACE nova   File "/usr/lib/python2.7/posixpath.py", 
line 61, in isabs
  2016-03-18 12:34:01.940 TRACE nova return s.startswith('/')
  2016-03-18 12:34:01.940 TRACE nova AttributeError: 'bool' object has no 
attribute 'startswith'
  2016-03-18 12:34:01.940 TRACE nova 

  
  The 'record' argument should be string, not boolean.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1559026/+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 1508442] Re: LOG.warn is deprecated

2016-03-20 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/291677
Committed: 
https://git.openstack.org/cgit/openstack/networking-vsphere/commit/?id=89083c5fdf9f3bee8d9752f8f0dfda31411f9913
Submitter: Jenkins
Branch:master

commit 89083c5fdf9f3bee8d9752f8f0dfda31411f9913
Author: Aman Kumar 
Date:   Fri Mar 11 03:54:03 2016 -0800

log.warn is deprecated in python 3

Python 3 deprecated the LOG.warn method, see:
https://docs.python.org/3/library/logging.html#logging.warning, so we
prefer to use warning to avoid DeprecationWarning.

Neutron Upstream review link is available here:
https://review.openstack.org/#/c/278277/

Change-Id: Id0c49c4f604518cdf40bf68572698d5cb623f32d
Closes-Bug: #1508442


** Changed in: networking-vsphere
   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/1508442

Title:
  LOG.warn is deprecated

Status in anvil:
  In Progress
Status in Aodh:
  Fix Released
Status in Astara:
  Fix Released
Status in Barbican:
  Fix Released
Status in bilean:
  Fix Released
Status in Blazar:
  In Progress
Status in Ceilometer:
  Fix Released
Status in cloud-init:
  In Progress
Status in cloudkitty:
  Fix Released
Status in congress:
  Fix Released
Status in Designate:
  Fix Released
Status in django-openstack-auth:
  Fix Released
Status in django-openstack-auth-kerberos:
  In Progress
Status in DragonFlow:
  Fix Released
Status in ec2-api:
  Fix Released
Status in Evoque:
  In Progress
Status in gce-api:
  Fix Released
Status in Gnocchi:
  Fix Committed
Status in heat:
  Fix Released
Status in heat-cfntools:
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in KloudBuster:
  Fix Released
Status in kolla:
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  In Progress
Status in networking-arista:
  In Progress
Status in networking-calico:
  In Progress
Status in networking-cisco:
  In Progress
Status in networking-fujitsu:
  Fix Released
Status in networking-odl:
  In Progress
Status in networking-ofagent:
  In Progress
Status in networking-plumgrid:
  In Progress
Status in networking-powervm:
  Fix Released
Status in networking-vsphere:
  Fix Released
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  In Progress
Status in nova-powervm:
  Fix Released
Status in nova-solver-scheduler:
  In Progress
Status in octavia:
  Fix Released
Status in openstack-ansible:
  In Progress
Status in oslo.cache:
  Fix Released
Status in Packstack:
  Fix Released
Status in python-dracclient:
  Fix Released
Status in python-magnumclient:
  Fix Released
Status in RACK:
  In Progress
Status in python-watcherclient:
  In Progress
Status in shaker:
  In Progress
Status in Solum:
  Fix Released
Status in tempest:
  In Progress
Status in tripleo:
  In Progress
Status in trove-dashboard:
  Fix Released
Status in watcher:
  Fix Released
Status in zaqar:
  In Progress

Bug description:
  LOG.warn is deprecated in Python 3 [1] . But it still used in a few
  places, non-deprecated LOG.warning should be used instead.

  Note: If we are using logger from oslo.log, warn is still valid [2],
  but I agree we can switch to LOG.warning.

  [1]https://docs.python.org/3/library/logging.html#logging.warning
  [2]https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L85

To manage notifications about this bug go to:
https://bugs.launchpad.net/anvil/+bug/1508442/+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 1551907] Re: Add API extension for reporting IP availability usage statistics

2016-03-20 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/278779
Committed: 
https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=daa62d3fff7dc188e07d34af47d6c4fc5e96367c
Submitter: Jenkins
Branch:master

commit daa62d3fff7dc188e07d34af47d6c4fc5e96367c
Author: Manjeet Singh Bhatia 
Date:   Wed Feb 10 22:31:54 2016 +

Add Network IP Availability API Extention

There was api merged for Network IP Availaibility [1]. This change
basically implements new extension that can be used to check network
usage stats of all the networks or specific network created by neutron.
There is also patch [2] upstream and close to merge for client commands

This patch will add how to configure it and commands used to get that
information.

[1]. https://review.openstack.org/#/c/212955/
[2]. https://review.openstack.org/#/c/269926/

Closes-Bug: #1551907
Change-Id: I5a6df488147240c11a4bad7f03320469bc8a3be6


** Changed in: openstack-manuals
   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/1551907

Title:
  Add API extension for reporting IP availability usage statistics

Status in OpenStack Dashboard (Horizon):
  New
Status in neutron:
  Fix Released
Status in openstack-api-site:
  In Progress
Status in openstack-manuals:
  Fix Released

Bug description:
  https://review.openstack.org/212955
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 2f741ca5f9545c388270ddab774e9e030b006d8a
  Author: Mike Dorman 
  Date:   Thu Aug 13 21:24:58 2015 -0600

  Add API extension for reporting IP availability usage statistics
  
  Implements an API extension for reporting availibility of IP
  addresses on Neutron networks/subnets based on the blueprint
  proposed at https://review.openstack.org/#/c/180803/
  
  This provides an easy way for operators to count the number of
  used and total IP addresses on any or all networks and/or
  subnets.
  
  Co-Authored-By: David Bingham 
  Co-Authored-By: Craig Jellick 
  
  APIImpact
  DocImpact: As a new API, will need all new docs. See devref for details.
  
  Implements: blueprint network-ip-usage-api
  Closes-Bug: 1457986
  Change-Id: I81406054d46b2c0e0ffcd56e898e329f943ba46f

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1551907/+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 1558205] [NEW] neutron-lbaas plugin installation breaks on gates

2016-03-20 Thread Darek Smigiel

Public bug reported:

Because of latest changes for neutron-lbaas devstack configuration, all
gates are broken.

VM with devstack doesn't have `add-apt-repository` command. added in
this commit https://github.com/openstack/neutron-
lbaas/commit/eb2a61b4e9082f97d3bc5c8ec9d02d29914e68a7


2016-03-16 17:40:42.787 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L10:
   [[ False == False ]]
2016-03-16 17:40:42.787 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L11:
   BACKPORT='deb http://archive.ubuntu.com/ubuntu trusty-backports main 
restricted universe multiverse'
2016-03-16 17:40:42.787 | +++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   grep '^' /etc/apt/sources.list '/etc/apt/sources.list.d/*'
2016-03-16 17:40:42.787 | +++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   grep 'deb http://archive.ubuntu.com/ubuntu trusty-backports main restricted 
universe multiverse'
2016-03-16 17:40:42.788 | grep: /etc/apt/sources.list.d/*: No such file or 
directory
2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   BACKPORT_EXISTS=
2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   true
2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L13:
   [[ -z '' ]]
2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L14:
   sudo add-apt-repository 'deb http://archive.ubuntu.com/ubuntu 
trusty-backports main restricted universe multiverse' -y
2016-03-16 17:40:42.792 | sudo: add-apt-repository: command not found
2016-03-16 17:40:42.793 | + 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L1:
   exit_trap
2016-03-16 17:40:42.793 | + ./stack.sh:exit_trap:L474:   local r=1

** Affects: neutron
 Importance: Critical
 Assignee: Brandon Logan (brandon-logan)
 Status: New


** Tags: lbaas

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

Title:
  neutron-lbaas plugin installation breaks on gates

Status in neutron:
  New

Bug description:
  Because of latest changes for neutron-lbaas devstack configuration,
  all gates are broken.

  VM with devstack doesn't have `add-apt-repository` command. added in
  this commit https://github.com/openstack/neutron-
  lbaas/commit/eb2a61b4e9082f97d3bc5c8ec9d02d29914e68a7

  
  2016-03-16 17:40:42.787 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L10:
   [[ False == False ]]
  2016-03-16 17:40:42.787 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L11:
   BACKPORT='deb http://archive.ubuntu.com/ubuntu trusty-backports main 
restricted universe multiverse'
  2016-03-16 17:40:42.787 | +++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   grep '^' /etc/apt/sources.list '/etc/apt/sources.list.d/*'
  2016-03-16 17:40:42.787 | +++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   grep 'deb http://archive.ubuntu.com/ubuntu trusty-backports main restricted 
universe multiverse'
  2016-03-16 17:40:42.788 | grep: /etc/apt/sources.list.d/*: No such file or 
directory
  2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   BACKPORT_EXISTS=
  2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   true
  2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L13:
   [[ -z '' ]]
  2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L14:
   sudo add-apt-repository 'deb http://archive.ubuntu.com/ubuntu 
trusty-backports main restricted universe multiverse' -y
  2016-03-16 17:40:42.792 | sudo: add-apt-repository: command not found
  2016-03-16 17:40:42.793 | + 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L1:
   exit_trap
  2016-03-16 17:40:42.793 | + ./stack.sh:exit_trap:L474:   local r=1

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

[Yahoo-eng-team] [Bug 1558392] [NEW] List command in Neutron throws list index out of range error, when there are no entries for a object

2016-03-20 Thread Preethi Dsilva

Public bug reported:

On removing the last entry of a object say network or floatingip ,if neutron 
list command is issued it throws "list index out of range" error 
stack@hlm:~$ neutron net-list
-
id  namesubnets
-
206d8033-a577-488f-b6bc-5558e37e0e54n1  
ac5353b7-edb5-4138-9be4-b84bc22b9718 1.1.1.0/24
-
stack@hlm:~$ neutron net-delete n1
Deleted network: n1
stack@hlm:~$ neutron net-list
list index out of range
stack@hlm:~$
stack@hlm:~$ neutron floatingip-list
list index out of range
stack@hlm:~$

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: liberty-backport-potential

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

Title:
  List command in Neutron throws list index out of range error,when
  there are no entries for a object

Status in neutron:
  New

Bug description:
  On removing the last entry of a object say network or floatingip ,if neutron 
list command is issued it throws "list index out of range" error 
  stack@hlm:~$ neutron net-list
  
-
  idnamesubnets
  
-
  206d8033-a577-488f-b6bc-5558e37e0e54  n1  
ac5353b7-edb5-4138-9be4-b84bc22b9718 1.1.1.0/24
  
-
  stack@hlm:~$ neutron net-delete n1
  Deleted network: n1
  stack@hlm:~$ neutron net-list
  list index out of range
  stack@hlm:~$
  stack@hlm:~$ neutron floatingip-list
  list index out of range
  stack@hlm:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1558392/+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 1558397] [NEW] functional job fails due to missing netcat

2016-03-20 Thread Armando Migliaccio

Public bug reported:

A good build:

http://logs.openstack.org/39/293239/3/check/gate-neutron-dsvm-
functional/f1284e9/logs/dpkg-l.txt.gz

A bad build:

http://logs.openstack.org/87/293587/1/check/gate-neutron-dsvm-
functional/53d6bee/logs/dpkg-l.txt.gz

** Affects: devstack
 Importance: Undecided
 Assignee: Armando Migliaccio (armando-migliaccio)
 Status: In Progress

** Affects: neutron
 Importance: Undecided
 Status: Invalid

** Also affects: devstack
   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/1558397

Title:
  functional job fails due to missing netcat

Status in devstack:
  In Progress
Status in neutron:
  Invalid

Bug description:
  A good build:

  http://logs.openstack.org/39/293239/3/check/gate-neutron-dsvm-
  functional/f1284e9/logs/dpkg-l.txt.gz

  A bad build:

  http://logs.openstack.org/87/293587/1/check/gate-neutron-dsvm-
  functional/53d6bee/logs/dpkg-l.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1558397/+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 1554195] Re: Nova (juno) ignores logging_*_format_string in syslog output

2016-03-20 Thread Markus Zoeller (markus_z)

@George Shuklin:
The Juno release has its EOL in December 2015 [1]. This means the
upstream development doesn't provide any fixes for that anymore.

References:
[1] http://releases.openstack.org/

** Changed in: nova
   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/1554195

Title:
  Nova (juno) ignores logging_*_format_string in syslog output

Status in OpenStack Compute (nova):
  Invalid
Status in nova package in Ubuntu:
  Confirmed

Bug description:
  Nova in juno ignores following settings in configuration file ([DEFAULT] 
section):
  logging_context_format_string
  logging_default_format_string
  logging_debug_format_suffix
  logging_exception_prefix

  when sending logs via syslog. Log entries on stderr / in log files are
  fine (use logging_*_format).

  Steps to reproduce:

  1. set up custom logging stings and enable syslog:

  [DEFAULT]
  logging_default_format_string=MYSTYLE-DEFAULT-%(message)s
  logging_context_format_string=MYSTYLE-CONTEXT-%(message)s
  use_syslog=true

  2. restart nova and perform some actions

  3. Check the syslog content

  Expected behaviour: MYSTYLE- prefix in all messages.
  Actual behaviour: no changes in log message styles.

  This bug is specific to Juno version of nova.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1554195/+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 1521815] Re: DVR functional tests failing intermittently

[Yahoo-eng-team] [Bug 1533984] Re: Unexpected API Error, Unable to launch instance

[Yahoo-eng-team] [Bug 1536470] Re: Fixing test cases

[Yahoo-eng-team] [Bug 1558807] Re: Volume attached at different path than reported by nova/cinder when using config drive

[Yahoo-eng-team] [Bug 1538620] Re: Attach with host and instance_uuid not backwards compatible

[Yahoo-eng-team] [Bug 1557255] Re: keystone crashes after installing networking-odl in Liberty

[Yahoo-eng-team] [Bug 1558690] Re: project set works for invalid properties

[Yahoo-eng-team] [Bug 1558343] Re: configdrive is lost after resize.(libvirt driver)

[Yahoo-eng-team] [Bug 1559026] [NEW] nova-novncproxy doesn't start when 'record' is specified

[Yahoo-eng-team] [Bug 1508442] Re: LOG.warn is deprecated

[Yahoo-eng-team] [Bug 1551907] Re: Add API extension for reporting IP availability usage statistics

[Yahoo-eng-team] [Bug 1558205] [NEW] neutron-lbaas plugin installation breaks on gates

[Yahoo-eng-team] [Bug 1558392] [NEW] List command in Neutron throws list index out of range error, when there are no entries for a object

[Yahoo-eng-team] [Bug 1558397] [NEW] functional job fails due to missing netcat

[Yahoo-eng-team] [Bug 1554195] Re: Nova (juno) ignores logging_*_format_string in syslog output

15 matches

Site Navigation

Mail list logo

Footer information