date:20160202

[Yahoo-eng-team] [Bug 1540208] Re: CSRF mechanism is not safe.

2016-02-02 Thread Matthias Runge

My feedback from Django project is, it's not exploitable. If this is an
issue, it's a Django one, not specific to Horizon.

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

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

Title:
  CSRF mechanism is not safe.

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in OpenStack Security Advisory:
  Incomplete

Bug description:
  I'm using burp suite to check secure of horizon 8.0.0.0. CSRF
  mechanism   is not safe.

  I saw : csrftoken equals with csrfmidlewaretoken ==> the reques is
  valid.

  Example: Do update network's name.

  The first request: 
   - I got csrftoken and csrfmidlewaretoken: PvVPmsOEqepSWnWgJa1GKYtBxcSXMTu1
  -  network's name :  attt_net_test_129

  then I change  csrftoken and csrfmidlewaretoken to "1" ,  network 's
  name value to "attt_net_test_121"

  Final, do send request ==> Network is updated succesfuly. (attach
  file)

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1540208/+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 1540794] [NEW] deprecate signing config options

2016-02-02 Thread Steve Martinelli

Public bug reported:

PKI tokens have been deprecated, so should all the signing related
config options:

https://github.com/openstack/keystone/blob/master/keystone/common/config.py#L347-L374

** Affects: keystone
 Importance: Undecided
 Status: New

** Changed in: keystone
Milestone: None => mitaka-3

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

Title:
  deprecate signing config options

Status in OpenStack Identity (keystone):
  New

Bug description:
  PKI tokens have been deprecated, so should all the signing related
  config options:

  
https://github.com/openstack/keystone/blob/master/keystone/common/config.py#L347-L374

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1540794/+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 1539505] Re: Font file not found

2016-02-02 Thread Renjie Sun

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

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

Title:
  Font file not found

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  [29/Jan/2016 09:57:30] "GET /i18n/js/horizon+openstack_dashboard/ HTTP/1.1" 
200 2372
  Not Found: 
/dashboard/static/horizon/lib/font-awesome/fonts/fontawesome-webfont.woff2
  [29/Jan/2016 09:57:30] "GET 
/dashboard/static/horizon/lib/font-awesome/fonts/fontawesome-webfont.woff2?v=4.3.0
 HTTP/1.1" 404 4718
  Not Found: 
/dashboard/static/horizon/lib/font-awesome/fonts/fontawesome-webfont.woff
  [29/Jan/2016 09:57:30] "GET 
/dashboard/static/horizon/lib/font-awesome/fonts/fontawesome-webfont.woff?v=4.3.0
 HTTP/1.1" 404 4715
  Not Found: 
/dashboard/static/horizon/lib/font-awesome/fonts/fontawesome-webfont.ttf
  [29/Jan/2016 09:57:30] "GET 
/dashboard/static/horizon/lib/font-awesome/fonts/fontawesome-webfont.ttf?v=4.3.0
 HTTP/1.1" 404 4712

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1539505/+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 1535231] Re: md-meta with case insensitive string has problem when creating

2016-02-02 Thread Kairat Kushaev

We can add some additional info about case-insensitivity to exception
message but that must be fixed in glance.

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

** No longer affects: python-glanceclient

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

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

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  md-meta with case insensitive string has problem when creating

Status in Glance:
  Confirmed

Bug description:
  [Summary]
  md-meta with case sensitive has problem when creating

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  can create case sensitive md-meta

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) there is a md-tag named "ab" for namespace "new-ns":
  stack@45-59:~/devstack$ glance md-tag-create --name ab new-ns
  ++--+
  | Property   | Value|
  ++--+
  | created_at | 2016-01-18T16:36:13Z |
  | name   | ab   |
  | updated_at | 2016-01-18T16:36:13Z |
  ++--+
  stack@45-59:~/devstack$ glance md-tag-list new-ns
  +--+
  | name |
  +--+
  | ab   |
  +--+

  
  2)if create a new md-tag named "AB", conflict occur:   >>>ISSUE
  stack@45-59:~/devstack$ glance md-tag-create --name AB new-ns
  409 Conflict: A metadata tag with name=AB already exists in namespace=new-ns.
  stack@45-59:~/devstack$ 

  3)but if there is no md-tag "ab", the md-tag "AB" can be created.
  stack@45-59:~/devstack$ glance md-tag-delete new-ns ab
  stack@45-59:~/devstack$ 
  stack@45-59:~/devstack$ glance md-tag-list new-ns
  +--+
  | name |
  +--+
  +--+
  stack@45-59:~/devstack$ glance md-tag-create --name AB new-ns
  ++--+
  | Property   | Value|
  ++--+
  | created_at | 2016-01-18T16:37:20Z |
  | name   | AB   |
  | updated_at | 2016-01-18T16:37:20Z |
  ++--+

  [Configration]
  reproduceable bug, no need

  [logs]
  reproduceable bug, no need

  [Root cause anlyze or debug inf]
  reproduceable bug

  [Attachment]
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1535231/+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 1540844] [NEW] ML2's assumptions about transactions should be explicit

2016-02-02 Thread Kevin Benton

Public bug reported:

The create/update/delete of the core resource in ML2 all assume that
they will not be called inside of a transaction because they notify
drivers with a postcommit call before returning. Calling ML2 with a
session already in a transaction leads to unexpected behavior (e.g. no
notifications to driver on a rollback) so we should enforce this
assumption in code.

** Affects: neutron
 Importance: Undecided
 Assignee: Kevin Benton (kevinbenton)
 Status: In Progress

** Changed in: neutron
 Assignee: (unassigned) => 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/1540844

Title:
  ML2's assumptions about transactions should be explicit

Status in neutron:
  In Progress

Bug description:
  The create/update/delete of the core resource in ML2 all assume that
  they will not be called inside of a transaction because they notify
  drivers with a postcommit call before returning. Calling ML2 with a
  session already in a transaction leads to unexpected behavior (e.g. no
  notifications to driver on a rollback) so we should enforce this
  assumption in code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1540844/+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 1393391] Re: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-update_fanout..

2016-02-02 Thread Louis Bouchard

** Also affects: neutron (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-
  update_fanout..

Status in neutron:
  Confirmed
Status in neutron package in Ubuntu:
  New
Status in neutron source package in Trusty:
  New

Bug description:
  Under an HA deployment, neutron-openvswitch-agent can get stuck
  when receiving a close command on a fanout queue the agent is not subscribed 
to.

  It stops responding to any other messages, so it stops effectively
  working at all.

  2014-11-11 10:27:33.092 3027 INFO neutron.common.config [-] Logging enabled!
  2014-11-11 10:27:34.285 3027 INFO neutron.openstack.common.rpc.common 
[req-66ba318b-0fcc-42c2-959e-9a5233c292ef None] Connected to AMQP server on 
vip-rabbitmq:5672
  2014-11-11 10:27:34.370 3027 INFO neutron.openstack.common.rpc.common 
[req-66ba318b-0fcc-42c2-959e-9a5233c292ef None] Connected to AMQP server on 
vip-rabbitmq:5672
  2014-11-11 10:27:35.348 3027 INFO 
neutron.plugins.openvswitch.agent.ovs_neutron_agent 
[req-66ba318b-0fcc-42c2-959e-9a5233c292ef None] Agent initialized successfully, 
now running...
  2014-11-11 10:27:35.351 3027 INFO 
neutron.plugins.openvswitch.agent.ovs_neutron_agent 
[req-66ba318b-0fcc-42c2-959e-9a5233c292ef None] Agent out of sync with plugin!
  2014-11-11 10:27:35.401 3027 INFO 
neutron.plugins.openvswitch.agent.ovs_neutron_agent 
[req-66ba318b-0fcc-42c2-959e-9a5233c292ef None] Agent tunnel out of sync with 
plugin!
  2014-11-11 10:27:35.414 3027 INFO neutron.openstack.common.rpc.common 
[req-66ba318b-0fcc-42c2-959e-9a5233c292ef None] Connected to AMQP server on 
vip-rabbitmq:5672
  2014-11-11 10:32:33.143 3027 INFO neutron.agent.securitygroups_rpc 
[req-22c7fa11-882d-4278-9f83-6dd56ab95ba4 None] Security group member updated 
[u'4c7b3ad2-4526-48a7-959e-a8b8e4da6413']
  2014-11-11 10:58:11.916 3027 INFO neutron.agent.securitygroups_rpc 
[req-484fd71f-8f61-496c-aa8a-2d3abf8de365 None] Security group member updated 
[u'4c7b3ad2-4526-48a7-959e-a8b8e4da6413']
  2014-11-11 10:59:43.954 3027 INFO neutron.agent.securitygroups_rpc 
[req-2c0bc777-04ed-470a-aec5-927a59100b89 None] Security group member updated 
[u'4c7b3ad2-4526-48a7-959e-a8b8e4da6413']
  2014-11-11 11:00:22.500 3027 INFO neutron.agent.securitygroups_rpc 
[req-df447d01-d132-40f2-8528-1c1c4d57c0f5 None] Security group member updated 
[u'4c7b3ad2-4526-48a7-959e-a8b8e4da6413']
  2014-11-12 01:27:35.662 3027 ERROR neutron.openstack.common.rpc.common [-] 
Failed to consume message from queue: Socket closed
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common 
Traceback (most recent call last):
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common   File 
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py", 
line 579, in ensure
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common 
return method(*args, **kwargs)
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common   File 
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py", 
line 659, in _consume
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common 
return self.connection.drain_events(timeout=timeout)
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common   File 
"/usr/lib/python2.7/site-packages/kombu/connection.py", line 281, in 
drain_events
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common 
return self.transport.drain_events(self.connection, **kwargs)
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common   File 
"/usr/lib/python2.7/site-packages/kombu/transport/pyamqp.py", line 94, in 
drain_events
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common 
return connection.drain_events(**kwargs)
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common   File 
"/usr/lib/python2.7/site-packages/amqp/connection.py", line 266, in drain_events
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common 
chanmap, None, timeout=timeout,
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common   File 
"/usr/lib/python2.7/site-packages/amqp/connection.py", line 328, in 
_wait_multiple
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common 
channel, method_sig, args, content = read_timeout(timeout)
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common   File 
"/usr/lib/python2.7/site-packages/amqp/connection.py", line 292, in read_timeout
  2014-11-12 01:27:35.662 3027 TRACE neutron.openstack.common.rpc.common 
return self.method_reader.read_method()
  2014-11-12 01:27:35.66

[Yahoo-eng-team] [Bug 1540873] [NEW] Error: Service n-xvnc is not running

2016-02-02 Thread Federico Ressi

Public bug reported:

When stacking I am getting below error many times since a pair of days:

2016-02-02 11:07:08,277 | + echo 'Error: Service n-xvnc is not running'
2016-02-02 11:07:08,278 | Error: Service n-xvnc is not running
2016-02-02 11:07:08,278 | + '[' -n /opt/stack/status/stack/n-xvnc.failure ']'
2016-02-02 11:07:08,278 | + die 1642 'More details about the above errors can 
be found with screen, with ./rejoin-stack.sh'
2016-02-02 11:07:08,278 | + local exitcode=0
2016-02-02 11:07:08,278 | [Call Trace]
2016-02-02 11:07:08,278 | ./stack.sh:1353:service_check
2016-02-02 11:07:08,279 | /opt/stack/devstack/functions-common:1642:die
2016-02-02 11:07:08,279 | [ERROR] /opt/stack/devstack/functions-common:1642 
More details about the above errors can be found with screen, with 
./rejoin-stack.sh
2016-02-02 11:07:08,279 | Error on exit

This is new. I am not sure witch repository between devstack, nova and
neutron introduced it.

** Affects: devstack
 Importance: Undecided
 Status: New

** Affects: neutron
 Importance: Undecided
 Status: New

** Affects: nova
 Importance: Undecided
 Status: New

** Affects: tempest
 Importance: Undecided
 Status: New

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

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

** Also affects: tempest
   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/1540873

Title:
  Error: Service n-xvnc is not running

Status in devstack:
  New
Status in neutron:
  New
Status in OpenStack Compute (nova):
  New
Status in tempest:
  New

Bug description:
  When stacking I am getting below error many times since a pair of
  days:

  2016-02-02 11:07:08,277 | + echo 'Error: Service n-xvnc is not running'
  2016-02-02 11:07:08,278 | Error: Service n-xvnc is not running
  2016-02-02 11:07:08,278 | + '[' -n /opt/stack/status/stack/n-xvnc.failure ']'
  2016-02-02 11:07:08,278 | + die 1642 'More details about the above errors can 
be found with screen, with ./rejoin-stack.sh'
  2016-02-02 11:07:08,278 | + local exitcode=0
  2016-02-02 11:07:08,278 | [Call Trace]
  2016-02-02 11:07:08,278 | ./stack.sh:1353:service_check
  2016-02-02 11:07:08,279 | /opt/stack/devstack/functions-common:1642:die
  2016-02-02 11:07:08,279 | [ERROR] /opt/stack/devstack/functions-common:1642 
More details about the above errors can be found with screen, with 
./rejoin-stack.sh
  2016-02-02 11:07:08,279 | Error on exit

  This is new. I am not sure witch repository between devstack, nova and
  neutron introduced it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1540873/+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 1540873] Re: Error: Service n-xvnc is not running

2016-02-02 Thread Federico Ressi

** No longer affects: tempest

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

Title:
  Error: Service n-xvnc is not running

Status in devstack:
  New
Status in neutron:
  New
Status in OpenStack Compute (nova):
  New

Bug description:
  When stacking I am getting below error many times since a pair of
  days:

  2016-02-02 11:07:08,277 | + echo 'Error: Service n-xvnc is not running'
  2016-02-02 11:07:08,278 | Error: Service n-xvnc is not running
  2016-02-02 11:07:08,278 | + '[' -n /opt/stack/status/stack/n-xvnc.failure ']'
  2016-02-02 11:07:08,278 | + die 1642 'More details about the above errors can 
be found with screen, with ./rejoin-stack.sh'
  2016-02-02 11:07:08,278 | + local exitcode=0
  2016-02-02 11:07:08,278 | [Call Trace]
  2016-02-02 11:07:08,278 | ./stack.sh:1353:service_check
  2016-02-02 11:07:08,279 | /opt/stack/devstack/functions-common:1642:die
  2016-02-02 11:07:08,279 | [ERROR] /opt/stack/devstack/functions-common:1642 
More details about the above errors can be found with screen, with 
./rejoin-stack.sh
  2016-02-02 11:07:08,279 | Error on exit

  This is new. I am not sure witch repository between devstack, nova and
  neutron introduced it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1540873/+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 1540873] Re: Error: Service n-xvnc is not running

2016-02-02 Thread Federico Ressi

I suspect the problem appeared when the change was merged:

https://review.openstack.org/#/c/235398/

This should fix it:

https://review.openstack.org/#/c/274889/


** No longer affects: neutron

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

Title:
  Error: Service n-xvnc is not running

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

Bug description:
  When stacking I am getting below error many times since a pair of
  days:

  2016-02-02 11:07:08,277 | + echo 'Error: Service n-xvnc is not running'
  2016-02-02 11:07:08,278 | Error: Service n-xvnc is not running
  2016-02-02 11:07:08,278 | + '[' -n /opt/stack/status/stack/n-xvnc.failure ']'
  2016-02-02 11:07:08,278 | + die 1642 'More details about the above errors can 
be found with screen, with ./rejoin-stack.sh'
  2016-02-02 11:07:08,278 | + local exitcode=0
  2016-02-02 11:07:08,278 | [Call Trace]
  2016-02-02 11:07:08,278 | ./stack.sh:1353:service_check
  2016-02-02 11:07:08,279 | /opt/stack/devstack/functions-common:1642:die
  2016-02-02 11:07:08,279 | [ERROR] /opt/stack/devstack/functions-common:1642 
More details about the above errors can be found with screen, with 
./rejoin-stack.sh
  2016-02-02 11:07:08,279 | Error on exit

  This is new. I am not sure witch repository between devstack, nova and
  neutron introduced it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1540873/+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 1540254] Re: "#flake8: noqa" is using incorrectly

2016-02-02 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/274637
Committed: 
https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=0105fd120659baf3445b994af29837755d155c73
Submitter: Jenkins
Branch:master

commit 0105fd120659baf3445b994af29837755d155c73
Author: Bo Wang 
Date:   Mon Feb 1 20:17:47 2016 +0800

Use # noqa to ignore one line but not whole file

"# flake8: noqa" option disables all checks for the whole file.
To disable one line we should use "# noqa".

Closes Bug: #1540254

Change-Id: I34c8a2218f974cd7e78c60e9c1fec26751c4e82d


** Changed in: python-novaclient
   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/1540254

Title:
  "#flake8: noqa" is using incorrectly

Status in OpenStack Dashboard (Horizon):
  In Progress
Status in python-heatclient:
  Fix Released
Status in python-novaclient:
  Fix Released

Bug description:
  "# flake8: noqa" option disables all checks for the whole file. To
  disable one line we should use "# noqa".

  Refer to: https://pypi.python.org/pypi/flake8
  
https://github.com/openstack/python-keystoneclient/commit/3b766c51438396a0ab0032de309c9d56e275e0cb

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1540254/+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 1372564] Re: Incorrect status change after image uploading in v2

2016-02-02 Thread OpenStack Infra

** Changed in: glance
   Status: Invalid => In Progress

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

Title:
  Incorrect status change after image uploading in v2

Status in Glance:
  In Progress
Status in Glance juno series:
  Fix Released
Status in Glance kilo series:
  Fix Released

Bug description:
  If the image is deleted (i.e. its status changed to 'deleted' in db) when 
it's uploading through image-upload command in v2, its status surprisingly 
switches from 'deleted' to 'active' without any exception.
  There is the code that should handle NotFound exception in that case
  https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py 
:77

  except exception.NotFound as e:
  msg = (_("Image %(id)s could not be found after upload."
  "The image may have been deleted during the upload: "
  "%(error)s Cleaning up the chunks uploaded") %
  {'id': image_id,
  'error': utils.exception_to_str(e)})

  but it never executes because the exception is not raised.
  In v1 this problem is solved with explicitly passing from_state argument, but 
in v2 it's not possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1372564/+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 1540873] Re: Error: Service n-xvnc is not running

2016-02-02 Thread Davanum Srinivas (DIMS)

https://review.openstack.org/#/c/274889/ was merged.

** Changed in: nova
   Status: New => 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/1540873

Title:
  Error: Service n-xvnc is not running

Status in devstack:
  New
Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  When stacking I am getting below error many times since a pair of
  days:

  2016-02-02 11:07:08,277 | + echo 'Error: Service n-xvnc is not running'
  2016-02-02 11:07:08,278 | Error: Service n-xvnc is not running
  2016-02-02 11:07:08,278 | + '[' -n /opt/stack/status/stack/n-xvnc.failure ']'
  2016-02-02 11:07:08,278 | + die 1642 'More details about the above errors can 
be found with screen, with ./rejoin-stack.sh'
  2016-02-02 11:07:08,278 | + local exitcode=0
  2016-02-02 11:07:08,278 | [Call Trace]
  2016-02-02 11:07:08,278 | ./stack.sh:1353:service_check
  2016-02-02 11:07:08,279 | /opt/stack/devstack/functions-common:1642:die
  2016-02-02 11:07:08,279 | [ERROR] /opt/stack/devstack/functions-common:1642 
More details about the above errors can be found with screen, with 
./rejoin-stack.sh
  2016-02-02 11:07:08,279 | Error on exit

  This is new. I am not sure witch repository between devstack, nova and
  neutron introduced it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1540873/+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 1540934] [NEW] glance-cache-prefetcher is broken

2016-02-02 Thread Niall Bunting

Public bug reported:

Glance prefetcher is still configured to use keystone v1. As it still
does not use the right uri or pass the values as json but rather uses
headers.

** Affects: glance
 Importance: Undecided
 Assignee: Niall Bunting (niall-bunting)
 Status: New

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

Title:
  glance-cache-prefetcher is broken

Status in Glance:
  New

Bug description:
  Glance prefetcher is still configured to use keystone v1. As it still
  does not use the right uri or pass the values as json but rather uses
  headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1540934/+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 1540873] Re: Error: Service n-xvnc is not running

2016-02-02 Thread Federico Ressi

I tested, it fixed it.

** No longer affects: devstack

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

Title:
  Error: Service n-xvnc is not running

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  When stacking I am getting below error many times since a pair of
  days:

  2016-02-02 11:07:08,277 | + echo 'Error: Service n-xvnc is not running'
  2016-02-02 11:07:08,278 | Error: Service n-xvnc is not running
  2016-02-02 11:07:08,278 | + '[' -n /opt/stack/status/stack/n-xvnc.failure ']'
  2016-02-02 11:07:08,278 | + die 1642 'More details about the above errors can 
be found with screen, with ./rejoin-stack.sh'
  2016-02-02 11:07:08,278 | + local exitcode=0
  2016-02-02 11:07:08,278 | [Call Trace]
  2016-02-02 11:07:08,278 | ./stack.sh:1353:service_check
  2016-02-02 11:07:08,279 | /opt/stack/devstack/functions-common:1642:die
  2016-02-02 11:07:08,279 | [ERROR] /opt/stack/devstack/functions-common:1642 
More details about the above errors can be found with screen, with 
./rejoin-stack.sh
  2016-02-02 11:07:08,279 | Error on exit

  This is new. I am not sure witch repository between devstack, nova and
  neutron introduced it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1540873/+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 1540939] [NEW] Instance delete causing port leak

2016-02-02 Thread Chuck Carmack

Public bug reported:

Nova can cause a neutron port leak after deleting an instance.

If neutron has the port binding extension installed, then nova uses admin 
credentials to create the port during instance create:
https://github.com/openstack/nova/blob/master/nova/network/neutronv2/api.py#L537

However, during instance delete, nova always uses the user creds:
https://github.com/openstack/nova/blob/master/nova/network/neutronv2/api.py#L739

Depending on the neutron policy settings, this can leak ports in
neutron.

Can someone explain this behavior?

We are running on nova kilo.

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

Title:
  Instance delete causing port leak

Status in OpenStack Compute (nova):
  New

Bug description:
  Nova can cause a neutron port leak after deleting an instance.

  If neutron has the port binding extension installed, then nova uses admin 
credentials to create the port during instance create:
  
https://github.com/openstack/nova/blob/master/nova/network/neutronv2/api.py#L537

  However, during instance delete, nova always uses the user creds:
  
https://github.com/openstack/nova/blob/master/nova/network/neutronv2/api.py#L739

  Depending on the neutron policy settings, this can leak ports in
  neutron.

  Can someone explain this behavior?

  We are running on nova kilo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1540939/+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 1540960] [NEW] DHCP: when upgrading from icehouse DHCP breaks

2016-02-02 Thread Gary Kotton

Public bug reported:

When upgrading the J, K or any other version the DNS support break. 
That is, the DHCP agent has the option for setting DNS servers, this is via the 
the options dnsmasq_config_file=/etc/neutron/myconfig.ini
Where myconfig will have support for the following:
dhcp-option=5,2.4.5.6,2.4.5.7
dhcp-option=6,2.4.5.7,2.4.5.6

In the guest /etc/resolve.conf we see the DHCP address and not the
configured IP's

The reason for this is
https://github.com/openstack/neutron/commit/3686d035ded94eadab6a3268e4b0f0cca11a22f8

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

Title:
  DHCP: when upgrading from icehouse DHCP breaks

Status in neutron:
  New

Bug description:
  When upgrading the J, K or any other version the DNS support break. 
  That is, the DHCP agent has the option for setting DNS servers, this is via 
the the options dnsmasq_config_file=/etc/neutron/myconfig.ini
  Where myconfig will have support for the following:
  dhcp-option=5,2.4.5.6,2.4.5.7
  dhcp-option=6,2.4.5.7,2.4.5.6

  In the guest /etc/resolve.conf we see the DHCP address and not the
  configured IP's

  The reason for this is
  
https://github.com/openstack/neutron/commit/3686d035ded94eadab6a3268e4b0f0cca11a22f8

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1540960/+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 1540748] Re: ml2: port_update and port_delete should not use faout notify

2016-02-02 Thread Nate Johnston

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

Title:
  ml2: port_update and port_delete should not use faout notify

Status in neutron:
  Invalid

Bug description:
  Now for ml2 plugin,  neutron-server use faout RPC  message for port_update 
and port_delete, the codes as below:
  def port_update(self, context, port, network_type, segmentation_id,   
   physical_network):
  cctxt = self.client.prepare(topic=self.topic_port_update,fanout=True)
  cctxt.cast(context, 'port_update', port=port,
     network_type=network_type,
     segmentation_id=segmentation_id,
     physical_network=physical_network)

  def port_delete(self, context, port_id):
  cctxt = self.client.prepare(topic=self.topic_port_delete, fanout=True)
  cctxt.cast(context, 'port_delete', port_id=port_id)

  I think neutron-server should directly sends the RPC message to port's
  binding_host, this can offload work for AMQP

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1540748/+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 1387055] Re: glanceclient/shell.py:592: raise exc.CommandError("Invalid OpenStack Identity credentials.")

2016-02-02 Thread Kairat Kushaev

Closing due to inactivity. Latest devstack has been installed
successfully.

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

** Changed in: python-glanceclient
   Status: New => Won't Fix

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

Title:
  glanceclient/shell.py:592:raise exc.CommandError("Invalid
  OpenStack Identity credentials.")

Status in devstack:
  New
Status in Glance:
  Won't Fix
Status in python-glanceclient:
  Won't Fix

Bug description:
  When using DevStack to install OpenStack, I got the following error:

  2014-10-29 15:06:45.890 | ++ glance --os-auth-token 
12a7b1359dc044ff9e9e1c81a2390152 --os-image-url http://192.168.56.101:9292 
image-create --name cirros-0.3.1-x86_64-uec-kernel --is-public True 
--container-format aki --disk-format aki
  2014-10-29 15:06:45.915 | ++ read data
  2014-10-29 15:06:50.456 | Invalid OpenStack Identity credentials.
  2014-10-29 15:06:50.584 | + KERNEL_ID=
  2014-10-29 15:06:50.640 | + '[' -n 
/home/xtrutri/Work/devstack/files/images/cirros-0.3.1-x86_64-uec/cirros-0.3.1-x86_64-initrd
 ']'
  2014-10-29 15:06:50.657 | ++ glance --os-auth-token 
12a7b1359dc044ff9e9e1c81a2390152 --os-image-url http://192.168.56.101:9292 
image-create --name cirros-0.3.1-x86_64-uec-ramdisk --is-public True 
--container-format ari --disk-format ari
  2014-10-29 15:06:50.681 | ++ grep ' id '
  2014-10-29 15:06:50.690 | ++ get_field 2
  2014-10-29 15:06:50.699 | ++ read data
  2014-10-29 15:06:55.658 | Invalid OpenStack Identity credentials.
  2014-10-29 15:06:55.733 | + RAMDISK_ID=
  2014-10-29 15:06:55.783 | + glance --os-auth-token 
12a7b1359dc044ff9e9e1c81a2390152 --os-image-url http://192.168.56.101:9292 
image-create --name cirros-0.3.1-x86_64-uec --is-public True --container-format 
ami --disk-format ami
  2014-10-29 15:07:00.966 | Invalid OpenStack Identity credentials.
  xtrutri@ubuntu:~/Work/devstack$ 2014-10-29 15:07:01.061 | + exit_trap


  DevStack version: at commit 8cedabcea8bb446f1c29aab42fbcbf5a87218f7f (Sat May 
10 12:24:16 2014 +)
  KeyStone version: 2014.2.rc1-106-gf45b3e5
  GlanceClient version: 0.14.1-11-gcfe0623
  Glance version: 2014.2.rc1-91-gded0852

  
  Here is the traceback:

  2014-10-29 15:06:57.263 16394 DEBUG glance.api.middleware.version_negotiation 
[-] Using url versioning process_request 
/opt/stack_stable_juno/glance/glance/api/middleware/version_negotiation.py:57
  2014-10-29 15:06:57.265 16394 DEBUG glance.api.middleware.version_negotiation 
[-] Matched version: v1 process_request 
/opt/stack_stable_juno/glance/glance/api/middleware/version_negotiation.py:69
  2014-10-29 15:06:57.266 16394 DEBUG glance.api.middleware.version_negotiation 
[-] new path /v1/images process_request 
/opt/stack_stable_juno/glance/glance/api/middleware/version_negotiation.py:70
  2014-10-29 15:06:57.267 16394 DEBUG keystoneclient.session [-] REQ: curl -i 
-X GET http://127.0.0.1:35357/ -H "Accept: application/json" -H "User-Agent: 
python-keystoneclient" _http_log_request 
/opt/stack_stable_juno/python-keystoneclient/keystoneclient/session.py:162
  2014-10-29 15:06:57.270 16394 WARNING keystonemiddleware.auth_token [-] 
Retrying on HTTP connection exception: Unable to establish connection to 
http://127.0.0.1:35357/
  2014-10-29 15:06:57.772 16394 DEBUG keystoneclient.session [-] REQ: curl -i 
-X GET http://127.0.0.1:35357/ -H "Accept: application/json" -H "User-Agent: 
python-keystoneclient" _http_log_request 
/opt/stack_stable_juno/python-keystoneclient/keystoneclient/session.py:162
  2014-10-29 15:06:57.775 16394 WARNING keystonemiddleware.auth_token [-] 
Retrying on HTTP connection exception: Unable to establish connection to 
http://127.0.0.1:35357/
  2014-10-29 15:06:58.777 16394 DEBUG keystoneclient.session [-] REQ: curl -i 
-X GET http://127.0.0.1:35357/ -H "Accept: application/json" -H "User-Agent: 
python-keystoneclient" _http_log_request 
/opt/stack_stable_juno/python-keystoneclient/keystoneclient/session.py:162
  2014-10-29 15:06:58.782 16394 WARNING keystonemiddleware.auth_token [-] 
Retrying on HTTP connection exception: Unable to establish connection to 
http://127.0.0.1:35357/
  2014-10-29 15:07:00.793 16394 DEBUG keystoneclient.session [-] REQ: curl -i 
-X GET http://127.0.0.1:35357/ -H "Accept: application/json" -H "User-Agent: 
python-keystoneclient" _http_log_request 
/opt/stack_stable_juno/python-keystoneclient/keystoneclient/session.py:162
  2014-10-29 15:07:00.803 16394 ERROR keystonemiddleware.auth_token [-] HTTP 
connection exception: Unable to establish connection to http://127.0.0.1:35357/
  2014-10-29 15:07:00.807 16394 WARNING keystonemiddleware.auth_token [-] 
Authorization failed for token

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1387055/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.laun

[Yahoo-eng-team] [Bug 1540983] [NEW] Gate failures for neutron in test_dualnet_multi_prefix_slaac

2016-02-02 Thread Davanum Srinivas (DIMS)

Public bug reported:

24 hits in 7 days for logstash query : message:"in
test_dualnet_multi_prefix_slaac" AND voting:1

2016-02-02 14:35:49.054 | Captured traceback:
2016-02-02 14:35:49.054 | ~~~
2016-02-02 14:35:49.054 | Traceback (most recent call last):
2016-02-02 14:35:49.054 |   File "tempest/test.py", line 113, in wrapper
2016-02-02 14:35:49.055 | return f(self, *func_args, **func_kwargs)
2016-02-02 14:35:49.055 |   File "tempest/scenario/test_network_v6.py", 
line 246, in test_dualnet_multi_prefix_slaac
2016-02-02 14:35:49.055 | dualnet=True)
2016-02-02 14:35:49.055 |   File "tempest/scenario/test_network_v6.py", 
line 155, in _prepare_and_test
2016-02-02 14:35:49.055 | sshv4_1, ips_from_api_1, sid1 = 
self.prepare_server(networks=net_list)
2016-02-02 14:35:49.055 |   File "tempest/scenario/test_network_v6.py", 
line 128, in prepare_server
2016-02-02 14:35:49.055 | username=username)
2016-02-02 14:35:49.056 |   File "tempest/scenario/manager.py", line 390, 
in get_remote_client
2016-02-02 14:35:49.056 | linux_client.validate_authentication()
2016-02-02 14:35:49.056 |   File 
"tempest/common/utils/linux/remote_client.py", line 63, in 
validate_authentication
2016-02-02 14:35:49.056 | self.ssh_client.test_connection_auth()
2016-02-02 14:35:49.056 |   File 
"/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py",
 line 172, in test_connection_auth
2016-02-02 14:35:49.056 | connection = self._get_ssh_connection()
2016-02-02 14:35:49.056 |   File 
"/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py",
 line 87, in _get_ssh_connection
2016-02-02 14:35:49.057 | password=self.password)
2016-02-02 14:35:49.057 | tempest_lib.exceptions.SSHTimeout: Connection to 
the 172.24.5.141 via SSH timed out.
2016-02-02 14:35:49.057 | User: cirros, Password: None

** Affects: neutron
 Importance: Undecided
 Status: New

** Affects: openstack-gate
 Importance: Undecided
 Status: New

** Also 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/1540983

Title:
  Gate failures for neutron in test_dualnet_multi_prefix_slaac

Status in neutron:
  New
Status in OpenStack-Gate:
  New

Bug description:
  24 hits in 7 days for logstash query : message:"in
  test_dualnet_multi_prefix_slaac" AND voting:1

  2016-02-02 14:35:49.054 | Captured traceback:
  2016-02-02 14:35:49.054 | ~~~
  2016-02-02 14:35:49.054 | Traceback (most recent call last):
  2016-02-02 14:35:49.054 |   File "tempest/test.py", line 113, in wrapper
  2016-02-02 14:35:49.055 | return f(self, *func_args, **func_kwargs)
  2016-02-02 14:35:49.055 |   File "tempest/scenario/test_network_v6.py", 
line 246, in test_dualnet_multi_prefix_slaac
  2016-02-02 14:35:49.055 | dualnet=True)
  2016-02-02 14:35:49.055 |   File "tempest/scenario/test_network_v6.py", 
line 155, in _prepare_and_test
  2016-02-02 14:35:49.055 | sshv4_1, ips_from_api_1, sid1 = 
self.prepare_server(networks=net_list)
  2016-02-02 14:35:49.055 |   File "tempest/scenario/test_network_v6.py", 
line 128, in prepare_server
  2016-02-02 14:35:49.055 | username=username)
  2016-02-02 14:35:49.056 |   File "tempest/scenario/manager.py", line 390, 
in get_remote_client
  2016-02-02 14:35:49.056 | linux_client.validate_authentication()
  2016-02-02 14:35:49.056 |   File 
"tempest/common/utils/linux/remote_client.py", line 63, in 
validate_authentication
  2016-02-02 14:35:49.056 | self.ssh_client.test_connection_auth()
  2016-02-02 14:35:49.056 |   File 
"/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py",
 line 172, in test_connection_auth
  2016-02-02 14:35:49.056 | connection = self._get_ssh_connection()
  2016-02-02 14:35:49.056 |   File 
"/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py",
 line 87, in _get_ssh_connection
  2016-02-02 14:35:49.057 | password=self.password)
  2016-02-02 14:35:49.057 | tempest_lib.exceptions.SSHTimeout: Connection 
to the 172.24.5.141 via SSH timed out.
  2016-02-02 14:35:49.057 | User: cirros, Password: None

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1540983/+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 1517839] Re: Make CONF.set_override with parameter enforce_type=True by default

2016-02-02 Thread David TARDIVEL

** Changed in: watcher
   Status: New => 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/1517839

Title:
  Make CONF.set_override with parameter enforce_type=True by default

Status in Ceilometer:
  New
Status in cloudkitty:
  New
Status in Designate:
  Confirmed
Status in Gnocchi:
  In Progress
Status in heat:
  New
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  New
Status in Murano:
  In Progress
Status in neutron:
  In Progress
Status in oslo.config:
  New
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Released
Status in watcher:
  Fix Released

Bug description:
  1. Problems :
 oslo_config provides method CONF.set_override[1] , developers usually use 
it to change config option's value in tests. That's convenient .
 By default  parameter enforce_type=False,  it doesn't check any type or 
value of override. If set enforce_type=True , will check parameter
 override's type and value.  In production code(running time code),  
oslo_config  always checks  config option's value.
 In short, we test and run code in different ways. so there's  gap:  config 
option with wrong type or invalid value can pass tests when
 parameter enforce_type = False in consuming projects.  that means some 
invalid or wrong tests are in our code base.
 There is nova POC result when I enable "enforce_type=true" [2],  and I 
must fix them in [3]

 [1] 
https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173
 [2] 
http://logs.openstack.org/16/242416/1/check/gate-nova-python27/97b5eff/testr_results.html.gz
 [3]  https://review.openstack.org/#/c/242416/  
https://review.openstack.org/#/c/242717/  
https://review.openstack.org/#/c/243061/

  2. Proposal 
 1) Make  method CONF.set_override with  enforce_type=True  in consuming 
projects. and  fix violations when  enforce_type=True in each project.

2) Make  method CONF.set_override with  enforce_type=True by default
  in oslo_config

 Hope some one from consuming projects can help make
  enforce_type=True in consuming projects and fix violations,

 You can find more details and comments  in
  https://etherpad.openstack.org/p/enforce_type_true_by_default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1517839/+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 1538197] Re: booting from volume throws http 500 if volume size is not specified

2016-02-02 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/272732
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=5cad74c27befb8f1bd584753de21d8ca60eaf901
Submitter: Jenkins
Branch:master

commit 5cad74c27befb8f1bd584753de21d8ca60eaf901
Author: Balazs Gibizer 
Date:   Tue Jan 26 21:48:11 2016 +0100

Return HTTP 400 if volume size is not defined

Nova API properly checks that in case of booting from a image to
volume bdm the client shall specify the size of the created volume.
However the API does not handle the exception properly and returns
HTTP 500. This patch handles the InvalidBDM exception and returns
HTTP 400.

Change-Id: I80d0aa64885f25081dad91b1f45da5b318d8ae25
Closes-bug: #1538197


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

Title:
  booting from volume throws http 500 if volume size is not specified

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  If a instance is booted from volume with an image to volume bdm where
  the volume size is not specified nova throws http 500 instead of http
  400.

  Visible on master (b558d616c3b123dbe2a0914162b45765192f3a12) with
  devstack.

  To reproduce:

  $ nova image-list
  
+--+-+++
  | ID   | Name| 
Status | Server |
  
+--+-+++
  | a7e6b974-0b5a-4d60-8d68-d4745aae9bb3 | cirros-0.3.4-x86_64-uec | 
ACTIVE ||
  | 10672d57-30b3-4c41-9f5b-f42c030970fa | cirros-0.3.4-x86_64-uec-kernel  | 
ACTIVE ||
  | 70790401-6760-48d5-9bf4-175d18cfc9d6 | cirros-0.3.4-x86_64-uec-ramdisk | 
ACTIVE ||
  
+--+-+++

  $ nova boot --flavor 42 --block-device 
source=image,id=a7e6b974-0b5a-4d60-8d68-d4745aae9bb3,dest=volume,shutdown=preserve,bootindex=0
 --poll vm1
  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-996d695a-3f36-48ee-b91f-567c3ab2f1ce)

  
  There is a stack trace in the nova-api log:
  2016-01-20 18:51:58.400 ERROR nova.api.openstack.extensions 
[req-996d695a-3f36-48ee-b91f-567c3ab2f1ce admin admin] Unexpected exception in 
API method
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions Traceback (most 
recent call last):
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/extensions.py", line 478, in wrapped
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions return 
f(*args, **kwargs)
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/validation/__init__.py", line 73, in wrapper
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions return 
func(*args, **kwargs)
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/validation/__init__.py", line 73, in wrapper
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions return 
func(*args, **kwargs)
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/compute/servers.py", line 604, in create
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions 
**create_kwargs)
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/hooks.py", line 149, in inner
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions rv = f(*args, 
**kwargs)
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/compute/api.py", line 1504, in create
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions 
check_server_group_quota=check_server_group_quota)
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/compute/api.py", line 1127, in _create_instance
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions 
instance_group, check_server_group_quota)
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/compute/api.py", line 976, in _provision_instances
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions 
quotas.rollback()
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/compute/a

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

2016-02-02 Thread Steve Martinelli

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

Title:
  LOG.warn is deprecated

Status in anvil:
  In Progress
Status in Aodh:
  In Progress
Status in Astara:
  Fix Released
Status in Barbican:
  In Progress
Status in bilean:
  In Progress
Status in Blazar:
  In Progress
Status in Ceilometer:
  Fix Released
Status in cloud-init:
  In Progress
Status in cloudkitty:
  Fix Released
Status in congress:
  In Progress
Status in Designate:
  Fix Released
Status in django-openstack-auth:
  Fix Released
Status in django-openstack-auth-kerberos:
  New
Status in DragonFlow:
  Fix Released
Status in ec2-api:
  In Progress
Status in Evoque:
  In Progress
Status in gce-api:
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in Gnocchi:
  In Progress
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:
  In Progress
Status in networking-odl:
  In Progress
Status in networking-ofagent:
  In Progress
Status in networking-plumgrid:
  In Progress
Status in networking-powervm:
  In Progress
Status in networking-vsphere:
  In Progress
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:
  In Progress
Status in openstack-ansible:
  In Progress
Status in oslo.cache:
  Fix Released
Status in oslo.privsep:
  In Progress
Status in Packstack:
  Fix Released
Status in python-dracclient:
  In Progress
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:
  In Progress
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 1534625] Re: [Pluggable IPAM] Ipam driver is not called on update subnet if allocation pools are blank

2016-02-02 Thread John Belamaric

** Also affects: networking-infoblox
Importance: Undecided
Status: New

** Changed in: networking-infoblox
Importance: Undecided => Medium

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

Title:
[Pluggable IPAM] Ipam driver is not called on update subnet if
allocation pools are blank

Status in networking-infoblox:
New
Status in neutron:
In Progress

Bug description:
Currently ipam driver is called on subnet_update only if allocation_pools set
in subnet dict. See [1].
This happens because original design expectation is that the only information
ipam driver
has to update is allocation pools.
For reference ipam driver that is absolutely correct.

But 3rd party ipam vendors might want to utilize this call to keep track of
other fields updates in subnet.
So my suggestion here is to call update_subnet in ipam_driver on each subnet
update
and let ipam driver decide if it has to do some processing or not.

In Infoblox we need it to keep track of dns_nameservers on subnet_update.
Currently we can obtain this dns_nameservers info on subnet update only if
allocation_pools present in subnet_update request.

Is it a bug from neutron perspective?

[1]

https://github.com/openstack/neutron/blob/master/neutron/db/ipam_pluggable_backend.py#L356

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

85 matches

Mail list logo