date:20151023

[Yahoo-eng-team] [Bug 1509475] [NEW] Octiva driver doesn't need DevStack q-lbaasv2 service

2015-10-23 Thread Richard Theis

Public bug reported:

Using DevStack to deploy the master branch code, with neutron LBaaS V2
enabled, will start the q-lbaasv2 screen service.  However, the service
isn't needed and generates error messages in its log.  This is because
the LBaaS V2 reference driver is based on Octavia which doesn't require
the service.

DevStack deployments with LBaaS V2 enabled using the Octavia driver
should not start the q-lbaasv2 screen service.   However, LBaaS V2 with
the HAProxy driver should start the q-lbaasv2 screen service since it is
required.

** Affects: neutron
 Importance: Undecided
 Assignee: Richard Theis (rtheis)
 Status: In Progress


** Tags: lbaas

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

** Changed in: neutron
 Assignee: (unassigned) => Richard Theis (rtheis)

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

Title:
  Octiva driver doesn't need DevStack q-lbaasv2 service

Status in neutron:
  In Progress

Bug description:
  Using DevStack to deploy the master branch code, with neutron LBaaS V2
  enabled, will start the q-lbaasv2 screen service.  However, the
  service isn't needed and generates error messages in its log.  This is
  because the LBaaS V2 reference driver is based on Octavia which
  doesn't require the service.

  DevStack deployments with LBaaS V2 enabled using the Octavia driver
  should not start the q-lbaasv2 screen service.   However, LBaaS V2
  with the HAProxy driver should start the q-lbaasv2 screen service
  since it is required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1509475/+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 1509312] [NEW] unable to use tenant network after kilo to liberty update due to port security extension

2015-10-23 Thread Mihai Gheorghe

Public bug reported:

After updating to liberty from kilo all networks created in kilo release
are useless in liberty.

If i try to spawn a new isntance with a port on a network created in
kilo i get the following error in nova-compute.log :

BadRequest: Port does not have port security binding.

I guess this has to do with the new extension in ml2 plugin
port_security.

Using neutron DVR on Ubuntu 14.04.3!

This is my first bug report so sry in advance for any mistakes.

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

Title:
  unable to use tenant network after kilo to liberty update due to port
  security extension

Status in neutron:
  New

Bug description:
  After updating to liberty from kilo all networks created in kilo
  release are useless in liberty.

  If i try to spawn a new isntance with a port on a network created in
  kilo i get the following error in nova-compute.log :

  BadRequest: Port does not have port security binding.

  I guess this has to do with the new extension in ml2 plugin
  port_security.

  Using neutron DVR on Ubuntu 14.04.3!

  This is my first bug report so sry in advance for any mistakes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1509312/+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 1509295] [NEW] L3: agent may do double work upon start/resync

2015-10-23 Thread Oleg Bondarev

Public bug reported:

The issue was noticed during scale testing of DVR.
When l3 agent starts up it initiates a full sync with neutron server: requests 
full info about all the routers scheduled to it. At the same time agent may 
receive different notifications (router_added/updated/deleted) which were sent 
while agent was offline or starting up. For each of such notifications the 
agent will request router info again, so server will have to process it twice 
(first is for resync request). 

The following optimization makes sense: when agent is about to fullsync
we can skip all router notifications since fyllsync should bring the
agent up to date anyway.

** Affects: neutron
 Importance: Undecided
 Assignee: Oleg Bondarev (obondarev)
 Status: In Progress


** Tags: l3-ipam-dhcp loadimpact

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

Title:
  L3: agent may do double work upon start/resync

Status in neutron:
  In Progress

Bug description:
  The issue was noticed during scale testing of DVR.
  When l3 agent starts up it initiates a full sync with neutron server: 
requests full info about all the routers scheduled to it. At the same time 
agent may receive different notifications (router_added/updated/deleted) which 
were sent while agent was offline or starting up. For each of such 
notifications the agent will request router info again, so server will have to 
process it twice (first is for resync request). 

  The following optimization makes sense: when agent is about to
  fullsync we can skip all router notifications since fyllsync should
  bring the agent up to date anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1509295/+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 1505134] Re: Glance should allow to delete de-activated images

2015-10-23 Thread Flavio Percoco

** Summary changed:

- error message not clear when image-delete is called on deactivated image
+ Glance should allow to delete de-activated images

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

** Changed in: glance/liberty
   Status: New => Triaged

** Changed in: glance/liberty
   Importance: Undecided => High

** Changed in: glance
   Importance: Critical => High

** Changed in: glance/liberty
   Status: Triaged => Fix Released

** Changed in: glance
   Status: Triaged => Fix Released

** Changed in: glance
   Status: Fix Released => Fix Committed

** Changed in: glance
   Status: Fix Committed => Invalid

** Changed in: glance/liberty
 Assignee: (unassigned) => Ramaraja (ramaraja-r)

** Changed in: glance
 Assignee: Ramaraja (ramaraja-r) => (unassigned)

** Changed in: glance/liberty
 Assignee: Ramaraja (ramaraja-r) => Mike Fedosin (mfedosin)

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

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

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

Title:
  Glance should allow to delete de-activated images

Status in Glance:
  Invalid
Status in Glance kilo series:
  Triaged
Status in Glance liberty series:
  Fix Released

Bug description:
  Glance should allow to delete de-activated images

  Steps to reproduce:
  1. Create image
  2. Deactivate image
  3. Call image-delete on deactivated image

  Actual message:
  glance image-delete 5f0f914b-9f04-42c4-9769-07dc09e09056
  u'deactivated' is not one of [u'queued', u'saving', u'active', u'killed', 
u'deleted', u'pending_delete']

  Failed validating u'enum' in schema[u'properties'][u'status']:
  {u'description': u'Status of the image (READ-ONLY)',
   u'enum': [u'queued',
     u'saving',
     u'active',
     u'killed',
     u'deleted',
     u'pending_delete'],
   u'type': u'string'}

  On instance[u'status']:
  u'deactivated'

  Expected output:
  Deactivated image should be deleted successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1505134/+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 1509304] [NEW] l2-cache-size support for drives

2015-10-23 Thread Tim Bell

Public bug reported:

QCOW2 performance can be significantly improved by setting the l2-cache-
size parameter for large qcow2 based storage (such as images and
ephemeral drives) (see
https://events.linuxfoundation.org/sites/events/files/slides/p0.pp_.pdf).

Adding support for this optional parameter (which adds [...]-drive
file=hd.qcow2,l2-cache-size=2097152 to the qemu CLI) would allow
operators and/or users to configure a more tuned configuration.

A simple simple implementation where a default value could be set in
nova.conf would already give an improved flexibility. Ideally, this
could also be specified as an image or flavor property so that only
large drives would need to allocate the additional memory.

I could not locate an option such as this in the OpenStack versions up
to Liberty.

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

Title:
  l2-cache-size support for drives

Status in OpenStack Compute (nova):
  New

Bug description:
  QCOW2 performance can be significantly improved by setting the l2
  -cache-size parameter for large qcow2 based storage (such as images
  and ephemeral drives) (see
  https://events.linuxfoundation.org/sites/events/files/slides/p0.pp_.pdf).

  Adding support for this optional parameter (which adds [...]-drive
  file=hd.qcow2,l2-cache-size=2097152 to the qemu CLI) would allow
  operators and/or users to configure a more tuned configuration.

  A simple simple implementation where a default value could be set in
  nova.conf would already give an improved flexibility. Ideally, this
  could also be specified as an image or flavor property so that only
  large drives would need to allocate the additional memory.

  I could not locate an option such as this in the OpenStack versions up
  to Liberty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1509304/+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 1509373] [NEW] ERROR (UnsupportedVersion): Server doesn't support microversions

2015-10-23 Thread Ed Novak

Public bug reported:

Nova client generates this error:
ERROR (UnsupportedVersion): Server doesn't support microversions
with Openstack installed by the Falkor project

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

Title:
  ERROR (UnsupportedVersion): Server doesn't support microversions

Status in OpenStack Compute (nova):
  New

Bug description:
  Nova client generates this error:
  ERROR (UnsupportedVersion): Server doesn't support microversions
  with Openstack installed by the Falkor project

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1509373/+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 1509349] [NEW] [docs] Update the glance_store swift section with new auth params

2015-10-23 Thread ologvinova

Public bug reported:

New authentication parameters are added to the Swift storage backend
configuration according to the patch
https://review.openstack.org/#/c/193422/3:

glance_swift_store_auth_version (now defaults to v3
glance_swift_store_user_domain
glance_swift_store_project_domain

The appropriate section of the guide should reflect this change 
( 
http://docs.openstack.org/developer/glance/configuring.html#configuring-the-swift-storage-backend
 ).

** Affects: glance
 Importance: Undecided
 Assignee: ologvinova (ologvinova)
 Status: Confirmed


** Tags: documentation

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

** Changed in: glance
 Assignee: (unassigned) => ologvinova (ologvinova)

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

Title:
  [docs] Update the glance_store swift section with new auth params

Status in Glance:
  Confirmed

Bug description:
  New authentication parameters are added to the Swift storage backend
  configuration according to the patch
  https://review.openstack.org/#/c/193422/3:

  glance_swift_store_auth_version (now defaults to v3
  glance_swift_store_user_domain
  glance_swift_store_project_domain

  The appropriate section of the guide should reflect this change 
  ( 
http://docs.openstack.org/developer/glance/configuring.html#configuring-the-swift-storage-backend
 ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1509349/+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 1509431] [NEW] Enhance BGP Dynamic Routing with L2VPN/L3VPN support

2015-10-23 Thread Mickey Spiegel

Public bug reported:

In BGP Dynamic Routing [1], on behalf of an OpenStack region, BGP
Speakers advertise external reachability information to upstream
(physical) routers. BGP Dynamic Routing alleviates the need to provision
upstream routers whenever reachable subnets or floating IP addresses are
added.

In a public data center environment, BGP Dynamic Routing is limited to
internet reachability. For some tenants, access to the public Internet
is not enough. They may have networks connecting OpenStack routers to
upstream L2VPNs or L3VPNs. This enhancement extends the scope of BGP
Dynamic Routing so that it works with those upstream L2VPNs/L3VPNs. The
BGP Speakers associate the routes that they advertise with
L2VPNs/L3VPNs. The intention is to leverage both the BGP Dynamic Routing
and BGPVPN [2] frameworks, bringing aspects of both together and adding
functionality to associate advertised routes with the appropriate
L2VPNs/L3VPNs.

With BGP Dynamic Routing, the internal operation of OpenStack (between
compute nodes, and between compute nodes and network nodes) remains
untouched, using any of the variants and features available in
OpenStack. This RFE does not propose any data plane changes.

The reference implementation will use BGP EVPN Prefix Advertisement [3],
based on EVPN Route Type 5 (EVPN IP Prefix Route) specifying a recursion
through a GW IP address, linking to an EVPN Route Type 2 (MAC/IP). The
data plane will use VXLAN encapsulation on the networks connecting to
the outside world (1).

The initial scope will be network nodes only. Subsequent enhancements
will extend support to DVR.

(1) It is currently under investigation whether the networks connecting
to the outside world must be specified as external gateway networks from
OpenStack routers. A separate RFE will be filed to add VXLAN
encapsulation support on external networks, if necessary.

[1] https://blueprints.launchpad.net/neutron/+spec/bgp-dynamic-routing

[2] http://docs.openstack.org/developer/networking-bgpvpn/

[3] draft-ietf-bess-evpn-prefix-advertisement

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: rfe

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

Title:
  Enhance BGP Dynamic Routing with L2VPN/L3VPN support

Status in neutron:
  New

Bug description:
  In BGP Dynamic Routing [1], on behalf of an OpenStack region, BGP
  Speakers advertise external reachability information to upstream
  (physical) routers. BGP Dynamic Routing alleviates the need to
  provision upstream routers whenever reachable subnets or floating IP
  addresses are added.

  In a public data center environment, BGP Dynamic Routing is limited to
  internet reachability. For some tenants, access to the public Internet
  is not enough. They may have networks connecting OpenStack routers to
  upstream L2VPNs or L3VPNs. This enhancement extends the scope of BGP
  Dynamic Routing so that it works with those upstream L2VPNs/L3VPNs.
  The BGP Speakers associate the routes that they advertise with
  L2VPNs/L3VPNs. The intention is to leverage both the BGP Dynamic
  Routing and BGPVPN [2] frameworks, bringing aspects of both together
  and adding functionality to associate advertised routes with the
  appropriate L2VPNs/L3VPNs.

  With BGP Dynamic Routing, the internal operation of OpenStack (between
  compute nodes, and between compute nodes and network nodes) remains
  untouched, using any of the variants and features available in
  OpenStack. This RFE does not propose any data plane changes.

  The reference implementation will use BGP EVPN Prefix Advertisement
  [3], based on EVPN Route Type 5 (EVPN IP Prefix Route) specifying a
  recursion through a GW IP address, linking to an EVPN Route Type 2
  (MAC/IP). The data plane will use VXLAN encapsulation on the networks
  connecting to the outside world (1).

  The initial scope will be network nodes only. Subsequent enhancements
  will extend support to DVR.

  (1) It is currently under investigation whether the networks
  connecting to the outside world must be specified as external gateway
  networks from OpenStack routers. A separate RFE will be filed to add
  VXLAN encapsulation support on external networks, if necessary.

  [1] https://blueprints.launchpad.net/neutron/+spec/bgp-dynamic-routing

  [2] http://docs.openstack.org/developer/networking-bgpvpn/

  [3] draft-ietf-bess-evpn-prefix-advertisement

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1509431/+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 1509436] [NEW] Add BGP Listener Support to BGP Dynamic Routing with VPN, for Dynamic Separation of Internet and Tenant External Traffic

2015-10-23 Thread Mickey Spiegel

Public bug reported:

>From a compute instance with one Neutron port, depending on the destination IP 
>address, some traffic is destined for the Internet, while other traffic is 
>meant to go to a tenant VPN outside of the OpenStack region. There are many 
>possible reasons to have such a tenant VPN, including:
1.  Connectivity to an on premises tenant site using L3VPN connectivity, 
similar to AWS DirectConnect or SoftLayer DirectLink
2.  Connectivity between OpenStack regions, either for geographic diversity 
or due to specific services available in specific OpenStack regions (e.g. bare 
metal support)
3.  Connectivity to a non-OpenStack public data center

One common use case is a web front end within the OpenStack region,
connected to a back end database tier that resides outside of this
OpenStack region. The web front end must be reachable from the Internet.
The back end database tier must not be reachable from the Internet.

Specifically, the scenario of interest involves one or more OpenStack
routers, where each OpenStack router has multiple networks connecting to
the outside world (1). Relying on received BGP VPN routes, the OpenStack
router’s routing table is programmed, causing traffic to different
destination addresses to be directed towards different networks
connecting to the outside world.

The intention is to leave the internal operation of OpenStack (between
compute nodes, and between compute nodes and network nodes) untouched,
only affecting route selection from an OpenStack router to the outside
world. For this reason, this effort is targeted at BGP Dynamic Routing
[1] with VPN support [2].

Note that one goal is to hide the complexity of multiple networks
connecting to the outside world from OpenStack compute instances. The
solution should work with OpenStack compute instances that have only one
Neutron port. The solution should not impose any requirement for host
routing within the compute instances.

The reference implementation will use BGP EVPN Prefix Advertisement [3],
based on EVPN Route Type 5 (EVPN Prefix Route) specifying a recursion
through a GW IP address, linking to an EVPN Route Type 2 (MAC/IP). The
data plane will use VXLAN encapsulation on the networks connecting to
the outside world (2).

The initial scope will be network nodes only. Subsequent enhancements
will extend support to DVR.

(1) How to get more than one network connecting to the outside world,
onto a single OpenStack router, is currently under investigation. This
is not straightforward due to the limitation of one external gateway
network per OpenStack router. Currently under consideration is an
approach where all but one of the networks have router:external set to
false, i.e. the external gateway network connects to the internet (since
that needs Floating IP functionality and possibly a default route),
while networks with router:external set to false connect to tenant VPNs
(no Floating IP or NAT support). If enhancements are required to allow
multiple networks connecting to the outside world from a single
OpenStack router, a separate RFE will be filed.

(2) From an OpenStack router, if one of the networks connecting to the
outside world is considered to be an external gateway network, some
enhancements may be required to support VXLAN encapsulation on that
external gateway network. A separate RFE will be filed, if necessary.

[1] https://blueprints.launchpad.net/neutron/+spec/bgp-dynamic-routing

[2] https://bugs.launchpad.net/neutron/+bug/1509431

[3] draft-ietf-bess-evpn-prefix-advertisement

[4] http://docs.openstack.org/developer/networking-bgpvpn/

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: rfe

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

Title:
  Add BGP Listener Support to BGP Dynamic Routing with VPN, for Dynamic
  Separation of Internet and Tenant External Traffic

Status in neutron:
  New

Bug description:
  From a compute instance with one Neutron port, depending on the destination 
IP address, some traffic is destined for the Internet, while other traffic is 
meant to go to a tenant VPN outside of the OpenStack region. There are many 
possible reasons to have such a tenant VPN, including:
  1.Connectivity to an on premises tenant site using L3VPN connectivity, 
similar to AWS DirectConnect or SoftLayer DirectLink
  2.Connectivity between OpenStack regions, either for geographic diversity 
or due to specific services available in specific OpenStack regions (e.g. bare 
metal support)
  3.Connectivity to a non-OpenStack public data center

  One common use case is a web front end within the OpenStack region,
  connected to a back end database tier that resides outside of this
  OpenStack region. The web front end must be reachable from the
  Internet. The back end database tier must not be reachable from the
  Internet.

[Yahoo-eng-team] [Bug 1509581] [NEW] Comment spelling error in assignment section

2015-10-23 Thread zouyee

Public bug reported:

Comment spelling error： guaranteed to

** Affects: keystone
 Importance: Undecided
 Assignee: zouyee (zoues)
 Status: In Progress

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

Title:
  Comment spelling error in assignment section

Status in OpenStack Identity (keystone):
  In Progress

Bug description:
  Comment spelling error： guaranteed to

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1509581/+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 1378187] Re: IPv6 unit tests should have "ipv6" rather "v6"

2015-10-23 Thread Akihiro Motoki

When this bug was filed, there are various plugins in the neutron main tree.
Now vendor decomposition are almost completed and the need to address this bug 
significantly decreased (and almost there is no need).
I would like to make this bug "Won't Fix".

** Changed in: neutron
   Status: Incomplete => Won't Fix

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

Title:
  IPv6 unit tests should have "ipv6" rather "v6"

Status in neutron:
  Won't Fix

Bug description:
  At now some plugins do not have IPv6 support and keyword "v6" is checked to 
skip IPv6 unit tests in these plugins.
  "v6" is too short and may be used in a different context.
  It is better to have more clear keyword like "ipv6" in IPv6 related unit 
tests.

  
https://review.openstack.org/#/c/126407/3/neutron/tests/unit/opencontrail/test_contrail_plugin.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1378187/+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 1509195] [NEW] error VM state when evacuate fail

2015-10-23 Thread hougangliu

Public bug reported:

when I evacuate a stopped VM, after the target host rebuilds the VM
failed with error message like below, the VM changed to ACTIVE(I think
the VM state should be ERROR or stopped):

2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 129, 
in _do_dispatch
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 142, in 
inner
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher return 
func(*args, **kwargs)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/exception.py", line 89, in wrapped
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher payload)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 195, in __exit__
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/exception.py", line 72, in wrapped
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher return 
f(self, context, *args, **kw)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 352, in 
decorated_function
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher 
LOG.warning(msg, e, instance=instance)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 195, in __exit__
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 195, in __exit__
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 325, in 
decorated_function
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 402, in 
decorated_function
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 380, in 
decorated_function
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher 
kwargs['instance'], e, sys.exc_info())
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 195, in __exit__
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 368, in 
decorated_function
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2726, in 
rebuild_instance
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher bdms, 
recreate, on_shared_storage, preserve_ephemeral)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2765, in 
_do_rebuild_instance_with_claim
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher 
self._do_rebuild_instance(*args, **kwargs)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2872, in 
_do_rebuild_instance
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher 
self._rebuild_default_impl(**kwargs)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2646, in 
_rebuild_default_impl
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher 
block_device_info=new_block_device_info)
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2431, in 
spawn
2015-10-23 13:44:58.535 20194 ERROR oslo_messaging.rpc.dispatcher 
block_device_info)

[Yahoo-eng-team] [Bug 1509200] [NEW] There is ¨distrubuted¨ option for routers in Horizon

2015-10-23 Thread Reedip

Public bug reported:

Router creation in Neutron allows a --distributed and High Availability
option, which is not present in Horizon.

usage: neutron router-create [-h]
 [-f {html,json,json,shell,table,value,yaml,yaml}]
 [-c COLUMN] [--max-width ] [--noindent]
 [--prefix PREFIX] [--request-format {json,xml}]
 [--tenant-id TENANT_ID] [--admin-state-down]
 [--distributed {True,False}] [--ha {True,False}]
 NAME

Distributed and HA option must be present in the Creation option for
routers

** Affects: horizon
 Importance: Undecided
 Status: New

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

Title:
  There is ¨distrubuted¨ option for routers in Horizon

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Router creation in Neutron allows a --distributed and High
  Availability option, which is not present in Horizon.

  usage: neutron router-create [-h]
   [-f {html,json,json,shell,table,value,yaml,yaml}]
   [-c COLUMN] [--max-width ] [--noindent]
   [--prefix PREFIX] [--request-format {json,xml}]
   [--tenant-id TENANT_ID] [--admin-state-down]
   [--distributed {True,False}] [--ha {True,False}]
   NAME

  Distributed and HA option must be present in the Creation option for
  routers

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1509200/+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 1509217] [NEW] Spaces allowed as key-pair name

2015-10-23 Thread Christoph Held

Public bug reported:

Steps to reproduce:

1. Open launch instance dialog
2. Switch to tab Access & Security
3. Enter one space into name field
4. Paste key 
5. Click import key pair

Expected result:
- Key name is trimmed and rejected

Observered result:
- Key is imported
- Empty line appears in key selection fields

Remark:
- see also: https://bugs.launchpad.net/horizon/+bug/1288583

** Affects: horizon
 Importance: Undecided
 Status: New

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

Title:
  Spaces allowed as key-pair name

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Steps to reproduce:

  1. Open launch instance dialog
  2. Switch to tab Access & Security
  3. Enter one space into name field
  4. Paste key 
  5. Click import key pair

  Expected result:
  - Key name is trimmed and rejected

  Observered result:
  - Key is imported
  - Empty line appears in key selection fields

  Remark:
  - see also: https://bugs.launchpad.net/horizon/+bug/1288583

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1509217/+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 1509204] [NEW] validation error at wrong place

2015-10-23 Thread Christoph Held

Public bug reported:

Steps to reproduce:

0. Open Firefox
1. Go to launch instance dialog
2. Enter name
3. Enter character in instance count field
4. Switch to tab 'Access & Security'
5. Click on launch

Expected result:
- e.g. tab is switched, error displayed

Result:
- Error is shown below browser window

Remark:
- Behavior is browser dependant.

** Affects: horizon
Importance: Undecided
Status: New

** Attachment added: "wrong-error-placement.png"

https://bugs.launchpad.net/bugs/1509204/+attachment/4502888/+files/wrong-error-placement.png

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

Title:
validation error at wrong place

Status in OpenStack Dashboard (Horizon):
New

Bug description:
Steps to reproduce:

0. Open Firefox
1. Go to launch instance dialog
2. Enter name
3. Enter character in instance count field
4. Switch to tab 'Access & Security'
5. Click on launch

Expected result:
- e.g. tab is switched, error displayed

Result:
- Error is shown below browser window

Remark:
- Behavior is browser dependant.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1509204/+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 1505153] Re: gates broken by WebOb 1.5 release

2015-10-23 Thread Jesse Pretorius

** Changed in: openstack-ansible
   Status: Fix Committed => Fix Released

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

Title:
  gates broken by WebOb 1.5 release

Status in Cinder:
  Fix Released
Status in Manila:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in openstack-ansible:
  Fix Released

Bug description:
  Hi,

  WebOb 1.5 was released yesterday. test_misc of Cinder starts failing
  with this release. I wrote this simple fix which should be enough to
  repair it:

  https://review.openstack.org/233528
  "Fix test_misc for WebOb 1.5"

   class ConvertedException(webob.exc.WSGIHTTPException):
  -def __init__(self, code=0, title="", explanation=""):
  +def __init__(self, code=500, title="", explanation=""):

  Victor

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1505153/+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 1505677] Re: oslo.versionedobjects 0.11.0 causing KeyError: 'objects' in nova-conductor log

2015-10-23 Thread Jesse Pretorius

** Changed in: openstack-ansible
   Status: Fix Committed => Fix Released

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

Title:
  oslo.versionedobjects 0.11.0 causing KeyError: 'objects' in nova-
  conductor log

Status in OpenStack Compute (nova):
  Fix Released
Status in openstack-ansible:
  Fix Released
Status in oslo.versionedobjects:
  Fix Released

Bug description:
  In nova-conductor we're seeing the following error for stable/liberty:

  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher Traceback 
(most recent call last):
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
142, in _dispatch_and_reply
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher 
executor_callback))
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
186, in _dispatch
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher 
executor_callback)
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
129, in _do_dispatch
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/nova/conductor/manager.py", line 937, 
in object_class_action_versions
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher context, 
objname, objmethod, object_versions, args, kwargs)
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/nova/conductor/manager.py", line 477, 
in object_class_action_versions
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher if 
isinstance(result, nova_object.NovaObject) else result)
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 
535, in obj_to_primitive
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher 
version_manifest)
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 
507, in obj_make_compatible_from_manifest
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher return 
self.obj_make_compatible(primitive, target_version)
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/nova/objects/instance.py", line 1325, 
in obj_make_compatible
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher 
target_version)
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/nova/objects/base.py", line 262, in 
obj_make_compatible
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher 
rel_versions = self.obj_relationships['objects']
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher KeyError: 
'objects'
  2015-10-12 23:29:14.413 2243 ERROR oslo_messaging.rpc.dispatcher

  More details here:
  
http://logs.openstack.org/56/233756/8/check/gate-openstack-ansible-dsvm-commit/879f745/logs/aio1_nova_conductor_container-5ec67682/nova-conductor.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1505677/+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 1509232] [NEW] If we update a QoSPolicy description, the agents get notified and rules get rewired for nothing

2015-10-23 Thread Miguel Angel Ajo

Public bug reported:

https://github.com/openstack/neutron/blob/master/neutron/services/qos/qos_plugin.py#L59
https://github.com/openstack/neutron/blob/master/neutron/services/qos/notification_drivers/message_queue.py


We should be smarter on the message_queue and not send useless notifications, 
alternativelty we could make the agent smarter and ignore those.

** Affects: neutron
 Importance: Medium
 Status: New


** Tags: dos

** Tags added: dos

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

** Changed in: neutron
   Importance: Low => 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/1509232

Title:
  If we update a QoSPolicy description, the agents get notified and
  rules get rewired for nothing

Status in neutron:
  New

Bug description:
  
https://github.com/openstack/neutron/blob/master/neutron/services/qos/qos_plugin.py#L59
  
https://github.com/openstack/neutron/blob/master/neutron/services/qos/notification_drivers/message_queue.py

  
  We should be smarter on the message_queue and not send useless notifications, 
alternativelty we could make the agent smarter and ignore those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1509232/+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 1508421] Re: Projects dropdown fails due to incomplete Keystone endpoint URL

2015-10-23 Thread Johannes Grassler

** Also affects: django-openstack-auth
   Importance: Undecided
   Status: New

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

Title:
  Projects dropdown fails due to incomplete Keystone endpoint URL

Status in django-openstack-auth:
  New
Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  Problem Description
  ===

  The 'Projects' dropdown in our Horizon dashboard (the one on the top
  left) is empty since we switched to Openstack Kilo. We investigated the
  issue and found the following error message in horizon.log:

AuthorizationFailure: Authorization Failed: The resource could not
  be found. (HTTP 404) http://10.0.81.10:5000

  [You will find a full stack trace in stacktrace.txt in the attached
  tarball.]

  Further investigation (see keystone.pcap in the attached tarball for a
  packet trace) revealed that horizon is trying to access
  http://10.0.81.10:5000/tokens (as opposed to the correct URL,
  http://10.0.81.10:5000/v2.0/tokens). We found the problem could be
  worked around by appending missing versioning information in backend.py
  (see below), but it should be possible to fix this in a cleaner manner.

  
  Environment
  ===

  We are running Openstack Kilo with the Ubuntu Cloud packages, some of
  them modified locally with backported bugfixes. You will find these
  packages at https://launchpad.net/~syseleven-platform/+archive/ubuntu/kilo. 
  In particular, we are running the following Horizon package:

  https://launchpad.net/~syseleven-platform/+archive/ubuntu/kilo

  
  Configuration
  =

  You will find our full Horizon configuration in local_settings.py in the
  attached tarball. Relevant points:

  * OPENSTACK_KEYSTONE_URL is http://10.0.81.10:5000/v2.0
  * OPENSTACK_API_VERSIONS is configured for Keystone 2.0
  * The identity endpoints as reported by Keystone itself do not contain
versioning information (the way it is supposed to be as of Kilo).

  
  Steps to reproduce
  ==

  * Run Horizon/Kilo (with the Ubuntu Cloud packages or our modified
packages; both should exhibit this problem)
  * Configure the end points and OPENSTACK_KEYSTONE_URL as described under
"Configuration"
  * Log into the web interface.

  This should yield an empty Projects dropdown list and the stacktrace in
  stacktrace.txt in /var/log/horizon/horizon.log).

  
  Workaround
  ==

  I modified /usr/lib/python2.7/dist-packages/openstack_auth/backend.py to
  append versioning information to the endpoint URL if it is missing. This
  can be used to work around the problem in a pinch, but I do not consider
  it a clean fix.

  
  Files
  =

  I attached a couple of files to illustrate the problem (you will find
  all of these in horizon-projects-dropdown.tar):

  backend.py  The modified backend.py described under "Workaround"
  endpoints.txt   A list of identity endpoints as reported by Keystone
  keystone.pcap   A packet capture of Horizon's interactions with
  Keystone
  local_settings.py   Our Horizon configuration
  stacktrace.txt  The stack trace that appears in 
  /var/log/horizon/horizon.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/django-openstack-auth/+bug/1508421/+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 1509200] Re: Options missing in while creating routers in Horizon