[Yahoo-eng-team] [Bug 1595778] Re: There are some spelling mistakes in keystone

[OpenStack Infra]

Reviewed:  https://review.openstack.org/333659
Committed: 
https://git.openstack.org/cgit/openstack/keystone/commit/?id=3f78996cfa163291cadecb72fb3c102e578bec0d
Submitter: Jenkins
Branch:master

commit 3f78996cfa163291cadecb72fb3c102e578bec0d
Author: gecong1973 
Date:   Fri Jun 24 10:42:28 2016 +0800

Fix a few spelling mistakes

   Donmain should be domain
   prvider should be provider
   boudary should be boundary
   convesion should be conversion
   inteface should be interface
   projcets should be projects
   sensistive should be sensitive
   environemt should be environment
   validaton shoud be validation

Closes-Bug: #1595778

Change-Id: I304d0de68aa096ea1c1a26c8712a2312578e9c30


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

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

Title:
  There are some spelling mistakes in keystone

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  in keystone/cmd/cli.py:633:
   Donmain configs match the filename pattern of, Donmain should be domain 
in keystone/federation/backends/base.py:277:
   :param sp: service prvider object, prvider should be provider
in keystone/identity/backends/ldap/common.py:338:
boudary, examples of type conversions are, boudary should be boundary
in keystone/identity/backends/ldap/common.py:384:
   the type convesion class would have to subclass each of, convesion 
should be conversion
in keystone/identity/backends/ldap/common.py:842:
   This LDAP inteface wraps the python-ldap based interfaces., inteface 
should be interface
in keystone/resource/backends/base.py:519:
   projcets always have a non-None value for domain_id. projcets should be 
projects
in keystone/resource/config_backends/base.py:113:
   irrespective of whether it is sensistive ot not.  sensistive should be 
sensitive
in  keystone/tests/functional/core.py:70:
   This method doesn't do any token validaton.validaton shoud be validation
in keystone/common/wsgi.py:808:
  context. Also, its OK to pass the environemt as it is read-only 
in,environemt should be environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1595778/+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 1595805] [NEW] Instance do not boot.

[YoshiakiGoto]

Public bug reported:

I am trying to do in Mitaka version.

When Attempting to boot instance by running the following command.

# nova boot --flavor 1 --key-name test-key2 --image 0f78c38d-b6bd-
4b42-9ee5-32552f72fc44 test_instance

Error such as the following has been returned.


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-c0928fee-97a6-483d-aecd-f870cf94941b)


Please tell me the solution.

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

Title:
  Instance do not boot.

Status in OpenStack Compute (nova):
  New

Bug description:
  I am trying to do in Mitaka version.

  When Attempting to boot instance by running the following command.

  # nova boot --flavor 1 --key-name test-key2 --image 0f78c38d-b6bd-
  4b42-9ee5-32552f72fc44 test_instance

  Error such as the following has been returned.

  
  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-c0928fee-97a6-483d-aecd-f870cf94941b)
  

  Please tell me the solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1595805/+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 1557308] Re: Restart openvswitch service，dhcp and l3 ports in namespaces exit the namespaces

[xiewj]

In Mitaka,The problem is not reappeared

** Changed in: neutron
   Status: Incomplete => 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/1557308

Title:
  Restart openvswitch service，dhcp and l3 ports  in namespaces exit the
  namespaces

Status in neutron:
  Invalid

Bug description:
  reproduce steps:
  1) Create a network with subnet
  2) dhcp port created,the dhcp tap existed in dhcp namespace
  3) restart openvswitch service
  4) the dhcp tap exit the  dhcp namespace

  For router port, also is such.

  [root@~(keystone_admin)]# ip netns exec 
qdhcp-1afa4268-a05b-44d8-a871-9cd93464d937 ifconfig -a
  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 0  (Local Loopback)
  RX packets 1  bytes 28 (28.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 1  bytes 28 (28.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  tap90f18aa5-57: flags=67  mtu 1500
  inet 33.0.0.2  netmask 255.255.255.0  broadcast 33.0.0.255
  inet6 fe80::f816:3eff:fead:931a  prefixlen 64  scopeid 0x20
  ether fa:16:3e:ad:93:1a  txqueuelen 0  (Ethernet)
  RX packets 398  bytes 32468 (31.7 KiB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 11  bytes 906 (906.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  [root@~(keystone_admin)]# ifconfig tap90f18aa5-57
  tap90f18aa5-57: error fetching interface information: Device not found
  [root@~(keystone_admin)]# systemctl restart openvswitch.service
  [root@~(keystone_admin)]# ip netns exec 
qdhcp-1afa4268-a05b-44d8-a871-9cd93464d937 ifconfig -a
  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 0  (Local Loopback)
  RX packets 1  bytes 28 (28.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 1  bytes 28 (28.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  [root@~(keystone_admin)]# ifconfig tap90f18aa5-57
  tap90f18aa5-57: flags=67  mtu 1500
  inet6 fe80::d86a:5eff:fe36:6f0f  prefixlen 64  scopeid 0x20
  ether da:6a:5e:36:6f:0f  txqueuelen 0  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 7  bytes 578 (578.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  [root@~(keystone_admin)]#

  [root@ ~(keystone_admin)]# ip netns exec 
qrouter-b2a169bf-446c-4c4c-b676-be047b626bbc ifconfig -a
  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 0  (Local Loopback)
  RX packets 1  bytes 28 (28.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 1  bytes 28 (28.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  qr-e6321062-27: flags=67  mtu 1500
  inet 20.0.0.1  netmask 255.255.255.0  broadcast 20.0.0.255
  inet6 fe80::f816:3eff:fe6a:a1cb  prefixlen 64  scopeid 0x20
  ether fa:16:3e:6a:a1:cb  txqueuelen 0  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 12  bytes 952 (952.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  [root@~(keystone_admin)]# systemctl restart openvswitch.service
  [root@~(keystone_admin)]# ip netns exec 
qrouter-b2a169bf-446c-4c4c-b676-be047b626bbc ifconfig -a
  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 0  (Local Loopback)
  RX packets 1  bytes 28 (28.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 1  bytes 28 (28.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  [root@ ~(keystone_admin)]# ifconfig qr-e6321062-27
  qr-e6321062-27: flags=67  mtu 1500
  inet6 fe80::9014:2dff:fec3:15d6  prefixlen 64  scopeid 0x20
  ether 92:14:2d:c3:15:d6  txqueuelen 0  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 8  bytes 648 (648.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  [root@S ~(keystone_admin)]#

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

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

[Yahoo-eng-team] [Bug 1595801] [NEW] Using the neutron purge command to delete all supported resources owned by a tenant, the returned result of deleted port number doesn't contain the port that devic

[xiewj]

Public bug reported:

Using the neutron purge command to delete all supported resources owned
by a tenant,the returned result of deleted port number doesn't contain
the port that device_owner is 'network: router_gateway'.

1)Creating a external network with a subnet;
2)Creating a router
3)Using router-gateway-set command sets a external gateway for the router 
created
4)Using port-list command returns one port whose device_owner is 'network: 
router_gateway'.
5)Using the neutron purge command to delete all supported resources owned by 
the tenant owning the network resources,the returned result contains no deleted 
port info.

Detail Operation process,please
see:http://paste.openstack.org/show/521791/

** Affects: neutron
 Importance: Undecided
 Assignee: xiewj (36429515-3)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => xiewj (36429515-3)

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

Title:
  Using the neutron purge command to delete all supported resources
  owned by a tenant,the returned result of deleted port number doesn't
  contain the port that device_owner is 'network: router_gateway'.

Status in neutron:
  New

Bug description:
  Using the neutron purge command to delete all supported resources
  owned by a tenant,the returned result of deleted port number doesn't
  contain the port that device_owner is 'network: router_gateway'.

  1)Creating a external network with a subnet;
  2)Creating a router
  3)Using router-gateway-set command sets a external gateway for the router 
created
  4)Using port-list command returns one port whose device_owner is 'network: 
router_gateway'.
  5)Using the neutron purge command to delete all supported resources owned by 
the tenant owning the network resources,the returned result contains no deleted 
port info.

  Detail Operation process,please
  see:http://paste.openstack.org/show/521791/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1595801/+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 1595773] Re: Make print py3 compatible

[Steve Martinelli]

a quick scan of the keystone code base shows this is not an issue, we
only use print in the py3 friendly way. marking this as invalid, re-open
if i'm wrong.

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

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

Title:
  Make print py3 compatible

Status in Cinder:
  New
Status in glance_store:
  New
Status in OpenStack Identity (keystone):
  Invalid
Status in OpenStack Compute (nova):
  In Progress
Status in python-cinderclient:
  New
Status in Rally:
  New
Status in SWIFT:
  New

Bug description:
  In PY3,

  Remove the print "", join the print () function to achieve the same
  function.

  Python 3:

  #!/usr/bin/python
  # -*- coding: utf-8 -*-
  print ("cinder")

  print "cinder"

  
File "code", line 5
  print "cinder"
   ^
  SyntaxError: Missing parentheses in call to 'print'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1595773/+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 1595795] [NEW] [BGP][devstack] Install bgp failed because of Permission denied

[Dongcan Ye]

Public bug reported:

Environment:
OS: Ubuntu 14.04
Code repo: master

Install Neutron bgp in DevStack failed.
http://paste.openstack.org/show/521784/

** Affects: neutron
 Importance: Undecided
 Assignee: Dongcan Ye (hellochosen)
 Status: New


** Tags: l3-bgp

** Changed in: neutron
 Assignee: (unassigned) => Dongcan Ye (hellochosen)

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

Title:
  [BGP][devstack] Install bgp failed because of Permission denied

Status in neutron:
  New

Bug description:
  Environment:
  OS: Ubuntu 14.04
  Code repo: master

  Install Neutron bgp in DevStack failed.
  http://paste.openstack.org/show/521784/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1595795/+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 1561310] Re: dashboard displays wrong quotas

[OpenStack Infra]

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

commit 35eb25a955f116cbd42e9952ba47cee61c0759aa
Author: Itxaka 
Date:   Thu Apr 21 12:18:30 2016 +0200

Make sure we always get all limits

When checking with nova for the absolute limits
we were not taking into account the reserved
quotas (i.e. instance in rebuilding will take
cpu and ram) so this could lead to wrongly
thinking that the user could launch more instances
that its quota allowed. It also made the overview
page display wrong quotas as it didnt took into
account those reserved resources.

Change-Id: If51470d185ddc122acbdf4cf0d0fd952f3f791a0
Closes-bug: 1561310


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

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

Title:
  dashboard displays wrong quotas

Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  1. User try to  boot a new vm by click the button "+ Launch Instance"  in 
dashboard web->project->compute->instances.
  2. But the button "+ Launch Instance"  is disabled and shows "quota exceeded".
  3. Then user go to dashboard web->project->compute->overview perspective, but 
find Instances,VCPU and RAM haven't exceed 
  the quotas. In this case, it's shows like below:
  Instances
  Used 8 of 10
  VCPUs
  Used 18 of 20
  RAM
  Used 512MB of 50.0GB 
  This will confuse the user, is there anything incorrect?

  root cause: 
  I think one of the root cause is that the current project have another work, 
such as rebuilding vm, which obtail some quotas and mark
  the 'reserved' fields(nova->quota_usages table) to a none zero value .
  So I select *  from nova.quota_usages where project_id = 'current project 
id', and find thati in  the row 'cores' , the 'reserved' = 2. Because of this,  
the VCPU is actually Used 10 of 10. 
  Excepted result:
  The 'reserved' quota should also be taken as an used quota ,and so in 
dashboard web->project->compute->overview perspectiv, it should shows as below:
  VCPUs
  Used 20 of 20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1561310/+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 1595786] Re: Make string.letters PY3 compatible

[jingtao liang]

** Also affects: swift-swf
   Importance: Undecided
   Status: New

** Changed in: swift-swf
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

Title:
  Make  string.letters PY3 compatible

Status in OpenStack Compute (nova):
  New
Status in python-novaclient:
  New
Status in SWIFT:
  New

Bug description:
  String.letters and related.Lowercase and.Uppercase are removed, please
  switch to string.ascii_letters, etc.

  
  as:
  
https://github.com/openstack/nova/blob/04f2d81bb4d1e26482b613ab799bb38ce304e143/nova/tests/unit/api/openstack/compute/test_console_output.py#L102

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1595786/+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 1595786] Re: Make string.letters PY3 compatible

[YaoZheng_ZTE]

** Project changed: nova => python-novaclient

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

Title:
  Make  string.letters PY3 compatible

Status in OpenStack Compute (nova):
  New
Status in python-novaclient:
  New
Status in SWIFT:
  New

Bug description:
  String.letters and related.Lowercase and.Uppercase are removed, please
  switch to string.ascii_letters, etc.

  
  as:
  
https://github.com/openstack/nova/blob/04f2d81bb4d1e26482b613ab799bb38ce304e143/nova/tests/unit/api/openstack/compute/test_console_output.py#L102

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1595786/+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 1595786] [NEW] Make string.letters PY3 compatible

[Ji.Wei]

Public bug reported:

String.letters and related.Lowercase and.Uppercase are removed, please
switch to string.ascii_letters, etc.


as:
https://github.com/openstack/nova/blob/04f2d81bb4d1e26482b613ab799bb38ce304e143/nova/tests/unit/api/openstack/compute/test_console_output.py#L102

** Affects: nova
 Importance: Undecided
 Assignee: Ji.Wei (jiwei)
 Status: New

** Affects: python-novaclient
 Importance: Undecided
 Assignee: YaoZheng_ZTE (zheng-yao1)
 Status: New

** Affects: swift-swf
 Importance: Undecided
 Assignee: jingtao liang (liang-jingtao)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Ji.Wei (jiwei)

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

Title:
  Make  string.letters PY3 compatible

Status in OpenStack Compute (nova):
  New
Status in python-novaclient:
  New
Status in SWIFT:
  New

Bug description:
  String.letters and related.Lowercase and.Uppercase are removed, please
  switch to string.ascii_letters, etc.

  
  as:
  
https://github.com/openstack/nova/blob/04f2d81bb4d1e26482b613ab799bb38ce304e143/nova/tests/unit/api/openstack/compute/test_console_output.py#L102

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1595786/+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 1595773] Re: Make print py3 compatible

[Ji.Wei]

** No longer affects: glance

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

Title:
  Make print py3 compatible

Status in Cinder:
  New
Status in glance_store:
  New
Status in OpenStack Identity (keystone):
  New
Status in OpenStack Compute (nova):
  In Progress
Status in python-cinderclient:
  New
Status in Rally:
  New
Status in SWIFT:
  New

Bug description:
  In PY3,

  Remove the print "", join the print () function to achieve the same
  function.

  Python 3:

  #!/usr/bin/python
  # -*- coding: utf-8 -*-
  print ("cinder")

  print "cinder"

  
File "code", line 5
  print "cinder"
   ^
  SyntaxError: Missing parentheses in call to 'print'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1595773/+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 1595782] [NEW] Optional argument '--router:external' is absent in the help msg of 'net-create' command.

[xiewj]

Public bug reported:

In Mitaka,
Optional argument '--router:external' is absent in the help msg of 'net-create' 
command.

However,'--router:external' argument can be specified when executing
net-create command,it seems that '--router:external' argument is
forgetten in Mitaka release.

[root@localhost devstack]# neutron help net-create
usage: neutron net-create [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN]
  [--max-width ] [--noindent]
  [--prefix PREFIX] [--request-format {json}]
  [--tenant-id TENANT_ID] [--admin-state-down]
  [--shared] [--provider:network_type ]
  [--provider:physical_network ]
  [--provider:segmentation_id ]
  [--vlan-transparent {True,False}]
  [--description DESCRIPTION]
  [--qos-policy QOS_POLICY]
  [--availability-zone-hint AVAILABILITY_ZONE]
  [--dns-domain DNS_DOMAIN]
  NAME

Create a network for a given tenant.

positional arguments:
  NAME  Name of network to create.

optional arguments:
  -h, --helpshow this help message and exit
  --request-format {json}
DEPRECATED! Only JSON request format is supported.
  --tenant-id TENANT_ID
The owner tenant ID.
  --admin-state-downSet admin state up to false.
  --shared  Set the network as shared.
  --provider:network_type 
The physical mechanism by which the virtual network is
implemented.
  --provider:physical_network 
Name of the physical network over which the virtual
network is implemented.
  --provider:segmentation_id 
VLAN ID for VLAN networks or tunnel-id for GRE/VXLAN
networks.
  --vlan-transparent {True,False}
Create a vlan transparent network.
  --description DESCRIPTION
Description of network.
  --qos-policy QOS_POLICY
Attach QoS policy ID or name to the resource.
  --availability-zone-hint AVAILABILITY_ZONE
Availability Zone for the network (requires
availability zone extension, this option can be
repeated).
  --dns-domain DNS_DOMAIN
Assign DNS domain to the network (requires DNS
integration extension)

output formatters:
  output formatter options

  -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml}
the output format, defaults to table
  -c COLUMN, --column COLUMN
specify the column(s) to include, can be repeated

table formatter:
  --max-width 
Maximum display width, <1 to disable. You can also use
the CLIFF_MAX_TERM_WIDTH environment variable, but the
parameter takes precedence.

json formatter:
  --noindentwhether to disable indenting the JSON

shell formatter:
  a format a UNIX shell can parse (variable="value")

  --prefix PREFIX   add a prefix to all variable names
[root@localhost devstack]# 

[root@localhost devstack]# neutron net-create public --shared --router:external
Created a new network:
+---+--+
| Field | Value|
+---+--+
| admin_state_up| True |
| availability_zone_hints   |  |
| availability_zones|  |
| created_at| 2016-06-24T02:08:06  |
| description   |  |
| id| 8fc03cba-36f9-4efa-b40c-d9a478bebea7 |
| ipv4_address_scope|  |
| ipv6_address_scope|  |
| is_default| False|
| mtu   | 1450 |
| name  | public   |
| port_security_enabled | True |
| provider:network_type | vxlan|
| provider:physical_network |  |
| provider:segmentation_id  | 1096 |
| router:external   | True |
| shared| True |
| status| ACTIVE   |
| subnets   | 

[Yahoo-eng-team] [Bug 1595083] Re: Instance with powering-off task-state stop failure when the nova-compute restarts

[Tina Kevin]

** Changed in: nova
 Assignee: Tina Kevin (song-ruixia) => (unassigned)

** Changed in: nova
Milestone: newton-3 => None

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

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

Title:
  Instance with powering-off task-state stop failure when the nova-
  compute restarts

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===
  There is an active instance and stop the instance. When the task_state of the
  instance is powering-off, then I restart the nova-compute services, the 
_init_instance
  function will stop the instance again. The expected result is stop instance 
success and
  instance is SHUTOFF, but now stop raise error.
  code:
  if instance.task_state == task_states.POWERING_OFF:
    try:
       LOG.debug("Instance in transitional state %s at start-up "
   "retrying stop request",
   instance.task_state, instance=instance)
  self.stop_instance(context, instance)
    except Exception:
  # we don't want that an exception blocks the init_host
  msg = _LE('Failed to stop instance')
  LOG.exception(msg, instance=instance)
  return

  The powering-on task-state also has the same issue.

  Steps to reproduce
  ==
  A chronological list of steps which will bring off the
  issue :
  * I boot an instance
     nova boot --flavor 2 --image c61966bd-7969-40af-9f9b-ed282fb25bdf --nic
     net-id=ea2a9eb5-f52e-4822-aa5d-168658e9c383  test_iso8
  * then I stop the instance
     nova stop test_iso8
  * then I restart the nova-compute service when instance in powering-off 
task-state

  Expected result
  ===
  When nova-compute service restart，the instance test_iso8 should be stopped.

  Actual result
  =
  After the nova-compute service restart, the instance test_iso8 is active.
  The nova-compute.log has error information.

  Environment
  ===
  1. Exact version of OpenStack you are running.
     Mitaka
  2. Which hypervisor did you use?
     Libvirt + KVM
  3. Which networking type did you use?
      Neutron with OpenVSwitch

  Logs & Configs
  ==
  [root@slot4 ~(keystone_admin)]# nova boot --flavor 2 --image 
c61966bd-7969-40af-9f9b-ed282fb25bdf --nic 
net-id=ea2a9eb5-f52e-4822-aa5d-168658e9c383  test_iso8
  [root@slot4 ~(keystone_admin)]# nova stop test_iso8
  Request to stop server test_iso8 has been accepted.

  restart nova-compute service

  [root@slot4 ~(keystone_admin)]# nova list
  
+--+---+++-+-+
  | ID   | Name  | Status | Task State | 
Power State | Networks|
  
+--+---+++-+-+
  | 40d78f1d-38fc-4bfb-8e7e-a3dfe60398d9 | test_iso8 | ACTIVE | -  | 
Running | net01=5.5.5.249 |
  
+--+---+++-+-+
  [root@slot4 ~(keystone_admin)]# nova instance-action-list 
40d78f1d-38fc-4bfb-8e7e-a3dfe60398d9
  
+---+--+-++
  | Action| Request_ID   | Message | 
Start_Time |
  
+---+--+-++
  | create| req-25400b17-6c33-45e5-ae4e-87cba0d0de15 | -   | 
2016-06-22T04:40:43.00 |
  | stop  | req-5a7d26eb-79d3-4e69-86a8-d40c02bc6a00 | -   | 
2016-06-22T07:08:23.00 |
  
+---+--+-++

  nova-compute.log error information:
  2016-06-22 15:08:29.942 28875 ERROR nova.compute.manager 
[req-b6bbfa68-334c-4c31-9f6d-4d5523cebc4d - - - - -] [instance: 
40d78f1d-38fc-4bfb-8e7e-a3dfe60398d9] Failed to stop instance
  2016-06-22 15:08:29.942 28875 TRACE nova.compute.manager [instance: 
40d78f1d-38fc-4bfb-8e7e-a3dfe60398d9] Traceback (most recent call last):
  2016-06-22 15:08:29.942 28875 TRACE nova.compute.manager [instance: 
40d78f1d-38fc-4bfb-8e7e-a3dfe60398d9]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1304, in 
_init_instance
  2016-06-22 15:08:29.942 28875 TRACE nova.compute.manager [instance: 
40d78f1d-38fc-4bfb-8e7e-a3dfe60398d9] self.stop_instance(context, instance)
  2016-06-22 15:08:29.942 28875 TRACE nova.compute.manager [instance: 
40d78f1d-38fc-4bfb-8e7e-a3dfe60398d9]   File 
"/usr/lib/python2.7/site-packages/nova/exception.py", line 88, in wrapped
  2016-06-22 15:08:29.942 28875 TRACE nova.compute.manager [instance: 

[Yahoo-eng-team] [Bug 1595773] Re: Make print py3 compatible

[jingtao liang]

** Also affects: swift-swf
   Importance: Undecided
   Status: New

** Changed in: swift-swf
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

Title:
  Make print py3 compatible

Status in Cinder:
  New
Status in Glance:
  Invalid
Status in glance_store:
  New
Status in OpenStack Identity (keystone):
  New
Status in OpenStack Compute (nova):
  In Progress
Status in python-cinderclient:
  New
Status in Rally:
  New
Status in SWIFT:
  New

Bug description:
  In PY3,

  Remove the print "", join the print () function to achieve the same
  function.

  Python 3:

  #!/usr/bin/python
  # -*- coding: utf-8 -*-
  print ("cinder")

  print "cinder"

  
File "code", line 5
  print "cinder"
   ^
  SyntaxError: Missing parentheses in call to 'print'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1595773/+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 1595778] [NEW] There are some spelling mistakes in keystone

[gecong]

Public bug reported:

in keystone/cmd/cli.py:633:
 Donmain configs match the filename pattern of, Donmain should be domain 
  in keystone/federation/backends/base.py:277:
 :param sp: service prvider object, prvider should be provider
  in keystone/identity/backends/ldap/common.py:338:
  boudary, examples of type conversions are, boudary should be boundary
  in keystone/identity/backends/ldap/common.py:384:
 the type convesion class would have to subclass each of, convesion should 
be conversion
  in keystone/identity/backends/ldap/common.py:842:
 This LDAP inteface wraps the python-ldap based interfaces., inteface 
should be interface
  in keystone/resource/backends/base.py:519:
 projcets always have a non-None value for domain_id. projcets should be 
projects
  in keystone/resource/config_backends/base.py:113:
 irrespective of whether it is sensistive ot not.  sensistive should be 
sensitive
  in  keystone/tests/functional/core.py:70:
 This method doesn't do any token validaton.validaton shoud be validation
  in keystone/common/wsgi.py:808:
context. Also, its OK to pass the environemt as it is read-only 
in,environemt should be environment

** Affects: keystone
 Importance: Undecided
 Assignee: gecong (ge-cong)
 Status: New

** Changed in: keystone
 Assignee: (unassigned) => gecong (ge-cong)

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

Title:
  There are some spelling mistakes in keystone

Status in OpenStack Identity (keystone):
  New

Bug description:
  in keystone/cmd/cli.py:633:
   Donmain configs match the filename pattern of, Donmain should be domain 
in keystone/federation/backends/base.py:277:
   :param sp: service prvider object, prvider should be provider
in keystone/identity/backends/ldap/common.py:338:
boudary, examples of type conversions are, boudary should be boundary
in keystone/identity/backends/ldap/common.py:384:
   the type convesion class would have to subclass each of, convesion 
should be conversion
in keystone/identity/backends/ldap/common.py:842:
   This LDAP inteface wraps the python-ldap based interfaces., inteface 
should be interface
in keystone/resource/backends/base.py:519:
   projcets always have a non-None value for domain_id. projcets should be 
projects
in keystone/resource/config_backends/base.py:113:
   irrespective of whether it is sensistive ot not.  sensistive should be 
sensitive
in  keystone/tests/functional/core.py:70:
   This method doesn't do any token validaton.validaton shoud be validation
in keystone/common/wsgi.py:808:
  context. Also, its OK to pass the environemt as it is read-only 
in,environemt should be environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1595778/+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 1595773] Re: Make print py3 compatible

[Ji.Wei]

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

** No longer affects: neutron

** No longer affects: tempest

** Changed in: rally
 Assignee: (unassigned) => Ji.Wei (jiwei)

** Changed in: nova
 Assignee: Ji.Wei (jiwei) => (unassigned)

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

Title:
  Make print py3 compatible

Status in Cinder:
  New
Status in Glance:
  Invalid
Status in glance_store:
  New
Status in OpenStack Identity (keystone):
  New
Status in OpenStack Compute (nova):
  New
Status in python-cinderclient:
  New
Status in Rally:
  New

Bug description:
  In PY3,

  Remove the print "", join the print () function to achieve the same
  function.

  Python 3:

  #!/usr/bin/python
  # -*- coding: utf-8 -*-
  print ("cinder")

  print "cinder"

  
File "code", line 5
  print "cinder"
   ^
  SyntaxError: Missing parentheses in call to 'print'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1595773/+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 1595773] Re: Make print py3 compatible

[jingtao liang]

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

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

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

Title:
  Make print py3 compatible

Status in Cinder:
  New
Status in Glance:
  Invalid
Status in glance_store:
  New
Status in OpenStack Identity (keystone):
  New
Status in OpenStack Compute (nova):
  New
Status in python-cinderclient:
  New
Status in Rally:
  New

Bug description:
  In PY3,

  Remove the print "", join the print () function to achieve the same
  function.

  Python 3:

  #!/usr/bin/python
  # -*- coding: utf-8 -*-
  print ("cinder")

  print "cinder"

  
File "code", line 5
  print "cinder"
   ^
  SyntaxError: Missing parentheses in call to 'print'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1595773/+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 1595773] Re: Make print py3 compatible

[Ji.Wei]

** Also affects: rally
   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/1595773

Title:
  Make print py3 compatible

Status in Cinder:
  New
Status in Glance:
  Invalid
Status in glance_store:
  New
Status in OpenStack Identity (keystone):
  New
Status in OpenStack Compute (nova):
  New
Status in python-cinderclient:
  New
Status in Rally:
  New

Bug description:
  In PY3,

  Remove the print "", join the print () function to achieve the same
  function.

  Python 3:

  #!/usr/bin/python
  # -*- coding: utf-8 -*-
  print ("cinder")

  print "cinder"

  
File "code", line 5
  print "cinder"
   ^
  SyntaxError: Missing parentheses in call to 'print'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1595773/+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 1595773] [NEW] Make print py3 compatible

[Ji.Wei]

Public bug reported:

In PY3,

Remove the print "", join the print () function to achieve the same
function.

Python 3:

#!/usr/bin/python
# -*- coding: utf-8 -*-
print ("cinder")

print "cinder"


  File "code", line 5
print "cinder"
 ^
SyntaxError: Missing parentheses in call to 'print'

** Affects: cinder
 Importance: Undecided
 Assignee: Ji.Wei (jiwei)
 Status: New

** Affects: glance
 Importance: Undecided
 Assignee: YaoZheng_ZTE (zheng-yao1)
 Status: Invalid

** Affects: glance-store
 Importance: Undecided
 Assignee: YaoZheng_ZTE (zheng-yao1)
 Status: New

** Affects: keystone
 Importance: Undecided
 Status: New

** Affects: nova
 Importance: Undecided
 Status: New

** Affects: python-cinderclient
 Importance: Undecided
 Assignee: Ji.Wei (jiwei)
 Status: New

** Affects: rally
 Importance: Undecided
 Assignee: Ji.Wei (jiwei)
 Status: New

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

** Changed in: cinder
 Assignee: (unassigned) => Ji.Wei (jiwei)

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

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

** Also affects: python-cinderclient
   Importance: Undecided
   Status: New

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

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

** Changed in: nova
 Assignee: (unassigned) => Ji.Wei (jiwei)

** Changed in: python-cinderclient
 Assignee: (unassigned) => Ji.Wei (jiwei)

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

Title:
  Make print py3 compatible

Status in Cinder:
  New
Status in Glance:
  Invalid
Status in glance_store:
  New
Status in OpenStack Identity (keystone):
  New
Status in OpenStack Compute (nova):
  New
Status in python-cinderclient:
  New
Status in Rally:
  New

Bug description:
  In PY3,

  Remove the print "", join the print () function to achieve the same
  function.

  Python 3:

  #!/usr/bin/python
  # -*- coding: utf-8 -*-
  print ("cinder")

  print "cinder"

  
File "code", line 5
  print "cinder"
   ^
  SyntaxError: Missing parentheses in call to 'print'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1595773/+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 1595771] [NEW] neutronclient reports '400 Bad request' in large scale of networks and ports

[Yi Zhao]

Public bug reported:

neutron net-list reports '400 Bad request' in large scale of networks and ports.
The debug below shows that subnets request URL is really long. We manually 
changed the value of MAX_URI_LEN=8192 to MAX_URI_LEN=4096 (which is used for 
pagination in client.py) can solve the problem. I am not sure anyone 
encountered this problem.
Test is under Kilo version

# neutron net-list --debug
DEBUG: keystoneclient.session REQ: curl -g -i -X GET 
http://172.20.78.80:5000/v2.0/ -H "Accept: application/json" -H "User-Agent: 
python-keystoneclient"
DEBUG: keystoneclient.session RESP: [200] content-length: 338 vary: 
X-Auth-Token server: Apache/2.4.6 (CentOS) mod_wsgi/3.4 Python/2.7.5 date: Mon, 
30 May 2016 09:26:57 GMT content-type: application/json x-openstack-request-id: 
req-30c7b7bf-0109-47c6-b61d-16a159930a18 
RESP BODY: {"version": {"status": "stable", "updated": "2014-04-17T00:00:00Z", 
"media-types": [{"base": "application/json", "type": 
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links": 
[{"href": "http://172.20.78.80:5000/v2.0/;, "rel": "self"}, {"href": 
"http://docs.openstack.org/;, "type": "text/html", "rel": "describedby"}]}}

DEBUG: stevedore.extension found extension EntryPoint.parse('table = 
cliff.formatters.table:TableFormatter')
DEBUG: stevedore.extension found extension EntryPoint.parse('csv = 
cliff.formatters.commaseparated:CSVLister')
DEBUG: neutronclient.neutron.v2_0.network.ListNetwork 
get_data(Namespace(columns=[], fields=[], formatter='table', max_width=0, 
page_size=None, quote_mode='nonnumeric', request_format='json', 
show_details=False, sort_dir=[], sort_key=[]))
DEBUG: keystoneclient.auth.identity.v2 Making authentication request to 
http://172.20.78.80:5000/v2.0/tokens
DEBUG: keystoneclient.session REQ: curl -g -i -X GET 
http://BFJD-PSC-SDN-VN-VIP:9696/v2.0/networks.json -H "User-Agent: 
python-neutronclient" -H "Accept: application/json" -H "X-Auth-Token: 
{SHA1}774ff40f09dd0de5a62a399cd6067fd7486f1c20"
DEBUG: keystoneclient.session RESP: [200] date: Mon, 30 May 2016 09:26:58 GMT 
content-length: 35959 content-type: application/json; charset=UTF-8 
x-openstack-request-id: req-0ee25e63-5359-4849-861c-48394c29a976 
RESP BODY: {"networks": [{"status": "ACTIVE", "subnets": 
["1c245a8a-23bb-4d8c-ae02-71411c6b35a8"], "name": "s_rally_6f043ee9_W6zsIrgP", 
"provider:physical_network": null, "router:external": false, "tenant_id": 
"6df00e78c5f0422295b375666f7f48fc", "admin_state_up": true, "mtu": 0, "shared": 
false, "provider:network_type": "vxlan", "id": 
"02336d92-b0cd-4636-a013-c50a02e13500", "provider:segmentation_id": 68}, 
{"status": "ACTIVE", "subnets": ["0e372b86-a840-46b7-904c-8d9163cf4f0b", 
"ab3e7b5e-c4e5-418d-b079-ff3056930ae5", 
"e5a661d9-4a41-4012-82d0-d3bcfd837243"], "name": "rally_net_CmwCX5TDJLFdpT4U", 
"provider:physical_network": null, "router:external": false, "tenant_id": 
"ce29b73a8db84449b94e5c20c94e9e3d", "admin_state_up": true, "mtu": 0, "shared": 
false, "provider:network_type": "vxlan", "id": 
"0eb789b2-b75d-490c-8cc9-7b74ce1b0928", "provider:segmentation_id": 75}, 
{"status": "ACTIVE", "subnets": ["67791d07-1705-469c-b60a-60b4f063cc25"], 
"name": "s_rally_6f043ee9_NgIY4iT5", "provider:p
 hysical_network": null, "router:external": false, "tenant_id": 
"099f6f3bc36546fe988c76049193cbfd", "admin_state_up": true, "mtu": 0, "shared": 
false, "provider:network_type": "vxlan", "id": 
"1031e941-7f46-432c-92b6-eeab03194b9b", "provider:segmentation_id": 116}, 
{"status": "ACTIVE", "subnets": ["2e98f4de-2308-469a-88a9-8531c8282c15"], 
"name": "s_rally_6f043ee9_t19OFYlD", "provider:physical_network": null, 
"router:external": false, "tenant_id": "331e0974b4dc4d94ad5862e3bcba24d3", 
"admin_state_up": true, "mtu": 0, "shared": false, "provider:network_type": 
"vxlan", "id": "172e69de-18b5-44c6-abe7-b6e6916962a6", 
"provider:segmentation_id": 78}, {"status": "ACTIVE", "subnets": 
["3d2709f9-bbae-4e56-a1d0-b15d9445a201"], "name": "s_rally_6f043ee9_KsxaeeAt", 
"provider:physical_network": null, "router:external": false, "tenant_id": 
"b6a7eba9eb9641dcab81a43b34621765", "admin_state_up": true, "mtu": 0, "shared": 
false, "provider:network_type": "vxlan", "id": 
"18ef69db-451e-46f9-a26e-e8c2131a7ba
 2", "provider:segmentation_id": 70}, {"status": "ACTIVE", "subnets": 
["6ea2be5c-927a-46c3-aa63-fd2bf78bf157"], "name": "s_rally_6f043ee9_dSlWisrG", 
"provider:physical_network": null, "router:external": false, "tenant_id": 
"1a2263c1fb6b4a5384b1d8235a56e801", "admin_state_up": true, "mtu": 0, "shared": 
false, "provider:network_type": "vxlan", "id": 
"1f277db4-96e3-4248-9a27-6fe97e628cc5", "provider:segmentation_id": 141}, 
{"status": "ACTIVE", "subnets": ["deccb883-09c9-456e-810e-70df1a3eb75e"], 
"name": "s_rally_6f043ee9_terVIwjs", "provider:physical_network": null, 
"router:external": false, "tenant_id": "3d1b749ea3c44013afcff315749f2bc0", 
"admin_state_up": true, "mtu": 0, "shared": false, "provider:network_type": 
"vxlan", "id": 

[Yahoo-eng-team] [Bug 1595768] [NEW] Executing 'neutron purge TENANT' command，the result returned doesn't contain the subnet resource.

[xiewj]

Public bug reported:

In Mitaka,

Creating network resources as follows，it contains：
Networks
Subnets
Ports
Router Interfaces
Routers
Floating IPs
Security Groups
Executing 'neutron purge TENANT' command，the result returned doesn't contain 
subnet resource.

[root@localhost devstack]# neutron net-list
neutron subnet-list
neutron port-list
neutron router-list
neutron router-port-list
neutron floatingip-list
+--+-++
| id   | name| subnets  
  |
+--+-++
| d34befc5-2d78-493a-b4b0-ee771eea153a | big_net | 
d6c59ba1-bce1-4223-9ddf-576cc1a48df6 10.10.10.0/24 |
| 45f7255d-1559-47a8-ba94-714be5598243 | net_xwj | 
5c3f4fb5-a0ae-437c-9f11-9c2e8cd4d1ed 102.1.1.0/24  |
|  | | 
0d400302-da37-40a2-a7a6-f9ba3134a6fa 101.1.1.0/24  |
+--+-++
[root@localhost devstack]# neutron subnet-list
+--++---++
| id   | name   | cidr  | 
allocation_pools   |
+--++---++
| d6c59ba1-bce1-4223-9ddf-576cc1a48df6 | big_subnet | 10.10.10.0/24 | {"start": 
"10.10.10.2", "end": "10.10.10.254"} |
| 5c3f4fb5-a0ae-437c-9f11-9c2e8cd4d1ed | subnet_xwj | 102.1.1.0/24  | {"start": 
"102.1.1.2", "end": "102.1.1.254"}   |
| 0d400302-da37-40a2-a7a6-f9ba3134a6fa | subnet_xwj | 101.1.1.0/24  | {"start": 
"101.1.1.2", "end": "101.1.1.254"}   |
+--++---++
[root@localhost devstack]# neutron port-list
+--+--+---+---+
| id   | name | mac_address   | fixed_ips   
  |
+--+--+---+---+
| 0291537e-d912-47cc-a3ee-4c677cebd61f |  | fa:16:3e:e4:51:6e | 
{"subnet_id": "0d400302-da37-40a2-a7a6-f9ba3134a6fa", |
|  |  |   | 
"ip_address": "101.1.1.2"}|
|  |  |   | 
{"subnet_id": "5c3f4fb5-a0ae-437c-9f11-9c2e8cd4d1ed", |
|  |  |   | 
"ip_address": "102.1.1.2"}|
| 092cf37c-409d-4ab0-9be2-da30113a6235 |  | fa:16:3e:9e:81:5d | 
{"subnet_id": "d6c59ba1-bce1-4223-9ddf-576cc1a48df6", |
|  |  |   | 
"ip_address": "10.10.10.3"}   |
| 83c4fad1-6875-4dca-8695-d0e80dd3cdb7 |  | fa:16:3e:2d:8d:6a | 
{"subnet_id": "d6c59ba1-bce1-4223-9ddf-576cc1a48df6", |
|  |  |   | 
"ip_address": "10.10.10.2"}   |
| a7ad23cf-d7df-47b5-9839-b1ace0641090 |  | fa:16:3e:94:f2:60 | 
{"subnet_id": "d6c59ba1-bce1-4223-9ddf-576cc1a48df6", |
|  |  |   | 
"ip_address": "10.10.10.4"}   |
| d0041621-b8dc-4b2c-9455-eb37f3f26b08 |  | fa:16:3e:7e:72:e5 | 
{"subnet_id": "d6c59ba1-bce1-4223-9ddf-576cc1a48df6", |
|  |  |   | 
"ip_address": "10.10.10.9"}   |
+--+--+---+---+
[root@localhost devstack]# neutron router-list
+--+-+---+-+---+
| id   | name| external_gateway_info
 | distributed | ha|
+--+-+---+-+---+
| f47136b0-6c84-4037-aeb9-95a3cead76a4 | router-list | {"network_id": 
"d34befc5-2d78-493a-   | False   | False |
|  | | b4b0-ee771eea153a", 
"enable_snat": true,  | |   |
|  | | "external_fixed_ips": 
[{"subnet_id":  | 

[Yahoo-eng-team] [Bug 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong

[jingtao liang]

** Also affects: swift-swf
   Importance: Undecided
   Status: New

** Changed in: swift-swf
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

Title:
  Some tests use assertEqual(observed, expected) , the argument order is
  wrong

Status in Astara:
  In Progress
Status in Barbican:
  In Progress
Status in Blazar:
  New
Status in Ceilometer:
  Invalid
Status in Cinder:
  Fix Released
Status in congress:
  Fix Released
Status in Designate:
  Fix Released
Status in Freezer:
  In Progress
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Murano:
  Fix Released
Status in OpenStack Compute (nova):
  Won't Fix
Status in os-brick:
  In Progress
Status in python-ceilometerclient:
  Invalid
Status in python-cinderclient:
  Fix Released
Status in python-designateclient:
  Fix Committed
Status in python-glanceclient:
  In Progress
Status in python-mistralclient:
  Fix Released
Status in python-solumclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in Sahara:
  Fix Released
Status in sqlalchemy-migrate:
  New
Status in SWIFT:
  New
Status in tacker:
  New
Status in tempest:
  New
Status in zaqar:
  Fix Released

Bug description:
  The test cases will produce a confusing error message if the tests
  ever fail, so this is worth fixing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/astara/+bug/1259292/+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 1595762] [NEW] HTTPS connection failing for Docker >= 1.10

[Michael Stieler]

Public bug reported:

We experience problems with outgoing HTTPS connections from inside
Docker containers when running in OpenStack.

- Ubuntu 14, 16 and CoreOS show the same problems
- While there are no problems with Docker 1.6.2 and 1.9.1, 1.10 and 1.11 
versions are broken
- The same containers work outside OpenStack 

This is why we assume that the bug must be related to OpenStack.

The bug can easily be reproduced with:

docker run -it ubuntu apt-get update

Expected output: Ubuntu updates its package list
Actual output: Nothing is downloaded, package sources are skipped after a 
timeout.

The same problem seems to occur with wget and curl and our Java
application.

Please note that plain HTTP works as expected, also issuing the Https
requests from the host machine.

Disabling network virtualization with Docker flag --net="host" fixes the
problems with wget, curl and apt-get, unfortunately not with the Java
app we're trying to deploy in OpenStack.

For our current project this is actually a blocker since CoreOS comes
bundles with a recent Docker version which is not so easy to downgrade.

I can't see any version information in the Horizon interface of our
provider, however I think I heard they are using Mitaka release.

Links:
- Related issue at Docker: https://github.com/docker/docker/issues/20178
- ServerFault question by me: 
http://serverfault.com/questions/785768/https-request-fails-in-docker-1-10-with-virtualized-network
- StackOverflow question by someone else: 
http://stackoverflow.com/questions/35300497/docker-container-not-connecting-to-https-endpoints

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

Title:
  HTTPS connection failing for Docker >= 1.10

Status in neutron:
  New

Bug description:
  We experience problems with outgoing HTTPS connections from inside
  Docker containers when running in OpenStack.

  - Ubuntu 14, 16 and CoreOS show the same problems
  - While there are no problems with Docker 1.6.2 and 1.9.1, 1.10 and 1.11 
versions are broken
  - The same containers work outside OpenStack 

  This is why we assume that the bug must be related to OpenStack.

  The bug can easily be reproduced with:

  docker run -it ubuntu apt-get update

  Expected output: Ubuntu updates its package list
  Actual output: Nothing is downloaded, package sources are skipped after a 
timeout.

  The same problem seems to occur with wget and curl and our Java
  application.

  Please note that plain HTTP works as expected, also issuing the Https
  requests from the host machine.

  Disabling network virtualization with Docker flag --net="host" fixes
  the problems with wget, curl and apt-get, unfortunately not with the
  Java app we're trying to deploy in OpenStack.

  For our current project this is actually a blocker since CoreOS comes
  bundles with a recent Docker version which is not so easy to
  downgrade.

  I can't see any version information in the Horizon interface of our
  provider, however I think I heard they are using Mitaka release.

  Links:
  - Related issue at Docker: https://github.com/docker/docker/issues/20178
  - ServerFault question by me: 
http://serverfault.com/questions/785768/https-request-fails-in-docker-1-10-with-virtualized-network
  - StackOverflow question by someone else: 
http://stackoverflow.com/questions/35300497/docker-container-not-connecting-to-https-endpoints

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1595762/+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 1585209] Re: In integration tests table-level deletion is used in an inefficient way

[OpenStack Infra]

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

commit b450a03282665aa8da4190d47421aecbfc9afb59
Author: jlopezgu 
Date:   Fri May 27 12:11:43 2016 -0500

Improved table deletion efficiency

Volumes and instances integration tests deleted and validated entities
one row at a time, now they are able to delete and validate multiple
rows at a time.

Change-Id: I7f8fdc7e0ccefdd0f6d71f9f92c8a2aefeec8d54
Closes-bug: #1585209


** Changed in: horizon
   Status: Fix Committed => 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/1585209

Title:
  In integration tests table-level deletion is used in an inefficient
  way

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  First, even when one entity is deleted from a table, first it is
  marked then 'Delete ' table-level button is clicked, while
  row-level action could be used for that, omitting 'click checkbox'
  phase.

  Second, when multiple entities are deleted, they are still deleted by
  one (using table-level delete), while it would be faster to first
  select all entities, then click 'Delete ' one time and wait
  until each of them is deleted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1585209/+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 1595754] [NEW] Magic Search shouldn't hardcode width

[Diana Whitten]

Public bug reported:

Recent fixed have caused much oddity around magic search in Swift.  The
layout is now broken and shifts to two line even on a single input.

** Affects: horizon
 Importance: Medium
 Assignee: Diana Whitten (hurgleburgler)
 Status: In Progress


** Tags: branding

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

Title:
  Magic Search shouldn't hardcode width

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  Recent fixed have caused much oddity around magic search in Swift.
  The layout is now broken and shifts to two line even on a single
  input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1595754/+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 1594711] Re: Remove the deprecated config "router_id"

[OpenStack Infra]

Reviewed:  https://review.openstack.org/332018
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=448bc8e5220d3633f9c9ee804de0a38c2d829d78
Submitter: Jenkins
Branch:master

commit 448bc8e5220d3633f9c9ee804de0a38c2d829d78
Author: Hong Hui Xiao 
Date:   Tue Jun 21 08:49:42 2016 +

Remove the deprecated config 'router_id'

It was deprecated at [1].
Remove the deprecated config 'router_id' and its related tests.

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

DocImpact: All references of 'router_id' configuration option
and its description should be removed from the docs.

UpgradeImpact: Remove 'router_id' configuration option from the
l3_agent.ini.

Change-Id: Ic9420191e8c1a333e4dcc0b70411591b8573ec7c
Closes-Bug: #1594711


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

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

Title:
  Remove the deprecated config "router_id"

Status in neutron:
  Fix Released

Bug description:
  This option is deprecated at https://review.openstack.org/#/c/248498/
  at M release and can be removed in N release now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1594711/+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 1595706] [NEW] Remove the deprecated config 'router_id'

[OpenStack Infra]

Public bug reported:

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

commit 448bc8e5220d3633f9c9ee804de0a38c2d829d78
Author: Hong Hui Xiao 
Date:   Tue Jun 21 08:49:42 2016 +

Remove the deprecated config 'router_id'

It was deprecated at [1].
Remove the deprecated config 'router_id' and its related tests.

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

DocImpact: All references of 'router_id' configuration option
and its description should be removed from the docs.

UpgradeImpact: Remove 'router_id' configuration option from the
l3_agent.ini.

Change-Id: Ic9420191e8c1a333e4dcc0b70411591b8573ec7c
Closes-Bug: #1594711

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: doc 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/1595706

Title:
  Remove the deprecated config 'router_id'

Status in neutron:
  New

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

  commit 448bc8e5220d3633f9c9ee804de0a38c2d829d78
  Author: Hong Hui Xiao 
  Date:   Tue Jun 21 08:49:42 2016 +

  Remove the deprecated config 'router_id'
  
  It was deprecated at [1].
  Remove the deprecated config 'router_id' and its related tests.
  
  [1] https://review.openstack.org/#/c/248498
  
  DocImpact: All references of 'router_id' configuration option
  and its description should be removed from the docs.
  
  UpgradeImpact: Remove 'router_id' configuration option from the
  l3_agent.ini.
  
  Change-Id: Ic9420191e8c1a333e4dcc0b70411591b8573ec7c
  Closes-Bug: #1594711

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1595706/+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 1574113] Re: curtin/maas don't support multiple (derived) archives/repositories with custom keys

[Scott Moser]

Hello,
An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been 
made under bug 1595302.  Please track that bug if you are interested.

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => In Progress

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

** Changed in: cloud-init (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

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

Title:
  curtin/maas don't support multiple (derived) archives/repositories
  with custom keys

Status in cloud-init:
  Fix Committed
Status in curtin:
  Confirmed
Status in MAAS:
  Triaged
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress

Bug description:
  In a customer environment I have to deploy using offline resources (no
  internet connection at all), so I created apt mirror and MAAS images
  mirror. I configured MAAS  to use the local  mirrors and I'm able to
  commission the nodes but I'm not able to deploy the nodes because
  there is no way to add gpg key of the local repo in target before the
  'late' stage'.

  Using curtin I'm able to add the key but too late, in fact  according
  with http://bazaar.launchpad.net/~curtin-
  dev/curtin/trunk/view/head:/curtin/commands/install.py#L52 "late"
  stage is executed  after "curthooks" this prevent to add the key.

  I checked also apt_config function in curthooks.py  I did't see code
  that add the key for each mirror.

  It should be possible to add gpg public of the repository in maas.

  --
  configs/config-000.cfg
  --

  #cloud-config
  debconf_selections:
   maas: |
    cloud-init   cloud-init/datasources  multiselect MAAS
    cloud-init   cloud-init/maas-metadata-url  string 
http://100.107.231.164/MAAS/metadata/
    cloud-init   cloud-init/maas-metadata-credentials  string 
oauth_token_key=8eZmzQWSSQzsUkaLnE_token_secret=LKmn8sHgzEXfvzSZePAa9jUXvTMRrFNP_consumer_key=htwDZJFtmv2YvQXhUW
    cloud-init   cloud-init/local-cloud-config  string 
apt_preserve_sources_list: true\nmanage_etc_hosts: false\nmanual_cache_clean: 
true\nreporting:\n  maas: {consumer_key: htwDZJFtmv2YvQXhUW, endpoint: 
'http://100.107.231.164/MAAS/metadata/status/node-61b6987c-07a7-11e6-9d23-5254003d2515',\n
token_key: 8eZmzQWSSQzsUkaLnE, token_secret: 
LKmn8sHgzEXfvzSZePAa9jUXvTMRrFNP,\ntype: webhook}\nsystem_info:\n  
package_mirrors:\n  - arches: [i386, amd64]\nfailsafe: {primary: 
'http://archive.ubuntu.com/ubuntu', security: 
'http://security.ubuntu.com/ubuntu'}\nsearch:\n  primary: 
['http://100.107.231.166/']\n  security: ['http://100.107.231.166/']\n  - 
arches: [default]\nfailsafe: {primary: 
'http://ports.ubuntu.com/ubuntu-ports', security: 
'http://ports.ubuntu.com/ubuntu-ports'}\nsearch:\n  primary: 
['http://ports.ubuntu.com/ubuntu-ports']\n  security: 
['http://ports.ubuntu.com/ubuntu-ports']\n
  late_commands:
    maas: [wget, '--no-proxy', 
'http://100.107.231.164/MAAS/metadata/latest/by-id/node-61b6987c-07a7-11e6-9d23-5254003d2515/',
 '--post-data', 'op=netboot_off', '-O', '/dev/null']
apt_key: ["curtin", "in-target", "--", "sh", "-c", "/usr/bin/wget 
--no-proxy -qO - http://100.107.231.166/magellan.key | apt-key add -"]
  power_state:
    mode: reboot
  apt_mirrors:
    ubuntu_archive: http://100.107.231.166//
    ubuntu_security: http://100.107.231.166//

  - curtin end of log --
  Leaving 'diversion of /etc/init/ureadahead.conf to 
/etc/init/ureadahead.conf.disabled by cloud-init'
  Setting up swapspace version 1, size = 8388604 KiB
  no label, UUID=e2fe91bc-91e9-4e43-b50f-209dfcf04089
  Get:1 http://100.107.231.166 trusty InRelease [17.7 kB]
  Get:2 http://100.107.231.166 trusty-updates InRelease [17.7 kB]
  Get:3 http://100.107.231.166 trusty-security InRelease [17.7 kB]
  Ign http://100.107.231.166 trusty InRelease
  Get:4 http://100.107.231.166 trusty/main amd64 Packages [412 kB]
  Ign http://100.107.231.166 trusty-updates InRelease
  Ign http://100.107.231.166 trusty-security InRelease
  Get:5 http://100.107.231.166 trusty/restricted amd64 Packages [20 B]
  Get:6 http://100.107.231.166 trusty/universe amd64 Packages [20 B]
  Get:7 http://100.107.231.166 trusty/multiverse amd64 Packages [20 B]
  Get:8 http://100.107.231.166 trusty-updates/main amd64 Packages [33.0 kB]
  Get:9 http://100.107.231.166 trusty-updates/restricted amd64 Packages [20 B]
  Get:10 http://100.107.231.166 trusty-updates/universe amd64 Packages [20 B]
  Get:11 http://100.107.231.166 trusty-updates/multiverse amd64 Packages [20 B]
  Get:12 http://100.107.231.166 trusty-security/main amd64 Packages [6,578 B]
  Get:13 http://100.107.231.166 

[Yahoo-eng-team] [Bug 1575938] Re: Instance path in / if instance-id starts with '/'

[Scott Moser]

Hello,
An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been 
made under bug 1595302.  Please track that bug if you are interested.

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: cloud-init (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

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

Title:
  Instance path in / if instance-id starts with '/'

Status in cloud-init:
  In Progress
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress

Bug description:
  A cloud using the Ec2 datasource has an instance-id metadata value in
  the form:

  /Compute-$TENANT/$CLOUDUSERNAME/$UUID

  The leading '/' causes /var/lib/cloud/instance to link to
  /Compute-$TENANT/$CLOUDUSERNAME/$UUID rather than
  /var/lib/cloud/instances/Compute-$TENANT/$CLOUDUSERNAME/$UUID

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1575938/+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 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

[Scott Moser]

Hello,
An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been 
made under bug 1595302.  Please track that bug if you are interested.

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: cloud-init (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

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

Title:
  Commissioning fails when competing cloud metadata resides on disk

Status in cloud-init:
  Fix Committed
Status in MAAS:
  Triaged
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress

Bug description:
  A customer reused hardware that had previously deployed a RHEL
  Overcloud-controller which places metadata on the disk as a legitimate
  source, that cloud-init looks at by default.  When the newly enlisted
  node appeared it had the name of "overcloud-controller-0" vs. maas-
  enlist, pulled from the disk metadata which had overridden MAAS'
  metadata.  Commissioning continually failed on all of the nodes until
  the disk metadata was manually removed (KVM boot Ubuntu ISO, rm -f
  data or dd zeros to disk).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1582323/+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 1493576] Re: Incorrect usage of python-novaclient

[OpenStack Infra]

Reviewed:  https://review.openstack.org/332420
Committed: 
https://git.openstack.org/cgit/openstack/congress/commit/?id=57411fec5e44c720381d95e1f7c5f83ebf7a5b0d
Submitter: Jenkins
Branch:master

commit 57411fec5e44c720381d95e1f7c5f83ebf7a5b0d
Author: Andrey Kurilin 
Date:   Tue Jun 21 21:27:28 2016 +0300

Fix wrong usage of novaclient

novaclient.client.Client is a documented way to initialize novaclient.
Also, it provides a backward compatible layer.

Change-Id: I9dd15abbeda26c5a6a40139ce47a200720decce8
Closes-Bug: #1493576


** Changed in: congress
   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/1493576

Title:
  Incorrect usage of python-novaclient

Status in Cinder:
  Fix Released
Status in congress:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in networking-cisco:
  Fix Released
Status in os-cloud-config:
  In Progress
Status in OpenStack DBaaS (Trove):
  Fix Released

Bug description:
  All projects should use only `novaclient.client` as entry point. It designed 
with some version checks and backward compatibility.
  Direct import of versioned client object(i.e. novaclient.v2.client) is a way 
to "shoot yourself in the foot".

  Python-novaclient's doc: http://docs.openstack.org/developer/python-
  novaclient/api.html

  Affected projects:
   - Horizon - 
https://github.com/openstack/horizon/blob/69d6d50ef4a26e2629643ed35ebd661e82e10586/openstack_dashboard/api/nova.py#L31

   - Manila -
  
https://github.com/openstack/manila/blob/473b46f6edc511deaba88b48392b62bfbb979787/manila/compute/nova.py#L23

   - Cinder-
  
https://github.com/openstack/cinder/blob/de64f5ad716676b7180365798efc3ea69a4fef0e/cinder/compute/nova.py#L23

   - Mistral - 
https://github.com/openstack/mistral/blob/f42b7f5f5e4bcbce8db7e7340b4cac12de3eec4d/mistral/actions/openstack/actions.py#L23
   
   - Congress - 
https://github.com/openstack/congress/blob/88f4a87f4899fc29e9dde6482ceb2a0e42896ece/contrib/nova/congress.py#L92

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1493576/+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 1595662] [NEW] auth_url in api/nova.py should be keystone url not nova url

[Daniel Castellanos]

Public bug reported:

In
https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/nova.py#L477,
the auth_url value should be the keystone url not nova url

** Affects: horizon
 Importance: Undecided
 Assignee: Daniel Castellanos (luis-daniel-castellanos)
 Status: In Progress


** Tags: low-hanging-fruit

** Changed in: horizon
 Assignee: (unassigned) => Daniel Castellanos (luis-daniel-castellanos)

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

Title:
  auth_url in api/nova.py should be keystone url not nova url

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  In
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/nova.py#L477,
  the auth_url value should be the keystone url not nova url

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1595662/+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 1593565] Re: test_cisco_fwaas_plugin failure

[OpenStack Infra]

Reviewed:  https://review.openstack.org/330909
Committed: 
https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=b1b2b2af1c1c14eb86681c8e88455729af380c00
Submitter: Jenkins
Branch:master

commit b1b2b2af1c1c14eb86681c8e88455729af380c00
Author: YAMAMOTO Takashi 
Date:   Fri Jun 17 15:50:27 2016 +0900

Fix a few test cases in test_cisco_fwaas_plugin

Update them after the recent neutron change. [1]

[1] I1415c7a29af86d377ed31cce40888631a34d4811

Closes-Bug: #1593565
Change-Id: I4847fd512e78b41cfce9c0e043324a40dd01f42a


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

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

Title:
  test_cisco_fwaas_plugin failure

Status in neutron:
  Fix Released

Bug description:
  some of cisco unit tests, namely test_update_csr_firewall and 
test_update_csr_firewall_port_id,
  are failing with "KeyError: 'firewall'".

  http://logs.openstack.org/65/330865/1/check/gate-neutron-fwaas-
  python27/eac8202/testr_results.html.gz

  ft20.3: 
neutron_fwaas.tests.unit.services.firewall.plugins.cisco.test_cisco_fwaas_plugin.TestCiscoFirewallPlugin.test_update_csr_firewall_StringException:
 Empty attachments:
stdout

  pythonlogging:'': {{{
  WARNING [neutron.api.extensions] Extension address-scope not supported by any 
of loaded plugins
   WARNING [neutron.api.extensions] Extension agent not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension allowed-address-pairs not 
supported by any of loaded plugins
   WARNING [neutron.api.extensions] Extension auto-allocated-topology not 
supported by any of loaded plugins
   WARNING [neutron.api.extensions] Extension availability_zone not supported 
by any of loaded plugins
   WARNING [neutron.api.extensions] Extension default-subnetpools not supported 
by any of loaded plugins
   WARNING [neutron.api.extensions] Extension dhcp_agent_scheduler not 
supported by any of loaded plugins
   WARNING [neutron.api.extensions] Extension dvr not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension extra_dhcp_opt not supported by 
any of loaded plugins
   WARNING [neutron.api.extensions] Extension extraroute not supported by any 
of loaded plugins
   WARNING [neutron.api.extensions] Extension flavors not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension ext-gw-mode not supported by any 
of loaded plugins
   WARNING [neutron.api.extensions] Extension l3-ha not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension l3_agent_scheduler not supported 
by any of loaded plugins
   WARNING [neutron.api.extensions] Extension metering not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension multi-provider not supported by 
any of loaded plugins
   WARNING [neutron.api.extensions] Extension net-mtu not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension network_availability_zone not 
supported by any of loaded plugins
   WARNING [neutron.api.extensions] Extension network-ip-availability not 
supported by any of loaded plugins
   WARNING [neutron.api.extensions] Extension binding not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension port-security not supported by 
any of loaded plugins
   WARNING [neutron.api.extensions] Extension provider not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension qos not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension quotas not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension router_availability_zone not 
supported by any of loaded plugins
   WARNING [neutron.api.extensions] Extension router-service-type not supported 
by any of loaded plugins
   WARNING [neutron.api.extensions] Extension security-group not supported by 
any of loaded plugins
   WARNING [neutron.api.extensions] Extension segment not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension service-type not supported by any 
of loaded plugins
   WARNING [neutron.api.extensions] Extension subnet_allocation not supported 
by any of loaded plugins
   WARNING [neutron.api.extensions] Extension tag not supported by any of 
loaded plugins
   WARNING [neutron.api.extensions] Extension timestamp_core not supported by 
any of loaded plugins
   WARNING [neutron.api.extensions] Extension vlan-transparent not supported by 
any of loaded plugins
   WARNING [neutron.quota.resource_registry] subnetpool is already registered
   WARNING [neutron.quota.resource_registry] subnet is already registered
   WARNING [neutron.quota.resource_registry] port is already registered
   WARNING [neutron.quota.resource_registry] network is already registered
   WARNING 

[Yahoo-eng-team] [Bug 1515768] Re: Instance creation fails with libvirtError: Unable to create tap device: Device or resource busy

[Corey Bryant]

Also marking this as fix-released for Ubuntu since it is available in
nova 13.0.0+.

** Changed in: nova (Ubuntu)
   Status: Confirmed => Fix Released

** Also affects: nova (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: nova (Ubuntu Xenial)
   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/1515768

Title:
  Instance creation fails with libvirtError: Unable to create tap
  device: Device or resource busy

Status in OpenStack Compute (nova):
  Fix Released
Status in tacker:
  Fix Committed
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Fix Released

Bug description:
  Summary:
  This issue is observed frequently on Jenkins gate and has been reproducible 
in local setup too.

  Steps:
  Initiate 3 stack create requests at once in a script:

  heat stack-create -f /home/stack/template_file stack1
  heat stack-create -f /home/stack/template_file stack2
  heat stack-create -f /home/stack/template_file stack3

  using the following HOT file:
  http://paste.openstack.org/show/479920/

  
  One of the stack creations fails with CreateFailed: Resource Create Failed: 
Conflict: Resources. vdu3: Port Is Still In Use.

  From the nova logs, there are duplicate bridges created for one of the
  servers. The qemu xml fails with libvirtError: Unable to create tap
  device tapd3a3d9e9-5d: Device or resource busy. See timestamp
  2015-11-25 23:03:14.940 in n-cpu.log

  Attaching the relevant n-cpu.log, q-svc.log and h-eng.log

  Observation:
  The 1st network interface for the nova instance is a Neutron Port resource 
provided in HOT template.
  Nova sends a PUT request to update the port information. It also sends 2 POST 
requests for the 2nd and 3rd network interfaces.
  Neutron receives the PUT request and sends network-event changed event while 
nova is still waiting for the POST response for the 2 ports.
  If the network-changed event is received before the 3rd port POST response is 
received, refresh_cache is acquired by nova_service
  Nova sends a query for port information, updates the cache and release the 
lock.
  By then, POST requests are completed which acquires the cache lock again and 
sends request for network info. refresh_cache is updated twice and contains 
duplicate set of ports
  Network vifs are built for all 6 ports and qemu xml is build based on that.
  Duplicate bridges in xml is complained by libvirt as device or resource busy.

  Version and environment:
  Devstack Master

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1515768/+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 1493576] Re: Incorrect usage of python-novaclient

[OpenStack Infra]

Reviewed:  https://review.openstack.org/332423
Committed: 
https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=4028533aeda842be6576895e7cc8b48f91137aea
Submitter: Jenkins
Branch:master

commit 4028533aeda842be6576895e7cc8b48f91137aea
Author: Andrey Kurilin 
Date:   Tue Jun 21 21:38:59 2016 +0300

Fix wrong usage of novaclient

novaclient.client.Client is a documented way to initialize novaclient.
Also, it provides a backward compatible layer.

Change-Id: I4f95356835e043fdaeb5f4f5c96139c54eaa32b3
Closes-Bug: #1493576


** Changed in: networking-cisco
   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/1493576

Title:
  Incorrect usage of python-novaclient

Status in Cinder:
  Fix Released
Status in congress:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in networking-cisco:
  Fix Released
Status in os-cloud-config:
  In Progress
Status in OpenStack DBaaS (Trove):
  Fix Released

Bug description:
  All projects should use only `novaclient.client` as entry point. It designed 
with some version checks and backward compatibility.
  Direct import of versioned client object(i.e. novaclient.v2.client) is a way 
to "shoot yourself in the foot".

  Python-novaclient's doc: http://docs.openstack.org/developer/python-
  novaclient/api.html

  Affected projects:
   - Horizon - 
https://github.com/openstack/horizon/blob/69d6d50ef4a26e2629643ed35ebd661e82e10586/openstack_dashboard/api/nova.py#L31

   - Manila -
  
https://github.com/openstack/manila/blob/473b46f6edc511deaba88b48392b62bfbb979787/manila/compute/nova.py#L23

   - Cinder-
  
https://github.com/openstack/cinder/blob/de64f5ad716676b7180365798efc3ea69a4fef0e/cinder/compute/nova.py#L23

   - Mistral - 
https://github.com/openstack/mistral/blob/f42b7f5f5e4bcbce8db7e7340b4cac12de3eec4d/mistral/actions/openstack/actions.py#L23
   
   - Congress - 
https://github.com/openstack/congress/blob/88f4a87f4899fc29e9dde6482ceb2a0e42896ece/contrib/nova/congress.py#L92

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1493576/+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 1584076] Re: Swift acl which disappears on Glance images

[OpenStack Infra]

Reviewed:  https://review.openstack.org/320588
Committed: 
https://git.openstack.org/cgit/openstack/glance/commit/?id=d719b3a1646167e750b9920128d57a7bca331d80
Submitter: Jenkins
Branch:master

commit d719b3a1646167e750b9920128d57a7bca331d80
Author: Nolwenn Cauchois 
Date:   Tue May 24 17:01:03 2016 +0200

Fix bug Swift ACL which disappears on Glance v1 images

Currently, when we make an update on a public image, Swift ACL disappears.
This patch allows to avoid the ACL update if there is no change to the
is_public_attribute.
If an update is made on a Glance image without changing the public attribute
or location, then the function which modifies ACLS is not called, in order
to keep ACLS.

Closes-Bug: 1584076

Change-Id: I21e9deb9105faee87500998eff47c6faa1d02914


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

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

Title:
  Swift acl which disappears on Glance images

Status in Glance:
  Fix Released

Bug description:
  The public images stored in swift have the rights which disappears when we 
make a "glance image-update".
  Consequence : Glance can't fetch the image and the instancation of VM fails 
with this image.
  This bug is only present on the Glance v1 api and it was tested with a juno 
and mitaka environment.

  Here how to reproduce:
  http://paste.openstack.org/show/497986/

  The problem here is :
  - After the modification on the image, acls in reading disappeared ( "Read 
ACL: ")
  - Expected result is "Read ACL: *:*"

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1584076/+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 1590316] Re: exception handling of callback failures doesn't take into account retriable errors

[OpenStack Infra]

Reviewed:  https://review.openstack.org/326928
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=143b19c8d5e6805c4ce0abe78748c0add42a2072
Submitter: Jenkins
Branch:master

commit 143b19c8d5e6805c4ce0abe78748c0add42a2072
Author: Kevin Benton 
Date:   Tue Jun 7 15:27:48 2016 -0700

Separate exception class for retriables in callbacks

There are various places where we emit a callback to allow
subscribers to do validation or additional bookkeeping during
the various life-cycle events of objects. However, a subscriber
can encounter a DB Deadlock, StaleDataError or other retriable
error that just needs the transaction to be restarted. In the
rest of the Neutron code these exceptions bubble up to the API
layer where the whole request is restarted. However, the exception
catching for the callbacks in various places was preventing these
errors from being retried because they were lost in conversion.

This patch has the callback manager convert retriable exceptions
into RetryRequest exceptions that will not be caught by handlers
of CallbackError so by default it will bubble up to the API layer
and be retried. 'notify' callers can avoid this behavior by
additionally catching RetryRequest.

Closes-Bug: #1590316
Change-Id: I6732c60f89de4318b5f56327c5bc966bd250baae


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

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

Title:
  exception handling of callback failures doesn't take into account
  retriable errors

Status in neutron:
  Fix Released

Bug description:
  Subscribers to callback events can perform DB operations that may
  encounter deadlocks or other DB errors that should be retried after
  restarting the entire transaction. However, in the cases where we
  catch exceptions.CallbackFailure and then raise a different exception,
  the DB retry wrapper cannot recognize that it is retriable failure and
  will make it fatal for the request. This can lead to a user getting a
  SubnetInUse or something similar because of something completely
  unrelated to the actual validation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1590316/+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 1594419] Re: lbaas loadbalancers statuses command failed on stable/liberty release

[Corey Bryant]

Alex, Thanks for submitting this bug.  It looks like this bug should be
targeted at upstream neutron-lbaas for stable/liberty so I'm going to do
that.

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

Title:
  lbaas loadbalancers statuses command  failed on stable/liberty release

Status in neutron:
  New
Status in neutron-lbaas package in Ubuntu:
  New

Bug description:
  /lbaas/loadbalancers//statuses used to retrieve load-balancer
  and its related resources in a dict. This RESTful API works at Kilo
  and Master, but not stable/liberty.

  lbaasv2 driver in my devstack configuration:
  enable_plugin neutron-lbaas https://git.openstack.org/openstack/neutron-lbaas 
stable/liberty
  
NEUTRON_LBAAS_SERVICE_PROVIDERV2=LOADBALANCERV2:Haproxy:neutron_lbaas.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default
  enable_service q-lbaasv2

  lbaas resource tree:
  load-balancer
-- listener1
-- pool1 -- health monitor (HTTP)
   -- member-1, it server has floating ip
   -- member-1, it server has floating ip

  Error message from the statuses API:

  URI: u'/lbaas/loadbalancers/2a0c262f-4ff8-44a2-bacf-
  9c01923be1b7/statuses’ causing “ServerFault: ServerFault()”

  q-svc log:

  2016-06-17 14:51:56.635 INFO neutron.wsgi 
[req-43338856-0889-4072-8aa0-f304b723dbad admin 
06b000ad46398f454b8803b28f45] 10.144.139.55 - - [17/Jun/2016 14:51:56] "GET 
/v2.0/lbaas/loadbalancers/2a0c262f-4ff8-44a2-bacf-9c01923be1b7 HTTP/1.1" 200 
666 0.093880
  2016-06-17 14:51:56.638 INFO neutron.wsgi [-] (23451) accepted 
('10.144.139.55', 51711)
  2016-06-17 14:51:56.734 ERROR neutron.api.v2.resource 
[req-f546f674-3c68-408e-bcdf-237e79d3f45e admin 
06b000ad46398f454b8803b28f45] statuses failed
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource Traceback (most recent 
call last):
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron/neutron/api/v2/resource.py", line 83, in resource
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource result = 
method(request=request, **args)
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 146, in wrapper
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource ectxt.value = 
e.inner_exc
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource 
six.reraise(self.type_, self.value, self.tb)
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 136, in wrapper
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource return f(*args, 
**kwargs)
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron/neutron/api/v2/base.py", line 217, in _handle_action
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource ret_value = 
getattr(self._plugin, name)(*arg_list, **kwargs)
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron-lbaas/neutron_lbaas/services/loadbalancer/plugin.py", line 
1035, in statuses
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource 
self._set_degraded(self, listener_status, lb_status)
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron-lbaas/neutron_lbaas/services/loadbalancer/plugin.py", line 
1068, in _set_degraded
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource 
obj["operating_status"] = lb_const.DEGRADED
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource TypeError: 
'LoadBalancerPluginv2' object does not support item assignment
  2016-06-17 14:51:56.734 TRACE neutron.api.v2.resource 

  
stack@htb-1n-eng-dhcp8:/opt/devtest/vmware-nsx-devel/vmware_nsx_tempest/tests/nsxv/api/lbaas$
 neutron lbaas-loadbalancer-show 2a0c262f-4ff8-44a2-bacf-9c01923be1b7
  +-++
  | Field   | Value  |
  +-++
  | admin_state_up  | True   |
  | description ||
  | id  | 2a0c262f-4ff8-44a2-bacf-9c01923be1b7   |
  | listeners   | {"id": "c435a653-91c1-4e66-84cb-92bf0a16d57c"} |
  | name||
  | operating_status| ONLINE |
  | provider| haproxy|
  | provisioning_status | ACTIVE |
  | tenant_id   | 

[Yahoo-eng-team] [Bug 1594926] Re: In integration tests loading a new page interferes with dropdown opening

[OpenStack Infra]

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

commit fe04af039f369bfeb71ca2c51301dde5711ca20b
Author: Timur Sufiev 
Date:   Wed Jun 15 23:44:50 2016 +0300

Fix dropdowns sometimes not opening in integration tests

Since most probable cause of dropdowns not opening intermittently is
Bootstrap initialization code not having enough time to complete
before test tries to open dropdown, make test wait a specified timeout
before clicking it (by means of setting a CSS class after that
timeout, which test in turn waits before clicking the dropdown).

Closes-Bug: #1594926
Change-Id: I32625caa4433f4af0de72c94b61e85ab4e16b1f9


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

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

Title:
  In integration tests loading a new page interferes with dropdown
  opening

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The following scenario has been seen many times in failed integration
  tests: all test actions are completed successfully, then test cleanup
  method goes to home page, and tries to log out - which fails, because
  the test clicks User dropdown menu (in upper right corner) too
  quickly, before the dropdown constructors have been finished by
  bootstrap JS - so the dropdown which contains Log Out link never
  opens.

  This sometimes happens not only with log out link (if that was true,
  we could simply workaround it), but for some other dropdowns as well,
  but the failure rate with other dropdowns is lower - simply because
  they operated less frequently than Log Out link (which is present in
  every test).

  The desired solution here is to wait until dropdowns become truly
  clickable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1594926/+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 1595623] [NEW] Improperly rendered Modal Form after one invalid submission

[Tatiana Ovchinnikova]

Public bug reported:

Steps to reproduce:

1. Go to Project -> Volumes
2. Pick an existing volume, click "Extend Volume" and get a modal form
3. Enter or select an invalid value for "New Size" field and click "Extend 
Volume"
4. Get another modal form with a warning message "New size must be greater than 
current size."
5. Enter an arbitrary value for "New Size" field, correct or not, and click 
"Extend Volume"

Expected:
You should get another modal form with a warning message or successfully 
extended volume depending on new size value.

Current behaviour:
The form closes with a message: "Danger: There was an error submitting the 
form. Please try again."

** Affects: horizon
 Importance: High
 Assignee: Tatiana Ovchinnikova (tmazur)
 Status: New

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

** Changed in: horizon
 Assignee: (unassigned) => Tatiana Ovchinnikova (tmazur)

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

Title:
  Improperly rendered Modal Form after one invalid submission

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Steps to reproduce:

  1. Go to Project -> Volumes
  2. Pick an existing volume, click "Extend Volume" and get a modal form
  3. Enter or select an invalid value for "New Size" field and click "Extend 
Volume"
  4. Get another modal form with a warning message "New size must be greater 
than current size."
  5. Enter an arbitrary value for "New Size" field, correct or not, and click 
"Extend Volume"

  Expected:
  You should get another modal form with a warning message or successfully 
extended volume depending on new size value.

  Current behaviour:
  The form closes with a message: "Danger: There was an error submitting the 
form. Please try again."

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1595623/+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 1572341] Re: Failed migration 90 -> 91 Can't DROP 'ixu_user_name_domain_id'

[Dolph Mathews]

** Also affects: keystone/mitaka
   Importance: Undecided
   Status: New

** Changed in: keystone/mitaka
   Importance: Undecided => High

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

Title:
  Failed migration 90 -> 91 Can't DROP 'ixu_user_name_domain_id'

Status in OpenStack Identity (keystone):
  Fix Released
Status in OpenStack Identity (keystone) mitaka series:
  New

Bug description:
  Get the following error running DB migration when  upgrading from kilo
  -> mitaka

  2016-04-20 09:31:37.560 10471 INFO migrate.versioning.api [-] 90 -> 91... 
  2016-04-20 09:31:37.822 10471 CRITICAL keystone [-] OperationalError: 
(_mysql_exceptions.OperationalError) (1091, "Can't DROP 
'ixu_user_name_domain_id'; check that column/key exists") [SQL: u'ALTER TABLE 
user DROP INDEX ixu_user_name_domain_id']
  2016-04-20 09:31:37.822 10471 ERROR keystone Traceback (most recent call 
last):
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/usr/bin/keystone-manage", line 10, in 
  2016-04-20 09:31:37.822 10471 ERROR keystone sys.exit(main())
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/keystone/keystone/cmd/manage.py", line 47, in main
  2016-04-20 09:31:37.822 10471 ERROR keystone cli.main(argv=sys.argv, 
config_files=config_files)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/keystone/keystone/cmd/cli.py", line 992, in main
  2016-04-20 09:31:37.822 10471 ERROR keystone CONF.command.cmd_class.main()
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/keystone/keystone/cmd/cli.py", line 371, in main
  2016-04-20 09:31:37.822 10471 ERROR keystone 
migration_helpers.sync_database_to_version(extension, version)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/keystone/keystone/common/sql/migration_helpers.py", line 210, in 
sync_database_to_version
  2016-04-20 09:31:37.822 10471 ERROR keystone _sync_common_repo(version)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/keystone/keystone/common/sql/migration_helpers.py", line 136, in 
_sync_common_repo
  2016-04-20 09:31:37.822 10471 ERROR keystone init_version=init_version, 
sanity_check=False)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/mitaka/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/migration.py",
 line 79, in db_sync
  2016-04-20 09:31:37.822 10471 ERROR keystone migration = 
versioning_api.upgrade(engine, repository, version)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/mitaka/local/lib/python2.7/site-packages/migrate/versioning/api.py", line 
186, in upgrade
  2016-04-20 09:31:37.822 10471 ERROR keystone return _migrate(url, 
repository, version, upgrade=True, err=err, **opts)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File "", 
line 2, in _migrate
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/mitaka/local/lib/python2.7/site-packages/migrate/versioning/util/__init__.py",
 line 160, in with_engine
  2016-04-20 09:31:37.822 10471 ERROR keystone return f(*a, **kw)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/mitaka/local/lib/python2.7/site-packages/migrate/versioning/api.py", line 
366, in _migrate
  2016-04-20 09:31:37.822 10471 ERROR keystone schema.runchange(ver, 
change, changeset.step)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/mitaka/local/lib/python2.7/site-packages/migrate/versioning/schema.py", 
line 93, in runchange
  2016-04-20 09:31:37.822 10471 ERROR keystone change.run(self.engine, step)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/mitaka/local/lib/python2.7/site-packages/migrate/versioning/script/py.py",
 line 148, in run
  2016-04-20 09:31:37.822 10471 ERROR keystone script_func(engine)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/keystone/keystone/common/sql/migrate_repo/versions/091_migrate_data_to_local_user_and_password_tables.py",
 line 61, in upgrade
  2016-04-20 09:31:37.822 10471 ERROR keystone 
name='ixu_user_name_domain_id').drop()
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/mitaka/local/lib/python2.7/site-packages/migrate/changeset/constraint.py",
 line 59, in drop
  2016-04-20 09:31:37.822 10471 ERROR keystone 
self.__do_imports('constraintdropper', *a, **kw)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/mitaka/local/lib/python2.7/site-packages/migrate/changeset/constraint.py",
 line 32, in __do_imports
  2016-04-20 09:31:37.822 10471 ERROR keystone run_single_visitor(engine, 
visitorcallable, self, *a, **kw)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 
"/opt/mitaka/local/lib/python2.7/site-packages/migrate/changeset/databases/visitor.py",
 line 85, in run_single_visitor
  2016-04-20 09:31:37.822 10471 ERROR keystone fn(element, **kwargs)
  2016-04-20 09:31:37.822 10471 ERROR keystone   File 

[Yahoo-eng-team] [Bug 1568202] Re: linux bridge agent gets out of sync with plugin

[Steven Dake]

** No longer affects: kolla/mitaka

** No longer affects: kolla/liberty

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

Title:
  linux bridge agent gets out of sync with plugin

Status in kolla:
  Triaged
Status in neutron:
  Invalid

Bug description:
  I am using ml2 plugin with linux bridge which 3 control 3 network and
  51 compute nodes.

  while spinning 500 to 1000 vms sometimes the success rate of getting
  vms active is 60%

  2 out of 6 time 500 or 1000 vms were getting active when being spun.

  logs here

  http://paste.openstack.org/show/493553/

To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla/+bug/1568202/+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 1595587] [NEW] Cannot save HostMapping object

[Andrey Volkov]

Public bug reported:

While I was looking at HostMapping object I found inconsistency in signature 
and call:
HostMapping._save_in_db(context, obj, updates) uses objects attributes id and 
host.
But then it is called from HostMapping.save second param is self.host which is 
not object
but just a string.

Existing test
(nova.tests.unit.objects.test_host_mapping.TestHostMappingObject.test_save)
doesn't catch this error because _save_in_db is mocked.

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

Title:
  Cannot save HostMapping object

Status in OpenStack Compute (nova):
  New

Bug description:
  While I was looking at HostMapping object I found inconsistency in signature 
and call:
  HostMapping._save_in_db(context, obj, updates) uses objects attributes id and 
host.
  But then it is called from HostMapping.save second param is self.host which 
is not object
  but just a string.

  Existing test
  (nova.tests.unit.objects.test_host_mapping.TestHostMappingObject.test_save)
  doesn't catch this error because _save_in_db is mocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1595587/+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 1595575] [NEW] The hash of a notification object does not depend on its SCHEMA

[Balazs Gibizer]

Public bug reported:

Description
===
As oslo ObjectVersionChecker.test_hashes() does not provide a way to supply 
exta information to the fingerprint generation the current unit test does not 
detect if the SCHEMA of a versioned notification object has been changed 
without proper version bump. 

Compare the unit test test_versions with
test_notification_payload_version_depends_on_the_schema in
TestNotificationObjectVersions [1]

The former uses test_hashes without the extra_data_func while the later
uses the get_hashes() with extra_data_func.

[1]
https://github.com/openstack/nova/blob/master/nova/tests/unit/notifications/objects/test_notification.py#L267

Steps to reproduce
==
Modify the SCHEMA of one of the notification object. 
Run the unit test
SCHEMA changes are not detected

Environment
===
6a119fc72096fa65678112e151e4a7a00091ce26

** Affects: nova
 Importance: Undecided
 Assignee: Balazs Gibizer (balazs-gibizer)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)

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

Title:
  The hash of a notification object does not depend on its SCHEMA

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===
  As oslo ObjectVersionChecker.test_hashes() does not provide a way to supply 
exta information to the fingerprint generation the current unit test does not 
detect if the SCHEMA of a versioned notification object has been changed 
without proper version bump. 

  Compare the unit test test_versions with
  test_notification_payload_version_depends_on_the_schema in
  TestNotificationObjectVersions [1]

  The former uses test_hashes without the extra_data_func while the
  later uses the get_hashes() with extra_data_func.

  [1]
  
https://github.com/openstack/nova/blob/master/nova/tests/unit/notifications/objects/test_notification.py#L267

  Steps to reproduce
  ==
  Modify the SCHEMA of one of the notification object. 
  Run the unit test
  SCHEMA changes are not detected

  Environment
  ===
  6a119fc72096fa65678112e151e4a7a00091ce26

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1595575/+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 1595574] [NEW] VXLan fails to be created between dhcp and compute node

[Michał Jastrzębski]

Public bug reported:

I have strange issue. VXLan fails to connect dhcp agent and compute
node. VXLan compute-compute builds successfully. No log ERROR or even
WARNING.

compute node:

 Bridge br-tun
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port "vxlan-c0a86424"
Interface "vxlan-c0a86424"
type: vxlan
options: {df_default="true", in_key=flow, 
local_ip="192.168.100.29", out_key=flow, remote_ip="192.168.100.36"}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}

DHCP agent node:
Bridge br-tun
fail_mode: secure
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port "vxlan-c0a8641d"
Interface "vxlan-c0a8641d"
type: vxlan
options: {df_default="true", in_key=flow, 
local_ip="192.168.100.31", out_key=flow, remote_ip="192.168.100.29"}
Port "vxlan-c0a86424"
Interface "vxlan-c0a86424"
type: vxlan
options: {df_default="true", in_key=flow, 
local_ip="192.168.100.31", out_key=flow, remote_ip="192.168.100.36"}
Port br-tun
Interface br-tun
type: internal


I have 2 vms, at compute .36 and .29. As you can see, compute doesn't have 
tunnel exit from dhcp agent node.
This was deployed by latest master kolla, which translates to latest master 
neutron.

** Affects: neutron
 Importance: Undecided
 Assignee: Darek Smigiel (smigiel-dariusz)
 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/1595574

Title:
  VXLan fails to be created between dhcp and compute node

Status in neutron:
  New

Bug description:
  I have strange issue. VXLan fails to connect dhcp agent and compute
  node. VXLan compute-compute builds successfully. No log ERROR or even
  WARNING.

  compute node:

   Bridge br-tun
  fail_mode: secure
  Port br-tun
  Interface br-tun
  type: internal
  Port "vxlan-c0a86424"
  Interface "vxlan-c0a86424"
  type: vxlan
  options: {df_default="true", in_key=flow, 
local_ip="192.168.100.29", out_key=flow, remote_ip="192.168.100.36"}
  Port patch-int
  Interface patch-int
  type: patch
  options: {peer=patch-tun}

  DHCP agent node:
  Bridge br-tun
  fail_mode: secure
  Port patch-int
  Interface patch-int
  type: patch
  options: {peer=patch-tun}
  Port "vxlan-c0a8641d"
  Interface "vxlan-c0a8641d"
  type: vxlan
  options: {df_default="true", in_key=flow, 
local_ip="192.168.100.31", out_key=flow, remote_ip="192.168.100.29"}
  Port "vxlan-c0a86424"
  Interface "vxlan-c0a86424"
  type: vxlan
  options: {df_default="true", in_key=flow, 
local_ip="192.168.100.31", out_key=flow, remote_ip="192.168.100.36"}
  Port br-tun
  Interface br-tun
  type: internal

  
  I have 2 vms, at compute .36 and .29. As you can see, compute doesn't have 
tunnel exit from dhcp agent node.
  This was deployed by latest master kolla, which translates to latest master 
neutron.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1595574/+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 1587115] Re: output parameter of show console output might be missing

[Markus Zoeller (markus_z)]

@Gergely:
As you already figured out, the api-ref documentation is under construction 
right now to fix those documentation issues (see bp [1]). Therefore I'm closing 
this bug report. If you find such issues after the blueprint [1] is marked as 
implemented, feel free to open such bug reports again.

References:
[1] https://blueprints.launchpad.net/nova/+spec/api-ref-in-rst

** Tags added: doc

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

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

Title:
  output parameter of show console output  might be missing

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  The example of show console output in the web API reference [1] shows an 
"output" parameter. 
  This parameter is missing from the list of parameters in the web API 
reference and from Chapter 4.4.10.1 of the pdf API reference [2]. 
  [1]: 
http://developer.openstack.org/api-ref-compute-v2.1.html#showConsoleOutput
  [2]: http://api.openstack.org/api-ref-guides/bk-api-ref.pdf

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1587115/+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 1587842] Re: address is missing from the parameter list of Remove (disassociate) fixed IP

[Markus Zoeller (markus_z)]

The api-ref documentation is currently under construction. Those
documentation issues will be fixed with bp [1]. You'll notice comments
in the doc sources like "needs:parameter_verification" or
"needs:example_verification" [2]. As long as these comments are in the
doc sources, they aren't yet checked for validity but will be targeted
soon.

As the effort will be driven by the blueprint, I'm closing this bug
report. If you find such issues after the blueprint [1] is marked as
implemented, feel free to open such bug reports again.

In the meantime, new contributors which like to work on improving those
doc sources are *highly* welcome. You can ping alex_xu, oomichi, sdague
or auggy in the #openstack-nova IRC channel for that [3]. More
information can be found at [4].

References:
[1] https://blueprints.launchpad.net/nova/+spec/api-ref-in-rst
[2] 
https://github.com/openstack/nova/blob/850d8cdc2cb8163285bdacd1ea83b4fe145e8d16/api-ref/source/servers-action-fixed-ip.inc#L2
[3] https://wiki.openstack.org/wiki/Nova/Mentoring
[4] https://wiki.openstack.org/wiki/NovaAPIRef

** Tags added: api-ref

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

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

Title:
  address is missing from the parameter list of Remove (disassociate)
  fixed IP

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  According to the example Remove (disassociate) fixed IP has a parameter 
called "address".
  This "address" parameter is not listed in the Parameter list of Change 
administrative password in the web API reference [1] and not mentioned in 
Chapter 4.4.17 of the pdf API reference [2].
  [1]: http://developer.openstack.org/api-ref-compute-v2.1.html#removeFixedIp
  [2]: http://api.openstack.org/api-ref-guides/bk-api-ref.pdf

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1587842/+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 1587845] Re: address is missing from the parameter list of Remove (disassociate) floating IP

[Markus Zoeller (markus_z)]

The api-ref documentation is currently under construction. Those
documentation issues will be fixed with bp [1]. You'll notice comments
in the doc sources like "needs:parameter_verification" or
"needs:example_verification" [2]. As long as these comments are in the
doc sources, they aren't yet checked for validity but will be targeted
soon.

As the effort will be driven by the blueprint, I'm closing this bug
report. If you find such issues after the blueprint [1] is marked as
implemented, feel free to open such bug reports again.

In the meantime, new contributors which like to work on improving those
doc sources are *highly* welcome. You can ping alex_xu, oomichi, sdague
or auggy in the #openstack-nova IRC channel for that [3]. More
information can be found at [4].

References:
[1] https://blueprints.launchpad.net/nova/+spec/api-ref-in-rst
[2] 
https://github.com/openstack/nova/blob/850d8cdc2cb8163285bdacd1ea83b4fe145e8d16/api-ref/source/servers-action-fixed-ip.inc#L2
[3] https://wiki.openstack.org/wiki/Nova/Mentoring
[4] https://wiki.openstack.org/wiki/NovaAPIRef

** Tags added: api-ref

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

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

Title:
  address is missing from the parameter list of Remove (disassociate)
  floating IP

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  According to the example Remove (disassociate) floating IP has a parameter 
called "address".
  This "address" parameter is not listed in the Parameter list of Remove 
(disassociate) floating IP in the web API reference [1] and not mentioned in 
Chapter 4.4.18 of the pdf API reference [2].
  [1]: http://developer.openstack.org/api-ref-compute-v2.1.html#removeFloatingIp
  [2]: http://api.openstack.org/api-ref-guides/bk-api-ref.pdf

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1587845/+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 1595515] [NEW] IpConntrackManager class in ip_conntrack.py should be a singleton to be used by both SG and FWaaS

[chandan dutta chowdhury]

Public bug reported:

The FWaaS V2 APIs is going to configure security rules at a port level.
It will need to use connection tracking and zone configuration methods
defined in the ip_conntrack.py and iptables_firewall.py in neutron
project.

Some methods in the IptablesFirewallDriver in iptables_firewall needs to
be moved to IpConntrackManager class in ip_conntrack.py. As
IpConntrackManager will be used by both SG and FWaaS V2 APIs and both of
them can be used at the same time, the IpConntrackManager should be a
singleton responsible for allocating and reclaiming zones assigned to
ports.

** Affects: neutron
 Importance: Undecided
 Assignee: chandan dutta chowdhury (chandanc)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => chandan dutta chowdhury (chandanc)

** Description changed:

  The FWaaS V2 APIs is going to configure security rules at a port level.
- It will need to use connection and zone configuration methods defined in
- the ip_conntrack.py and iptables_firewall.py in neutron project.
+ It will need to use connection tracking and zone configuration methods
+ defined in the ip_conntrack.py and iptables_firewall.py in neutron
+ project.
  
  Some methods in the IptablesFirewallDriver in iptables_firewall needs to
  be moved to IpConntrackManager class in ip_conntrack.py. As
  IpConntrackManager will be used by both SG and FWaaS V2 APIs and both of
  them can be used at the same time, the IpConntrackManager should be a
  singleton responsible for allocating and reclaiming zones assigned to
  ports.

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

Title:
  IpConntrackManager class in ip_conntrack.py should be a singleton to
  be used by both SG and FWaaS

Status in neutron:
  New

Bug description:
  The FWaaS V2 APIs is going to configure security rules at a port
  level. It will need to use connection tracking and zone configuration
  methods defined in the ip_conntrack.py and iptables_firewall.py in
  neutron project.

  Some methods in the IptablesFirewallDriver in iptables_firewall needs
  to be moved to IpConntrackManager class in ip_conntrack.py. As
  IpConntrackManager will be used by both SG and FWaaS V2 APIs and both
  of them can be used at the same time, the IpConntrackManager should be
  a singleton responsible for allocating and reclaiming zones assigned
  to ports.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1595515/+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 1595513] [NEW] keystone spamming logs with stacktraces for non critical errors

[Rudolf Vriend]

Public bug reported:

Several api's dump errors with full stack traces into the logs, although
it usually is perfectly OK that someone issues a api-request for an
object that does not exist.

This log spam makes it hard to filter between real issues and simple
'record not found' situations..

Some examples:
https://github.com/openstack/keystone/blob/master/keystone/auth/controllers.py#L193
https://github.com/openstack/keystone/blob/master/keystone/auth/controllers.py#L457
https://github.com/openstack/keystone/blob/master/keystone/auth/plugins/core.py#L150
https://github.com/openstack/keystone/blob/master/keystone/auth/plugins/core.py#L180

Suggest to use LOG.error with some meaningful error message instead.

** Affects: keystone
 Importance: Undecided
 Assignee: Rudolf Vriend (rudolf-vriend)
 Status: New

** Changed in: keystone
 Assignee: (unassigned) => Rudolf Vriend (rudolf-vriend)

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

Title:
  keystone spamming logs with stacktraces for non critical errors

Status in OpenStack Identity (keystone):
  New

Bug description:
  Several api's dump errors with full stack traces into the logs,
  although it usually is perfectly OK that someone issues a api-request
  for an object that does not exist.

  This log spam makes it hard to filter between real issues and simple
  'record not found' situations..

  Some examples:
  
https://github.com/openstack/keystone/blob/master/keystone/auth/controllers.py#L193
  
https://github.com/openstack/keystone/blob/master/keystone/auth/controllers.py#L457
  
https://github.com/openstack/keystone/blob/master/keystone/auth/plugins/core.py#L150
  
https://github.com/openstack/keystone/blob/master/keystone/auth/plugins/core.py#L180

  Suggest to use LOG.error with some meaningful error message instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1595513/+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 1595506] [NEW] Update Server resonse description includes host_status

[Gergely Csatari]

Public bug reported:

The parameter list in Update Servers response list includes host_status,
while this parameter is not part of the response.

** Affects: nova
 Importance: Undecided
 Assignee: Gergely Csatari (gergely-csatari)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Gergely Csatari (gergely-csatari)

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

Title:
  Update Server resonse description includes host_status

Status in OpenStack Compute (nova):
  New

Bug description:
  The parameter list in Update Servers response list includes
  host_status, while this parameter is not part of the response.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1595506/+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 1588042] Re: UnboundLocalError with native openflow agent on switch timeout

[OpenStack Infra]

Reviewed:  https://review.openstack.org/324078
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=b22c7ae42813ca7c9c791b5acd4da24566784e9c
Submitter: Jenkins
Branch:master

commit b22c7ae42813ca7c9c791b5acd4da24566784e9c
Author: Inessa Vasilevskaya 
Date:   Wed Jun 1 20:54:43 2016 +0300

OVS: UnboundLocalError on switch timeout fixed

In case there is some cached datapath id in OVSAgentBridge
and openflow switch does not respond in time for some
reason, a call to OVSAgentBridge._dpid() method will result
in UnboundLocalError.
This patch addresses the issue by calculating dpid_str
value from cached dpid instead of referencing unassigned
variable.
Some minor refactor also took place.

Closes-Bug: #1588042

Change-Id: If50183bf95cbe50c3a2393be8c2ab913c9715a10


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

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

Title:
  UnboundLocalError with native openflow agent on switch timeout

Status in neutron:
  Fix Released

Bug description:
  In situation when there is some cached datapath_id and openflow switch
  doesn't respond in time (causing RuntimeError), UnboundLocalError is
  raised

  2016-05-25 14:57:28 ERR ryu.lib.hub [req-6efe2697-b494-4c54-97dc-4d8d1f43cab6 
- - - - -] hub: uncaught exception: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/ryu/lib/hub.py", line 52, in _launch
  func(*args, **kwargs)
File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/ovs_ryuapp.py",
 line 35, in agent_main_wrapper
  ovs_agent.main(bridge_classes)
File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
 line 2118, in main
  agent.daemon_loop()
File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
 line 2041, in daemon_loop
  self.rpc_loop(polling_manager=pm)
File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
 line 1910, in rpc_loop
  ovs_status = self.check_ovs_status()
File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
 line 1718, in check_ovs_status
  status = self.int_br.check_canary_table()
File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/br_int.py",
 line 52, in check_canary_table
  flows = self.dump_flows(constants.CANARY_TABLE)
File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/ofswitch.py",
 line 125, in dump_flows
  (dp, ofp, ofpp) = self._get_dp()
File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/ovs_bridge.py",
 line 61, in _get_dp
  if new_dpid_str != dpid_str:
  UnboundLocalError: local variable 'dpid_str' referenced before assignment

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1588042/+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 1595467] Re: Signature verification failure leads to saving image

[Niall Bunting]

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

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

Title:
  Signature verification failure leads to saving image

Status in Glance:
  Invalid

Bug description:
  Overview:
  When signature verification fails it can cause a 500 error. This causes the 
image to become stuck in the saving state.

  What should happen is that it returns a 40? and the image is put into
  the deleted state.

  Reproducing:

  glance image-create --name mySignedImage --container-format bare 
--disk-format qcow2 --property img_signature="WRONG SIGNATURE" --property 
img_signature_certificate_uuid="$cert_uuid" --property 
img_signature_hash_method='SHA-256' --property img_signature_key_type='RSA-PSS' 
< myimage
  ++--+
  | Property   | Value|
  ++--+
  | checksum   | None |
  | container_format   | bare |
  | created_at | 2016-06-23T09:46:34Z |
  | disk_format| qcow2|
  | id | f0839709-4ff6-4291-9997-a4d387e20582 |
  | img_signature  |  |
  | img_signature_certificate_uuid | cd7cc675-e573-419c-8fff-33a72734a243 |
  | img_signature_hash_method  | SHA-256  |
  | img_signature_key_type | RSA-PSS  |
  | min_disk   | 0|
  | min_ram| 0|
  | name   | mySignedImage|
  | owner  | 7f065427534f49ab97a0b68ecc73fd07 |
  | protected  | False|
  | size   | None |
  | status | queued   |
  | tags   | []   |
  | updated_at | 2016-06-23T09:46:34Z |
  | virtual_size   | None |
  | visibility | private  |
  ++--+
  500 Internal Server Error
  The server has either erred or is incapable of performing the requested 
operation.
  (HTTP 500)

  
  nib@work-devstack:/tmp/testtmp/nest$ glance image-show 
f0839709-4ff6-4291-9997-a4d387e20582
  ++--+
  | Property   | Value|
  ++--+
  | checksum   | None |
  | container_format   | bare |
  | created_at | 2016-06-23T09:46:34Z |
  | disk_format| qcow2|
  | id | f0839709-4ff6-4291-9997-a4d387e20582 |
  | img_signature  |  |
  | img_signature_certificate_uuid | cd7cc675-e573-419c-8fff-33a72734a243 |
  | img_signature_hash_method  | SHA-256  |
  | img_signature_key_type | RSA-PSS  |
  | min_disk   | 0|
  | min_ram| 0|
  | name   | mySignedImage|
  | owner  | 7f065427534f49ab97a0b68ecc73fd07 |
  | protected  | False|
  | size   | None |
  | status | saving   |
  | tags   | []   |
  | updated_at | 2016-06-23T09:46:34Z |
  | virtual_size   | None |
  | visibility | private  |
  ++--+

  Console:
  2016-06-23 09:46:35.619 TRACE glance.common.wsgi _('Signature 
verification failed')
  2016-06-23 09:46:35.619 TRACE glance.common.wsgi SignatureVerificationError: 
Signature verification failed
  2016-06-23 09:46:35.619 TRACE 

[Yahoo-eng-team] [Bug 1595475] [NEW] In multinode setup - glance-cache-manage and glance-cache-prefetcher fails to find an image, since it tries the first available glance_api server and fails

[Grzegorz]

Public bug reported:

In multinode setup - glance-cache-manage and glance-cache-prefetcher
fails to find an image, since it tries the first available glance_api
server and fails.

I know this problem is known, since there is a opened bug for how cinder 
acceses glance :
https://bugs.launchpad.net/cinder/+bug/1571211

But even if we move glance backend to swift or whatever, we still cant
use glance-cache properly, because of glance lacking replication between
Image directories in multinode setup.

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: glance glance-cache

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

Title:
  In multinode setup - glance-cache-manage and glance-cache-prefetcher
  fails to find an image, since it tries the first available glance_api
  server and fails

Status in Glance:
  New

Bug description:
  In multinode setup - glance-cache-manage and glance-cache-prefetcher
  fails to find an image, since it tries the first available glance_api
  server and fails.

  I know this problem is known, since there is a opened bug for how cinder 
acceses glance :
  https://bugs.launchpad.net/cinder/+bug/1571211

  But even if we move glance backend to swift or whatever, we still cant
  use glance-cache properly, because of glance lacking replication
  between Image directories in multinode setup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1595475/+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 1595467] [NEW] Signature verification failure leads to saving image

[Niall Bunting]

Public bug reported:

Overview:
When signature verification fails it can cause a 500 error. This causes the 
image to become stuck in the saving state.

What should happen is that it returns a 40? and the image is put into
the deleted state.

Reproducing:

glance image-create --name mySignedImage --container-format bare --disk-format 
qcow2 --property img_signature="WRONG SIGNATURE" --property 
img_signature_certificate_uuid="$cert_uuid" --property 
img_signature_hash_method='SHA-256' --property img_signature_key_type='RSA-PSS' 
< myimage
++--+
| Property   | Value|
++--+
| checksum   | None |
| container_format   | bare |
| created_at | 2016-06-23T09:46:34Z |
| disk_format| qcow2|
| id | f0839709-4ff6-4291-9997-a4d387e20582 |
| img_signature  |  |
| img_signature_certificate_uuid | cd7cc675-e573-419c-8fff-33a72734a243 |
| img_signature_hash_method  | SHA-256  |
| img_signature_key_type | RSA-PSS  |
| min_disk   | 0|
| min_ram| 0|
| name   | mySignedImage|
| owner  | 7f065427534f49ab97a0b68ecc73fd07 |
| protected  | False|
| size   | None |
| status | queued   |
| tags   | []   |
| updated_at | 2016-06-23T09:46:34Z |
| virtual_size   | None |
| visibility | private  |
++--+
500 Internal Server Error
The server has either erred or is incapable of performing the requested 
operation.
(HTTP 500)


nib@work-devstack:/tmp/testtmp/nest$ glance image-show 
f0839709-4ff6-4291-9997-a4d387e20582
++--+
| Property   | Value|
++--+
| checksum   | None |
| container_format   | bare |
| created_at | 2016-06-23T09:46:34Z |
| disk_format| qcow2|
| id | f0839709-4ff6-4291-9997-a4d387e20582 |
| img_signature  |  |
| img_signature_certificate_uuid | cd7cc675-e573-419c-8fff-33a72734a243 |
| img_signature_hash_method  | SHA-256  |
| img_signature_key_type | RSA-PSS  |
| min_disk   | 0|
| min_ram| 0|
| name   | mySignedImage|
| owner  | 7f065427534f49ab97a0b68ecc73fd07 |
| protected  | False|
| size   | None |
| status | saving   |
| tags   | []   |
| updated_at | 2016-06-23T09:46:34Z |
| virtual_size   | None |
| visibility | private  |
++--+

Console:
2016-06-23 09:46:35.619 TRACE glance.common.wsgi _('Signature verification 
failed')
2016-06-23 09:46:35.619 TRACE glance.common.wsgi SignatureVerificationError: 
Signature verification failed
2016-06-23 09:46:35.619 TRACE glance.common.wsgi

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

Title:
  Signature verification failure leads to saving image

Status in Glance:
  New

Bug description:
  Overview:
  When signature verification 

[Yahoo-eng-team] [Bug 1595468] [NEW] Cannot encode revokeTree object when mongo is configured as cache

[Jose Castro Leon]

Public bug reported:

When you configure mongo as the cache subsystem for keystone, it fails
to store the revoke tree in the cache. This is due that the
basetransform only expects single types or dictionaries.

def transform_incoming(self, son, collection):
"""Used while saving data to MongoDB."""
for (key, value) in list(son.items()):
if isinstance(value, api.CachedValue):
son[key] = value.payload  # key is 'value' field here
son['meta'] = value.metadata
elif isinstance(value, dict):  # Make sure we recurse into sub-docs
son[key] = self.transform_incoming(value, collection)
return son

In mitaka this code has been sent to oslo_cache.mongo but the issue is
still there

As a result there is a 500 error on the response for validating a token.

This is the exception I am getting

2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi 
[req-9508d2e4-4e4c-4fd1-8daa-bc7c3456a320 - - - - -] Cannot encode object: 

2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi Traceback (most recent 
call last):
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/keystone/common/wsgi.py", line 452, in 
__call__
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi response = 
self.process_request(request)
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/keystone/middleware/core.py", line 305, in 
process_request
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi auth_context = 
self._build_auth_context(request)
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/keystone/middleware/core.py", line 193, in 
_build_auth_context
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi 
token_data=self.token_provider_api.validate_token(token_id))
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/keystone/token/provider.py", line 190, in 
validate_token
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi 
self._is_valid_token(token)
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/keystone/token/provider.py", line 296, in 
_is_valid_token
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi 
self.check_revocation(token)
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/keystone/token/provider.py", line 230, in 
check_revocation
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi return 
self.check_revocation_v3(token)
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/keystone/token/provider.py", line 223, in 
check_revocation_v3
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi 
self.revoke_api.check_token(token_values)
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/keystone/contrib/revoke/core.py", line 226, 
in check_token
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi if 
self._get_revoke_tree().is_revoked(token_values):
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/dogpile/cache/region.py", line 1040, in 
decorate
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi should_cache_fn)
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/dogpile/cache/region.py", line 651, in 
get_or_create
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi async_creator) as 
value:
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/dogpile/core/dogpile.py", line 158, in 
__enter__
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi return 
self._enter()
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/dogpile/core/dogpile.py", line 98, in _enter
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi generated = 
self._enter_create(createdtime)
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/dogpile/core/dogpile.py", line 149, in 
_enter_create
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi created = 
self.creator()
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/dogpile/cache/region.py", line 624, in 
gen_value
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi 
self.backend.set(key, value)
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 
"/usr/lib/python2.7/site-packages/keystone/common/cache/backends/mongo.py", 
line 186, in set
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi 
self.client.set(key, value)
2016-06-23 06:42:13.248 30288 ERROR keystone.common.wsgi   File 

[Yahoo-eng-team] [Bug 1583419] Re: Make dict.keys() PY3 compatible

[liuwei]

** No longer affects: ceilometer

** No longer affects: python-ceilometerclient

** No longer affects: python-heatclient

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

Title:
  Make dict.keys() PY3 compatible

Status in Cinder:
  In Progress
Status in neutron:
  In Progress
Status in python-cinderclient:
  Fix Released
Status in python-glanceclient:
  New
Status in python-manilaclient:
  In Progress
Status in python-troveclient:
  Fix Released
Status in Rally:
  Fix Released
Status in tempest:
  In Progress

Bug description:
  In PY3, dict.keys() will return a view of list but not a list anymore, i.e.
  $ python3.4
  Python 3.4.3 (default, Mar 31 2016, 20:42:37) 
  >>> body={"11":"22"}
  >>> body[body.keys()[0]]
  Traceback (most recent call last):
File "", line 1, in 
  TypeError: 'dict_keys' object does not support indexing

  so for py3 compatible we should change it as follows:
  >>> body[list(body.keys())[0]]
  '22'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1583419/+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 1575055] Re: check_instance_id() error on reboots when using config-drive

[Frank Heimes]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Status: New => Fix Committed

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

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

Title:
  check_instance_id() error on reboots when using config-drive

Status in cloud-init:
  Fix Committed
Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed

Bug description:
  Problem Description
  =
  When using a config-drive to provide meta-data to cloud-init on ubuntu (for 
Linux guest running in KVM for z Systems) we get a check_instance_id() error 
whenever we soft reboot after the (successful) initial boot.

  The error shows:

  [5.283203] cloud-init[1637]: Cloud-init v. 0.7.7 running 'init-local' at 
Sat, 23 Apr 2016 00:50:58 +. Up 5.25 seconds.
  [5.283368] cloud-init[1637]: 2016-04-22 20:50:58,839 - util.py[WARNING]: 
failed of stage init-local
  [5.286659] cloud-init[1637]: failed run of stage init-local
  [5.286770] cloud-init[1637]: 

  [5.286849] cloud-init[1637]: Traceback (most recent call last):
  [5.286924] cloud-init[1637]:   File "/usr/bin/cloud-init", line 520, in 
status_wrapper
  [5.286998] cloud-init[1637]: ret = functor(name, args)
  [5.287079] cloud-init[1637]:   File "/usr/bin/cloud-init", line 250, in 
main_init
  [5.287152] cloud-init[1637]: init.fetch(existing=existing)
  [5.287225] cloud-init[1637]:   File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 322, in fetch
  [5.287298] cloud-init[1637]: return 
self._get_data_source(existing=existing)
  [5.287371] cloud-init[1637]:   File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 229, in 
_get_data_source
  [5.287445] cloud-init[1637]: ds.check_instance_id(self.cfg)):
  [5.287518] cloud-init[1637]: TypeError: check_instance_id() takes 1 
positional argument but 2 were given
  [5.287592] cloud-init[1637]: 

  [FAILED] Failed to start Initial cloud-init job (pre-networking).

  
  The failure of the init-local pre-networking does seem to lead to a boot up 
delay as cloud-init tries to search for networking outside of the already saved 
networking data.   

  Otherwise the error is purely cosmetic as later init modules find (or
  let existing IP configuration take over) and bring up the correct
  interfaces.

  The original problem was found outside of openstack with stand-alone
  cloud-config iso images.  But have been able to reproduce the problem
  within an openstack ICM environment.

  Team has had some success getting around the problem by patching the
  check_instance_id function in /usr/lib/python3/dist-
  packages/cloudinit/sources/DataSourceConfigDrive.py so that it
  accepted an extra argument, ex:

  ubuntu@markvercd:~$ sudo cat check_instance_id.patch 
  --- /usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py 
2016-04-06 15:29:59.0 +
  +++ 
/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py.new   
  2016-04-11 22:53:47.799867139 +
  @@ -155,7 +155,7 @@
   
   return True
   
  -def check_instance_id(self):
  +def check_instance_id(self,somecfg):
   # quickly (local check only) if self.instance_id is still valid
   return 
sources.instance_id_matches_system_uuid(self.get_instance_id())
   
  ubuntu@markvercd:~$ 

  ---uname output---
  Linux k6mpathcl.pokprv.stglabs.ibm.com 4.4.0-21-generic #37-Ubuntu SMP Mon 
Apr 18 18:31:26 UTC 2016 s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest on a z13 (2827-732) LPAR 

  Steps to Reproduce
  =
   1) set up ubuntu guest image with cloud-init
  2) pass in iso image with cloud-config data in cdrom device
  3) boot up successfully with cloud-config data
  4) attempt a soft reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1575055/+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 1595440] [NEW] neutron-fwaas ships /usr/bin/neutron-l3-agent a 2nd time

[Thomas Goirand]

Public bug reported:

In distributions, it's not possible to ship twice a daemon in /usr/bin
with 2 different packages. This means that /usr/bin/neutron-l3-agent in
neutron-fwaas is clashing with /usr/bin/neutron-l3-agent from python-
neutron. In Debian, we will rename /usr/bin/neutron-l3-agent as /usr/bin
/neutron-fwaas-l3-agent. Please do the same upstream.

Full explanations on why this is a problem is available here:
http://lists.openstack.org/pipermail/openstack-dev/2016-June/097956.html

I'm available on IRC if you want to discuss the problem as well.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: fwaas

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

Title:
  neutron-fwaas ships /usr/bin/neutron-l3-agent a 2nd time

Status in neutron:
  New

Bug description:
  In distributions, it's not possible to ship twice a daemon in /usr/bin
  with 2 different packages. This means that /usr/bin/neutron-l3-agent
  in neutron-fwaas is clashing with /usr/bin/neutron-l3-agent from
  python-neutron. In Debian, we will rename /usr/bin/neutron-l3-agent as
  /usr/bin/neutron-fwaas-l3-agent. Please do the same upstream.

  Full explanations on why this is a problem is available here:
  http://lists.openstack.org/pipermail/openstack-dev/2016-June/097956.html

  I'm available on IRC if you want to discuss the problem as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1595440/+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 1595439] [NEW] There are some spelling mistakes in horizon

[gecong]

Public bug reported:

in horizon/openstack_dashboard/django_pyscss_fix/__init__.py:25: 
  intermittantly because of concurrency issues.  This code ignores the ,  
intermittantly should be intermittently

   in 
horizon/openstack_dashboard/test/integration_tests/tests/test_flavors.py:62:   
 """Tests the flavor Edit row action finctionality:, finctionality should 
be  functionality   
   
   in 
horizon/openstack_dashboard/test/integration_tests/tests/test_security_groups.py:77:
  
 """tests the manage rules creation and deletion funcionalities:  
funcionalities should be functionalities

in 
horizon/openstack_dashboard/test/integration_tests/tests/test_security_groups.py:94:
   
 """tests the manage rules creation and deletion funcionalities:  
funcionalities should be functionalities

in horizon/openstack_dashboard/api/rest/utils.py:94: 
  - JSON serialisable data ,  serialisable should be serializable

** Affects: horizon
 Importance: Undecided
 Assignee: gecong (ge-cong)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => gecong (ge-cong)

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

Title:
  There are some spelling mistakes in horizon

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  in horizon/openstack_dashboard/django_pyscss_fix/__init__.py:25: 
intermittantly because of concurrency issues.  This code ignores the ,  
intermittantly should be intermittently

 in 
horizon/openstack_dashboard/test/integration_tests/tests/test_flavors.py:62:   
   """Tests the flavor Edit row action finctionality:, finctionality should 
be  functionality   
 
 in 
horizon/openstack_dashboard/test/integration_tests/tests/test_security_groups.py:77:
  
   """tests the manage rules creation and deletion funcionalities:  
funcionalities should be functionalities

  in 
horizon/openstack_dashboard/test/integration_tests/tests/test_security_groups.py:94:
   
   """tests the manage rules creation and deletion funcionalities:  
funcionalities should be functionalities

  in horizon/openstack_dashboard/api/rest/utils.py:94: 
- JSON serialisable data ,  serialisable should be serializable

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1595439/+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 1595433] [NEW] Failed to generate conf of glance

[leixin]

Public bug reported:

When exec:
oslo-config-generator --config-dir=etc/oslo-config-generator/
Traceback (most recent call last):
  File "/usr/bin/oslo-config-generator", line 11, in 
sys.exit(main())
  File "/usr/lib/python2.7/site-packages/oslo_config/generator.py", line 439, 
in main
generate(conf)
  File "/usr/lib/python2.7/site-packages/oslo_config/generator.py", line 421, 
in generate
groups = _get_groups(_list_opts(conf.namespace))
  File "/usr/lib/python2.7/site-packages/oslo_config/generator.py", line 340, 
in _list_opts
loaders = _get_raw_opts_loaders(namespaces)
  File "/usr/lib/python2.7/site-packages/oslo_config/generator.py", line 312, 
in _get_raw_opts_loaders
invoke_on_load=False)
  File "/usr/lib/python2.7/site-packages/stevedore/named.py", line 55, in 
__init__
verify_requirements)
  File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 171, in 
_load_plugins
self._on_load_failure_callback(self, ep, err)
  File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 163, in 
_load_plugins
verify_requirements,
  File "/usr/lib/python2.7/site-packages/stevedore/named.py", line 123, in 
_load_one_plugin
verify_requirements,
  File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 184, in 
_load_one_plugin
plugin = ep.resolve()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2235, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
ImportError: No module named db.concurrency
error: Bad exit status from /var/tmp/rpm-tmp.jzkU1v (%build)

** Affects: glance
 Importance: Undecided
 Assignee: leixin (leixin)
 Status: New

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

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

Title:
  Failed to generate conf of glance

Status in Glance:
  New

Bug description:
  When exec:
  oslo-config-generator --config-dir=etc/oslo-config-generator/
  Traceback (most recent call last):
File "/usr/bin/oslo-config-generator", line 11, in 
  sys.exit(main())
File "/usr/lib/python2.7/site-packages/oslo_config/generator.py", line 439, 
in main
  generate(conf)
File "/usr/lib/python2.7/site-packages/oslo_config/generator.py", line 421, 
in generate
  groups = _get_groups(_list_opts(conf.namespace))
File "/usr/lib/python2.7/site-packages/oslo_config/generator.py", line 340, 
in _list_opts
  loaders = _get_raw_opts_loaders(namespaces)
File "/usr/lib/python2.7/site-packages/oslo_config/generator.py", line 312, 
in _get_raw_opts_loaders
  invoke_on_load=False)
File "/usr/lib/python2.7/site-packages/stevedore/named.py", line 55, in 
__init__
  verify_requirements)
File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 171, 
in _load_plugins
  self._on_load_failure_callback(self, ep, err)
File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 163, 
in _load_plugins
  verify_requirements,
File "/usr/lib/python2.7/site-packages/stevedore/named.py", line 123, in 
_load_one_plugin
  verify_requirements,
File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 184, 
in _load_one_plugin
  plugin = ep.resolve()
File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 
2235, in resolve
  module = __import__(self.module_name, fromlist=['__name__'], level=0)
  ImportError: No module named db.concurrency
  error: Bad exit status from /var/tmp/rpm-tmp.jzkU1v (%build)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1595433/+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 1583419] Re: Make dict.keys() PY3 compatible

[Dinesh Bhor]

** No longer affects: nova

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

Title:
  Make dict.keys() PY3 compatible

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in neutron:
  In Progress
Status in python-ceilometerclient:
  New
Status in python-cinderclient:
  Fix Released
Status in python-glanceclient:
  New
Status in python-heatclient:
  New
Status in python-manilaclient:
  In Progress
Status in python-troveclient:
  Fix Released
Status in Rally:
  Fix Released
Status in tempest:
  New

Bug description:
  In PY3, dict.keys() will return a view of list but not a list anymore, i.e.
  $ python3.4
  Python 3.4.3 (default, Mar 31 2016, 20:42:37) 
  >>> body={"11":"22"}
  >>> body[body.keys()[0]]
  Traceback (most recent call last):
File "", line 1, in 
  TypeError: 'dict_keys' object does not support indexing

  so for py3 compatible we should change it as follows:
  >>> body[list(body.keys())[0]]
  '22'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1583419/+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 1595416] [NEW] Add new config attribute to Radware driver

[Evgeny Fedoruk]

Public bug reported:

Need to add a new configuration attribute for Radware LBaaS v2 driver.
add_allowed_address_pairs

** Affects: neutron
 Importance: Undecided
 Assignee: Evgeny Fedoruk (evgenyf)
 Status: New


** Tags: lbaas

** Changed in: neutron
 Assignee: (unassigned) => Evgeny Fedoruk (evgenyf)

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

Title:
  Add new config attribute to Radware driver

Status in neutron:
  New

Bug description:
  Need to add a new configuration attribute for Radware LBaaS v2 driver.
  add_allowed_address_pairs

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