[Yahoo-eng-team] [Bug 1529836] Re: Fix deprecated library function (os.popen()).

[OpenStack Infra]

Reviewed:  https://review.openstack.org/263594
Committed: 
https://git.openstack.org/cgit/openstack/python-keystoneclient/commit/?id=13ade585c6e0212db8f89935f107e1d1718b59c3
Submitter: Jenkins
Branch:master

commit 13ade585c6e0212db8f89935f107e1d1718b59c3
Author: Yatin Kumbhare 
Date:   Tue Jan 5 12:30:29 2016 +0530

Fix for the deprecated library function

os.popen() is deprecated since version 2.6. Resolved with use of
subprocess module.

Change-Id: I53c21d6e8a9d23646c236ae33d652f1aefc20153
Closes-Bug: #1529836


** Changed in: python-keystoneclient
   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/1529836

Title:
  Fix deprecated library function (os.popen()).

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in heat:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  In Progress
Status in python-keystoneclient:
  Fix Released
Status in Sahara:
  In Progress
Status in senlin:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in zaqar:
  In Progress

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1529836/+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 1529836] Re: Fix deprecated library function (os.popen()).

[OpenStack Infra]

Reviewed:  https://review.openstack.org/265590
Committed: 
https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=0a718818f4d7f4bc1ab745eb3081321ef6cf9a3a
Submitter: Jenkins
Branch:master

commit 0a718818f4d7f4bc1ab745eb3081321ef6cf9a3a
Author: LiuNanke 
Date:   Sun Jan 10 04:22:34 2016 +0800

Replace deprecated library function os.popen() with subprocess

os.popen() is deprecated since version 2.6. Resolved with use of
subprocess module.
Closes-bug: #1529836

Change-Id: I61cf2ff6ef939b97c1c70325e15b89a47e5646e4


** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1529836

Title:
  Fix deprecated library function (os.popen()).

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in heat:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  In Progress
Status in python-keystoneclient:
  Fix Released
Status in Sahara:
  In Progress
Status in senlin:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in zaqar:
  Fix Released

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1529836/+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 1334523] Re: Cinder volume type delete return none informative error

[OpenStack Infra]

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

commit dfeb362b95f2b481ff3231b4821d4a5e94fa2e89
Author: Masco Kaliyamoorthy 
Date:   Mon Aug 17 19:12:23 2015 +0530

Adding informative message when deleting a used volume type

Currently when you try to delete a volume type (which is in use) Horizon
returns a generic message.

This patch includes in this message the text from the exception, resulting 
on
the following message:
'Error: Volume type '' is still in use.'

Change-Id: I9577127909dca70a4c45129bf5df7e11b6ab1c2f
Closes-bug: #1334523


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

Title:
  Cinder volume type delete return none informative error

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Description of problem: 
  Currently when you try to delete a volume type (which is in use) Horizon 
returns -> Error: Unable to delete volume type: ssd

  Notice on cinder api.log we get a better explanation->  "deletion
  failed, VolumeType in use.

  Improving Horizon's none informative error would be helpful.

  Version-Release number of selected component (if applicable):
  RHEL7
  openstack-dashboard-2014.1-7.el7ost.noarch

  How reproducible:
  Every time

  Steps to Reproduce:
  1. Create volume type
  2. Create a new volume, from volume type created above.
  3. On admin page, try to delete volume type (it should fail) but notice error 
message. 
  4. grep -ir error /var/log/cinder/api.log  -> will show cinder's better error 
notice.

  
  Actual results:
  Horizon returns -> Error: Unable to delete volume type: ssd
  None informative error.

  Expected results:
  Should return -> Error: Unable to delete volume type while it's still in use, 
volume type: ssd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1334523/+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 1532258] Re: neutronclient commands do not follow cliff command guideline

[OpenStack Infra]

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

commit c4aa41a25a7828adddcd0f314082b63e78a23676
Author: Akihiro Motoki 
Date:   Sat Jan 9 03:35:05 2016 +0900

Make neutron-debug command follow cliff command convention

In the guideline of cliff command, developers implementing
commands should override take_action() rather than run().
The similar effort is being done in neutronclient side and
this fix is required to complete the effort.

Logger definition in each command class is no longer needed.
This commit also drops them.

Closes-Bug: #1532258
Change-Id: I613b7e18b3c058568fc3669ad1524e60a93eb9f8


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

Title:
  neutronclient commands do not follow cliff command guideline

Status in neutron:
  Fix Released
Status in python-neutronclient:
  In Progress

Bug description:
  The docstring of cliff.command.Command says  that developers
  implementing commands should override take_action instead of run [1].

  neutornclient DeleteCommand and UpdateCommand override run().
  take_action() should be used.

  In addition, neutronclient.common.command.OpenStackCommand provides an
  extra and meaningless layer and interface get_data(). get_data()
  provides no addition value. take_action() should be used.
  CreateCommand, ShowCommand and ListCommand are affected.

  [1]
  https://github.com/openstack/cliff/blob/master/cliff/command.py#L39-L52

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1532258/+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 1532033] Re: test_create_floatingip_with_specified_ip_address is racey

[OpenStack Infra]

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

commit 9390dde943915da9fe0e21b8d4822a3f31a347cf
Author: Kevin Benton 
Date:   Thu Jan 7 15:40:27 2016 -0800

make floating IP specification test robust to races

The get_unused_ip function returns an address that isn't in use on
the network at the time it's called. However, by the time the caller
uses it, it may have been allocated to another concurrent test if
the network is shared or external.

The test_create_floatingip_with_specified_ip_address test creates
a floating IP with an unused IP on the external network, which has
lots of activity on it from other tests so it would occasionally
have its address taken by another test.

This patch just catches the in use error and tries again with a
new IP.

Change-Id: I5a2f78a6da1e400dea07949f35964abb767edbb2
Closes-Bug: #1532033


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

Title:
  test_create_floatingip_with_specified_ip_address is racey

Status in neutron:
  Fix Released

Bug description:
  test_create_floatingip_with_specified_ip_address gets an unused IP
  address and then tries to use it for an operation. The issue is that
  it gets it from an external network that other tests may be allocating
  ports from. So it can grab an IP and then another test can allocate a
  port that gets that IP before it tries it floating IP creation. In
  this case the floating IP creation will fail:

  Details: {u'message': u'Unable to complete operation for network
  477f7fb6-aea4-470c-82ca-c05936264e2e. The IP address 172.24.5.8 is in
  use.', u'detail': u'', u'type': u'IpAddressInUse'}

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1532033/+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 1519980] Re: Add advanced Availability Zone section to networking guide

[Armando Migliaccio]

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

Title:
  Add advanced Availability Zone section to networking guide

Status in neutron:
  Fix Released
Status in openstack-manuals:
  Fix Released

Bug description:
  https://review.openstack.org/204436
  commit 6e500278191296f75e6bd900b94f7e36cc69edf2
  Author: Hirofumi Ichihara 
  Date:   Thu Nov 19 15:05:27 2015 +0900

  Add availability_zone support for network
  
  This patch adds the availability_zone support for network.
  
  APIImpact
  DocImpact
  
  Change-Id: I9259d9679c74d3b3658771290e920a7896631e62
  Co-Authored-By: IWAMOTO Toshihiro 
  Partially-implements: blueprint add-availability-zone

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1519980/+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 1522525] Re: test_signature_utils tests fail when openssl is older than 1.0.1

[OpenStack Infra]

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

commit 2752fd6e161944f5875e4f4d0b4cdf4e178d05cd
Author: Brianna Poulos 
Date:   Wed Jan 6 17:16:33 2016 -0500

Catch UnsupportedAlgorithm exceptions

For signature verification, only SHA-2 family hash algorithms are
used.  Some older platforms, with an older version of openssl (older
than 1.0.1) do not support SHA-2 hashes.

This patch skips the signature verification unit tests that require
SHA-2 support on systems that do not have SHA-2 support.  It also
catches the UnsupportedAlgorithm exception that is generated when a
system that does not have SHA-2 support tries to verify the signature,
providing better feedback to the user.

Change-Id: I11b2366e96d49a5d502d6fccb0b6f620eb6c381d
Closes-Bug: 1522525


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

Title:
  test_signature_utils tests fail when openssl is older than 1.0.1

Status in Glance:
  Fix Released

Bug description:
  In liberty, initial support for image signature verification was added
  to glance (see spec at [1] and patch at [2]).  In this feature, if
  certain signature properties are provided when an image is uploaded,
  glance will perform verification on the signature.  This includes the
  certificate uuid, the hash method, the signature, and the signature
  type.

  The hash methods supported [3] are only in the SHA-2 family.  SHA-1 is
  not included, since it is no longer considered secure.

  There are some older platforms which do not support SHA-2 hashes,
  since they have an older version of openssl (older than 1.0.1).  When
  the test_signature_utils tests are run on such a platform, exceptions
  [4] are generated.

  The signature_utils class needs to be updated in order to catch these
  UnsupportedAlgorithm exceptions, and notify the user that signature
  verification cannot be performed due to an out-of-date openssl
  installation.

  Note that this issue was brought up during a glance drivers meeting
  [5] and a glance meeting [6].  It was also further discussed on the
  #openstack-glance IRC channel [7].

  [1] 
http://specs.openstack.org/openstack/glance-specs/specs/liberty/image-signing-and-verification-support.html
  [2] https://review.openstack.org/#/c/183137/
  [3] 
https://github.com/openstack/glance/blob/master/glance/common/signature_utils.py#L43-L48
  [4] http://paste.openstack.org/show/480800/
  [5] 
http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-12-03-13.59.html
  [6] 
http://eavesdrop.openstack.org/meetings/glance_drivers/2015/glance_drivers.2015-12-01-13.59.html
  [7] 
http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2015-12-03.log.html
 -- 17:32 to 17:54

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1522525/+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 1532542] Re: TypeError: _live_migration_copy_disk_paths() takes exactly 2 arguments (4 given)

[OpenStack Infra]

Reviewed:  https://review.openstack.org/266057
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=829ccf382189b77239489975aeef0a6c766296a0
Submitter: Jenkins
Branch:master

commit 829ccf382189b77239489975aeef0a6c766296a0
Author: Matt Riedemann 
Date:   Mon Jan 11 13:52:52 2016 -0800

libvirt: fix TypeError calling _live_migration_copy_disk_paths

f0d5fc61916f41214da580097a09136e4ed2c99a introduced a
TypeError with what looks like simply a bad rebase missed by
lack of adequate unit test coverage. The multinode job is
non-voting which doesn't help since reviewers missed the
failures it shows in the logs during the live migration tests.

This fixes the TypeError and adds very basic test coverage of
the call to the mocked method.

Change-Id: I9c3607b3efea70f011a60539d52eb09c03ff2850
Closes-Bug: #1532542


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

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

Title:
  TypeError: _live_migration_copy_disk_paths() takes exactly 2 arguments
  (4 given)

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  logstash query:
  (message:"(LiveBlockMigrationTestJSON:test_live_block_migration_paused)" OR 
message:"(LiveBlockMigrationTestJSON:test_live_block_migration)") AND 
message:"Current status: MIGRATING. Current task state: migrating."

  Example failure:
  
http://logs.openstack.org/98/265598/3/check/gate-tempest-dsvm-multinode-full/920b60a/logs/testr_results.html.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1532542/+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 1520255] Re: All linuxbridge agent tests executed with prevent_arp_spoofing=False

[OpenStack Infra]

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

commit 75dcd5f2ecbdc7491b520e3c317929e1e644b025
Author: Anand Shanmugam 
Date:   Tue Jan 5 10:35:05 2016 -0800

Add unit test cases for linuxbridge agent when prevent_arp_spoofing is True

Currently there is no test coverage for when prevent_arp_spoofing is set to 
true.
This fix address that issue.

Change-Id: Ie8bfa873120378dcdcb9d43e307daa5d55c038f2
Closes-Bug: #1520255


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

Title:
  All linuxbridge agent tests executed with prevent_arp_spoofing=False

Status in neutron:
  Fix Released

Bug description:
  All testcases of the linuxbridge agent are executed with
  prevent_arp_spoofing=False.

  The solution is to add testcases that are executed with
  prevent_arp_spoofing=True. arp_protect should be mocked and it should
  be ensured, that it has been called.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1520255/+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 1532656] [NEW] Duplicated content in "Using Glance’s Image Public APIs" page

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In "Using Glance’s Image Public APIs", the content for the section:

"Retrieve Raw Image Data"
(http://docs.openstack.org/developer/glance/glanceapi.html#retrieve-raw-
image-data)

is simply a dupe of  the section:

"Retrieve Image Metadata"
(http://docs.openstack.org/developer/glance/glanceapi.html#retrieve-
image-metadata)

Please fix it with the correct documentation for retrieving image data.

Here is the text-snapshot of these two sections in case the live site is
not available for any reason: http://paste.openstack.org/show/483381/.

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: glance
-- 
Duplicated content in "Using Glance’s Image Public APIs" page
https://bugs.launchpad.net/bugs/1532656
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to Glance.

-- 
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 1532051] Re: api retries result in double notificaitons

[OpenStack Infra]

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

commit 447f4b14614988f38a26d5d1b8e439ad0a44d8ad
Author: Kevin Benton 
Date:   Thu Jan 7 17:27:52 2016 -0800

Move notifications before DB retry decorator

This patch moves the start notifications emitted in the API
layer ('network.create.start', etc) to before the DB retry
decorator. This prevents benign retry events from resending
notifications onto the message bus.

Change-Id: I8159692a107ede397a4abeff71310a99fffa4862
Closes-Bug: #1532051


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

Title:
  api retries result in double notificaitons

Status in neutron:
  Fix Released

Bug description:
  the db retry decorator in api/v2/base.py results in a notification for
  update.start or create.start being sent out on each retry. so a benign
  DB error results in multiple notifications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1532051/+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 1527759] Re: Default domain no longer lets keystone tenant-list work

[OpenStack Infra]

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

commit c75f39f3d6e4a2caa37322adcf2e296ec7c573c8
Author: Morgan Fainberg 
Date:   Thu Jan 7 15:18:03 2016 -0800

Revert "Validate domain ownership for v2 tokens"

This reverts commit c4723550aa95be403ff591dd132c9024549eff10.

This revert is being proposed as it breaks behavior that real-world
deployments rely on. The deployments requested the V2 token with
user_id and tenantId and then used the V2 token for the
non-default-domain user to access swift.

While the deployment is being encouraged to fix their code to use V3,
this is behavior that was supported and used.

This revert was done by hand due to the volume of change that has
occured to the tests since the original patch landed.

Conflicts (a lot of test refactoring):
keystone/tests/unit/test_v3_assignment.py
keystone/tests/unit/test_v3_auth.py
keystone/tests/unit/test_v3_identity.py

Change-Id: I4a303a5fcc8c2dacef5960e9e26ad9402f34a790
Closes-Bug: 1527759


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

Title:
  Default domain no longer lets keystone tenant-list work

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  We recently upgraded from kilo.0 to kilo.2 in our dev environment and
  noticed that keystone tenant-list is always failing for the admin
  user.

  Our config is as follows default domain is tied to read-only ldap
  (AD), a heat domain is created to use for trusts to handle the created
  heatstack users/passwords. Under kilo.0 everything was happy. Under
  kilo0.2 we get the following error:

  keystone tenant-list
  The request you have made requires authentication. (HTTP 401) (Request-ID: 
req-d30289f0-778d-4577-8150-7ddd5438ad9c)

  The main error message is:
  2015-12-16 17:07:36.493 20386 WARNING keystone.common.wsgi [-] Authorization 
failed. Non-default domain is not supported (Disable debug mode to suppress 
these details.) (Disable debug mode to suppress these details.) from 
10.224.48.132

  Looking at the differences between kilo.0 and kilo.2  it seems like:
  
https://github.com/openstack/keystone/commit/9dfad21201251364c6d205e8e79813bfe78e6107
  is the most likely culprit for this regression. However, I have not
  yet been able to test if reverting that change fixes the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1527759/+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 1374999] Re: iSCSI volume detach does not correctly remove the multipath device descriptors

[Billy Olsen]

** Also affects: cloud-archive
   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/1374999

Title:
  iSCSI volume detach does not correctly remove the multipath device
  descriptors

Status in Ubuntu Cloud Archive:
  New
Status in OpenStack Compute (nova):
  In Progress
Status in nova package in Ubuntu:
  Triaged
Status in nova source package in Trusty:
  Triaged

Bug description:
  iSCSI volume detach does not correctly remove the multipath device
  descriptors

  tested environment:
  nova-compute on Ubuntu 14.04.1, iscsi_use_multipath=True and iSCSI volume 
backend is EMC VNX 5300.

   I created 3 cinder volumes and attached them to a nova instance. Then I 
detach them one by one. First 2 volumes volumes detached successfully.  3rd 
volume also successfully detached but ended up with  failed multipaths. 
  Here is the terminal log for last volume detach.

  openstack@W1DEV103:~/devstack$ cinder list
  
+--++--+--+-+--+--+
  |
   ID
   | Status | Name | Size | Volume Type | Bootable |
   Attached to
   |
  
+--++--+--+-+--+--+
  | 56a63288-5cc0-4f5c-9197-cde731172dd8 | in-use | None | 1 |
   None
   | false | 5bd68785-4acf-43ab-ae13-11b1edc3a62e |
  
+--++--+--+-+--+--+
  openstack@W1CN103:/etc/iscsi$ date;sudo multipath -l
  Fri Sep 19 21:38:13 JST 2014
  360060160cf0036002d1475f6e73fe411 dm-2 DGC,VRAID
  size=1.0G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
  |-+- policy='round-robin 0' prio=-1 status=active
  | |- 4:0:0:42 sdb 8:16 active undef running
  | |- 5:0:0:42 sdd 8:48 active undef running
  | |- 6:0:0:42 sdf 8:80 active undef running
  | `- 7:0:0:42 sdh 8:112 active undef running
  `-+- policy='round-robin 0' prio=-1 status=enabled
  |- 11:0:0:42 sdp 8:240 active undef running
  |- 8:0:0:42 sdj 8:144 active undef running
  |- 9:0:0:42 sdl 8:176 active undef running
  `- 10:0:0:42 sdn 8:208 active undef running
  openstack@W1CN103:/etc/iscsi$ date;sudo iscsiadm -m session
  Fri Sep 19 21:38:19 JST 2014
  tcp: [10] 172.23.58.228:3260,4 iqn.1992-04.com.emc:cx.fcn00133400150.a7
  tcp: [3] 172.23.58.238:3260,8 iqn.1992-04.com.emc:cx.fcn00133400150.b7
  tcp: [4] 172.23.58.235:3260,20 iqn.1992-04.com.emc:cx.fcn00133400150.b4
  tcp: [5] 172.23.58.236:3260,6 iqn.1992-04.com.emc:cx.fcn00133400150.b5
  tcp: [6] 172.23.58.237:3260,19 iqn.1992-04.com.emc:cx.fcn00133400150.b6
  tcp: [7] 172.23.58.225:3260,16 iqn.1992-04.com.emc:cx.fcn00133400150.a4
  tcp: [8] 172.23.58.226:3260,2 iqn.1992-04.com.emc:cx.fcn00133400150.a5
  tcp: [9] 172.23.58.227:3260,17 iqn.1992-04.com.emc:cx.fcn00133400150.a6

  openstack@W1DEV103:~/devstack$ nova volume-detach 
5bd68785-4acf-43ab-ae13-11b1edc3a62e
  56a63288-5cc0-4f5c-9197-cde731172dd8
  openstack@W1DEV103:~/devstack$
  openstack@W1DEV103:~/devstack$ cinder list
  
+--+---+--+--+-+--+--+
  |
   ID
   | Status | Name | Size | Volume Type | Bootable |
   Attached to
   |
  
+--+---+--+--+-+--+--+
  | 56a63288-5cc0-4f5c-9197-cde731172dd8 | detaching | None | 1 |
   None
   | false | 5bd68785-4acf-43ab-ae13-11b1edc3a62e|

  
+--+---+--+--+-+--+--+
  openstack@W1DEV103:~/devstack$
  openstack@W1DEV103:~/devstack$ cinder list
  
+--+---+--+--+-+--+-+
  |
   ID
   | Status | Name | Size | Volume Type | Bootable | Attached to |
  
+--+---+--+--+-+--+-+
  | 56a63288-5cc0-4f5c-9197-cde731172dd8 | available | None | 1 |
   None
   | false |
  
+--+---+--+--+-+--+-+
  |
  openstack@W1CN103:/etc/iscsi$ date;sudo multipath -l
  Fri Sep 19 21:39:23 JST 2014
  360060160cf0036002d1475f6e73fe411 dm-2 ,
  size=1.0G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
  |-+- policy='round-robin 0' prio=-1 status=active
  | |- #:#:#:# - #:# active undef running
  | |- #:#:#:# - #:# active undef running
  | |- #:#:#:# - #:# active undef running
  | `- #:#:#:# - #:# active undef running
  `-+- policy='round-robin 0' prio=-1 status=enabled
  |- #:#:#:# - #:# active undef running
  |- #:#:#:# - #:# active undef running
  |- #:#:#:# - #:# 

[Yahoo-eng-team] [Bug 1529836] Re: Fix deprecated library function (os.popen()).

[OpenStack Infra]

Reviewed:  https://review.openstack.org/265550
Committed: 
https://git.openstack.org/cgit/openstack/zaqar/commit/?id=5d228de79d074d8e4ab4bbf804bbf3d9e406ac6f
Submitter: Jenkins
Branch:master

commit 5d228de79d074d8e4ab4bbf804bbf3d9e406ac6f
Author: LiuNanke 
Date:   Sat Jan 9 21:55:24 2016 +0800

Replace deprecated library function os.popen() with subprocess

os.popen() is deprecated since version 2.6. Resolved with use of
subprocess module.
Closes-bug: #1529836

Change-Id: I3701a14026a85898bc01f3102369a2f87de56015


** Changed in: zaqar
   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/1529836

Title:
  Fix deprecated library function (os.popen()).

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in heat:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  In Progress
Status in python-keystoneclient:
  Fix Released
Status in Sahara:
  In Progress
Status in senlin:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in zaqar:
  Fix Released

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1529836/+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 1532656] Re: Duplicated content in "Using Glance’s Image Public APIs" page

[KATO Tomoyuki]

The pointed URL is the glance developer document. So, let me assign this
bug to glance project.

** Project changed: openstack-manuals => glance

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

Title:
  Duplicated content in "Using Glance’s Image Public APIs" page

Status in Glance:
  New

Bug description:
  In "Using Glance’s Image Public APIs", the content for the section:

  "Retrieve Raw Image Data"
  (http://docs.openstack.org/developer/glance/glanceapi.html#retrieve-
  raw-image-data)

  is simply a dupe of  the section:

  "Retrieve Image Metadata"
  (http://docs.openstack.org/developer/glance/glanceapi.html#retrieve-
  image-metadata)

  Please fix it with the correct documentation for retrieving image
  data.

  Here is the text-snapshot of these two sections in case the live site
  is not available for any reason:
  http://paste.openstack.org/show/483381/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1532656/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong

[Reedip]

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

** Changed in: python-solumclient
 Assignee: (unassigned) => Reedip (reedip-banerjee)

-- 
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 Barbican:
  In Progress
Status in Ceilometer:
  Invalid
Status in Cinder:
  Fix Released
Status in congress:
  In Progress
Status in Designate:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  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 python-ceilometerclient:
  Invalid
Status in python-cinderclient:
  Fix Released
Status in python-designateclient:
  Fix Committed
Status in python-mistralclient:
  Fix Released
Status in python-solumclient:
  New
Status in Python client library for Zaqar:
  Fix Released
Status in Sahara:
  Fix Released
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/barbican/+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 1277104] Re: wrong order of assertEquals args

[Reedip]

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

** Changed in: python-solumclient
 Assignee: (unassigned) => Reedip (reedip-banerjee)

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

Title:
  wrong order of assertEquals args

Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in oslo.messaging:
  Fix Released
Status in oslo.policy:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in Python client library for Sahara:
  Fix Released
Status in python-solumclient:
  New
Status in python-swiftclient:
  Won't Fix
Status in python-troveclient:
  Fix Released
Status in Rally:
  Confirmed
Status in Trove:
  Fix Released

Bug description:
  Args of assertEquals method in ceilometer.tests are arranged in wrong order. 
In result when test fails it shows incorrect information about observed and 
actual data. It's found more than 2000 times.
  Right order of arguments is "expected, actual".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1277104/+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 1374999] Re: iSCSI volume detach does not correctly remove the multipath device descriptors

[Corey Bryant]

** Also affects: cloud-archive/juno
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/icehouse
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/kilo
   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/1374999

Title:
  iSCSI volume detach does not correctly remove the multipath device
  descriptors

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive icehouse series:
  New
Status in Ubuntu Cloud Archive juno series:
  New
Status in Ubuntu Cloud Archive kilo series:
  New
Status in OpenStack Compute (nova):
  In Progress
Status in nova package in Ubuntu:
  Triaged
Status in nova source package in Trusty:
  Triaged

Bug description:
  iSCSI volume detach does not correctly remove the multipath device
  descriptors

  tested environment:
  nova-compute on Ubuntu 14.04.1, iscsi_use_multipath=True and iSCSI volume 
backend is EMC VNX 5300.

   I created 3 cinder volumes and attached them to a nova instance. Then I 
detach them one by one. First 2 volumes volumes detached successfully.  3rd 
volume also successfully detached but ended up with  failed multipaths. 
  Here is the terminal log for last volume detach.

  openstack@W1DEV103:~/devstack$ cinder list
  
+--++--+--+-+--+--+
  |
   ID
   | Status | Name | Size | Volume Type | Bootable |
   Attached to
   |
  
+--++--+--+-+--+--+
  | 56a63288-5cc0-4f5c-9197-cde731172dd8 | in-use | None | 1 |
   None
   | false | 5bd68785-4acf-43ab-ae13-11b1edc3a62e |
  
+--++--+--+-+--+--+
  openstack@W1CN103:/etc/iscsi$ date;sudo multipath -l
  Fri Sep 19 21:38:13 JST 2014
  360060160cf0036002d1475f6e73fe411 dm-2 DGC,VRAID
  size=1.0G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
  |-+- policy='round-robin 0' prio=-1 status=active
  | |- 4:0:0:42 sdb 8:16 active undef running
  | |- 5:0:0:42 sdd 8:48 active undef running
  | |- 6:0:0:42 sdf 8:80 active undef running
  | `- 7:0:0:42 sdh 8:112 active undef running
  `-+- policy='round-robin 0' prio=-1 status=enabled
  |- 11:0:0:42 sdp 8:240 active undef running
  |- 8:0:0:42 sdj 8:144 active undef running
  |- 9:0:0:42 sdl 8:176 active undef running
  `- 10:0:0:42 sdn 8:208 active undef running
  openstack@W1CN103:/etc/iscsi$ date;sudo iscsiadm -m session
  Fri Sep 19 21:38:19 JST 2014
  tcp: [10] 172.23.58.228:3260,4 iqn.1992-04.com.emc:cx.fcn00133400150.a7
  tcp: [3] 172.23.58.238:3260,8 iqn.1992-04.com.emc:cx.fcn00133400150.b7
  tcp: [4] 172.23.58.235:3260,20 iqn.1992-04.com.emc:cx.fcn00133400150.b4
  tcp: [5] 172.23.58.236:3260,6 iqn.1992-04.com.emc:cx.fcn00133400150.b5
  tcp: [6] 172.23.58.237:3260,19 iqn.1992-04.com.emc:cx.fcn00133400150.b6
  tcp: [7] 172.23.58.225:3260,16 iqn.1992-04.com.emc:cx.fcn00133400150.a4
  tcp: [8] 172.23.58.226:3260,2 iqn.1992-04.com.emc:cx.fcn00133400150.a5
  tcp: [9] 172.23.58.227:3260,17 iqn.1992-04.com.emc:cx.fcn00133400150.a6

  openstack@W1DEV103:~/devstack$ nova volume-detach 
5bd68785-4acf-43ab-ae13-11b1edc3a62e
  56a63288-5cc0-4f5c-9197-cde731172dd8
  openstack@W1DEV103:~/devstack$
  openstack@W1DEV103:~/devstack$ cinder list
  
+--+---+--+--+-+--+--+
  |
   ID
   | Status | Name | Size | Volume Type | Bootable |
   Attached to
   |
  
+--+---+--+--+-+--+--+
  | 56a63288-5cc0-4f5c-9197-cde731172dd8 | detaching | None | 1 |
   None
   | false | 5bd68785-4acf-43ab-ae13-11b1edc3a62e|

  
+--+---+--+--+-+--+--+
  openstack@W1DEV103:~/devstack$
  openstack@W1DEV103:~/devstack$ cinder list
  
+--+---+--+--+-+--+-+
  |
   ID
   | Status | Name | Size | Volume Type | Bootable | Attached to |
  
+--+---+--+--+-+--+-+
  | 56a63288-5cc0-4f5c-9197-cde731172dd8 | available | None | 1 |
   None
   | false |
  
+--+---+--+--+-+--+-+
  |
  openstack@W1CN103:/etc/iscsi$ date;sudo multipath -l
  Fri Sep 19 21:39:23 JST 2014
  360060160cf0036002d1475f6e73fe411 dm-2 ,
  size=1.0G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
  |-+- policy='round-robin 0' prio=-1 

[Yahoo-eng-team] [Bug 1532344] Re: lbaas:Remove OpenSSL from cert_parser

[OpenStack Infra]

Reviewed:  https://review.openstack.org/265457
Committed: 
https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=bb34d71c7772d1728d6ceaa04333856f8b6ea4d4
Submitter: Jenkins
Branch:master

commit bb34d71c7772d1728d6ceaa04333856f8b6ea4d4
Author: ptoohill1 
Date:   Fri Jan 8 16:33:19 2016 -0600

Remove OpenSSL from cert_parser

Utilize cryptography package instead of OpenSSL in the cert_parser

Change-Id: I66aa62d7f1f9ce1898bbb8593e4aedd1a1163137
Closes-Bug: #1532344


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

Title:
  lbaas:Remove OpenSSL from cert_parser

Status in neutron:
  Fix Released

Bug description:
  Utilize cryptography package instead of OpenSSL in the cert_parser

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1532344/+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 1531734] Re: Header Links are not working in Angularized Panels

[OpenStack Infra]

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

commit 6698d26fbaf68ab9c45ae267c27ba9644ef674c0
Author: Rajat Vig 
Date:   Wed Jan 6 22:53:38 2016 -0800

Set target to _self for Header Links

Angular Panels have enabled ngRoute and HTML5 which
allows Angular to handle routing which makes all
routes to pass via Angular.

Links that do not have route defintion as a result stop
working.
This can be fixed by specifying the target="_self" on the  tags.

This is already in place for the Sidebar. It needs to done for the
Header Links as well.

Closes-Bug: #1531734
Change-Id: Ida76b40fdf0b66ba3ee3af4d32701974c312af57


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

Title:
  Header Links are not working in Angularized Panels

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Location Provider is now set in Horizon which now allows for HTML5
  based routing.

  This implies all links on an Angular Panel which aren't routed in Angular 
using $routeProvider no longer work.
  This can be fixed by specifying the target="_self" on the  tags. 

  This is already in place for the Sidebar. It needs to done for the
  Header Links as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1531734/+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 1533013] [NEW] L2pop raises exception when deleting an unbound port

[Assaf Muller]

Public bug reported:

Some brilliant individual introduced a regression during a refactor
(https://review.openstack.org/#/c/263471/) that causes an exception to
be raised when an unbound port is deleted. For example:

neutron port-create --name=port some_network
neutron port-delete port
Deleted port: port

In the neutron-server log we can see:
http://paste.openstack.org/show/483517/

Apart from the scary TRACE there's no real implications. What should
have happened is an early return, so the l2pop mech driver shouldn't be
doing anything in this case, and it's spamming the log with bogus
information instead.

** Affects: neutron
 Importance: Low
 Assignee: Assaf Muller (amuller)
 Status: In Progress


** Tags: l2-pop

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

Title:
  L2pop raises exception when deleting an unbound port

Status in neutron:
  In Progress

Bug description:
  Some brilliant individual introduced a regression during a refactor
  (https://review.openstack.org/#/c/263471/) that causes an exception to
  be raised when an unbound port is deleted. For example:

  neutron port-create --name=port some_network
  neutron port-delete port
  Deleted port: port

  In the neutron-server log we can see:
  http://paste.openstack.org/show/483517/

  Apart from the scary TRACE there's no real implications. What should
  have happened is an early return, so the l2pop mech driver shouldn't
  be doing anything in this case, and it's spamming the log with bogus
  information instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1533013/+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 1532542] Re: multinode-full's test_live_block_migration and test_live_block_migration_paused are broken

[Matt Riedemann]

** No longer affects: tempest

** Changed in: nova
 Assignee: (unassigned) => Matt Riedemann (mriedem)

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

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

** Summary changed:

- multinode-full's test_live_block_migration and 
test_live_block_migration_paused are broken
+ TypeError: _live_migration_copy_disk_paths() takes exactly 2 arguments (4 
given)

** Tags removed: testing
** Tags added: libvirt live-migration

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

Title:
  TypeError: _live_migration_copy_disk_paths() takes exactly 2 arguments
  (4 given)

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  logstash query:
  (message:"(LiveBlockMigrationTestJSON:test_live_block_migration_paused)" OR 
message:"(LiveBlockMigrationTestJSON:test_live_block_migration)") AND 
message:"Current status: MIGRATING. Current task state: migrating."

  Example failure:
  
http://logs.openstack.org/98/265598/3/check/gate-tempest-dsvm-multinode-full/920b60a/logs/testr_results.html.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1532542/+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 1529561] [NEW] Not able to delete duplicate security groups by name

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

If there are two security group with duplicate name and if we are trying
to delete using the command nova secgroup-delete  it gives the
below error :-

ERROR (NoUniqueMatch): Multiple security group matches found for name
'NEC', use an ID to be more specific.

Expected result:-
Should not allow to create security group with duplicate name.

** Affects: neutron
 Importance: Undecided
 Status: In Progress

-- 
Not able to delete duplicate security groups by name
https://bugs.launchpad.net/bugs/1529561
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to neutron.

-- 
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 1529561] Re: Not able to delete duplicate security groups by name

[Shashi]

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

** Project changed: packstack => neutron

** Changed in: neutron
 Assignee: (unassigned) => Shashi (shashi-kant)

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

Title:
  Not able to delete duplicate security groups by name

Status in neutron:
  In Progress

Bug description:
  If there are two security group with duplicate name and if we are
  trying to delete using the command nova secgroup-delete  it
  gives the below error :-

  ERROR (NoUniqueMatch): Multiple security group matches found for name
  'NEC', use an ID to be more specific.

  Expected result:-
  Should not allow to create security group with duplicate name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1529561/+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 1532750] [NEW] VMware: unable to spin up instance as network not created on host

[Gary Kotton]

Public bug reported:

When using Neutron there are edge cases when the network created by
Neutron has not yet been created on the actual host. This results in the
VM creation failing as the network is still to be created on the host:

2016-01-08 20:56:29.486 ^[[00;32mDEBUG oslo_vmware.exceptions 
[^[[00;36m-^[[00;32m] ^[[01;35m^[[00;32mFault InvalidDeviceSpec not 
matched.^[[00m ^[[00;33mfrom (pid=28979) get_fault_class 
/usr/local/lib/python2.7/dist-packages/oslo_vmware/exceptions.py:295^[[00m
2016-01-08 20:56:29.486 ^[[01;31mERROR oslo_vmware.common.loopingcall 
[^[[00;36m-^[[01;31m] ^[[01;35m^[[01;31min fixed duration looping call^[[00m
^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00mTraceback (most recent call last):
^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00m  File 
"/usr/local/lib/python2.7/dist-packages/oslo_vmware/common/loopingcall.py", 
line 76, in _inner
^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00mself.f(*self.args, **self.kw)
^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00m  File 
"/usr/local/lib/python2.7/dist-packages/oslo_vmware/api.py", line 428, in 
_poll_task
^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00mraise task_ex
^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00mVimFaultException: Invalid configuration for device '0'.
^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00mFaults: ['InvalidDeviceSpec']
^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00m
 
Adding a retry will successfully address this - giving the actual host time to 
create the network

** Affects: nova
 Importance: High
 Assignee: Gary Kotton (garyk)
 Status: In Progress


** Tags: liberty-backport-potential vmware

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

** Tags added: liberty-backport-potential vmware

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

Title:
  VMware: unable to spin up instance as network not created on host

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  When using Neutron there are edge cases when the network created by
  Neutron has not yet been created on the actual host. This results in
  the VM creation failing as the network is still to be created on the
  host:

  2016-01-08 20:56:29.486 ^[[00;32mDEBUG oslo_vmware.exceptions 
[^[[00;36m-^[[00;32m] ^[[01;35m^[[00;32mFault InvalidDeviceSpec not 
matched.^[[00m ^[[00;33mfrom (pid=28979) get_fault_class 
/usr/local/lib/python2.7/dist-packages/oslo_vmware/exceptions.py:295^[[00m
  2016-01-08 20:56:29.486 ^[[01;31mERROR oslo_vmware.common.loopingcall 
[^[[00;36m-^[[01;31m] ^[[01;35m^[[01;31min fixed duration looping call^[[00m
  ^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00mTraceback (most recent call last):
  ^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00m  File 
"/usr/local/lib/python2.7/dist-packages/oslo_vmware/common/loopingcall.py", 
line 76, in _inner
  ^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00mself.f(*self.args, **self.kw)
  ^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00m  File 
"/usr/local/lib/python2.7/dist-packages/oslo_vmware/api.py", line 428, in 
_poll_task
  ^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00mraise task_ex
  ^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00mVimFaultException: Invalid configuration for device '0'.
  ^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00mFaults: ['InvalidDeviceSpec']
  ^[[01;31m2016-01-08 20:56:29.486 TRACE oslo_vmware.common.loopingcall 
^[[01;35m^[[00m
   
  Adding a retry will successfully address this - giving the actual host time 
to create the network

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1532750/+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 1529836] Re: Fix deprecated library function (os.popen()).

[lei zhang]

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

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

** Changed in: senlin
 Assignee: (unassigned) => lei zhang (zhang-lei)

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

Title:
  Fix deprecated library function (os.popen()).

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in heat:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in Manila:
  Fix Released
Status in Murano:
  In Progress
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  In Progress
Status in python-keystoneclient:
  In Progress
Status in senlin:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in zaqar:
  In Progress

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1529836/+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 1532696] [NEW] Created same SG rule to one SG in case of neutron server active-active

[Nam]

Public bug reported:

I had three controller. i found a bug, i can create same security group
rules to one security group at same timing

How to reproduce:

Topology:  http://codepad.org/ff0debPB

Step 1: Create on security group:
$ neutron security-group-create test-secgroup

Step 2: Create multiple security-group-rules that specifying same attributes
Please run following command from multiple servers at same timing.
-  On controller1:
$ neutron security-group-rule-create test-secgroup
- On controller2:
$ neutron security-group-rule-create test-secgroup

After check database: http://codepad.org/zFogYuVA
Please focus on record number 03 (line 06) and record number 12 (line 15)

** Affects: neutron
 Importance: Undecided
 Assignee: Nam (namnh)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => Nam (namnh)

** Description changed:

  I had three controller. i found a bug, i can create same security group
  rules to one security group at same timing
  
  How to reproduce:
  
- Topology:  http://codepad.org/WocbNR3d
+ Topology:  http://codepad.org/ff0debPB
  
  Step 1: Create on security group:
  $ neutron security-group-create test-secgroup
  
  Step 2: Create multiple security-group-rules that specifying same attributes
  Please run following command from multiple servers at same timing.
  -  On controller1:
  $ neutron security-group-rule-create test-secgroup
  - On controller2:
  $ neutron security-group-rule-create test-secgroup
  
  After check database: http://codepad.org/zFogYuVA
  Please focus on record number 03 and record number 12

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

Title:
  Created same SG rule to one SG  in case of neutron server active-
  active

Status in neutron:
  New

Bug description:
  I had three controller. i found a bug, i can create same security
  group rules to one security group at same timing

  How to reproduce:

  Topology:  http://codepad.org/ff0debPB

  Step 1: Create on security group:
  $ neutron security-group-create test-secgroup

  Step 2: Create multiple security-group-rules that specifying same attributes
  Please run following command from multiple servers at same timing.
  -  On controller1:
  $ neutron security-group-rule-create test-secgroup
  - On controller2:
  $ neutron security-group-rule-create test-secgroup

  After check database: http://codepad.org/zFogYuVA
  Please focus on record number 03 (line 06) and record number 12 (line 15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1532696/+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 1529836] Re: Fix deprecated library function (os.popen()).

[Bo Chi]

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

** Changed in: sahara
 Assignee: (unassigned) => Bo Chi (bochi-michael)

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

Title:
  Fix deprecated library function (os.popen()).

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in heat:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in Manila:
  Fix Released
Status in Murano:
  In Progress
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  In Progress
Status in python-keystoneclient:
  In Progress
Status in Sahara:
  In Progress
Status in senlin:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in zaqar:
  In Progress

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1529836/+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 1532695] Re: Created subnets on ONE network that duplicated CIDR in case of neutron server active-active

[Lubosz Kosnik]

** This bug is no longer a duplicate of bug 1271171
   Neutron allows overlapping IPs in the same tenant

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

Title:
  Created subnets on ONE network that duplicated CIDR  in case of
  neutron server active-active

Status in neutron:
  New

Bug description:
  I had three controllers.  I found a bug. I can create subnets on one
  network that duplicated CIDR range AT SAME TIMING

  How to reproduce:

  Topology : http://codepad.org/ff0debPB

  Step 1: Create a network
  $ neutron net-create test-net

  Step 2: Create multiple subnets that duplicated CIDR scope
  Please running commands AT SAME TIMMING
   - On controller1:
  $ neutron subnet-create --name test-subnet1 test-net 192.168.100.0/24
   - On controller2:
  $ neutron subnet-create --name test-subnet2 test-net 192.168.100.0/24

  After check subnet-list:

  Running command: $ neutron subnet-list
  This is the result: http://codepad.org/3hyHy8Lk

  After check database:
  This is the result: http://codepad.org/WJVJYLDn

  I think. In originally, one command on controller will be fail and we
  catch a message as following: "Invalid input for operation: Requested
  subnet with cidr: 192.168.0.0/16 for network: 39cc0850-1eeb-4c85-bcdc-
  338a3f1461aa overlaps with another subnet.". But currently, two
  commands are success

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

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

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

[OpenStack Infra]

Reviewed:  https://review.openstack.org/263588
Committed: 
https://git.openstack.org/cgit/openstack/cloudkitty/commit/?id=f806413b4c31368e7c4f79030536ce4e4b4ce3c7
Submitter: Jenkins
Branch:master

commit f806413b4c31368e7c4f79030536ce4e4b4ce3c7
Author: Swapnil Kulkarni (coolsvap) 
Date:   Tue Jan 5 12:21:12 2016 +0530

Replace deprecated LOG.warn with LOG.warning

LOG.warn is deprecated. It still used in a few places.
Updated to non-deprecated LOG.warning.

Change-Id: I402398b1130f18c91bb0c4fa7f677181089dcd29
Closes-Bug:#1508442


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

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

Title:
  LOG.warn is deprecated

Status in Aodh:
  In Progress
Status in Astara:
  In Progress
Status in Blazar:
  In Progress
Status in Ceilometer:
  Fix Released
Status in cloud-init:
  In Progress
Status in cloudkitty:
  Fix Released
Status in Designate:
  In Progress
Status in django-openstack-auth:
  In Progress
Status in DragonFlow:
  Fix Released
Status in Glance:
  In Progress
Status in Gnocchi:
  In Progress
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in Ironic Inspector:
  Fix Released
Status in ironic-lib:
  Fix Committed
Status in ironic-python-agent:
  Fix Released
Status in OpenStack Identity (keystone):
  In Progress
Status in kolla:
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-cisco:
  In Progress
Status in networking-odl:
  In Progress
Status in networking-ofagent:
  In Progress
Status in networking-vsphere:
  In Progress
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  In Progress
Status in nova-powervm:
  Fix Released
Status in octavia:
  In Progress
Status in openstack-ansible:
  In Progress
Status in oslo.cache:
  Fix Released
Status in oslo.privsep:
  In Progress
Status in Packstack:
  Fix Released
Status in python-magnumclient:
  Fix Released
Status in Solum:
  In Progress
Status in tempest:
  In Progress
Status in tripleo:
  In Progress
Status in tuskar:
  In Progress
Status in zaqar:
  In Progress

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

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

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

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

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

[Yahoo-eng-team] [Bug 1532695] [NEW] Created subnets on one network that duplicated CIDR in case of neutron server active-active

[Nam]

Public bug reported:

I had three controllers.  I found a bug. I can create subnets on one
network that duplicated CIDR range at same timing

How to reproduce:

Topology : http://codepad.org/ff0debPB

Step 1: Create a network
$ neutron net-create test-net

Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
 - On controller1:
$ neutron subnet-create --name test-subnet1 test-net 192.168.100.0/24
 - On controller2:
$ neutron subnet-create --name test-subnet2 test-net 192.168.100.0/16

After check database: http://codepad.org/MgVnOeJT

** Affects: neutron
 Importance: Undecided
 Assignee: Nam (namnh)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => Nam (namnh)

** Description changed:

  I had three controllers.  I found a bug. I can create subnets on one
  network that duplicated CIDR range at same timing
  
  How to reproduce:
  
- Topology : http://codepad.org/WocbNR3d
+ Topology : http://codepad.org/ff0debPB
  
  Step 1: Create a network
  $ neutron net-create test-net
  
  Step 2: Create multiple subnets that duplicated CIDR scope
  Please running commands at same timing
-  - On controller1:
+  - On controller1:
  $ neutron subnet-create --name test-subnet1 test-net 192.168.100.0/24
-  - On controller2:
+  - On controller2:
  $ neutron subnet-create --name test-subnet2 test-net 192.168.100.0/16
  
  After check database: http://codepad.org/MgVnOeJT

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

Title:
  Created subnets on one network that duplicated CIDR  in case of
  neutron server active-active

Status in neutron:
  New

Bug description:
  I had three controllers.  I found a bug. I can create subnets on one
  network that duplicated CIDR range at same timing

  How to reproduce:

  Topology : http://codepad.org/ff0debPB

  Step 1: Create a network
  $ neutron net-create test-net

  Step 2: Create multiple subnets that duplicated CIDR scope
  Please running commands at same timing
   - On controller1:
  $ neutron subnet-create --name test-subnet1 test-net 192.168.100.0/24
   - On controller2:
  $ neutron subnet-create --name test-subnet2 test-net 192.168.100.0/16

  After check database: http://codepad.org/MgVnOeJT

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1532695/+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 1458471] Re: get_router_for_floatingip does not check if router is default gateway

[Sreekumar S]

*** This bug is a duplicate of bug 1470765 ***
https://bugs.launchpad.net/bugs/1470765

** This bug has been marked a duplicate of bug 1470765
   multiple routers per subent cause a wrong placement of floating ips

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

Title:
  get_router_for_floatingip does not check if router is default gateway

Status in neutron:
  In Progress

Bug description:
  In the function db._get_router_for_floatingip() we check that the
  router has a suitable gateway IP, but we do not check if that router
  is the default gateway for that subnet.  When multiple routers exist
  with ip addresses in both the subnet for the instance, plus the
  gateway subnet, the function returns the first router it finds rather
  than the one that instances are using as default gateway.

  Can we check a condition such as router_gw_qry.floating_ip ==
  subnet_db['gateway_ip'] in addition to checking has_gw_port?

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

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

[Yahoo-eng-team] [Bug 1517839] Re: Make CONF.set_override with paramter enforce_type=True by default

[Chaozhe Chen]

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

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

** Changed in: cloudkitty
 Assignee: (unassigned) => Chaozhe Chen (chaozhe-chen)

** Changed in: ceilometer
 Assignee: (unassigned) => Chaozhe Chen (chaozhe-chen)

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

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

Status in Ceilometer:
  New
Status in cloudkitty:
  New
Status in Gnocchi:
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in oslo.config:
  New
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Released

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

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

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

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

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

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

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

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

[Yahoo-eng-team] [Bug 1532695] Re: Created subnets on one network that duplicated CIDR in case of neutron server active-active

[Lubosz Kosnik]

*** This bug is a duplicate of bug 1271171 ***
https://bugs.launchpad.net/bugs/1271171

** This bug has been marked a duplicate of bug 1271171
   Neutron allows overlapping IPs in the same tenant

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

Title:
  Created subnets on one network that duplicated CIDR  in case of
  neutron server active-active

Status in neutron:
  New

Bug description:
  I had three controllers.  I found a bug. I can create subnets on one
  network that duplicated CIDR range at same timing

  How to reproduce:

  Topology : http://codepad.org/ff0debPB

  Step 1: Create a network
  $ neutron net-create test-net

  Step 2: Create multiple subnets that duplicated CIDR scope
  Please running commands at same timing
   - On controller1:
  $ neutron subnet-create --name test-subnet1 test-net 192.168.100.0/24
   - On controller2:
  $ neutron subnet-create --name test-subnet2 test-net 192.168.100.0/24

  After check subnet-list:

  Running command: $ neutron subnet-list
  This is the result: http://codepad.org/3hyHy8Lk

  After check database:
  This is the result: http://codepad.org/WJVJYLDn

  I think. In originally, one command on controller will be fail and we
  catch a message as following: "Invalid input for operation: Requested
  subnet with cidr: 192.168.0.0/16 for network: 39cc0850-1eeb-4c85-bcdc-
  338a3f1461aa overlaps with another subnet.". But currently, two
  commands are success

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1532695/+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 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()

[OpenStack Infra]

Reviewed:  https://review.openstack.org/264097
Committed: 
https://git.openstack.org/cgit/openstack/sahara/commit/?id=0632881948bbe37fb3638fa7a6c83f27e163302d
Submitter: Jenkins
Branch:master

commit 0632881948bbe37fb3638fa7a6c83f27e163302d
Author: yangyapeng 
Date:   Mon Jan 4 17:35:17 2016 -0500

Change assertTrue(isinstance()) by optimal assert

Some of tests use different method of assertTrue(isinstance(A, B)),
The correct way is to use assertIsInstance(A,B) provided by testtools

Change-Id: I3ae21a25e5fea904401d45d1a5de4db19c45169e
Closes-bug: #1268480


** Changed in: sahara
   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/1268480

Title:
  assertTrue(isinstance()) in tests should be replace with
  assertIsInstance()

Status in Barbican:
  In Progress
Status in Ceilometer:
  Fix Released
Status in Cinder:
  In Progress
Status in CloudRoast:
  In Progress
Status in congress:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Monasca:
  In Progress
Status in Murano:
  In Progress
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-keystoneclient:
  Fix Released
Status in python-manilaclient:
  In Progress
Status in python-novaclient:
  Fix Released
Status in OpenStack SDK:
  Fix Released
Status in python-tuskarclient:
  In Progress
Status in Rally:
  In Progress
Status in Sahara:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in Trove:
  Fix Released

Bug description:
  some of tests use different method of assertTrue(isinstance(A, B)) or
  assertEqual(type(A), B). The correct way is to use assertIsInstance(A,
  B) provided by testtools

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1268480/+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 1532745] [NEW] Wrong links in Service Providers filtering API docs

[Marek Denis]

Public bug reported:

Some of the links in the Service Providers filtering API docs are
incorrect.

** Affects: keystone
 Importance: Low
 Assignee: Marek Denis (marek-denis)
 Status: In Progress


** Tags: documentation

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

Title:
  Wrong links in Service Providers filtering API docs

Status in OpenStack Identity (keystone):
  In Progress

Bug description:
  Some of the links in the Service Providers filtering API docs are
  incorrect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1532745/+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 1529836] Re: Fix deprecated library function (os.popen()).

[OpenStack Infra]

Reviewed:  https://review.openstack.org/262731
Committed: 
https://git.openstack.org/cgit/openstack/keystone/commit/?id=114f72f286888eee7c935470e9795099c41d64db
Submitter: Jenkins
Branch:master

commit 114f72f286888eee7c935470e9795099c41d64db
Author: Harshada Mangesh Kakad 
Date:   Thu Dec 31 02:00:15 2015 -0800

Replace deprecated library function os.popen() with subprocess

os.popen() is deprecated since version 2.6. Resolved with use of
subprocess module.

Change-Id: Id8edeb60aa32f556b58ed0397d27598c39945241
Closes-Bug: #1529836


** 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 Compute (nova).
https://bugs.launchpad.net/bugs/1529836

Title:
  Fix deprecated library function (os.popen()).

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in heat:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Murano:
  In Progress
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  In Progress
Status in python-keystoneclient:
  In Progress
Status in Sahara:
  In Progress
Status in senlin:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in zaqar:
  In Progress

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1529836/+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 1533024] [NEW] Lazy load tabs broken by element

[Thai Tran]

Public bug reported:

We introduced  tag recently which broke all lazy loaded tabs. It
changed tab url request to originate from base instead of the current
page.

 
http://localhost:8001/project/instances/3282eaec-569c-40b7-8f82-fd37d86a50ca/?tab=instance_details__audit
 -->
 http://localhost:8001/?tab=instance_details__audit

Visit instances details or volumes page to see this behavior.

** Affects: horizon
 Importance: Critical
 Assignee: Thai Tran (tqtran)
 Status: In Progress

** Description changed:

  We introduced  tag recently which broke all lazy loaded tabs. It
  changed tab url request to originate from base instead of the current
  page.
  
-  
http://localhost:8001/project/instances/3282eaec-569c-40b7-8f82-fd37d86a50ca/?tab=instance_details__audit
 -->
-  http://localhost:8001/?tab=instance_details__audit
+  
http://localhost:8001/project/instances/3282eaec-569c-40b7-8f82-fd37d86a50ca/?tab=instance_details__audit
 -->
+  http://localhost:8001/?tab=instance_details__audit
+ 
+ Visit instances details or volumes page to see this behavior.

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

Title:
  Lazy load tabs broken by  element

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  We introduced  tag recently which broke all lazy loaded tabs. It
  changed tab url request to originate from base instead of the current
  page.

   
http://localhost:8001/project/instances/3282eaec-569c-40b7-8f82-fd37d86a50ca/?tab=instance_details__audit
 -->
   http://localhost:8001/?tab=instance_details__audit

  Visit instances details or volumes page to see this behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1533024/+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 1522735] Re: Instance failure shows redundant data in overview page

[Tony Breeds]

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

** Tags added: quotas

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

Title:
  Instance failure shows redundant data in overview page

Status in OpenStack Dashboard (Horizon):
  Won't Fix
Status in OpenStack Compute (nova):
  New

Bug description:
  The overview section displays incorrect limit summary details when an 
instance creation has failed.
  I try to create an instance that needs 8192MB RAM and 4VCPUs (m1.large).
  The instance creations fails with an error status.
  Meanwhile the overview page shows instance, VCPUs and RAM summary 
details.(This should ideally be empty as the instance creation was 
unsuccessful).

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1522735/+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 1521477] Re: OFAgent deprecation and removal

[fumihiko kakuma]

Fix proposed to branch: master
Review: https://review.openstack.org/265075

** Also affects: openstack-manuals
   Importance: Undecided
   Status: New

** Changed in: openstack-manuals
 Assignee: (unassigned) => fumihiko kakuma (kakuma)

** Changed in: openstack-manuals
   Status: New => In Progress

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

Title:
  OFAgent deprecation and removal

Status in networking-ofagent:
  New
Status in neutron:
  In Progress
Status in openstack-manuals:
  In Progress

Bug description:
  The ryu team plans to deprecate the OFAgent mechanism driver and its agent in 
Mitaka
  and to remove them in the next N cycle.

  This bug report is intended to track it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-ofagent/+bug/1521477/+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 1533079] [NEW] Removal of EC2 code

[Christian Berendt]

Public bug reported:

Some time ago the EC2 code inside Nova was deprecated and will be
removed during Mitaka. With https://review.openstack.org/#/c/226856/ the
EC2 API is not longer enabled by default.

Because the EC2 API is not longer enabled by default I think we have to
remove the EC2 service/user from the tools/sample_data.sh script, the
endpoint from the etc/default_catalog.templates file, the EC2 service
from the doc/source/configuringservices.rst documentation file.

I am not sure about keystone.contrib.ec2. Also I am not sure about EC2
specifc test cases in keystone.tests. Are they required by the new
ec2-api project?

** Affects: keystone
 Importance: Undecided
 Status: New

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

Title:
  Removal of EC2 code

Status in OpenStack Identity (keystone):
  New

Bug description:
  Some time ago the EC2 code inside Nova was deprecated and will be
  removed during Mitaka. With https://review.openstack.org/#/c/226856/
  the EC2 API is not longer enabled by default.

  Because the EC2 API is not longer enabled by default I think we have
  to remove the EC2 service/user from the tools/sample_data.sh script,
  the endpoint from the etc/default_catalog.templates file, the EC2
  service from the doc/source/configuringservices.rst documentation
  file.

  I am not sure about keystone.contrib.ec2. Also I am not sure about EC2
  specifc test cases in keystone.tests. Are they required by the new
  ec2-api project?

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1533079/+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 1482773] Re: H405 violations: multi line docstring summary not separated with an empty line

[Steve Martinelli]

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

Title:
  H405 violations: multi line docstring summary not separated with an
  empty line

Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Released
Status in python-keystoneclient:
  Triaged

Bug description:
  Keystone's tox.ini contains an "ignore" entry for H405. All violations
  of H405 should be fixed so that H405 can be removed from the ignore
  list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1482773/+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 1533083] [NEW] useless HTTP info in the error info for creating existing flavor

[ibm-cloud-qa]

Public bug reported:

[Summary]
useless HTTP info in the error info for creating existing flavor
[Topo]
devstack all-in-one node

[Description and expect result]
no useless HTTP info in the error info for creating existing flavor

[Reproduceable or not]
reproduceable 

[Recreate Steps]
1) create an existing flavor:
root@45-59:/opt/stack/devstack# nova flavor-create --is-public
 false f1 13 1024 1 1
ERROR (Conflict): Flavor with name f1 already exists. (HTTP 409) 
(Request-ID: req-3769491c-5f82-4064-8b45-ef1a3442957d)
root@45-59:/opt/stack/devstack# 

ISSUE: For a cli user, the info "ERROR (Conflict): Flavor with name
 f1 already exists." is enough, it let user know what happened. 
But the info "HTTP 409" is useless

2) same issue when remove a non-existing flavor-access:
root@45-59:/opt/stack/devstack# nova  flavor-access-remove 13 adminm
ERROR (NotFound): Flavor access not found for 13 / adminm combination.
 (HTTP 404) (Request-ID: req-2eeb9656-72a9-45d8-bbe0-48536c8e0b5d)
root@45-59:/opt/stack/devstack# 

3)Below is the error info when remove a non-existing flavor for reference:
root@45-59:/opt/stack/devstack# nova flavor-delete aa
ERROR (CommandError): No flavor with a name or ID of 'aa' exists.
root@45-59:/opt/stack/devstack# 


[Configration]
reproduceable bug, no need

[logs]
reproduceable bug, no need

[Root cause anlyze or debug inf]
reproduceable bug

[Attachment]
None

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

Title:
  useless HTTP info in the error info for creating existing flavor

Status in OpenStack Compute (nova):
  New

Bug description:
  [Summary]
  useless HTTP info in the error info for creating existing flavor
  [Topo]
  devstack all-in-one node

  [Description and expect result]
  no useless HTTP info in the error info for creating existing flavor

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) create an existing flavor:
  root@45-59:/opt/stack/devstack# nova flavor-create --is-public
   false f1 13 1024 1 1
  ERROR (Conflict): Flavor with name f1 already exists. (HTTP 409) 
  (Request-ID: req-3769491c-5f82-4064-8b45-ef1a3442957d)
  root@45-59:/opt/stack/devstack# 

  ISSUE: For a cli user, the info "ERROR (Conflict): Flavor with name
   f1 already exists." is enough, it let user know what happened. 
  But the info "HTTP 409" is useless

  2) same issue when remove a non-existing flavor-access:
  root@45-59:/opt/stack/devstack# nova  flavor-access-remove 13 adminm
  ERROR (NotFound): Flavor access not found for 13 / adminm combination.
   (HTTP 404) (Request-ID: req-2eeb9656-72a9-45d8-bbe0-48536c8e0b5d)
  root@45-59:/opt/stack/devstack# 

  3)Below is the error info when remove a non-existing flavor for reference:
  root@45-59:/opt/stack/devstack# nova flavor-delete aa
  ERROR (CommandError): No flavor with a name or ID of 'aa' exists.
  root@45-59:/opt/stack/devstack# 


  [Configration]
  reproduceable bug, no need

  [logs]
  reproduceable bug, no need

  [Root cause anlyze or debug inf]
  reproduceable bug

  [Attachment]
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533083/+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 1522735] Re: Instance failure shows redundant data in overview page

[Richard Jones]

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

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

Title:
  Instance failure shows redundant data in overview page

Status in OpenStack Dashboard (Horizon):
  Won't Fix

Bug description:
  The overview section displays incorrect limit summary details when an 
instance creation has failed.
  I try to create an instance that needs 8192MB RAM and 4VCPUs (m1.large).
  The instance creations fails with an error status.
  Meanwhile the overview page shows instance, VCPUs and RAM summary 
details.(This should ideally be empty as the instance creation was 
unsuccessful).

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1522735/+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 1524231] Re: [RFE]Role-based access control for neutron fwaas policies

[Armando Migliaccio]

fwaas v2 [1] has a concept of public attribute that is being used to
share firewall policies etc. I believe RBAC was taken into account but
dismissed for lack of strong use cases that justified the extra layer of
complexity. For this reason, we'll have to reject this for now and
reassess later on, when we have some fwaas concrete to chew on.

[1] https://blueprints.launchpad.net/neutron/+spec/fwaas-api-2.0

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

** Changed in: neutron
 Assignee: zhaobo (zhaobo6) => (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/1524231

Title:
  [RFE]Role-based access control for neutron fwaas policies

Status in neutron:
  Won't Fix

Bug description:
  [Existing problem]
  Now, fwaas just contain the 'shared' field, when it is True, it can be 
fetched by all tenants.  But there is more requirements now, the enterprise who 
have the strong fw(more legitimate fw-rules/policies) want to share / sell its 
fw service to some tenants through our cloud system. 

  [Proposal]
  Now neutron can not fulfill this task until import rbac policies in L 
release. I think we could base on the existing rbac policies  mechanism to 
extend more resources which may have this application scene.  We could control 
the fw shared like existing network shared or maybe more cover.

  [What is the enhancement?]
  Share FW more sophisticated  to other specified tenants

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1524231/+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 1529836] Re: Fix deprecated library function (os.popen()).

[lei zhang]

** Changed in: murano
 Assignee: lei zhang (zhang-lei) => (unassigned)

** No longer affects: zaqar

** No longer affects: heat

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

Title:
  Fix deprecated library function (os.popen()).

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  In Progress
Status in python-keystoneclient:
  Fix Released
Status in Sahara:
  In Progress
Status in senlin:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1529836/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests

[zhangguoqing]

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

** Changed in: keystoneauth
 Assignee: (unassigned) => zhangguoqing (474751729-o)

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

Title:
  Replace assertEqual(None, *) with assertIsNone in tests

Status in Anchor:
  Fix Released
Status in bifrost:
  In Progress
Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in heat:
  Fix Released
Status in heat-cfntools:
  In Progress
Status in Heat Translator:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  In Progress
Status in Manila:
  Fix Released
Status in networking-cisco:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in ooi:
  In Progress
Status in os-client-config:
  Fix Released
Status in python-barbicanclient:
  In Progress
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-congressclient:
  Fix Released
Status in python-cueclient:
  Fix Released
Status in python-designateclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-heatclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-manilaclient:
  Fix Released
Status in python-neutronclient:
  Fix Released
Status in python-openstackclient:
  In Progress
Status in OpenStack SDK:
  In Progress
Status in python-troveclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in refstack:
  In Progress
Status in Sahara:
  Fix Released
Status in Solum:
  In Progress
Status in Stackalytics:
  In Progress
Status in tempest:
  Fix Released
Status in Trove:
  Fix Released
Status in tuskar:
  Fix Released
Status in zaqar:
  Fix Released

Bug description:
  Replace assertEqual(None, *) with assertIsNone in tests to have
  more clear messages in case of failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/anchor/+bug/1280522/+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 1532921] Re: networking-zvm has broken setup.cfg

[Assaf Muller]

Added networking-zvm as an affected component.

** Also affects: networking-zvm
   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/1532921

Title:
  networking-zvm has broken setup.cfg

Status in networking-zvm:
  New
Status in neutron:
  Invalid

Bug description:
  networking-zvm has in setup.cfg:

  [files]
  packages =
  neutron/plugins/zvm
  neutron/plugins/ml2/drivers/zvm

  
  It should have *one* package entry only and it is not allowed to use a "/".

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-zvm/+bug/1532921/+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 1533024] Re: Lazy load tabs broken by element

[OpenStack Infra]

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

commit 871505c130cf1fd02aae41aeb8f6062af4a5fe88
Author: Thai Tran 
Date:   Mon Jan 11 18:09:14 2016 -0800

Revert "Specify  element in all pages"

This reverts commit I8bad1cd274eec13ec805dc1701ddbf86cfd6e666.

This change is incomplete, and appears to break all lazy loaded tabs.
Since that will effectively freeze development, we should
revert the change until it is more complete.

Change-Id: I0e85f6eeba3fb2ba9f259d04f0b2a2e09137cd0e
Closes-Bug: #1533024


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

Title:
  Lazy load tabs broken by  element

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  We introduced  tag recently which broke all lazy loaded tabs. It
  changed tab url request to originate from base instead of the current
  page.

   
http://localhost:8001/project/instances/3282eaec-569c-40b7-8f82-fd37d86a50ca/?tab=instance_details__audit
 -->
   http://localhost:8001/?tab=instance_details__audit

  Visit instances details or volumes page to see this behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1533024/+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 1533046] [NEW] dashborad appear duplication of the same data

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

on my dashborad -> Project -> Network -> Networks :
that appear  duplication of my public network which is the same one.


#neurton net-list
+--+-+--+
| id   | name| subnets  
|
+--+-+--+
| d5eb23fb-069b-4642-ae82-11657d9f0b73 | private | 
179822df-5490-4090-bb89-93f981849639 fdc4:2769:5ba1::/64 |
|  | | 
60bc8942-2979-4870-8a9f-49aac7e44a29 10.0.0.0/24 |
| 9e0c1b5d-439f-4540-8d1e-e5eb08a7a02d | public  | 
4eead244-8e38-4d34-8e5e-f4a4314fd08e 2001:db8::/64   |
|  | | 
7b692067-e7fc-4721-8707-476275b30d1b 172.24.4.0/24   |
+--+-+--+


but i can see three netwoks on my dashborad..

** Affects: horizon
 Importance: Undecided
 Status: New

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

-- 
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 1529836] Re: Fix deprecated library function (os.popen()).

[MD NADEEM]

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

** Changed in: python-zaqarclient
 Assignee: (unassigned) => MD NADEEM (mail2nadeem92)

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

Title:
  Fix deprecated library function (os.popen()).

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  In Progress
Status in python-keystoneclient:
  Fix Released
Status in Python client library for Zaqar:
  New
Status in Sahara:
  In Progress
Status in senlin:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1529836/+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 1522307] Re: Disk usage not work for shared storage

[Richard Jones]

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

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

Title:
  Disk usage not work for shared storage

Status in OpenStack Dashboard (Horizon):
  Won't Fix
Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  We use a 50TB Ceph as backend but when we showing the hypervisor summary It 
shows double size of it (100TB).
  The cause of this is that Horizon didn't know storage backend for these two 
hypervisors are shared.

  The screen capture is attached fallowing

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1522307/+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 1533046] [NEW] dashborad appear duplication of the same data

[zhaozhilong]

Public bug reported:

on my dashborad -> Project -> Network -> Networks :
that appear  duplication of my public network which is the same one.


#neurton net-list
+--+-+--+
| id   | name| subnets  
|
+--+-+--+
| d5eb23fb-069b-4642-ae82-11657d9f0b73 | private | 
179822df-5490-4090-bb89-93f981849639 fdc4:2769:5ba1::/64 |
|  | | 
60bc8942-2979-4870-8a9f-49aac7e44a29 10.0.0.0/24 |
| 9e0c1b5d-439f-4540-8d1e-e5eb08a7a02d | public  | 
4eead244-8e38-4d34-8e5e-f4a4314fd08e 2001:db8::/64   |
|  | | 
7b692067-e7fc-4721-8707-476275b30d1b 172.24.4.0/24   |
+--+-+--+


but i can see three netwoks on my dashborad..

** Affects: horizon
 Importance: Undecided
 Assignee: zhaozhilong (zhaozhilong)
 Status: New

** Project changed: python-glanceclient => horizon

** Changed in: horizon
 Assignee: (unassigned) => zhaozhilong (zhaozhilong)

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

Title:
  dashborad appear duplication of the same data

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  on my dashborad -> Project -> Network -> Networks :
  that appear  duplication of my public network which is the same one.

  
  #neurton net-list
  
+--+-+--+
  | id   | name| subnets
  |
  
+--+-+--+
  | d5eb23fb-069b-4642-ae82-11657d9f0b73 | private | 
179822df-5490-4090-bb89-93f981849639 fdc4:2769:5ba1::/64 |
  |  | | 
60bc8942-2979-4870-8a9f-49aac7e44a29 10.0.0.0/24 |
  | 9e0c1b5d-439f-4540-8d1e-e5eb08a7a02d | public  | 
4eead244-8e38-4d34-8e5e-f4a4314fd08e 2001:db8::/64   |
  |  | | 
7b692067-e7fc-4721-8707-476275b30d1b 172.24.4.0/24   |
  
+--+-+--+

  
  but i can see three netwoks on my dashborad..

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1533046/+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 1481605] Re: selenium tests need to be runnable under phantomjs

[Richard Jones]

Ended up being a blueprint.

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

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

Title:
  selenium tests need to be runnable under phantomjs

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Currently phantomjs isn't available as a webdriver in Horizon's
  selenium test runner. This prevents users under non-X11 environments
  from reasonably running the selenium test suite, but also the
  phantomjs runner is significantly faster than firefox and would be
  good to enable just for that.

  phantomjs is currently used by the karma command-line so it's there
  anyway, we just need to configure it in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1481605/+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 1277104] Re: wrong order of assertEquals args

[Kan]

** Also affects: ironic-python-agent
   Importance: Undecided
   Status: New

** Changed in: ironic-python-agent
 Assignee: (unassigned) => Kan (kansks)

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

Title:
  wrong order of assertEquals args

Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in ironic-python-agent:
  New
Status in OpenStack Identity (keystone):
  Fix Released
Status in oslo.messaging:
  Fix Released
Status in oslo.policy:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in Python client library for Sahara:
  Fix Released
Status in python-solumclient:
  New
Status in python-swiftclient:
  Won't Fix
Status in python-troveclient:
  Fix Released
Status in Rally:
  Confirmed
Status in Trove:
  Fix Released

Bug description:
  Args of assertEquals method in ceilometer.tests are arranged in wrong order. 
In result when test fails it shows incorrect information about observed and 
actual data. It's found more than 2000 times.
  Right order of arguments is "expected, actual".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1277104/+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 1497057] Re: DB filtering applies REGEX to non-string columns

[Richard Jones]

** Project changed: horizon => nova

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

Title:
  DB filtering applies REGEX to non-string columns

Status in OpenStack Compute (nova):
  New

Bug description:
  While writing the patch https://review.openstack.org/#/c/224431/ I
  noticed that a separate test failed if I did not str() the filter
  values. The failing test is
  nova.tests.unit.compute.test_compute.ComputeAPITestCase.test_get_all_by_state
  and I'll attach the output, but it is also at this test output URL:

  
http://logs.openstack.org/31/224431/1/check/gate-nova-python27/41a4c00/console.html#_2015-09-17_05_47_20_844
  (also at http://paste.openstack.org/show/467079/)

  The code is in nova/db/sqlalchemy/api.py in the _regex_instance_filter
  function.  It would make sense to move non-string columns off to a
  separate filter, rather than applying a REGEX to them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1497057/+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 1522027] Re: Glance doesn't catches UnicodeDecodeError exception

[OpenStack Infra]

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

commit 4b018a117f1c405a85f2b9fd771eb07a7561519b
Author: Darja Shakhray 
Date:   Thu Dec 3 13:27:25 2015 +0300

Fix Glance doesn't catches UnicodeDecodeError exception

Added catch UnicodeDecodeError exception when either
the URL or the request body contained characters that
could not be decoded by Glance.

Change-Id: Ic93c218a74e08b7c7ef6ed0eda53601312fee980
Closes-bug: #1522027


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

Title:
  Glance doesn't catches UnicodeDecodeError exception

Status in Glance:
  Fix Released

Bug description:
  ENVIRONMENT: devstack, Glance (master, 02.12.2015)

  STEPS TO REPRODUCE:
  curl -H "X-Auth-Token: token"  -X GET 
http://localhost:9292/v2/images?name=%FF -i

  ACTUAL RESULT:
  HTTP/1.1 500 Internal Server Error
  Content-Length: 228
  Content-Type: text/html; charset=UTF-8
  X-Openstack-Request-Id: req-d2497fe5-443a-43eb-be30-c38418aca1e1
  Date: Wed, 02 Dec 2015 12:20:23 GMT

  
   
500 Internal Server Error
   
   
500 Internal Server Error
The server has either erred or is incapable of performing the requested 
operation.


   
  

  logs: http://paste.openstack.org/show/480634/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1522027/+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 1491049] Re: Filtering by invalid version string causes 500 error

[OpenStack Infra]

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

commit cd0ec70c952c439e3fdf271e14459ea0be88be6e
Author: Darja Shakhray 
Date:   Tue Sep 15 14:44:00 2015 +0300

Fix 500 error when filtering by invalid version string

Added checking the filter version pattern semver

ApiImpact
FastTrack

Change-Id: Id3e55faa7fdb6c69cd482c8a6b5b7152fda7310c
Closes-bug: #1491049


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

Title:
  Filtering by invalid version string causes 500 error

Status in Glance:
  Fix Released

Bug description:
  When I want to filter a list of artifacts by version if I provide
  invalid semver string (for example, 'version=') then the server
  returns 500 error.

  request:
  GET /v3/artifacts/some_type/2.0?version=

  Stacktrace: http://paste.openstack.org/show/438140/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1491049/+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 1524264] Re: [RFE] Role-based access control for VPNaaS resources

[Armando Migliaccio]

The P in VPN stands for Private. I am not sure I understand what sharing
VPN's across tenants would actually mean. It's an interesting concept,
but there's not enough details that would justify the extra layer of
complexity. As for VPNaaS I think there are a few existing unaddressed
needs that make this particular request not worth pursuing right now.
We'll have to reassess later on.

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

** Changed in: neutron
 Assignee: zhaobo (zhaobo6) => (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/1524264

Title:
  [RFE] Role-based access control for VPNaaS resources

Status in neutron:
  Won't Fix

Bug description:
  [Application scene]
  Tenant A have a vpn,  and A doesn't want to share own vpn to those A doesn't  
believe or no payment, so tenant A may be the  vpn supplier. Tenant B want to 
use the vpn through A shared  to B.  Generally, one share to specified ones to 
use owned vpn is an normal thing.

  [Proposal]
  Now vpn didn't contain the 'shared' field, so we should extend it and fulfill 
the function of share to specified tenants  based on rbac policies.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1524264/+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 1522307] Re: Disk usage not work for shared storage

[Tony Breeds]

Ahh that's a known bug in nova.

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

Title:
  Disk usage not work for shared storage

Status in OpenStack Dashboard (Horizon):
  Won't Fix
Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  We use a 50TB Ceph as backend but when we showing the hypervisor summary It 
shows double size of it (100TB).
  The cause of this is that Horizon didn't know storage backend for these two 
hypervisors are shared.

  The screen capture is attached fallowing

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1522307/+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 1530742] Re: Change LOG.warn to LOG.warning

[OpenStack Infra]

*** This bug is a duplicate of bug 1508442 ***
https://bugs.launchpad.net/bugs/1508442

Reviewed:  https://review.openstack.org/263251
Committed: 
https://git.openstack.org/cgit/openstack/kingbird/commit/?id=0161d781ae1d76045b5a64e330da1c99691a8b20
Submitter: Jenkins
Branch:master

commit 0161d781ae1d76045b5a64e330da1c99691a8b20
Author: zhangguoqing 
Date:   Mon Jan 4 13:25:08 2016 +

Change LOG.warn to LOG.warning

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

Change-Id: I3b8651ee69c9c817ad47db13b06f2f92077a3923
Closes-Bug: #1530742


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

Title:
  Change LOG.warn to LOG.warning

Status in ceilometer-powervm:
  Fix Released
Status in CloudPulse:
  Fix Released
Status in Evoque:
  Fix Released
Status in Gnocchi:
  Fix Committed
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in Kingbird:
  Fix Released
Status in Mistral:
  New
Status in Murano:
  Fix Released
Status in openstack-ansible:
  Fix Released
Status in oslo.messaging:
  In Progress
Status in oslo.middleware:
  New
Status in oslo.vmware:
  New
Status in python-cloudpulseclient:
  Fix Released
Status in python-evoqueclient:
  In Progress
Status in python-heatclient:
  Fix Released
Status in python-muranoclient:
  Fix Released
Status in senlin:
  Fix Released
Status in Stackalytics:
  New
Status in tacker:
  Fix Released
Status in tempest:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer-powervm/+bug/1530742/+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 1490976] Re: Glance ignores a headers when created artifact

[OpenStack Infra]

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

commit f68b3b176c9e4776d3c6e354f64f8272daabd1ac
Author: Darja Shakhray 
Date:   Fri Sep 4 14:56:26 2015 +0300

Fix glance ignored a headers when created artifact

Added check validate header when created, updated artifacts
and uploaded blob.

ApiImpact
FastTrack

Change-Id: Iedea97f708b0bb9706e1e1b13caef6572df92cca
Closes-bug: #1490976


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

Title:
  Glance ignores a headers when created artifact

Status in Glance:
  Fix Released

Bug description:
  ENVIRONMENT: devstack, Glance (master, 31.08.2015)

  STEPS TO REPRODUCE:

  1) curl -H "X-Auth-Token: 3b4e028c1e6f457595497afc1df37ffb"  -H "bla-
  bla" POST -d '{"name": "name1", "version": "2"}'
  http://172.18.76.44:9292/v3/artifacts/myartifact/v2.0/drafts -i

  2)curl -H "X-Auth-Token: 3b4e028c1e6f457595497afc1df37ffb" POST -d
  '{"name": "name1", "version": "2"}'
  http://172.18.76.44:9292/v3/artifacts/myartifact/v2.0/drafts -i

  EXPECTED RESULT:
  status code 400 and message error

  ACTUAL RESULT:
  Artifact is created

  curl: (6) Could not resolve host: POST
  HTTP/1.1 201 Created
  Content-Length: 512
  Content-Type: application/json; charset=UTF-8
  Location: 
http://172.18.76.44:9292/v3/artifacts/myartifact/v2.0/91671992-c84e-4723-9024-3c9b6dddf079
  X-Openstack-Request-Id: req-8d193d56-1e24-48cf-a409-82a016d443b8
  Date: Tue, 01 Sep 2015 13:02:40 GMT

  {"description": null, "published_at": null, "tags": [], "depends_on":
  null, "created_at": "2015-09-01T13:02:40.00", "type_name":
  "MyArtifact", "updated_at": "2015-09-01T13:02:40.00",
  "visibility": "private", "id": "91671992-c84e-4723-9024-3c9b6dddf079",
  "type_version": "2.0", "state": "creating", "version": "2.0.0",
  "references": [], "prop1": null, "prop2": null, "owner":
  "e883b496995f42e988e9c6c07c16d2da", "image_file": null, "deleted_at":
  null, "screenshots": [], "int_list": null, "name": "name1"}

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

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

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

[OpenStack Infra]

Reviewed:  https://review.openstack.org/264120
Committed: 
https://git.openstack.org/cgit/openstack/astara-appliance/commit/?id=3290a438a997f7e4c236f687395831aad5ed51a4
Submitter: Jenkins
Branch:master

commit 3290a438a997f7e4c236f687395831aad5ed51a4
Author: Swapnil Kulkarni (coolsvap) 
Date:   Wed Jan 6 16:16:45 2016 +0530

Replace deprecated LOG.warn with LOG.warning

LOG.warn is deprecated. It still used in a few places.
Updated to non-deprecated LOG.warning.

Change-Id: Ia78851fc4624328a43ab717f474b136326a0b789
Closes-Bug:#1508442


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

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

Title:
  LOG.warn is deprecated

Status in Aodh:
  In Progress
Status in Astara:
  Fix Released
Status in Blazar:
  In Progress
Status in Ceilometer:
  Fix Released
Status in cloud-init:
  In Progress
Status in cloudkitty:
  Fix Released
Status in Designate:
  Fix Released
Status in django-openstack-auth:
  In Progress
Status in DragonFlow:
  Fix Released
Status in Glance:
  In Progress
Status in Gnocchi:
  In Progress
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in Ironic Inspector:
  Fix Released
Status in ironic-lib:
  Fix Committed
Status in ironic-python-agent:
  Fix Released
Status in OpenStack Identity (keystone):
  In Progress
Status in kolla:
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-cisco:
  In Progress
Status in networking-odl:
  In Progress
Status in networking-ofagent:
  In Progress
Status in networking-vsphere:
  In Progress
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  In Progress
Status in nova-powervm:
  Fix Released
Status in octavia:
  In Progress
Status in openstack-ansible:
  In Progress
Status in oslo.cache:
  Fix Released
Status in oslo.privsep:
  In Progress
Status in Packstack:
  Fix Released
Status in python-magnumclient:
  Fix Released
Status in Solum:
  In Progress
Status in tempest:
  In Progress
Status in tripleo:
  In Progress
Status in tuskar:
  In Progress
Status in zaqar:
  In Progress

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

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

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

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

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

[Yahoo-eng-team] [Bug 1493122] Re: There is no quota check for instance snapshot

[Richard Jones]

Closing this bug since there's now a blueprint to track the feature
request.

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

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

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

Title:
  There is no quota check for instance snapshot

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  There is no quota check for snapshots getting from instances both via
  APIs and horizon. Imagine a situation in which a normal user can fill-
  out whole of the cinder(ceph) storage space by calling the
  get_instance_snapshot() API. But its need to control the amount of
  instance snapshots by defining instance-snapshot-quota.

  How to reproduce?
  1- In specific project, launch a new instance.
  2- Set the project's quota all the way down(e.g. instances: 1, 
volume_snapshots: 0, ...).
  3- Get snapshots from running instance as much as you can.

  You see that there is no quota check and user can fill-out the whole
  of the storage space.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1493122/+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 1529552] Re: fa-check Icon is not displayed on a single line

[OpenStack Infra]

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

commit b25e130865552124c5665464440cc73a815ff042
Author: kenji-ishii 
Date:   Sat Dec 26 08:34:21 2015 +0900

Modify so as to display fa-check icon with a single line

In header's dropdown to select project, fa-check icon is not
displayed on a single line if project name is long some degree.
This problem occur in case of using Chrome.
This patch fix this problem.

Change-Id: Iefd73df70456e4e363811b25d70cf2cf59d8c1c0
Closes-bug: #1529552


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

Title:
  fa-check Icon is not displayed on a single line

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  In dropdown to select project, fa-check icon is not displayed on a single 
line if project name is long some degree.
  It should be display on a single line.

  This problem occur in case of using Chrome.
  If we use firefox, it doesn't occur.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1529552/+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 1532949] [NEW] Trove Username/Password not required fields

[Mitali Parthasarathy]

Public bug reported:

In Horizon Databases, when you launch an instance, there is an
Initialize Databases tab. The Initial Admin User and Password fields are
mentioned as required (in the help text) but they are not enforced to be
required.  See attachment for Horizon view.

Solution: Change 'required' to True for these form fields.

** Affects: horizon
 Importance: Undecided
 Status: New

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

Title:
  Trove Username/Password not required fields

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In Horizon Databases, when you launch an instance, there is an
  Initialize Databases tab. The Initial Admin User and Password fields
  are mentioned as required (in the help text) but they are not enforced
  to be required.  See attachment for Horizon view.

  Solution: Change 'required' to True for these form fields.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1532949/+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 1491343] Re: Unable to delete object from a pseudo folder under container if pseudo folder name contains backslash "\"

[Richard Jones]

Bug no longer present.

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

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

Title:
  Unable to delete object from a pseudo folder under container if pseudo
  folder name contains backslash "\"

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Hi all,

  All the operations are performed from Horizon dashboard. (Openstack-
  kilo release)

  Inside a container if we create a pseudo folder with name which contains a 
backward slash ( like : “xyz\” )
  Then if we uplaod a object inside the pseudo folder.
  Then we can't delete this object .

  I installed openstack manually from http://docs.openstack.org/kilo
  /install-guide/install/yum/content/ch_basic_environment.html

  Thanks & Regards
  Ankur Jain

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1491343/+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 1532768] [NEW] Missing service 'region' and endpoint name for EndpointFilterCatalog

[Einar Forselv]

Public bug reported:

This is similar to :
https://bugs.launchpad.net/keystone/+bug/1410543 : Include service name in 
filtered catalog
(Work has been done to  collapse the catalog drivers into a single driver, but 
the progress on this has been fairly slow lately)

This bug is meant as a quick fix to get endpoint filtering to work and
be consistent with the normal v3 catalog.

The current EndpointFilterCatalog are missing the following to be consistent 
with the normal v3 catalog :
* EndpointFilterCatalog only returns 'region_id'. The normal v3 catalog also 
includes 'region' for backwards compatibility. The vast amount of tools still 
use 'region' and will fail unless it's present.
* EndpointFilterCatalog doesn't include the endpoint's name.

EndpointFilterCatalog currently returns the following :

'endpoints': [{

'url':'https://objects.zetta.io:8443/v1/AUTH_d67f3235ece449ecaf8a9f731ca9a10c', 
'interface': 'public', 
'region_id': 'no-osl1',
'id': u'6513c4a646594292a3f8cdf65a0882f3'
}], 
'type': 'object-store',
'id': '7a806e12a8644d7ea67e6e4f4c287fec'
}, 

Normal v3 catalog returns the following

'endpoints': [{
'url': 
'https://objects.zetta.io:8443/v1/AUTH_d67f3235ece449ecaf8a9f731ca9a10c', 
'interface': 'public', 
'region_id': 'no-osl1',
'region': 'no-osl1',
'id': u'6513c4a646594292a3f8cdf65a0882f3'
}], 
'type': 'object-store',
'name': 'swift',
'id': '7a806e12a8644d7ea67e6e4f4c287fec'
},

** Affects: keystone
 Importance: Undecided
 Assignee: Einar Forselv (eforselv)
 Status: New

** Changed in: keystone
 Assignee: (unassigned) => Einar Forselv (eforselv)

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

Title:
  Missing service 'region' and endpoint name for EndpointFilterCatalog

Status in OpenStack Identity (keystone):
  New

Bug description:
  This is similar to :
  https://bugs.launchpad.net/keystone/+bug/1410543 : Include service name in 
filtered catalog
  (Work has been done to  collapse the catalog drivers into a single driver, 
but the progress on this has been fairly slow lately)

  This bug is meant as a quick fix to get endpoint filtering to work and
  be consistent with the normal v3 catalog.

  The current EndpointFilterCatalog are missing the following to be consistent 
with the normal v3 catalog :
  * EndpointFilterCatalog only returns 'region_id'. The normal v3 catalog also 
includes 'region' for backwards compatibility. The vast amount of tools still 
use 'region' and will fail unless it's present.
  * EndpointFilterCatalog doesn't include the endpoint's name.

  EndpointFilterCatalog currently returns the following :

  'endpoints': [{

'url':'https://objects.zetta.io:8443/v1/AUTH_d67f3235ece449ecaf8a9f731ca9a10c', 
'interface': 'public', 
'region_id': 'no-osl1',
'id': u'6513c4a646594292a3f8cdf65a0882f3'
}], 
'type': 'object-store',
'id': '7a806e12a8644d7ea67e6e4f4c287fec'
  }, 

  Normal v3 catalog returns the following

  'endpoints': [{
'url': 
'https://objects.zetta.io:8443/v1/AUTH_d67f3235ece449ecaf8a9f731ca9a10c', 
'interface': 'public', 
'region_id': 'no-osl1',
'region': 'no-osl1',
'id': u'6513c4a646594292a3f8cdf65a0882f3'
}], 
'type': 'object-store',
'name': 'swift',
'id': '7a806e12a8644d7ea67e6e4f4c287fec'
  },

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1532768/+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 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()

[OpenStack Infra]

Reviewed:  https://review.openstack.org/265584
Committed: 
https://git.openstack.org/cgit/openstack/murano/commit/?id=097efaba32c8f27de46b9f4635cabe24e43961de
Submitter: Jenkins
Branch:master

commit 097efaba32c8f27de46b9f4635cabe24e43961de
Author: LiuNanke 
Date:   Sun Jan 10 03:27:07 2016 +0800

Replace assertTrue(isinstance()) by optimal assert

assertTrue(isinstance(A, B)) or assertEqual(type(A), B) in tests
should be replaced by assertIsInstance(A, B) provided by testtools.
Closes-bug: #1268480

Change-Id: Ia43c944c56e66631c758cc5146150c2b5abb12ed


** Changed in: murano
   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/1268480

Title:
  assertTrue(isinstance()) in tests should be replace with
  assertIsInstance()

Status in Barbican:
  In Progress
Status in Ceilometer:
  Fix Released
Status in Cinder:
  In Progress
Status in CloudRoast:
  In Progress
Status in congress:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Monasca:
  In Progress
Status in Murano:
  Fix Released
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-keystoneclient:
  Fix Released
Status in python-manilaclient:
  In Progress
Status in python-novaclient:
  Fix Released
Status in OpenStack SDK:
  Fix Released
Status in python-tuskarclient:
  In Progress
Status in Rally:
  In Progress
Status in Sahara:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in Trove:
  Fix Released

Bug description:
  some of tests use different method of assertTrue(isinstance(A, B)) or
  assertEqual(type(A), B). The correct way is to use assertIsInstance(A,
  B) provided by testtools

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1268480/+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 1532759] [NEW] instance list pagination broken

[Matthias Runge]

Public bug reported:

Pagination in tables is broken,

https://github.com/openstack/horizon/blob/master/horizon/templates/horizon/common/_data_table.html#L77

url is not set up with a full path

I would expect something like
http://localhost:8000/project/instances/?marker=aebdfa52-1bce-4729-b34e-
a19a85530987

instead of something like ?marker=aebdfa52-1bce-4729-b34e-a19a85530987
as link.

The former works as expected, the latter does not.

** Affects: horizon
 Importance: Medium
 Assignee: Matthias Runge (mrunge)
 Status: In Progress

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

** Changed in: horizon
   Importance: Low => Medium

** Changed in: horizon
 Assignee: (unassigned) => Matthias Runge (mrunge)

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

Title:
  instance list pagination broken

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  Pagination in tables is broken,

  
https://github.com/openstack/horizon/blob/master/horizon/templates/horizon/common/_data_table.html#L77

  url is not set up with a full path

  I would expect something like
  http://localhost:8000/project/instances/?marker=aebdfa52-1bce-4729
  -b34e-a19a85530987

  instead of something like ?marker=aebdfa52-1bce-4729-b34e-a19a85530987
  as link.

  The former works as expected, the latter does not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1532759/+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 1532809] [NEW] Gate failures when DHCP lease cannot be acquired

[Davanum Srinivas (DIMS)]

Public bug reported:

Example from:
http://logs.openstack.org/97/265697/1/check/gate-grenade-dsvm/6eeced7/console.html#_2016-01-11_07_42_30_838

Logstash query:
message:"No lease, failing" AND voting:1

dhcp_release for an ip/mac does not seem to reach dnsmasq (or it fails
to act on it - "unknown lease") as i don't see entries in syslog for it.

Logs from nova network:
dims@dims-mac:~/junk/6eeced7$ grep dhcp_release old/screen-n-net.txt.gz | grep 
10.1.0.3 | grep CMD
2016-01-11 07:25:35.548 DEBUG oslo_concurrency.processutils 
[req-62aaa0b9-093e-4f28-805d-d4bf3008bfe6 tempest-ServersTestJSON-1206086292 
tempest-ServersTestJSON-1551541405] CMD "sudo nova-rootwrap 
/etc/nova/rootwrap.conf dhcp_release br100 10.1.0.3 fa:16:3e:32:51:c3" 
returned: 0 in 0.117s execute 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:297
2016-01-11 07:25:51.259 DEBUG oslo_concurrency.processutils 
[req-31115ffa-8d43-4621-bb2e-351d6cd4bcef 
tempest-ServerActionsTestJSON-357128318 
tempest-ServerActionsTestJSON-854742699] CMD "sudo nova-rootwrap 
/etc/nova/rootwrap.conf dhcp_release br100 10.1.0.3 fa:16:3e:a4:f0:11" 
returned: 0 in 0.108s execute 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:297
2016-01-11 07:26:35.357 DEBUG oslo_concurrency.processutils 
[req-c32a216e-d909-41a0-a0bc-d5eb7a21c048 
tempest-TestVolumeBootPattern-46217374 
tempest-TestVolumeBootPattern-1056816637] CMD "sudo nova-rootwrap 
/etc/nova/rootwrap.conf dhcp_release br100 10.1.0.3 fa:16:3e:ed:de:f6" 
returned: 0 in 0.110s execute 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:297

Logs from syslog:
dims@dims-mac:~/junk$ grep 10.1.0.3 syslog.txt.gz
Jan 11 07:25:35 devstack-trusty-rax-iad-7090830 dnsmasq-dhcp[7798]: 
DHCPRELEASE(br100) 10.1.0.3 fa:16:3e:32:51:c3 unknown lease
Jan 11 07:25:51 devstack-trusty-rax-iad-7090830 dnsmasq-dhcp[7798]: 
DHCPRELEASE(br100) 10.1.0.3 fa:16:3e:a4:f0:11 unknown lease
Jan 11 07:26:24 devstack-trusty-rax-iad-7090830 dnsmasq-dhcp[7798]: 
DHCPOFFER(br100) 10.1.0.3 fa:16:3e:ed:de:f6
Jan 11 07:26:24 devstack-trusty-rax-iad-7090830 dnsmasq-dhcp[7798]: 
DHCPREQUEST(br100) 10.1.0.3 fa:16:3e:ed:de:f6
Jan 11 07:26:24 devstack-trusty-rax-iad-7090830 dnsmasq-dhcp[7798]: 
DHCPACK(br100) 10.1.0.3 fa:16:3e:ed:de:f6 tempest
Jan 11 07:27:34 devstack-trusty-rax-iad-7090830 object-auditor: Object audit 
(ALL). Since Mon Jan 11 07:27:34 2016: Locally: 1 passed, 0 quarantined, 0 
errors files/sec: 2.03 , bytes/sec: 10119063.16, Total time: 0.49, Auditing 
time: 0.00, Rate: 0.00
Jan 11 07:39:12 devstack-trusty-rax-iad-7090830 dnsmasq-dhcp[7798]: not using 
configured address 10.1.0.3 because it is leased to fa:16:3e:ed:de:f6
Jan 11 07:40:12 devstack-trusty-rax-iad-7090830 dnsmasq-dhcp[7798]: not using 
configured address 10.1.0.3 because it is leased to fa:16:3e:ed:de:f6
Jan 11 07:41:12 devstack-trusty-rax-iad-7090830 dnsmasq-dhcp[7798]: not using 
configured address 10.1.0.3 because it is leased to fa:16:3e:ed:de:f6
Jan 11 07:42:26 devstack-trusty-rax-iad-7090830 dnsmasq-dhcp[7798]: 
DHCPRELEASE(br100) 10.1.0.3 fa:16:3e:fe:1f:36 unknown lease

Net, The test that runs the ssh against the vm fails with the "No lease,
failing" in its serial console

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

Title:
  Gate failures when DHCP lease cannot be acquired

Status in OpenStack Compute (nova):
  New

Bug description:
  Example from:
  
http://logs.openstack.org/97/265697/1/check/gate-grenade-dsvm/6eeced7/console.html#_2016-01-11_07_42_30_838

  Logstash query:
  message:"No lease, failing" AND voting:1

  dhcp_release for an ip/mac does not seem to reach dnsmasq (or it fails
  to act on it - "unknown lease") as i don't see entries in syslog for
  it.

  Logs from nova network:
  dims@dims-mac:~/junk/6eeced7$ grep dhcp_release old/screen-n-net.txt.gz | 
grep 10.1.0.3 | grep CMD
  2016-01-11 07:25:35.548 DEBUG oslo_concurrency.processutils 
[req-62aaa0b9-093e-4f28-805d-d4bf3008bfe6 tempest-ServersTestJSON-1206086292 
tempest-ServersTestJSON-1551541405] CMD "sudo nova-rootwrap 
/etc/nova/rootwrap.conf dhcp_release br100 10.1.0.3 fa:16:3e:32:51:c3" 
returned: 0 in 0.117s execute 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:297
  2016-01-11 07:25:51.259 DEBUG oslo_concurrency.processutils 
[req-31115ffa-8d43-4621-bb2e-351d6cd4bcef 
tempest-ServerActionsTestJSON-357128318 
tempest-ServerActionsTestJSON-854742699] CMD "sudo nova-rootwrap 
/etc/nova/rootwrap.conf dhcp_release br100 10.1.0.3 fa:16:3e:a4:f0:11" 
returned: 0 in 0.108s execute 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:297
  2016-01-11 07:26:35.357 DEBUG oslo_concurrency.processutils 
[req-c32a216e-d909-41a0-a0bc-d5eb7a21c048 
tempest-TestVolumeBootPattern-46217374 

[Yahoo-eng-team] [Bug 1529836] Re: Fix deprecated library function (os.popen()).

[OpenStack Infra]

Reviewed:  https://review.openstack.org/265592
Committed: 
https://git.openstack.org/cgit/openstack/murano/commit/?id=b411ba3e5016f3f9ed04ba773f2dd0bc41721095
Submitter: Jenkins
Branch:master

commit b411ba3e5016f3f9ed04ba773f2dd0bc41721095
Author: LiuNanke 
Date:   Sun Jan 10 04:45:57 2016 +0800

Replace deprecated library function os.popen() with subprocess

os.popen() is deprecated since version 2.6. Resolved with use of
subprocess module.
Closes-bug: #1529836

Change-Id: I0f9d46e5402fcb809575163a27448d9463b703b0


** Changed in: murano
   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/1529836

Title:
  Fix deprecated library function (os.popen()).

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in heat:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  In Progress
Status in python-keystoneclient:
  In Progress
Status in Sahara:
  In Progress
Status in senlin:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in zaqar:
  In Progress

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1529836/+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 1531363] Re: internal server error returned when set gateway of router with an octal ip address

[Akihiro Motoki]

Did you change the status to Invalid by mistake?
There seems no reason to mark it as Invalid. Resetting to New.

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

Title:
  internal server error returned when set gateway of router with an
  octal ip address

Status in neutron:
  Invalid

Bug description:
  [Summary]
  internal server error returned when set gateway of router with an octal ip 
address

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  no error returned when set gateway of router with an octal ip address

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) create a router:
  root@45-59:/opt/stack/devstack# neutron router-create router100
  Created a new router:
  +-+--+
  | Field   | Value|
  +-+--+
  | admin_state_up  | True |
  | availability_zone_hints |  |
  | availability_zones  |  |
  | distributed | False|
  | external_gateway_info   |  |
  | ha  | False|
  | id  | ab35ac7b-dc5f-4ec4-b3a3-26f90ecd9fd7 |
  | name| router100|
  | routes  |  |
  | status  | ACTIVE   |
  | tenant_id   | 72a70635fa0c42a2bcba67edd760d516 |
  +-+--+

  2)internal server error returned when set gateway of router
   with an octal ip address:
  root@45-59:/opt/stack/devstack# neutron router-gateway-set --fixed-ip 
subnet_id=
  015bc64c-ab58-41a1-a296-b58198cffacc,ip_address=172.168.0.011 router100 
ext-net
  Request Failed: internal server error while processing your request.   
ISSUE
  root@45-59:/opt/stack/devstack# 

  Note: the ip address 172.168.0.011 may be interpreted as octal address since
   there is a leading "0" in the address

  3) if there is no leading "0" in the address, it's ok:
  root@45-59:/opt/stack/devstack# 
  root@45-59:/opt/stack/devstack# neutron router-gateway-set --fixed-ip 
  subnet_id=015bc64c-ab58-41a1-a296-b58198cffacc,ip_address=172.168.0.11 
router100 ext-net
  Set gateway for router router100
  root@45-59:/opt/stack/devstack# neutron router-show router100
  
+-+---
  

  | Field   | Value 


 |
  
+-+---
  

  | admin_state_up  | True  


 |
  | availability_zone_hints |   


 |
  | availability_zones  | nova  


 |
  | distributed | False 


 |
  | external_gateway_info   | {"network_id": 
"1fd330fa-e2f3-40a0-b6fc-5c1caa4981c8"
  , "enable_snat": true, "external_fixed_ips": [{"subnet_id": 
"015bc64c-ab58-41a1
  -a296-b58198cffacc", "ip_address": "172.168.0.11"}]} |
  | ha  | False 


 |
  | id  | ab35ac7b-dc5f-4ec4-b3a3-26f90ecd9fd7  


 |
  | name| router100   

[Yahoo-eng-team] [Bug 1531363] Re: internal server error returned when set gateway of router with an octal ip address

[Akihiro Motoki]

Ah I got it. The recent neutron commit fixed the same issue.
It makes sense to mark it as Invalid now.

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

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

Title:
  internal server error returned when set gateway of router with an
  octal ip address

Status in neutron:
  Invalid

Bug description:
  [Summary]
  internal server error returned when set gateway of router with an octal ip 
address

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  no error returned when set gateway of router with an octal ip address

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) create a router:
  root@45-59:/opt/stack/devstack# neutron router-create router100
  Created a new router:
  +-+--+
  | Field   | Value|
  +-+--+
  | admin_state_up  | True |
  | availability_zone_hints |  |
  | availability_zones  |  |
  | distributed | False|
  | external_gateway_info   |  |
  | ha  | False|
  | id  | ab35ac7b-dc5f-4ec4-b3a3-26f90ecd9fd7 |
  | name| router100|
  | routes  |  |
  | status  | ACTIVE   |
  | tenant_id   | 72a70635fa0c42a2bcba67edd760d516 |
  +-+--+

  2)internal server error returned when set gateway of router
   with an octal ip address:
  root@45-59:/opt/stack/devstack# neutron router-gateway-set --fixed-ip 
subnet_id=
  015bc64c-ab58-41a1-a296-b58198cffacc,ip_address=172.168.0.011 router100 
ext-net
  Request Failed: internal server error while processing your request.   
ISSUE
  root@45-59:/opt/stack/devstack# 

  Note: the ip address 172.168.0.011 may be interpreted as octal address since
   there is a leading "0" in the address

  3) if there is no leading "0" in the address, it's ok:
  root@45-59:/opt/stack/devstack# 
  root@45-59:/opt/stack/devstack# neutron router-gateway-set --fixed-ip 
  subnet_id=015bc64c-ab58-41a1-a296-b58198cffacc,ip_address=172.168.0.11 
router100 ext-net
  Set gateway for router router100
  root@45-59:/opt/stack/devstack# neutron router-show router100
  
+-+---
  

  | Field   | Value 


 |
  
+-+---
  

  | admin_state_up  | True  


 |
  | availability_zone_hints |   


 |
  | availability_zones  | nova  


 |
  | distributed | False 


 |
  | external_gateway_info   | {"network_id": 
"1fd330fa-e2f3-40a0-b6fc-5c1caa4981c8"
  , "enable_snat": true, "external_fixed_ips": [{"subnet_id": 
"015bc64c-ab58-41a1
  -a296-b58198cffacc", "ip_address": "172.168.0.11"}]} |
  | ha  | False 


 |
  | id  | ab35ac7b-dc5f-4ec4-b3a3-26f90ecd9fd7  


 |
  | name| router100

[Yahoo-eng-team] [Bug 1472449] Re: download error when the image status is not active

[Flavio Percoco]

** Also affects: glance/liberty
   Importance: Undecided
   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/1472449

Title:
  download error when the image status is not active

Status in Glance:
  Fix Released
Status in Glance liberty series:
  New
Status in python-glanceclient:
  Fix Released

Bug description:
  
  When the locations is blank, downloading image will show python error, but 
the error message is not correct.

  [root@vm134 pe]# glance image-show 9be94a27-367f-4a26-ae7a-045db3cb7332
  +--+--+
  | Property | Value|
  +--+--+
  | checksum | None |
  | container_format | None |
  | created_at   | 2015-07-02T09:09:22Z |
  | disk_format  | None |
  | id   | 9be94a27-367f-4a26-ae7a-045db3cb7332 |
  | locations| []   |
  | min_disk | 0|
  | min_ram  | 0|
  | name | test |
  | owner| e4b36a5b654942328943a835339a6289 |
  | protected| False|
  | size | None |
  | status   | queued   |
  | tags | []   |
  | updated_at   | 2015-07-02T09:09:22Z |
  | virtual_size | None |
  | visibility   | private  |
  +--+--+
  [root@vm134 pe]# glance image-download 9be94a27-367f-4a26-ae7a-045db3cb7332 
--file myimg
  iter() returned non-iterator of type 'NoneType'

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1472449/+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 1527016] Re: Security-rule's port value should 1-65535

[OpenStack Infra]

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

commit fbcf8e6b141906632af2d387767b58ece269538d
Author: lei zhang 
Date:   Thu Nov 26 23:36:05 2015 +0800

Fix Security-rule's port should not set to 0 when Protocol is TCP/UDP

security rule port can be set value 0 when protocol is TCP/UDP

This patch add port check in def_validate_port_range(self, rule),when
protocol is TCP or UDP,port value 0 should not accepted

APIImpact
Change-Id: I57836d730db602de2a6704fd11a13c74ac38a716
Closes-Bug: #1527016


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

Title:
  Security-rule's port value should 1-65535

Status in neutron:
  Fix Released

Bug description:
  When add a security from GUI and input port is 0,GUI can check this is 
invalid,But we can add port 0 rule from CLI
  eg:
  [root@controller extensions(keystone_admin)]# neutron 
security-group-rule-create 65aa027e-3808-41b8-9343-0a86092380ca --protocol TCP 
  --port_range_min 0 --port_range_max 0
  Created a new security_group_rule:
  +---+--+
  | Field | Value|
  +---+--+
  | direction | ingress  |
  | ethertype | IPv4 |
  | id| f2932274-63ca-4a1b-b176-77982c773c99 |
  | port_range_max| 0|
  | port_range_min| 0|
  | protocol  | tcp  |
  | remote_group_id   |  |
  | remote_ip_prefix  |  |
  | security_group_id | 65aa027e-3808-41b8-9343-0a86092380ca |
  | tenant_id | 2c0482cd169a4c1a8b16ab34e30b3984 |
  +---+--+

  so we should check port value range is 1-65535 from def
  convert_validate_port_value(port)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1527016/+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 1532745] Re: Wrong links in Service Providers filtering API docs

[OpenStack Infra]

Reviewed:  https://review.openstack.org/265761
Committed: 
https://git.openstack.org/cgit/openstack/keystone-specs/commit/?id=960b0da9692be63ca05344a42dd3eefa864b4e79
Submitter: Jenkins
Branch:master

commit 960b0da9692be63ca05344a42dd3eefa864b4e79
Author: Marek Denis 
Date:   Mon Jan 11 11:36:24 2016 +0100

Fix incorrect links in OS-EP-FILTER docs

Some links were incorrect for service providers filtering api responses.

Please note that even though the code is not merged yet the docs are
required while proposing feature specification.

The code implementing service providers filtering is available here
https://review.openstack.org/#/c/264854/

Change-Id: I41a8d902f405e6558324f1b49915f673f44e95cf
Closes-Bug: #1532745


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

Title:
  Wrong links in Service Providers filtering API docs

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  Some of the links in the Service Providers filtering API docs are
  incorrect.

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

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

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

[OpenStack Infra]

Reviewed:  https://review.openstack.org/263587
Committed: 
https://git.openstack.org/cgit/openstack/designate/commit/?id=60947dab2b66e6013c9d98e7b7730042f02ed577
Submitter: Jenkins
Branch:master

commit 60947dab2b66e6013c9d98e7b7730042f02ed577
Author: Swapnil Kulkarni (coolsvap) 
Date:   Tue Jan 5 12:17:54 2016 +0530

Replace deprecated LOG.warn with LOG.warning

LOG.warn is deprecated. It still used in a few places.
Updated to non-deprecated LOG.warning.

Change-Id: If2c041cc6bb9513d528ca35611e1e3a96946ce4d
Closes-Bug:#1508442


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

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

Title:
  LOG.warn is deprecated

Status in Aodh:
  In Progress
Status in Astara:
  In Progress
Status in Blazar:
  In Progress
Status in Ceilometer:
  Fix Released
Status in cloud-init:
  In Progress
Status in cloudkitty:
  Fix Released
Status in Designate:
  Fix Released
Status in django-openstack-auth:
  In Progress
Status in DragonFlow:
  Fix Released
Status in Glance:
  In Progress
Status in Gnocchi:
  In Progress
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in Ironic Inspector:
  Fix Released
Status in ironic-lib:
  Fix Committed
Status in ironic-python-agent:
  Fix Released
Status in OpenStack Identity (keystone):
  In Progress
Status in kolla:
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-cisco:
  In Progress
Status in networking-odl:
  In Progress
Status in networking-ofagent:
  In Progress
Status in networking-vsphere:
  In Progress
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  In Progress
Status in nova-powervm:
  Fix Released
Status in octavia:
  In Progress
Status in openstack-ansible:
  In Progress
Status in oslo.cache:
  Fix Released
Status in oslo.privsep:
  In Progress
Status in Packstack:
  Fix Released
Status in python-magnumclient:
  Fix Released
Status in Solum:
  In Progress
Status in tempest:
  In Progress
Status in tripleo:
  In Progress
Status in tuskar:
  In Progress
Status in zaqar:
  In Progress

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

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

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

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

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

[Yahoo-eng-team] [Bug 1445249] Re: Fix bad performance when editing domain members

[OpenStack Infra]

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

commit 1ccc4dd14adfe85946ff87529db144330cac53ae
Author: Jingjing Ren 
Date:   Mon Apr 20 01:16:05 2015 +

Fix bad performance when editing domain members

Modify the Edit action use get_domain_user_roles API
instead of making a separate call for each user.

Change-Id: I9a37cf0d74b8a5ef6e1a6d4013a2b6826649f0c2
Related-Bug: #1365685
Closes-Bug: #1445249


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

Title:
  Fix bad performance when editing domain members

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Closely related to bug #1365685. The same problem occurs in the Edit
  action under Identity->Domains panel.

  Function UpdateDomain.handle() uses API call user_list(), which
  doesn't scale and causes Horizon to take a long time to update the
  domain members. get_domain_users_roles() can be used here to improve
  the performance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1445249/+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 1530038] Re: when external_network_bridge is set to br-ex ovs does not create flow to EXT access

[Assaf Muller]

This is a documentation issue. Since the Icehouse days I believe,
Neutron allows you to configure external connectivity in one of two
ways:

1) Configure the external bridge name in l3_agent.ini. This means that
'qg' external router devices are plugged directly in to the bridge, the
OVS agent doesn't manage the bridge nor does it set up flows in case the
segmentation type for the external network is 'vlan'. This means that
you must set up a Linux VLAN device over the bridge with the external
network's VLAN ID.

2) Set the external bridge name in l3_agent.ini to ''. Configure bridge
mappings in the OVS agent so that it maps the external network's
physical_network to a bridge (Typically still called br-ex). Then the
OVS agent manages the bridge and sets up flows for VLAN translation.

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

** Changed in: neutron
 Assignee: ugvddm (271025598-9) => (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/1530038

Title:
  when external_network_bridge is set to  br-ex ovs does not create flow
  to EXT access

Status in neutron:
  Invalid

Bug description:
  Under  /etc/neutron/l3_agent.ini  when configuring external_network_bridge = 
br-ex 
  OVS does not create dump-flow for this vlan so we get external access. 

  version : # rpm -qa |grep neutron 
  openstack-neutron-7.0.1-2.el7ost.noarch
  python-neutronclient-3.1.0-1.el7ost.noarch
  python-neutron-7.0.1-2.el7ost.noarch
  openstack-neutron-openvswitch-7.0.1-2.el7ost.noarch
  openstack-neutron-common-7.0.1-2.el7ost.noarch
  openstack-neutron-ml2-7.0.1-2.el7ost.noarch
  [root@puma06 ~(keystone_admin)]# rpm -qa |grep openvswitch 
  python-openvswitch-2.4.0-1.el7.noarch
  openstack-neutron-openvswitch-7.0.1-2.el7ost.noarch
  openvswitch-2.4.0-1.el7.x86_64

  Installed by packstack OSP-8

  step to reproduce : 
  1. Deploy with packstack OSP-8 , set ETX bridge parameter -->  
CONFIG_NEUTRON_L3_EXT_BRIDGE= br-ex 
  2. setup ENV : 
  # neutron net-create external_network --provider:network_type=vlan  
--provider:segmentation_id=181 --provider:physical_network physnet 
--router:external
  # neutron subnet-create external_network 10.35.166.0/24 --disable-dhcp 
--gateway 10.35.166.254  --allocation-pool start=10.35.166.1,end=10.35.166.100 
  # neutron net-create int_net 
  # neutron subnet-create int_net 192.168.1.0/24 --dns_nameservers list=true 
10.35.28.28 --name int_sub
  # neutron router-create Router_eNet
  # neutron router-interface-add Router_eNet subnet=int_sub
  # neutron router-gateway-set Router_eNet external_network

  3. ovs-ofctl dump-flows br-ex
  NXST_FLOW reply (xid=0x4):
   cookie=0x0, duration=57707.344s, table=0, n_packets=21, n_bytes=1638, 
idle_age=60, priority=2,in_port=2 actions=drop
   cookie=0x0, duration=57707.394s, table=0, n_packets=1233857, 
n_bytes=85172234, idle_age=0, priority=0 actions=NORMAL

  try to ping EXT network (8.8.8.8)  -- no connectivity
  4. When we change external_network_bridge = provider and creating the ENV 
again (new router & new routr ports )
  I get EXT access and the flow created : 
  # ovs-ofctl dump-flows br-ex
  NXST_FLOW reply (xid=0x4):
   cookie=0x0, duration=105.955s, table=0, n_packets=5, n_bytes=402, 
idle_age=97, priority=4,in_port=2,dl_vlan=2 actions=mod_vlan_vid:181,NORMAL
   cookie=0x0, duration=58222.490s, table=0, n_packets=39, n_bytes=3174, 
idle_age=105, priority=2,in_port=2 actions=drop
   cookie=0x0, duration=58222.540s, table=0, n_packets=1244856, 
n_bytes=85931346, idle_age=0, priority=0 actions=NORMAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1530038/+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 1531256] Re: remove get_lock policy action and method

[Lauren Taylor]

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

** Changed in: nova
   Status: Fix Released => 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/1531256

Title:
  remove get_lock policy action and method

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  The get_lock method in compute/api.py is no longer in use or being called in 
Nova.
  Need to remove the get_lock method and the get_lock policy action from the 
default policy.json

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1531256/+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 1370033] Re: Admin should be able to manually select the active instance of a HA router

[Carl Baldwin]

** Changed in: neutron
   Status: Won't Fix => 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/1370033

Title:
  Admin should be able to manually select the active instance of a HA
  router

Status in neutron:
  New

Bug description:
  The admin can see where is the active replica of an HA router. Once this bug: 
https://bugs.launchpad.net/neutron/+bug/1401095
  Is solved, the admin will be able to manually move HA routers from one agent 
to the next. Combining the two, it gives a decent if not ideal way to move the 
master by unscheduling it from the master node thereby moving it a backup:

  For example if hosts A and B are hosting router R, and router R is
  active on host A, you can unschedule it from host A, invoking a
  failover and causing B to become the new active replica. You then
  schedule it to host A once more and it'll host the router again, this
  time as standby.

  This RFE is about adding the ability to manually move the master state
  of a router from one agent to another explicitly. I think this can
  only be done with an API modification, or even a new API verb just for
  HA routers. I think that any API modifications need a slim spec and an
  RFE bug is not enough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1370033/+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 1370033] Re: Admin should be able to manually select the active instance of a HA router

[Carl Baldwin]

I just adjusted the status and tags to reflect what has been discussed
on the review [1].  Maybe we need to discuss this again in the drivers
team meeting.

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

** Tags removed: rfe-approved
** Tags added: rfe

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

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

Title:
  Admin should be able to manually select the active instance of a HA
  router

Status in neutron:
  New

Bug description:
  The admin can see where is the active replica of an HA router. Once this bug: 
https://bugs.launchpad.net/neutron/+bug/1401095
  Is solved, the admin will be able to manually move HA routers from one agent 
to the next. Combining the two, it gives a decent if not ideal way to move the 
master by unscheduling it from the master node thereby moving it a backup:

  For example if hosts A and B are hosting router R, and router R is
  active on host A, you can unschedule it from host A, invoking a
  failover and causing B to become the new active replica. You then
  schedule it to host A once more and it'll host the router again, this
  time as standby.

  This RFE is about adding the ability to manually move the master state
  of a router from one agent to another explicitly. I think this can
  only be done with an API modification, or even a new API verb just for
  HA routers. I think that any API modifications need a slim spec and an
  RFE bug is not enough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1370033/+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 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()

[OpenStack Infra]

Reviewed:  https://review.openstack.org/265586
Committed: 
https://git.openstack.org/cgit/openstack/monasca-api/commit/?id=c082be5e8fab0c51002d00a282b13bf9a59cd993
Submitter: Jenkins
Branch:master

commit c082be5e8fab0c51002d00a282b13bf9a59cd993
Author: LiuNanke 
Date:   Sun Jan 10 03:50:49 2016 +0800

Replace assertTrue(isinstance()) with assertIsInstance()

Some of tests use different method of assertTrue(isinstance(A, B)) or
assertEqual(type(A), B). The correct way is to use assertIsInstance(A,
B) provided by testtools.
Closes-Bug: #1268480

Change-Id: Iaf9e1a36581b14fded7885ad27e8e9c9409397fd


** Changed in: monasca
   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/1268480

Title:
  assertTrue(isinstance()) in tests should be replace with
  assertIsInstance()

Status in Barbican:
  In Progress
Status in Ceilometer:
  Fix Released
Status in Cinder:
  In Progress
Status in CloudRoast:
  In Progress
Status in congress:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Monasca:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-keystoneclient:
  Fix Released
Status in python-manilaclient:
  In Progress
Status in python-novaclient:
  Fix Released
Status in OpenStack SDK:
  Fix Released
Status in python-tuskarclient:
  In Progress
Status in Rally:
  In Progress
Status in Sahara:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in Trove:
  Fix Released

Bug description:
  some of tests use different method of assertTrue(isinstance(A, B)) or
  assertEqual(type(A), B). The correct way is to use assertIsInstance(A,
  B) provided by testtools

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1268480/+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 1532890] [NEW] No network connectivity inside VMs after host reboot

[Roman Podoliaka]

Public bug reported:

When a host is rebooted and resume_guests_state_on_host_boot is set to True, it 
may happen that nova-compute starts before Neutron L2 agent finishes its 
initialization, which includes creation of an OVS integration bridge, and thus 
we'll see the following error when creating an ovs vif port:

 2016-01-05 02:57:57.970 11932 ERROR nova.network.linux_net 
[req-e5b5ba37-fff7-4b41-9dda-00c2c54a8e22 - - - - -] Unable to execute 
['ovs-vsctl', '--timeout=120', '--', '--if-exists', 'del-port', 
u'qvob2efeceb-e4', '--', 'add-port', u'br-int', u'qvob2efeceb-e4', '--', 'set', 
'Interface', u'qvob2efeceb-e4', 
u'external-ids:iface-id=b2efeceb-e46f-41f5-a1b2-add7f5dd7a80', 
'external-ids:iface-status=active', 
u'external-ids:attached-mac=fa:16:3e:34:91:87', 
'external-ids:vm-uuid=50118e0e-e104-4cc0-b154-b0dcdaef0494']. Exception: 
Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf ovs-vsctl --timeout=120 -- 
--if-exists del-port qvob2efeceb-e4 -- add-port br-int qvob2efeceb-e4 -- set 
Interface qvob2efeceb-e4 
external-ids:iface-id=b2efeceb-e46f-41f5-a1b2-add7f5dd7a80 
external-ids:iface-status=active external-ids:attached-mac=fa:16:3e:34:91:87 
external-ids:vm-uuid=50118e0e-e104-4cc0-b154-b0dcdaef0494
Exit code: 1
Stdout: u''
Stderr: u'ovs-vsctl: no bridge named br-int\n'

An instance will be booted successfully, but there will be no network 
connectivity inside the VM.

** Affects: nova
 Importance: Undecided
 Assignee: Roman Podoliaka (rpodolyaka)
 Status: In Progress

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

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

Title:
  No network connectivity inside VMs after host reboot

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  When a host is rebooted and resume_guests_state_on_host_boot is set to True, 
it may happen that nova-compute starts before Neutron L2 agent finishes its 
initialization, which includes creation of an OVS integration bridge, and thus 
we'll see the following error when creating an ovs vif port:
  
   2016-01-05 02:57:57.970 11932 ERROR nova.network.linux_net 
[req-e5b5ba37-fff7-4b41-9dda-00c2c54a8e22 - - - - -] Unable to execute 
['ovs-vsctl', '--timeout=120', '--', '--if-exists', 'del-port', 
u'qvob2efeceb-e4', '--', 'add-port', u'br-int', u'qvob2efeceb-e4', '--', 'set', 
'Interface', u'qvob2efeceb-e4', 
u'external-ids:iface-id=b2efeceb-e46f-41f5-a1b2-add7f5dd7a80', 
'external-ids:iface-status=active', 
u'external-ids:attached-mac=fa:16:3e:34:91:87', 
'external-ids:vm-uuid=50118e0e-e104-4cc0-b154-b0dcdaef0494']. Exception: 
Unexpected error while running command.
  Command: sudo nova-rootwrap /etc/nova/rootwrap.conf ovs-vsctl --timeout=120 
-- --if-exists del-port qvob2efeceb-e4 -- add-port br-int qvob2efeceb-e4 -- set 
Interface qvob2efeceb-e4 
external-ids:iface-id=b2efeceb-e46f-41f5-a1b2-add7f5dd7a80 
external-ids:iface-status=active external-ids:attached-mac=fa:16:3e:34:91:87 
external-ids:vm-uuid=50118e0e-e104-4cc0-b154-b0dcdaef0494
  Exit code: 1
  Stdout: u''
  Stderr: u'ovs-vsctl: no bridge named br-int\n'
  
  An instance will be booted successfully, but there will be no network 
connectivity inside the VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1532890/+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 1532897] [NEW] octal ip address disallowed during create but still works during update of setting router gw

[Jas]

Public bug reported:

environment: all-in-one devstack

description: we have disallowed the usage of leading "0" in ip v4
addresses due to the confusion of them being interpreted as octal
addresses in some instances. This was first reported:
https://bugs.launchpad.net/neutron/+bug/1524220 and then it was patched
https://review.openstack.org/255217 . I am able to bypass the fix while
updating gw router ip.

ex:
-VirtualBox:~/devstack$ neutron router-create test-routr
Created a new router:
+-+--+
| Field   | Value|
+-+--+
| admin_state_up  | True |
| availability_zone_hints |  |
| availability_zones  |  |
| distributed | False|
| external_gateway_info   |  |
| ha  | False|
| id  | 7b5a90b6-9db2-4a83-b249-e320cbc049e4 |
| name| test-routr   |
| routes  |  |
| status  | ACTIVE   |
| tenant_id   | 20042bf593564b21b5957f0977d746fc |
+-+--+
-VirtualBox:~/devstack$ neutron router-gateway-set --fixed-ip 
subnet_id=2a146a9d-9834-4fa1-a313-64f2ad677a97,ip_address=172.24.4.014 
test-routr public 
Request Failed: internal server error while processing your request.  < 
ERROR HERE IS EXPECTED
-VirtualBox:~/devstack$ neutron router-gateway-set --fixed-ip 
subnet_id=2a146a9d-9834-4fa1-a313-64f2ad677a97,ip_address=172.24.4.17 
test-routr public 
Set gateway for router test-routr 
-VirtualBox:~/devstack$ neutron router-gateway-set --fixed-ip 
subnet_id=2a146a9d-9834-4fa1-a313-64f2ad677a97,ip_address=172.24.4.014 
test-routr public 
Set gateway for router test-routr <-- THIS IS THE SAME THING THAT I TRIED 
EARLIER AND IT FAILED BUT SINCE THERE WAS ALREADY AN IP AND I WAS SIMPLY 
UPDATING, IT WAS ABLE TO BYPASS VALIDATION.

** Affects: neutron
 Importance: Undecided
 Assignee: Jas (singhj)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => Jas (singhj)

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

Title:
  octal ip address disallowed during create but still works during
  update of setting router gw

Status in neutron:
  New

Bug description:
  environment: all-in-one devstack

  description: we have disallowed the usage of leading "0" in ip v4
  addresses due to the confusion of them being interpreted as octal
  addresses in some instances. This was first reported:
  https://bugs.launchpad.net/neutron/+bug/1524220 and then it was
  patched  https://review.openstack.org/255217 . I am able to bypass the
  fix while updating gw router ip.

  ex:
  -VirtualBox:~/devstack$ neutron router-create test-routr
  Created a new router:
  +-+--+
  | Field   | Value|
  +-+--+
  | admin_state_up  | True |
  | availability_zone_hints |  |
  | availability_zones  |  |
  | distributed | False|
  | external_gateway_info   |  |
  | ha  | False|
  | id  | 7b5a90b6-9db2-4a83-b249-e320cbc049e4 |
  | name| test-routr   |
  | routes  |  |
  | status  | ACTIVE   |
  | tenant_id   | 20042bf593564b21b5957f0977d746fc |
  +-+--+
  -VirtualBox:~/devstack$ neutron router-gateway-set --fixed-ip 
subnet_id=2a146a9d-9834-4fa1-a313-64f2ad677a97,ip_address=172.24.4.014 
test-routr public 
  Request Failed: internal server error while processing your request.  < 
ERROR HERE IS EXPECTED
  -VirtualBox:~/devstack$ neutron router-gateway-set --fixed-ip 
subnet_id=2a146a9d-9834-4fa1-a313-64f2ad677a97,ip_address=172.24.4.17 
test-routr public 
  Set gateway for router test-routr 
  -VirtualBox:~/devstack$ neutron router-gateway-set --fixed-ip 
subnet_id=2a146a9d-9834-4fa1-a313-64f2ad677a97,ip_address=172.24.4.014 
test-routr public 
  Set gateway for router test-routr <-- THIS IS THE SAME THING THAT I TRIED 
EARLIER AND IT FAILED 

[Yahoo-eng-team] [Bug 1532921] [NEW] networking-zvm has broken setup.cfg

[Andreas Jaeger]

Public bug reported:

networking-zvm has in setup.cfg:

[files]
packages =
neutron/plugins/zvm
neutron/plugins/ml2/drivers/zvm


It should have *one* package entry only and it is not allowed to use a "/".

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

Title:
  networking-zvm has broken setup.cfg

Status in neutron:
  New

Bug description:
  networking-zvm has in setup.cfg:

  [files]
  packages =
  neutron/plugins/zvm
  neutron/plugins/ml2/drivers/zvm

  
  It should have *one* package entry only and it is not allowed to use a "/".

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1532921/+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 1490804] Re: PKI Token Revocation Bypass (CVE-2015-7546)

[OpenStack Infra]

Reviewed:  https://review.openstack.org/258143
Committed: 
https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=96ab58e6863c92575ada57615b19652e502adfd8
Submitter: Jenkins
Branch:master

commit 96ab58e6863c92575ada57615b19652e502adfd8
Author: Brant Knudson 
Date:   Tue Dec 1 16:08:00 2015 -0600

auth_token verify revocation by audit_id

If the revocation list includes audit_ids, then when doing offline
validation also validate the token isn't revoked by audit_id.

Closes-Bug: 1490804
Change-Id: I483bc57bd38eb81a0905bcaf94e4ea82604919d6


** Changed in: keystonemiddleware
   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/1490804

Title:
  PKI Token Revocation Bypass (CVE-2015-7546)

Status in django-openstack-auth:
  Invalid
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystonemiddleware:
  Fix Released
Status in OpenStack Security Advisory:
  Confirmed
Status in OpenStack Security Notes:
  Fix Released
Status in python-keystoneclient:
  Won't Fix

Bug description:
  A keystone token which has been revoked can still be used by manipulating 
particular byte fields within the token.
  When a Keystone token is revoked it is added to the revoked list which stores 
the exact token value. Any API will look at the token to see whether or not it 
should accept a token. By changing a single byte within the token, the 
revocation can be bypassed.  see the testing script [1].

  It is suggested that the revocation should be changed to only check
  the token's inner ID.

  [1] http://paste.openstack.org/show/436516/

To manage notifications about this bug go to:
https://bugs.launchpad.net/django-openstack-auth/+bug/1490804/+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 1532200] Re: Gate along resource creation are failing with AttributeError.

[Akihiro Motoki]

_get_tenant_id_for_create() has been restored and marked as deprecated not to 
break external plugins.
The discussion detail is available at 
http://lists.openstack.org/pipermail/openstack-dev/2016-January/thread.html#83612

commit 584d960a93a5ee278fd2c79887cd96da224e8fc5
Author: Gary Kotton 
Date:   Fri Jan 8 07:34:27 2016 -0800

Ensure that decomposed plugins do not break

Commit 5d53dfb8d64186b5b1d2f356fbff8f222e15d1b2 removed the
method _get_tenant_id_for_create. This is used by various plugins
and the *aaS libaries.

Change-Id: I6d5e2555d6c198102a3d5400609f1d671e0d388d


** Summary changed:

- Gate along resource creation are failing with AttributeError.
+ Gate along resource creation are failing with AttributeError 
_get_tenant_id_for_create

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

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

Title:
  Gate along resource creation are failing with AttributeError
  _get_tenant_id_for_create

Status in neutron:
  Fix Released

Bug description:
  Gate along resource creation are failing with 
AttributeError.(_get_tenant_id_for_create method).
  I assume that following commit affects because the method is deleted in this 
commit.
  
https://github.com/openstack/neutron/commit/3082949cffeefd7ef0dcc3f63f235ce597539ef3

  The error detail is following.
  2016-01-08 06:35:18.501 | Traceback (most recent call last):
  2016-01-08 06:35:18.501 |   File 
"/home/jenkins/workspace/gate-networking-midonet-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_db/api.py",
 line 137, in wrapper
  2016-01-08 06:35:18.501 | return f(*args, **kwargs)
  2016-01-08 06:35:18.501 |   File 
"/tmp/openstack/neutron/neutron/api/v2/base.py", line 516, in create
  2016-01-08 06:35:18.501 | obj = do_create(body)
  2016-01-08 06:35:18.501 |   File 
"/tmp/openstack/neutron/neutron/api/v2/base.py", line 498, in do_create
  2016-01-08 06:35:18.502 | request.context, reservation.reservation_id)
  2016-01-08 06:35:18.502 |   File 
"/home/jenkins/workspace/gate-networking-midonet-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
 line 204, in __exit__
  2016-01-08 06:35:18.502 | six.reraise(self.type_, self.value, self.tb)
  2016-01-08 06:35:18.502 |   File 
"/tmp/openstack/neutron/neutron/api/v2/base.py", line 491, in do_create
  2016-01-08 06:35:18.502 | return obj_creator(request.context, 
**kwargs)
  2016-01-08 06:35:18.502 |   File "midonet/neutron/plugin_v2.py", line 81, 
in create_network
  2016-01-08 06:35:18.502 | tenant_id = 
self._get_tenant_id_for_create(context, net_data)
  2016-01-08 06:35:18.502 | AttributeError: 'MidonetPluginV2' object has no 
attribute '_get_tenant_id_for_create'
  2016-01-08 06:35:18.502 | 2016-01-08 06:33:13,534ERROR 
[neutron.api.v2.resource] create failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1532200/+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 1532921] Re: networking-zvm has broken setup.cfg

[Assaf Muller]

This bug doesn't require a patch from the Neutron repo so the affected
component should not be Neutron, it should be networking-zvm, but I
couldn't find a launchpad component for it.

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

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

Title:
  networking-zvm has broken setup.cfg

Status in neutron:
  Invalid

Bug description:
  networking-zvm has in setup.cfg:

  [files]
  packages =
  neutron/plugins/zvm
  neutron/plugins/ml2/drivers/zvm

  
  It should have *one* package entry only and it is not allowed to use a "/".

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