[Yahoo-eng-team] [Bug 1695299] Re: Glance installation fails if password contains '@' symbol

[Gleb Zimin]

So, we can delete devstack from affects.

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

** No longer affects: devstack

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

Title:
  Glance installation fails if password contains '@' symbol

Status in Glance:
  New

Bug description:
  I was doing a fresh installation of devstack today and had set the
  admin password as "Test@321" in local.conf file. The installation
  started failing for Glance and when I had a look at the backtrace, it
  looks like it converts '@' to '%40' and starts failing.

  Either this needs to be fixed or proper note needs to be added in
  devstack setup stating that one cannot use '@' symbol in passwords.

  ubuntu@openstack:~/devstack$ glance --version
  2.6.0
  ubuntu@openstack:~/devstack$

  CRITICAL glance [-] Unhandled error: ValueError: invalid interpolation syntax 
in 'mysql+pymysql://root:Test%40321@127.0.0.1/glance?charset=utf8' at position 
27
  ERROR glance Traceback (most recent call last):
  ERROR glance   File "/usr/local/bin/glance-manage", line 10, in 
  ERROR glance sys.exit(main())
  ERROR glance   File "/opt/stack/glance/glance/cmd/manage.py", line 452, in 
main
  ERROR glance return CONF.command.action_fn()
  ERROR glance   File "/opt/stack/glance/glance/cmd/manage.py", line 291, in 
sync
  ERROR glance self.command_object.sync(CONF.command.version)
  ERROR glance   File "/opt/stack/glance/glance/cmd/manage.py", line 117, in 
sync
  ERROR glance alembic_migrations.place_database_under_alembic_control()
  ERROR glance   File 
"/opt/stack/glance/glance/db/sqlalchemy/alembic_migrations/__init__.py", line 
73, in place_database_under_alembic_control
  ERROR glance a_config = get_alembic_config()
  ERROR glance   File 
"/opt/stack/glance/glance/db/sqlalchemy/alembic_migrations/__init__.py", line 
37, in get_alembic_config
  ERROR glance config.set_main_option('sqlalchemy.url', str(engine.url))
  ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/alembic/config.py", line 218, in 
set_main_option
  ERROR glance self.set_section_option(self.config_ini_section, name, value)
  ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/alembic/config.py", line 245, in 
set_section_option
  ERROR glance self.file_config.set(section, name, value)
  ERROR glance   File "/usr/lib/python2.7/ConfigParser.py", line 752, in set
  ERROR glance "position %d" % (value, tmp_value.find('%')))
  ERROR glance ValueError: invalid interpolation syntax in 
'mysql+pymysql://root:Test%40321@127.0.0.1/glance?charset=utf8' at position 27
  ERROR glance
  +lib/glance:init_glance:1  exit_trap
  +./stack.sh:exit_trap:492  local r=1
  ++./stack.sh:exit_trap:493  jobs -p
  +./stack.sh:exit_trap:493  jobs=
  +./stack.sh:exit_trap:496  [[ -n '' ]]
  +./stack.sh:exit_trap:502  kill_spinner
  +./stack.sh:kill_spinner:388   '[' '!' -z '' ']'
  +./stack.sh:exit_trap:504  [[ 1 -ne 0 ]]
  +./stack.sh:exit_trap:505  echo 'Error on exit'
  Error on exit
  +./stack.sh:exit_trap:506  generate-subunit 1496417170 632 
fail
  +./stack.sh:exit_trap:507  [[ -z /opt/stack/logs ]]
  +./stack.sh:exit_trap:510  
/home/ubuntu/devstack/tools/worlddump.py -d /opt/stack/logs
  World dumping... see /opt/stack/logs/worlddump-2017-06-02-153642.txt for 
details
  +./stack.sh:exit_trap:516  exit 1
  ubuntu@openstack:~/devstack$

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1695299/+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 1668410] Re: [SRU] Infinite loop trying to delete deleted HA router

[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 neutron.
https://bugs.launchpad.net/bugs/1668410

Title:
  [SRU] Infinite loop trying to delete deleted HA router

Status in Ubuntu Cloud Archive:
  New
Status in neutron:
  In Progress
Status in OpenStack Security Advisory:
  Won't Fix
Status in neutron package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  When deleting a router the logfile is filled up. See full log -
  http://paste.ubuntu.com/25429257/

  I can see the error 'Error while deleting router
  c0dab368-5ac8-4996-88c9-f5d345a774a6' occured 3343386 times from
  _safe_router_removed() [1]:

  $ grep -r 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' 
|wc -l
  3343386

  This _safe_router_removed() is invoked by L488 [2], if
  _safe_router_removed() goes wrong it will return False, then
  self._resync_router(update) [3] will make the code
  _safe_router_removed be run again and again. So we saw so many errors
  'Error while deleting router X'.

  [1] 
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L361
  [2] 
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488
  [3] 
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L457

  [Test Case]

  That's because race condition between neutron server and L3 agent,
  after neutron server deletes HA interfaces the L3 agent may sync a HA
  router without HA interface info (just need to trigger L708[1] after
  deleting HA interfaces and before deleting HA router). If we delete HA
  router at this time, this problem will happen. So test case we design
  is as below:

  1, First update fixed package, and restart neutron-server by 'sudo
  service neutron-server restart'

  2, Create ha_router

  neutron router-create harouter --ha=True

  3, Delete ports associated with ha_router before deleting ha_router

  neutron router-port-list harouter |grep 'HA port' |awk '{print $2}' |xargs -l 
neutron port-delete
  neutron router-port-list harouter

  4, Update ha_router to trigger l3-agent to update ha_router info
  without ha_port into self.router_info

  neutron router-update harouter --description=test

  5, Delete ha_router this time

  neutron router-delete harouter

  [1] https://github.com/openstack/neutron/blob/mitaka-
  eol/neutron/db/l3_hamode_db.py#L708

  [Regression Potential]

  The fixed patch [1] for neutron-server will no longer return ha_router
  which is missing ha_ports, so L488 will no longer have chance to call
  _safe_router_removed() for a ha_router, so the problem has been
  fundamentally fixed by this patch and no regression potential.

  Besides, this fixed patch has been in mitaka-eol branch now, and
  neutron-server mitaka package is based on neutron-8.4.0, so we need to
  backport it to xenial and mitaka.

  $ git tag --contains 8c77ee6b20dd38cc0246e854711cb91cffe3a069
  mitaka-eol

  [1] https://review.openstack.org/#/c/440799/2/neutron/db/l3_hamode_db.py
  [2] 
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1668410/+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 1714131] [NEW] pecan hooks break on pagination + ID filter

[Kevin Benton]

Public bug reported:

The user filters are applied to the results before pagination in the
pecan hook pipeline so if the user filters out the ID field, the
pagination code will throw an exception trying to build the next link.

** Affects: neutron
 Importance: High
 Status: New

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

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

Title:
  pecan hooks break on pagination + ID filter

Status in neutron:
  New

Bug description:
  The user filters are applied to the results before pagination in the
  pecan hook pipeline so if the user filters out the ID field, the
  pagination code will throw an exception trying to build the next link.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1714131/+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 1639030] Re: Configure networking based on EC2 metadata source

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.9-259-g7e76c57b-
0ubuntu1

---
cloud-init (0.7.9-259-g7e76c57b-0ubuntu1) artful; urgency=medium

  * Disable upstart support, as upstart is no longer shipped in artful.
[Dimitri Ledkov]
  * New upstream snapshot.
- distro: allow distro to specify a default locale [Ryan Harper]
- tests: fix two recently added tests for sles distro.
- url_helper: dynamically import oauthlib import from inside oauth_headers
  [Chad Smith]
- tox: make xenial environment run with python3.6
- suse: Add support for openSUSE and return SLES to a working state.
  [Robert Schweikert]
- GCE: Add a main to the GCE Datasource.
- ec2: Add IPv6 dhcp support to Ec2DataSource. [Chad Smith] (LP: #1639030)
- url_helper: fail gracefully if oauthlib is not available
  [Lars Kellogg-Stedman] (LP: #1713760)
- cloud-init analyze: fix issues running under python 2. [Andrew Jorgensen]
- Configure logging module to always use UTC time.
  [Ryan Harper] (LP: #1713158)
- Log a helpful message if a user script does not include shebang.
  [Andrew Jorgensen]
- cli: Fix command line parsing of coniditionally loaded subcommands.
  [Chad Smith] (LP: #1712676)
- doc: Explain error behavior in user data include file format.
  [Jason Butz]
- cc_landscape & cc_puppet: Fix six.StringIO use in writing configs
  [Chad Smith] (LP: #1699282, #1710932)
- schema cli: Add schema subcommand to cloud-init cli and cc_runcmd schema
  [Chad Smith]
- Debian: Remove non-free repositories from apt sources template.
  [Joonas Kylmälä] (LP: #1700091)

 -- Scott Moser   Wed, 30 Aug 2017 21:18:05 -0400

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Configure networking based on EC2 metadata source

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  EC2 metadata[1] presents information regarding network devices (mac,
  name, etc) that would be useful to consume.  Chiefly we could match
  the network device names surfaced in the EC2 UIs (eth0, eth2...)
  rather than using our own enumeration at boot.

  A method to detemermine if we are on an instance in EC2 as been
  published[2] as part of their documentation so we can now do this in
  the EC2 datasource without impacting clouds that have copied that
  datasource.

  The work done for DO datasource[3] would be applicable here as a
  model.

  [1] 
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
  [2] 
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/identify_ec2_instances.html
  [3] 
https://git.launchpad.net/cloud-init/commit/?id=9f83bb8e80806d3dd79ba426474dc3c696e19a41

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1639030/+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 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR

[luqitao]

** Also affects: tacker
   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/1608980

Title:
  Remove MANIFEST.in as it is not explicitly needed by PBR

Status in anvil:
  Invalid
Status in networking-bgpvpn:
  In Progress
Status in craton:
  Fix Released
Status in DragonFlow:
  Fix Released
Status in ec2-api:
  Fix Released
Status in gce-api:
  Fix Released
Status in Glance:
  Fix Released
Status in Karbor:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Released
Status in Kosmos:
  Fix Released
Status in Magnum:
  Fix Released
Status in masakari:
  Fix Released
Status in BaGPipe:
  Fix Released
Status in networking-midonet:
  Fix Released
Status in networking-odl:
  Fix Released
Status in neutron:
  Fix Released
Status in Neutron LBaaS Dashboard:
  Fix Released
Status in octavia:
  Fix Released
Status in os-vif:
  Fix Released
Status in python-searchlightclient:
  In Progress
Status in OpenStack Search (Searchlight):
  Fix Released
Status in Solum:
  Fix Released
Status in storlets:
  In Progress
Status in Swift Authentication:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  In Progress
Status in Tricircle:
  Fix Released
Status in OpenStack DBaaS (Trove):
  Fix Released
Status in watcher:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  PBR do not explicitly require MANIFEST.in, so it can be removed.

  
  Snippet from: http://docs.openstack.org/infra/manual/developers.html

  Manifest

  Just like AUTHORS and ChangeLog, why keep a list of files you wish to
  include when you can find many of these in git. MANIFEST.in generation
  ensures almost all files stored in git, with the exception of
  .gitignore, .gitreview and .pyc files, are automatically included in
  your distribution. In addition, the generated AUTHORS and ChangeLog
  files are also included. In many cases, this removes the need for an
  explicit ‘MANIFEST.in’ file

To manage notifications about this bug go to:
https://bugs.launchpad.net/anvil/+bug/1608980/+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 1695299] Re: Glance installation fails if password contains '@' symbol

[Ian Wienand]

I've actually convinced myself this really is glance's fault.  I have a
suggested change incoming

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

Title:
  Glance installation fails if password contains '@' symbol

Status in devstack:
  In Progress
Status in Glance:
  New

Bug description:
  I was doing a fresh installation of devstack today and had set the
  admin password as "Test@321" in local.conf file. The installation
  started failing for Glance and when I had a look at the backtrace, it
  looks like it converts '@' to '%40' and starts failing.

  Either this needs to be fixed or proper note needs to be added in
  devstack setup stating that one cannot use '@' symbol in passwords.

  ubuntu@openstack:~/devstack$ glance --version
  2.6.0
  ubuntu@openstack:~/devstack$

  CRITICAL glance [-] Unhandled error: ValueError: invalid interpolation syntax 
in 'mysql+pymysql://root:Test%40321@127.0.0.1/glance?charset=utf8' at position 
27
  ERROR glance Traceback (most recent call last):
  ERROR glance   File "/usr/local/bin/glance-manage", line 10, in 
  ERROR glance sys.exit(main())
  ERROR glance   File "/opt/stack/glance/glance/cmd/manage.py", line 452, in 
main
  ERROR glance return CONF.command.action_fn()
  ERROR glance   File "/opt/stack/glance/glance/cmd/manage.py", line 291, in 
sync
  ERROR glance self.command_object.sync(CONF.command.version)
  ERROR glance   File "/opt/stack/glance/glance/cmd/manage.py", line 117, in 
sync
  ERROR glance alembic_migrations.place_database_under_alembic_control()
  ERROR glance   File 
"/opt/stack/glance/glance/db/sqlalchemy/alembic_migrations/__init__.py", line 
73, in place_database_under_alembic_control
  ERROR glance a_config = get_alembic_config()
  ERROR glance   File 
"/opt/stack/glance/glance/db/sqlalchemy/alembic_migrations/__init__.py", line 
37, in get_alembic_config
  ERROR glance config.set_main_option('sqlalchemy.url', str(engine.url))
  ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/alembic/config.py", line 218, in 
set_main_option
  ERROR glance self.set_section_option(self.config_ini_section, name, value)
  ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/alembic/config.py", line 245, in 
set_section_option
  ERROR glance self.file_config.set(section, name, value)
  ERROR glance   File "/usr/lib/python2.7/ConfigParser.py", line 752, in set
  ERROR glance "position %d" % (value, tmp_value.find('%')))
  ERROR glance ValueError: invalid interpolation syntax in 
'mysql+pymysql://root:Test%40321@127.0.0.1/glance?charset=utf8' at position 27
  ERROR glance
  +lib/glance:init_glance:1  exit_trap
  +./stack.sh:exit_trap:492  local r=1
  ++./stack.sh:exit_trap:493  jobs -p
  +./stack.sh:exit_trap:493  jobs=
  +./stack.sh:exit_trap:496  [[ -n '' ]]
  +./stack.sh:exit_trap:502  kill_spinner
  +./stack.sh:kill_spinner:388   '[' '!' -z '' ']'
  +./stack.sh:exit_trap:504  [[ 1 -ne 0 ]]
  +./stack.sh:exit_trap:505  echo 'Error on exit'
  Error on exit
  +./stack.sh:exit_trap:506  generate-subunit 1496417170 632 
fail
  +./stack.sh:exit_trap:507  [[ -z /opt/stack/logs ]]
  +./stack.sh:exit_trap:510  
/home/ubuntu/devstack/tools/worlddump.py -d /opt/stack/logs
  World dumping... see /opt/stack/logs/worlddump-2017-06-02-153642.txt for 
details
  +./stack.sh:exit_trap:516  exit 1
  ubuntu@openstack:~/devstack$

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1695299/+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 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR

[luqitao]

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

** Changed in: storlets
 Assignee: (unassigned) => luqitao (qtlu)

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

Title:
  Remove MANIFEST.in as it is not explicitly needed by PBR

Status in anvil:
  Invalid
Status in networking-bgpvpn:
  In Progress
Status in craton:
  Fix Released
Status in DragonFlow:
  Fix Released
Status in ec2-api:
  Fix Released
Status in gce-api:
  Fix Released
Status in Glance:
  Fix Released
Status in Karbor:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Released
Status in Kosmos:
  Fix Released
Status in Magnum:
  Fix Released
Status in masakari:
  Fix Released
Status in BaGPipe:
  Fix Released
Status in networking-midonet:
  Fix Released
Status in networking-odl:
  Fix Released
Status in neutron:
  Fix Released
Status in Neutron LBaaS Dashboard:
  Fix Released
Status in octavia:
  Fix Released
Status in os-vif:
  Fix Released
Status in python-searchlightclient:
  In Progress
Status in OpenStack Search (Searchlight):
  Fix Released
Status in Solum:
  Fix Released
Status in storlets:
  New
Status in Swift Authentication:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in Tricircle:
  Fix Released
Status in OpenStack DBaaS (Trove):
  Fix Released
Status in watcher:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  PBR do not explicitly require MANIFEST.in, so it can be removed.

  
  Snippet from: http://docs.openstack.org/infra/manual/developers.html

  Manifest

  Just like AUTHORS and ChangeLog, why keep a list of files you wish to
  include when you can find many of these in git. MANIFEST.in generation
  ensures almost all files stored in git, with the exception of
  .gitignore, .gitreview and .pyc files, are automatically included in
  your distribution. In addition, the generated AUTHORS and ChangeLog
  files are also included. In many cases, this removes the need for an
  explicit ‘MANIFEST.in’ file

To manage notifications about this bug go to:
https://bugs.launchpad.net/anvil/+bug/1608980/+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 1714117] [NEW] tox: long CI times

[Joshua Powers]

Public bug reported:

On Aug 10, 2017 the nightly and CI tests began taking 20 additional
minutes. The additional time is occurring during the tox run,
specifically during the 'py27' and 'xenial' environments. Here are
comparisons of run times:

Aug 8: 1 min 52 seconds
Aug 9: 1 min 47 seconds
Aug 10: 19 mins

These tests are run at ~23:40 UTC each day, therefore a change would
have occurred during the day resulting in the end-of-day run to see the
effect.

>From the Aug 10 run these two tox environments are adding a huge amount of 
>time:
py27: Ran 980 tests in 525.871s
xenial: Ran 980 tests in 518.678s

Here are timing results from the Aug 9 run:
py27: Ran 978 tests in 9.051s
xenial: Ran 978 tests in 14.122s

Per the git log I believe it is tied to this revision:
https://git.launchpad.net/cloud-init/commit/?id=d5f855dd96ccbea77f61b0515b574ad2c43d116d

Which added two new tests:
test_ec2_local_returns_false_on_bsd
test_ec2_local_performs_dhcp_on_non_bsd
hence the increase the number of tests run. I am not however, saying that these 
two tests are the cause of the additional test time.

** Affects: cloud-init
 Importance: Undecided
 Status: Confirmed

** Changed in: cloud-init
   Status: New => Confirmed

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

Title:
  tox: long CI times

Status in cloud-init:
  Confirmed

Bug description:
  On Aug 10, 2017 the nightly and CI tests began taking 20 additional
  minutes. The additional time is occurring during the tox run,
  specifically during the 'py27' and 'xenial' environments. Here are
  comparisons of run times:

  Aug 8: 1 min 52 seconds
  Aug 9: 1 min 47 seconds
  Aug 10: 19 mins

  These tests are run at ~23:40 UTC each day, therefore a change would
  have occurred during the day resulting in the end-of-day run to see
  the effect.

  From the Aug 10 run these two tox environments are adding a huge amount of 
time:
  py27: Ran 980 tests in 525.871s
  xenial: Ran 980 tests in 518.678s

  Here are timing results from the Aug 9 run:
  py27: Ran 978 tests in 9.051s
  xenial: Ran 978 tests in 14.122s

  Per the git log I believe it is tied to this revision:
  
https://git.launchpad.net/cloud-init/commit/?id=d5f855dd96ccbea77f61b0515b574ad2c43d116d

  Which added two new tests:
  test_ec2_local_returns_false_on_bsd
  test_ec2_local_performs_dhcp_on_non_bsd
  hence the increase the number of tests run. I am not however, saying that 
these two tests are the cause of the additional test time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1714117/+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 1713177] Re: api-ref missing 'protected' filter query for image-list call

[OpenStack Infra]

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

commit 7101d9ceea58533997257e39003db893dd1e4fd4
Author: Brian Rosmaita 
Date:   Fri Aug 25 21:11:52 2017 -0400

api-ref: add 'protected' query filter

Adds documentation for the 'protected' query filter introduced
in Pike.

Change-Id: I7c63ae1715e1bd35587f0f0954596ae1263d428b
Closes-bug: #1713177


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

Title:
  api-ref missing 'protected' filter query for image-list call

Status in Glance:
  Fix Released

Bug description:
  The 'protected' filter isn't listed among the query options for the
  image-list call.  It was introduced in Pike by Change-Id:
  Ie90d952e3f69b3f489f056ff506e63f96376

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1713177/+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 1713502] Re: PCI passthrough documentation needs updating since options moved to [pci] section

[Eric Fried]

https://review.openstack.org/#/c/498461 (master branch fix) merged on
8/28.  Bot didn't auto-update the status, so I did it.

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

Title:
  PCI passthrough documentation needs updating since options moved to
  [pci] section

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  The ``pci_passthrough_whitelist`` and ``pci_alias`` options in the
  ``[DEFAULT]`` section were deprecated and replaced by
  ``passthrough_whitelist`` and ``alias`` in the ``[pci]`` section,
  respectively, in ocata via [1].  However, the PCI passthrough
  documentation [2] was missed.

  [1] https://review.openstack.org/#/c/356604/
  [2] https://docs.openstack.org/nova/pike/admin/pci-passthrough.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1713502/+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 1559241] Re: cryptography-1.3 breaks unit tests

[Brian Haley]

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

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

Title:
  cryptography-1.3 breaks unit tests

Status in neutron:
  Invalid
Status in os-cloud-config:
  Fix Released

Bug description:
  With cryptography 1.3, the unit tests are failing with:

  Traceback (most recent call last):
File "os_cloud_config/tests/test_keystone_pki.py", line 36, in 
test_create_ca_and_signing_pairs
  self.assertTrue(ca_key.check())
File 
"/home/fedora/os-cloud-config/.tox/py27/lib/python2.7/site-packages/OpenSSL/crypto.py",
 line 243, in check
  if _lib.EVP_PKEY_type(self._pkey.type) != _lib.EVP_PKEY_RSA:
  AttributeError: '_cffi_backend.CDataGCP' object has no attribute 'type'

  I've opened https://github.com/pyca/cryptography/issues/2837 upstream
  to get this fixed.  In the meantime we may need to exclude
  cryptography 1.3 in global requirements.

  logstash query:
  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_status%3A%20FAILURE%20AND%20message%3A%20%5C%22_cffi_backend.CDataGCP%5C%22

  Appears to be affecting os-cloud-config and neutron-lbaas right now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1559241/+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 1678561] Re: Update metering agent to use stevedore alias for driver

[Brian Haley]

** No longer affects: neutron

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

Title:
  Update metering agent to use stevedore alias for driver

Status in openstack-manuals:
  Fix Released

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

  commit c9d46984096574d130465705ac68b9df272aaa98
  Author: Jean-Philippe Evrard 
  Date:   Fri Jan 13 10:47:52 2017 +

  Update metering agent to use stevedore alias for driver
  
  Currently the metering agent is using the old import method,
  use stevedore instead.
  
  DocImpact
  
  Two places in the networking guide should change to
  'driver = iptables' from current format.
  
  Partial-Bug: #1504536
  Change-Id: I1e6d196a3ada8fbfc2b70d6a983984d8db09bbd0

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-manuals/+bug/1678561/+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 1714072] [NEW] PUT /allocations/{consumer_id} fails with a 500 if "resources: {}"

[Matt Riedemann]

Public bug reported:

I hit this while writing a functional recreate test for bug 1713786
where the destination node during an evacuate doesn't have it's
allocations created by the scheduler. When the source node comes up
after the evacuation, it tries to remove the allocations on the source
node, which is the only one because of bug 1713786, but that results in
sending a request like this:

2017-08-30 14:45:13,495 INFO [nova.scheduler.client.report] Sending
updated allocation [{'resource_provider': {'uuid':
'7ab9dab7-65c6-4961-9403-c8fc50dedb6b'}, 'resources': {}}] for instance
dc8a686c-ad92-48f3-8594-d00c6e671a1c after removing resources for
7ab9dab7-65c6-4961-9403-c8fc50dedb6b.

And you get this stacktrace in the Placement API:

2017-08-30 14:45:13,502 ERROR [nova.api.openstack.placement.handler] Uncaught 
exception
Traceback (most recent call last):
  File "nova/api/openstack/placement/handler.py", line 217, in __call__
return dispatch(environ, start_response, self._map)
  File "nova/api/openstack/placement/handler.py", line 144, in dispatch
return handler(environ, start_response)
  File 
"/home/user/git/nova/.tox/functional/local/lib/python2.7/site-packages/webob/dec.py",
 line 131, in __call__
resp = self.call_func(req, *args, **self.kwargs)
  File "nova/api/openstack/placement/wsgi_wrapper.py", line 29, in call_func
super(PlacementWsgify, self).call_func(req, *args, **kwargs)
  File 
"/home/user/git/nova/.tox/functional/local/lib/python2.7/site-packages/webob/dec.py",
 line 196, in call_func
return self.func(req, *args, **kwargs)
  File "nova/api/openstack/placement/microversion.py", line 268, in 
decorated_func
return _find_method(f, version)(req, *args, **kwargs)
  File "nova/api/openstack/placement/util.py", line 138, in 
decorated_function
return f(req)
  File "nova/api/openstack/placement/handlers/allocation.py", line 286, in 
set_allocations
return _set_allocations(req, ALLOCATION_SCHEMA_V1_8)
  File "nova/api/openstack/placement/handlers/allocation.py", line 252, in 
_set_allocations
allocations.create_all()
  File "nova/objects/resource_provider.py", line 1877, in create_all
self._set_allocations(self._context, self.objects)
  File 
"/home/user/git/nova/.tox/functional/local/lib/python2.7/site-packages/oslo_db/api.py",
 line 150, in wrapper
ectxt.value = e.inner_exc
  File 
"/home/user/git/nova/.tox/functional/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
 line 220, in __exit__
self.force_reraise()
  File 
"/home/user/git/nova/.tox/functional/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
 line 196, in force_reraise
six.reraise(self.type_, self.value, self.tb)
  File 
"/home/user/git/nova/.tox/functional/local/lib/python2.7/site-packages/oslo_db/api.py",
 line 138, in wrapper
return f(*args, **kwargs)
  File 
"/home/user/git/nova/.tox/functional/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py",
 line 979, in wrapper
return fn(*args, **kwargs)
  File "nova/objects/resource_provider.py", line 1835, in _set_allocations
consumer_id = allocs[0].consumer_id
IndexError: list index out of range


The schema validation on PUT /allocations requires a minimum of one provider in 
the request, but it doesn't validate that there is at least one resource for 
that provider:

https://github.com/openstack/nova/blob/da4083d7bc0a0c1272df35ecb12c4c2fd2102e21/nova/api/openstack/placement/handlers/allocation.py#L52-L61

** Affects: nova
 Importance: Medium
 Status: Triaged

** Affects: nova/pike
 Importance: Undecided
 Status: New


** Tags: api placement

** Also affects: nova/pike
   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/1714072

Title:
  PUT /allocations/{consumer_id} fails with a 500 if "resources: {}"

Status in OpenStack Compute (nova):
  Triaged
Status in OpenStack Compute (nova) pike series:
  New

Bug description:
  I hit this while writing a functional recreate test for bug 1713786
  where the destination node during an evacuate doesn't have it's
  allocations created by the scheduler. When the source node comes up
  after the evacuation, it tries to remove the allocations on the source
  node, which is the only one because of bug 1713786, but that results
  in sending a request like this:

  2017-08-30 14:45:13,495 INFO [nova.scheduler.client.report] Sending
  updated allocation [{'resource_provider': {'uuid':
  '7ab9dab7-65c6-4961-9403-c8fc50dedb6b'}, 'resources': {}}] for
  instance dc8a686c-ad92-48f3-8594-d00c6e671a1c after removing resources
  for 7ab9dab7-65c6-4961-9403-c8fc50dedb6b.

  And you get this stacktrace in the Placement API:

  2017-08-30 

[Yahoo-eng-team] [Bug 1714068] [NEW] AttributeError in get_device_details when segment=None

[Brian Haley]

Public bug reported:

Found an AttributeError in this tempest log file:

http://logs.openstack.org/67/347867/52/check/gate-tempest-dsvm-neutron-
dvr-ubuntu-xenial/64d8d9a/logs/screen-q-agt.txt.gz

Aug 29 18:57:12.585412 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc [None 
req-0de9bdcb-9659-4971-9e03-4e2849af0169 None None] Failed to get details for 
device 4fe2030b-4af8-47e7-8dd3-52b544918e16: AttributeError: 'NoneType' object 
has no attribute 'network_type'
Aug 29 18:57:12.585578 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc Traceback (most 
recent call last):
Aug 29 18:57:12.585712 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc   File 
"/opt/stack/new/neutron/neutron/agent/rpc.py", line 216, in 
get_devices_details_list_and_failed_devices
Aug 29 18:57:12.585858 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc 
self.get_device_details(context, device, agent_id, host))
Aug 29 18:57:12.585987 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc   File 
"/opt/stack/new/neutron/neutron/agent/rpc.py", line 244, in get_device_details
Aug 29 18:57:12.586162 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc 'network_type': 
segment.network_type,
Aug 29 18:57:12.586289 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc AttributeError: 
'NoneType' object has no attribute 'network_type'
Aug 29 18:57:12.586414 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc

>From the same log just a second earlier, we can see that the port was
updated, and the 'segment' field of the port binding_level was cleared:

Aug 29 18:57:11.569684 ubuntu-xenial-rax-iad-10687932 neutron-
openvswitch-agent[28658]: DEBUG neutron.agent.resource_cache [None req-
1d914886-cbd7-4568-9290-bcbc98bd7ba6 None None] Resource Port 4fe2030b-
4af8-47e7-8dd3-52b544918e16 updated (revision_number 4->5). Old fields:
{'status': u'DOWN', 'binding_levels':
[PortBindingLevel(driver='openvswitch',host='ubuntu-xenial-rax-
iad-10687932',level=0,port_id=4fe2030b-
4af8-47e7-8dd3-52b544918e16,segment=NetworkSegment(ef53b2b6-f51e-495b-
9dda-b174fbed1122))]} New fields: {'status': u'ACTIVE',
'binding_levels': [PortBindingLevel(driver='openvswitch',host='ubuntu-
xenial-rax-iad-10687932',level=0,port_id=4fe2030b-
4af8-47e7-8dd3-52b544918e16,segment=None)]} {{(pid=28658)
record_resource_update
/opt/stack/new/neutron/neutron/agent/resource_cache.py:185}}

The code in question doesn't check if 'segment' is valid before using
it, and I'm not sure if such a simple change as that is appropriate to
fix it.

This code was added in the push notifications changes:

commit c3db9d6b0b990da6664955e4ce1c72758dc600e1
Author: Kevin Benton 
Date:   Sun Jan 22 17:01:47 2017 -0800

Use push-notificates for OVSPluginAPI

Replace the calls to the OVSPluginAPI info retrieval functions
with reads directly from the push notification cache.

Since we now depend on the cache for the source of truth, the
'port_update'/'port_delete'/'network_update' handlers are configured
to be called whenever the cache receives a corresponding resource update.
The OVS agent will no longer subscribe to topic notifications for ports
or networks from the legacy notification API.

Partially-Implements: blueprint push-notifications
Change-Id: Ib2234ec1f5d328649c6bb1c3fe07799d3e351f48

** Affects: neutron
 Importance: Medium
 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/1714068

Title:
  AttributeError in get_device_details when segment=None

Status in neutron:
  New

Bug description:
  Found an AttributeError in this tempest log file:

  http://logs.openstack.org/67/347867/52/check/gate-tempest-dsvm-
  neutron-dvr-ubuntu-xenial/64d8d9a/logs/screen-q-agt.txt.gz

  Aug 29 18:57:12.585412 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc [None 
req-0de9bdcb-9659-4971-9e03-4e2849af0169 None None] Failed to get details for 
device 4fe2030b-4af8-47e7-8dd3-52b544918e16: AttributeError: 'NoneType' object 
has no attribute 'network_type'
  Aug 29 18:57:12.585578 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc Traceback (most 
recent call last):
  Aug 29 18:57:12.585712 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc   File 
"/opt/stack/new/neutron/neutron/agent/rpc.py", line 216, in 
get_devices_details_list_and_failed_devices
  Aug 29 18:57:12.585858 ubuntu-xenial-rax-iad-10687932 
neutron-openvswitch-agent[28658]: ERROR neutron.agent.rpc 

[Yahoo-eng-team] [Bug 1688215] Re: Change list of available qos rules

[Boden R]

This implementation was reverted in
I88a216951d8996ac8bc90078b4239f0d25392e58 and therefore no doc changes
are necessary here.

** Changed in: neutron
   Status: In Progress => 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/1688215

Title:
  Change list of available qos rules

Status in neutron:
  Invalid

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

  commit 3299cdffae5cd7196a1676da103da5e2e413ec21
  Author: Sławek Kapłoński 
  Date:   Sun Apr 30 08:17:29 2017 +

  Change list of available qos rules
  
  This patch changes way how neutron calculates which QoS rules
  are available to use. It now returns all rule types which are
  supported by at least one loaded QoS driver.
  If user will want to apply policy with rule unsupported by driver
  used by port then it will be catched on port/network update event.
  This validation mechanism was introduced in
  I75bd18b3a1875daa5639dd141fb7bbd6e1c54118
  
  DocImpact: list of returned available QoS rule types is changed
  
  Change-Id: Ia00d349625db358ab486802fc0ff2e69eaa3895e
  Closes-Bug: #1686898

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1688215/+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 1705683] Re: Leaked resources after cold migration

[Matt Riedemann]

** Changed in: nova
 Assignee: Matt Riedemann (mriedem) => Alexandru Muresan (amuresan)

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

** Changed in: nova/pike
   Status: New => Confirmed

** Changed in: nova/pike
   Importance: Undecided => Medium

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

Title:
  Leaked resources after cold migration

Status in compute-hyperv:
  Fix Released
Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) pike series:
  Confirmed

Bug description:
  At the moment, the vif ports are not unplugged after cold migration on
  the source node.

  This affects ovs ports, which have to be unplugged by nova.

  At the same time, attached volumes are not disconnected from the
  source node.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compute-hyperv/+bug/1705683/+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 1712075] Re: [FWaaS v2] L3 agent restart breaks firewall iptables configuration for router ports

[OpenStack Infra]

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

commit 0fac0d515a0cf5696a37dcde4fb2fdff88a8b537
Author: Elena Ezhova 
Date:   Mon Aug 21 01:08:13 2017 +0400

Fix router update on L3 agent restart

Currently on L3 agent restart FWaaS L3 agent extension
_process_router_update iterates over all router ports and
trigger firewall group update if a port belong to it.
In case when a firewall group contains several ports iptables rules
get re-written each time and in the result only the chains for
the last port in a loop remain.

With this change each firewall group would be updated with a full
list of a router ports that belong to it. Additionaly, refactor of
the _process_router_update method reduced its complexity and made
it more readable.
If a router would appear to have ports associated with several
firewall groups a warning would be emitted.

Added a unit test.

Closes-Bug: #1712075
Change-Id: I251f4f50578cd10da904a56e1622c18f2adf2d18


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

Title:
  [FWaaS v2] L3 agent restart breaks firewall iptables configuration for
  router ports

Status in neutron:
  Fix Released

Bug description:
  *Seen on:* Pike and master devstack with FWaaS v2

  *Scenario:*
  1. Create deny_icmp rule, a policy, a fw group, security group with all 
allowed.
  2. Create 1 router, 2 subnets, fw group assigned to router ports.
  3. Boot a VM in each subnet
  4. Check that iptables rules are applied and it is impossible to ping VMs by 
floating IP or from qrouter namespace
  5. Restart L3 agent

  *Expected result:*
  After the restart iptables rules are reapplied in the same way and the 
traffic is still blocked.

  *Actual result:*
  In case when a firewall group contains several ports iptables rules get 
re-written for each port and in the result only the chains for the last port in 
a loop remain.

  Example scenario: http://paste.openstack.org/show/618908/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1712075/+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 1714061] [NEW] test bug

[Rob Cresswell]

Public bug reported:

test bug ignore

** Affects: horizon
 Importance: Undecided
 Status: Invalid

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

Title:
  test bug

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  test bug ignore

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1714061/+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 1713975] Re: create subnet fails if we use non-default IPAM Driver

[Armando Migliaccio]

** Also affects: networking-infoblox
   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/1713975

Title:
  create subnet fails if we use non-default IPAM Driver

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

Bug description:
  Using ipam_driver=infoblox in neutron.conf, create subnet fails with
  following error:

  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00m  File 
"/opt/stack/neutron/neutron/db/api.py", line 124, in wrapped
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mreturn f(*dup_args, 
**dup_kwargs)
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00m  File 
"/opt/stack/neutron/neutron/db/db_base_plugin_v2.py", line 689, in 
_create_subnet_postcommit
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mresult, ipam_subnet)
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00m  File 
"/opt/stack/neutron/neutron/db/ipam_pluggable_backend.py", line 453, in 
add_auto_addrs_on_network_ports
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mif subnet['id'] != 
ipam_subnet.subnet_manager.neutron_id:
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mAttributeError: 
'InfobloxSubnet' object has no attribute 'subnet_manager'

  Further verified code in ipam_pluggable_backend.py file and observed
  following code at
  
https://github.com/openstack/neutron/blob/stable/pike/neutron/db/ipam_pluggable_backend.py#L453

  # TODO(kevinbenton): remove after bug/1666493 is resolved
  if subnet['id'] != ipam_subnet.subnet_manager.neutron_id:
  raise RuntimeError(
  "Subnet manager doesn't match subnet. %s != %s"
  % (subnet['id'], ipam_subnet.subnet_manager.neutron_id))

  As ipam_subnet.subnet_manager is defined specific to the neutron
  default ipam driver at
  
https://github.com/openstack/neutron/blob/stable/pike/neutron/ipam/drivers/neutrondb_ipam/driver.py#L129
  , it should not be used in generic file such as
  ipam_pluggable_backend.py which is used by other ipam_drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-infoblox/+bug/1713975/+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 1713590] Re: Plugging VFs no longer works without a readable phys_switch_id

[Brent Eagles]

** Project changed: os-vif => neutron

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

Title:
  Plugging VFs no longer works without a readable phys_switch_id

Status in neutron:
  Triaged

Bug description:
  Attempting to plug a VF fails with the following stack trace in the
  nova compute logs:

  2017-08-28 17:50:34.716 2843 ERROR os_vif 
[req-9fe05e3e-f7ae-4b2d-be27-90d81fe0b9fd 66e36d5620c24020ac6fa6fb8e580b6c 
df21f729c47347b299783a4c1f83e774 - default default] Failed to plug vif 
VIFHostDevice(active=False,address=fa:16:3e:de:b2:7d,dev_address=:0b:11.0,dev_type='ethernet',has_traffic_filtering=True,id=b5858ca0-c315-4b2a-b1a9-82a5b508bf2f,network=Network(19c75cc1-a553-4d3d-9a1a-9ad010102e31),plugin='ovs',port_profile=VIFPortProfileOVSRepresentor,preserve_on_delete=True):
 PciDeviceNotFoundById: PCI device :0b:11.0 not found
  2017-08-28 17:50:34.716 2843 ERROR os_vif Traceback (most recent call last):
  2017-08-28 17:50:34.716 2843 ERROR os_vif   File 
"/usr/lib/python2.7/site-packages/os_vif/__init__.py", line 77, in plug
  2017-08-28 17:50:34.716 2843 ERROR os_vif plugin.plug(vif, instance_info)
  2017-08-28 17:50:34.716 2843 ERROR os_vif   File 
"/usr/lib/python2.7/site-packages/vif_plug_ovs/ovs.py", line 191, in plug
  2017-08-28 17:50:34.716 2843 ERROR os_vif self._plug_vf_passthrough(vif, 
instance_info)
  2017-08-28 17:50:34.716 2843 ERROR os_vif   File 
"/usr/lib/python2.7/site-packages/vif_plug_ovs/ovs.py", line 163, in 
_plug_vf_passthrough
  2017-08-28 17:50:34.716 2843 ERROR os_vif pci_slot, pf_interface=True, 
switchdev=True)
  2017-08-28 17:50:34.716 2843 ERROR os_vif   File 
"/usr/lib/python2.7/site-packages/vif_plug_ovs/linux_net.py", line 373, in 
get_ifname_by_pci_address
  2017-08-28 17:50:34.716 2843 ERROR os_vif raise 
exception.PciDeviceNotFoundById(id=pci_addr)
  2017-08-28 17:50:34.716 2843 ERROR os_vif PciDeviceNotFoundById: PCI device 
:0b:11.0 not found
  2017-08-28 17:50:34.716 2843 ERROR os_vif 

  
  It appears that patch https://review.openstack.org/#/c/484051/ altered 
get_ifname_by_pci_address() always run a new helper function _is_switchdev() 
(it appears that it is assumed that switchdev should always be True). This 
causes plugging VFs on systems with drivers that do not support a readable 
phys_switch_id to fail.

  I ran the code interactively on the host system to determine the
  actual exception:

  >>> f = open('/sys/class/net/enp11s17/phys_switch_id', 'r')
  >>> print f.readline()
  Traceback (most recent call last):
File "", line 1, in 
  IOError: [Errno 95] Operation not supported

  From what I can tell, this should also cause plugging to fail on
  systems that have no phys_switch_id file at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1713590/+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 1713590] [NEW] Plugging VFs no longer works without a readable phys_switch_id

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Attempting to plug a VF fails with the following stack trace in the nova
compute logs:

2017-08-28 17:50:34.716 2843 ERROR os_vif 
[req-9fe05e3e-f7ae-4b2d-be27-90d81fe0b9fd 66e36d5620c24020ac6fa6fb8e580b6c 
df21f729c47347b299783a4c1f83e774 - default default] Failed to plug vif 
VIFHostDevice(active=False,address=fa:16:3e:de:b2:7d,dev_address=:0b:11.0,dev_type='ethernet',has_traffic_filtering=True,id=b5858ca0-c315-4b2a-b1a9-82a5b508bf2f,network=Network(19c75cc1-a553-4d3d-9a1a-9ad010102e31),plugin='ovs',port_profile=VIFPortProfileOVSRepresentor,preserve_on_delete=True):
 PciDeviceNotFoundById: PCI device :0b:11.0 not found
2017-08-28 17:50:34.716 2843 ERROR os_vif Traceback (most recent call last):
2017-08-28 17:50:34.716 2843 ERROR os_vif   File 
"/usr/lib/python2.7/site-packages/os_vif/__init__.py", line 77, in plug
2017-08-28 17:50:34.716 2843 ERROR os_vif plugin.plug(vif, instance_info)
2017-08-28 17:50:34.716 2843 ERROR os_vif   File 
"/usr/lib/python2.7/site-packages/vif_plug_ovs/ovs.py", line 191, in plug
2017-08-28 17:50:34.716 2843 ERROR os_vif self._plug_vf_passthrough(vif, 
instance_info)
2017-08-28 17:50:34.716 2843 ERROR os_vif   File 
"/usr/lib/python2.7/site-packages/vif_plug_ovs/ovs.py", line 163, in 
_plug_vf_passthrough
2017-08-28 17:50:34.716 2843 ERROR os_vif pci_slot, pf_interface=True, 
switchdev=True)
2017-08-28 17:50:34.716 2843 ERROR os_vif   File 
"/usr/lib/python2.7/site-packages/vif_plug_ovs/linux_net.py", line 373, in 
get_ifname_by_pci_address
2017-08-28 17:50:34.716 2843 ERROR os_vif raise 
exception.PciDeviceNotFoundById(id=pci_addr)
2017-08-28 17:50:34.716 2843 ERROR os_vif PciDeviceNotFoundById: PCI device 
:0b:11.0 not found
2017-08-28 17:50:34.716 2843 ERROR os_vif 


It appears that patch https://review.openstack.org/#/c/484051/ altered 
get_ifname_by_pci_address() always run a new helper function _is_switchdev() 
(it appears that it is assumed that switchdev should always be True). This 
causes plugging VFs on systems with drivers that do not support a readable 
phys_switch_id to fail.

I ran the code interactively on the host system to determine the actual
exception:

>>> f = open('/sys/class/net/enp11s17/phys_switch_id', 'r')
>>> print f.readline()
Traceback (most recent call last):
  File "", line 1, in 
IOError: [Errno 95] Operation not supported

>From what I can tell, this should also cause plugging to fail on systems
that have no phys_switch_id file at all.

** Affects: neutron
 Importance: Medium
 Status: Triaged

-- 
Plugging VFs no longer works without a readable phys_switch_id
https://bugs.launchpad.net/bugs/1713590
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 1285000] Re: instance data resides on destination node when vm is deleted during live-migration

[Matt Riedemann]

Marked newton as won't fix for this since we're past the support window
for newton on non-critical fixes like this one.

https://docs.openstack.org/project-team-guide/stable-branches.html

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

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

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

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

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

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

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

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

** Changed in: nova/newton
 Assignee: (unassigned) => Maciej Jozefczyk (maciej.jozefczyk)

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

** Changed in: nova/newton
   Importance: Undecided => Medium

** Changed in: nova/ocata
   Importance: Undecided => Medium

** Changed in: nova/pike
   Importance: Undecided => Medium

** Changed in: nova/ocata
 Assignee: (unassigned) => Maciej Jozefczyk (maciej.jozefczyk)

** Changed in: nova/pike
 Assignee: (unassigned) => Maciej Jozefczyk (maciej.jozefczyk)

** Changed in: nova/newton
   Status: In Progress => 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/1285000

Title:
  instance data resides on destination node when vm is deleted during
  live-migration

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) newton series:
  Won't Fix
Status in OpenStack Compute (nova) ocata series:
  In Progress
Status in OpenStack Compute (nova) pike series:
  In Progress

Bug description:
  If the VM is deleted during live-migration process, there is possibility that 
the instance data residing on the destination compute node is not deleted.
  Please refer to http://paste.openstack.org/show/69730/ reproduce the issue.

  IMO, One of the possible solution is to restrict the user from
  deleting the VM when live-migration is in progress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1285000/+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 1682020] Re: Remove nova default keymap option for qemu-kvm (deprecated)

[Matt Riedemann]

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

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

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

** Changed in: nova/pike
   Importance: Undecided => Medium

** Changed in: nova/pike
 Assignee: (unassigned) => Stephen Finucane (stephenfinucane)

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

Title:
  Remove nova default keymap option for qemu-kvm (deprecated)

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) pike series:
  In Progress

Bug description:
  Hi,

  Nowdays, qemu-kvm default keymap option -k en-us, or any keymap option
  is deprecated.

  In OpenStack it renders the web console access to vm unsuable even
  with the proper keymap in nova.conf. For exapmle the use of 'Alt-Gr +
  key' combination in French, Belgium, spanish, or alike keyboard is not
  working, this can be problematic for hard passwords.

  Using the linked patch and removing/commenting the keymap options in
  nova.conf, makes everything working again (depending on the NoVnc
  version which might be patched also on previous ones).

  So maybe by default the nova.conf should now comment/remove this
  option and we need to remove the default option in the nova code.

  Regards,
  Pierre-André

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1682020/+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 1714017] [NEW] The 'Provide user data to instances' article was lost in the current Nova Documentation

[Pavlukhin Max]

Public bug reported:

The 'Provide user data to instances' article was lost in the current
Nova Documentation.

There is one link to this article in Heat Documentation. We can see it
on this page: https://docs.openstack.org/heat/latest/glossary.html in
the 'User data' item. This link is called ' User data (OpenStack End
User Guide)'.

The article needs to be restored. I found the saved version on the
Amazon website: https://ec2-54-66-129-240.ap-
southeast-2.compute.amazonaws.com/httrack/docs/docs.openstack.org/user-
guide/cli.html


Thank you for attention!

** Affects: heat
 Importance: Undecided
 Status: New

** Affects: nova
 Importance: Undecided
 Status: New

** Affects: python-novaclient
 Importance: Undecided
 Status: New


** Tags: cli data doc docs documentation heat nova openstack user userdata

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

** Also affects: heat
   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/1714017

Title:
  The 'Provide user data to instances' article was lost in the current
  Nova Documentation

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

Bug description:
  The 'Provide user data to instances' article was lost in the current
  Nova Documentation.

  There is one link to this article in Heat Documentation. We can see it
  on this page: https://docs.openstack.org/heat/latest/glossary.html in
  the 'User data' item. This link is called ' User data (OpenStack End
  User Guide)'.

  The article needs to be restored. I found the saved version on the
  Amazon website: https://ec2-54-66-129-240.ap-
  southeast-2.compute.amazonaws.com/httrack/docs/docs.openstack.org
  /user-guide/cli.html

  
  Thank you for attention!

To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1714017/+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 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR

[Thomas Morin]

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

** Also affects: networking-bagpipe
   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/1608980

Title:
  Remove MANIFEST.in as it is not explicitly needed by PBR

Status in anvil:
  Invalid
Status in networking-bgpvpn:
  New
Status in craton:
  Fix Released
Status in DragonFlow:
  Fix Released
Status in ec2-api:
  Fix Released
Status in gce-api:
  Fix Released
Status in Glance:
  Fix Released
Status in Karbor:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Released
Status in Kosmos:
  Fix Released
Status in Magnum:
  Fix Released
Status in masakari:
  Fix Released
Status in BaGPipe:
  New
Status in networking-midonet:
  Fix Released
Status in networking-odl:
  Fix Released
Status in neutron:
  Fix Released
Status in Neutron LBaaS Dashboard:
  Fix Released
Status in octavia:
  Fix Released
Status in os-vif:
  Fix Released
Status in python-searchlightclient:
  In Progress
Status in OpenStack Search (Searchlight):
  Fix Released
Status in Solum:
  Fix Released
Status in Swift Authentication:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in Tricircle:
  Fix Released
Status in OpenStack DBaaS (Trove):
  Fix Released
Status in watcher:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  PBR do not explicitly require MANIFEST.in, so it can be removed.

  
  Snippet from: http://docs.openstack.org/infra/manual/developers.html

  Manifest

  Just like AUTHORS and ChangeLog, why keep a list of files you wish to
  include when you can find many of these in git. MANIFEST.in generation
  ensures almost all files stored in git, with the exception of
  .gitignore, .gitreview and .pyc files, are automatically included in
  your distribution. In addition, the generated AUTHORS and ChangeLog
  files are also included. In many cases, this removes the need for an
  explicit ‘MANIFEST.in’ file

To manage notifications about this bug go to:
https://bugs.launchpad.net/anvil/+bug/1608980/+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 1713141] Re: Some links of User doc is invalid

[OpenStack Infra]

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

commit 60248f0f595dc12ac40f8f937bc235869cafa059
Author: Rui Yuan Dou 
Date:   Mon Aug 21 11:20:20 2017 +0800

Update invalid links of User doc

Change-Id: I2ca27680f663642d4c3e4914bac07e1bedba71c1
Closes-bug: 1713141


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

Title:
  Some links of User doc is invalid

Status in Glance:
  Fix Released

Bug description:
  Links of user doc should be replaced with new address:

  doc/source/user/glanceapi.rst:

  Designated sections (definition) 

  > 
https://github.com/openstack/interop/blob/master/doc/source/process/Lexicon.rst

  OpenStack Core Definition 

  > 
https://github.com/openstack/interop/blob/master/doc/source/process/CoreDefinition.rst

  DefCore Guidelines Repository 
  > https://github.com/openstack/interop

  
  doc/source/user/metadefs-concepts.rst:

  Heat resource types: 
http://docs.openstack.org/developer/heat/template_guide/openstack.html
  > https://docs.openstack.org/heat/latest/template_guide/openstack.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1713141/+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 1714007] [NEW] Incorrect assert in test_routers._verify_gateway_port under neutron tests

[Abhilash S]

Public bug reported:

_verify_gateway_port() has the following code, which seems to be trying
to assert that the fixed ip of the port on the router is allocated from
an appropriate public subnet. Since it only takes the first subnet of
the public network, this will always fail if the ip of the port is in a
different subnet.

public_net_body = self.admin_client.show_network(
CONF.network.public_network_id)
public_subnet_id = public_net_body['network']['subnets'][0]
self.assertIn(public_subnet_id,
  [x['subnet_id'] for x in fixed_ips])

Similar bug: https://bugs.launchpad.net/tempest/+bug/1624057
The above bug has been fixed in openstack/tempest 14.0 onwards, however bug fix 
for same tests are not reflected under openstack/neutron tests.

This causes the following neutron tests to fail when having multiple
public subnets :

neutron.tests.tempest.api.test_routers.RoutersTest.test_update_router_set_gateway_with_snat_explicit
neutron.tests.tempest.api.test_routers.RoutersTest.test_update_router_set_gateway_without_snat
neutron.tests.tempest.api.test_routers.RoutersTest.test_update_router_reset_gateway_without_snat

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: neutron tempest

** Summary changed:

- Incorrect assert in test_routers._verify_gateway_port
+ Incorrect assert in test_routers._verify_gateway_port  under neutron tests

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

Title:
  Incorrect assert in test_routers._verify_gateway_port  under neutron
  tests

Status in neutron:
  New

Bug description:
  _verify_gateway_port() has the following code, which seems to be
  trying to assert that the fixed ip of the port on the router is
  allocated from an appropriate public subnet. Since it only takes the
  first subnet of the public network, this will always fail if the ip of
  the port is in a different subnet.

  public_net_body = self.admin_client.show_network(
  CONF.network.public_network_id)
  public_subnet_id = public_net_body['network']['subnets'][0]
  self.assertIn(public_subnet_id,
[x['subnet_id'] for x in fixed_ips])

  Similar bug: https://bugs.launchpad.net/tempest/+bug/1624057
  The above bug has been fixed in openstack/tempest 14.0 onwards, however bug 
fix for same tests are not reflected under openstack/neutron tests.

  This causes the following neutron tests to fail when having multiple
  public subnets :

  
neutron.tests.tempest.api.test_routers.RoutersTest.test_update_router_set_gateway_with_snat_explicit
  
neutron.tests.tempest.api.test_routers.RoutersTest.test_update_router_set_gateway_without_snat
  
neutron.tests.tempest.api.test_routers.RoutersTest.test_update_router_reset_gateway_without_snat

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1714007/+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 1713740] Re: task status change incorrectly reported in info log message

[OpenStack Infra]

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

commit e1321298e7899d0d0d6b96243935454c427e2464
Author: Brian Rosmaita 
Date:   Tue Aug 29 11:10:22 2017 -0400

Change variable used by log message

The code was changing the status of a task and then logging an
info message about the change using the already-changed variable.
This patch saves the old status before the task status is modified
so that the status transition can be accurately reported in the log.

Change-Id: I84fef1d710f24f601971a348f53d74b6a6d6a2f9
Closes-bug: #1713740


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

Title:
  task status change incorrectly reported in info log message

Status in Glance:
  Fix Released

Bug description:
  This is minor but annoying.  The INFO message reporting the status
  change of a task always looks like this:

  2017-08-29 09:49:22.561 INFO glance.domain [-] Task 
[9cc88fb7-eb80-48e9-8bfd-be68bdbadb7f] status changing from processing to 
processing
  2017-08-29 09:49:24.700 INFO glance.domain [-] Task 
[9cc88fb7-eb80-48e9-8bfd-be68bdbadb7f] status changing from success to success

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1713740/+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 1713975] [NEW] create subnet fails if we use non-default IPAM Driver

[Akash Deep]

Public bug reported:

Using ipam_driver=infoblox in neutron.conf, create subnet fails with
following error:

Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00m  File 
"/opt/stack/neutron/neutron/db/api.py", line 124, in wrapped
Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mreturn f(*dup_args, 
**dup_kwargs)
Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00m  File 
"/opt/stack/neutron/neutron/db/db_base_plugin_v2.py", line 689, in 
_create_subnet_postcommit
Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mresult, ipam_subnet)
Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00m  File 
"/opt/stack/neutron/neutron/db/ipam_pluggable_backend.py", line 453, in 
add_auto_addrs_on_network_ports
Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mif subnet['id'] != 
ipam_subnet.subnet_manager.neutron_id:
Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mAttributeError: 
'InfobloxSubnet' object has no attribute 'subnet_manager'

Further verified code in ipam_pluggable_backend.py file and observed
following code:

# TODO(kevinbenton): remove after bug/1666493 is resolved
if subnet['id'] != ipam_subnet.subnet_manager.neutron_id:
raise RuntimeError(
"Subnet manager doesn't match subnet. %s != %s"
% (subnet['id'], ipam_subnet.subnet_manager.neutron_id))

As ipam_subnet.subnet_manager is defined specific to the neutron default
ipam driver at
https://github.com/openstack/neutron/blob/stable/pike/neutron/ipam/drivers/neutrondb_ipam/driver.py#L129
, it should not be used in generic file such as
ipam_pluggable_backend.py which is used by other ipam_drivers.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: ipam-driver neutron openstack pike

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

Title:
  create subnet fails if we use non-default IPAM Driver

Status in neutron:
  New

Bug description:
  Using ipam_driver=infoblox in neutron.conf, create subnet fails with
  following error:

  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00m  File 
"/opt/stack/neutron/neutron/db/api.py", line 124, in wrapped
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mreturn f(*dup_args, 
**dup_kwargs)
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00m  File 
"/opt/stack/neutron/neutron/db/db_base_plugin_v2.py", line 689, in 
_create_subnet_postcommit
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mresult, ipam_subnet)
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00m  File 
"/opt/stack/neutron/neutron/db/ipam_pluggable_backend.py", line 453, in 
add_auto_addrs_on_network_ports
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mif subnet['id'] != 
ipam_subnet.subnet_manager.neutron_id:
  Aug 30 13:09:07 localhost neutron-server[767]: ERROR 
neutron.pecan_wsgi.hooks.translation #033[01;35m#033[00mAttributeError: 
'InfobloxSubnet' object has no attribute 'subnet_manager'

  Further verified code in ipam_pluggable_backend.py file and observed
  following code:

  # TODO(kevinbenton): remove after bug/1666493 is resolved
  if subnet['id'] != ipam_subnet.subnet_manager.neutron_id:
  raise RuntimeError(
  "Subnet manager doesn't match subnet. %s != %s"
  % (subnet['id'], ipam_subnet.subnet_manager.neutron_id))

  As ipam_subnet.subnet_manager is defined specific to the neutron
  default ipam driver at
  
https://github.com/openstack/neutron/blob/stable/pike/neutron/ipam/drivers/neutrondb_ipam/driver.py#L129
  , it should not be used in generic file such as
  ipam_pluggable_backend.py which is used by other ipam_drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1713975/+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 1713974] [NEW] payload samples are not hidden in the notification devref by default

[Balazs Gibizer]

Public bug reported:

With the new doc template the showing and hiding of the notification
samples in the notification dev-ref[1] isn't working and therefore every
sample shown by default that makes the document hard to read.

Most probably the html structure has been changed in a way that breaks
the javascript doing the hiding.

[1] https://docs.openstack.org/nova/latest/reference/notifications.html
#existing-versioned-notifications

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


** Tags: doc notifications

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

** Tags added: doc notifications

** Summary changed:

- examples isn't hidden in the notification devref by default
+ payload samples are not hidden in the notification devref by default

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

Title:
  payload samples are not hidden in the notification devref by default

Status in OpenStack Compute (nova):
  New

Bug description:
  With the new doc template the showing and hiding of the notification
  samples in the notification dev-ref[1] isn't working and therefore
  every sample shown by default that makes the document hard to read.

  Most probably the html structure has been changed in a way that breaks
  the javascript doing the hiding.

  [1]
  https://docs.openstack.org/nova/latest/reference/notifications.html
  #existing-versioned-notifications

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1713974/+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 1713970] [NEW] Keystone Internal Server Error (HTTP 500) after apache restart when influxdb is installed

[Rohit Bagde]

Public bug reported:

When influxdb is installed, a Internal Server Error is shown with this trace in 
/var/log/apache2/keystone.log after executing systemctl restart apache2.
Logs:
2017-08-30 17:32:36.492291 OSError: [Errno 13] Permission denied: 
'/usr/local/lib/python2.7/dist-packages/urllib3-1.22.dist-info'
2017-08-30 17:33:15.741127 mod_wsgi (pid=3736): Target WSGI script 
'/usr/bin/keystone-wsgi-public' cannot be loaded as Python module.
2017-08-30 17:33:15.741187 mod_wsgi (pid=3736): Exception occurred processing 
WSGI script '/usr/bin/keystone-wsgi-public'.
2017-08-30 17:33:15.741218 Traceback (most recent call last):
2017-08-30 17:33:15.741235 File "/usr/bin/keystone-wsgi-public", line 6, in
2017-08-30 17:33:15.741295 from keystone.server.wsgi import 
initialize_public_application
2017-08-30 17:33:15.741306 File 
"/usr/lib/python2.7/dist-packages/keystone/server/wsgi.py", line 18, in
2017-08-30 17:33:15.741360 from oslo_log import log
2017-08-30 17:33:15.741369 File 
"/usr/lib/python2.7/dist-packages/oslo_log/log.py", line 42, in
2017-08-30 17:33:15.741467 from oslo_config import cfg
2017-08-30 17:33:15.741476 File 
"/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 458, in
2017-08-30 17:33:15.742008 import debtcollector
2017-08-30 17:33:15.742031 File 
"/usr/lib/python2.7/dist-packages/debtcollector/init.py", line 15, in
2017-08-30 17:33:15.742077 import pbr.version
2017-08-30 17:33:15.742087 File 
"/usr/lib/python2.7/dist-packages/pbr/version.py", line 25, in
2017-08-30 17:33:15.742198 import pkg_resources
2017-08-30 17:33:15.742208 File 
"/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3019, in
2017-08-30 17:33:15.742784 @_call_aside
2017-08-30 17:33:15.742801 File 
"/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3003, in 
_call_aside
2017-08-30 17:33:15.742819 f(*args, **kwargs)
2017-08-30 17:33:15.742841 File 
"/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3032, in 
_initialize_master_working_set
2017-08-30 17:33:15.742852 working_set = WorkingSet._build_master()
2017-08-30 17:33:15.742858 File 
"/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 646, in 
_build_master
2017-08-30 17:33:15.742867 ws = cls()
2017-08-30 17:33:15.742872 File 
"/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 639, in init
2017-08-30 17:33:15.742879 self.add_entry(entry)
2017-08-30 17:33:15.742884 File 
"/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 695, in add_entry
2017-08-30 17:33:15.742892 for dist in find_distributions(entry, True):
2017-08-30 17:33:15.742897 File 
"/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2012, in 
find_on_path
2017-08-30 17:33:15.742905 if len(os.listdir(fullpath)) == 0:

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

Title:
  Keystone Internal Server Error (HTTP 500) after apache restart when
  influxdb is installed

Status in OpenStack Identity (keystone):
  New

Bug description:
  When influxdb is installed, a Internal Server Error is shown with this trace 
in /var/log/apache2/keystone.log after executing systemctl restart apache2.
  Logs:
  2017-08-30 17:32:36.492291 OSError: [Errno 13] Permission denied: 
'/usr/local/lib/python2.7/dist-packages/urllib3-1.22.dist-info'
  2017-08-30 17:33:15.741127 mod_wsgi (pid=3736): Target WSGI script 
'/usr/bin/keystone-wsgi-public' cannot be loaded as Python module.
  2017-08-30 17:33:15.741187 mod_wsgi (pid=3736): Exception occurred processing 
WSGI script '/usr/bin/keystone-wsgi-public'.
  2017-08-30 17:33:15.741218 Traceback (most recent call last):
  2017-08-30 17:33:15.741235 File "/usr/bin/keystone-wsgi-public", line 6, in
  2017-08-30 17:33:15.741295 from keystone.server.wsgi import 
initialize_public_application
  2017-08-30 17:33:15.741306 File 
"/usr/lib/python2.7/dist-packages/keystone/server/wsgi.py", line 18, in
  2017-08-30 17:33:15.741360 from oslo_log import log
  2017-08-30 17:33:15.741369 File 
"/usr/lib/python2.7/dist-packages/oslo_log/log.py", line 42, in
  2017-08-30 17:33:15.741467 from oslo_config import cfg
  2017-08-30 17:33:15.741476 File 
"/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 458, in
  2017-08-30 17:33:15.742008 import debtcollector
  2017-08-30 17:33:15.742031 File 
"/usr/lib/python2.7/dist-packages/debtcollector/init.py", line 15, in
  2017-08-30 17:33:15.742077 import pbr.version
  2017-08-30 17:33:15.742087 File 
"/usr/lib/python2.7/dist-packages/pbr/version.py", line 25, in
  2017-08-30 17:33:15.742198 import pkg_resources
  2017-08-30 17:33:15.742208 File 
"/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3019, in
  2017-08-30 17:33:15.742784 @_call_aside
  2017-08-30 17:33:15.742801 File 
"/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3003, in 

[Yahoo-eng-team] [Bug 1713750] Re: typo in admin doc ssh-configuration.html

[OpenStack Infra]

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

commit e9c30d62e641c6ce852c7efe6a8d6296cf5b73ef
Author: rajat29 
Date:   Wed Aug 30 11:36:46 2017 +0530

Typo fix in admin doc ssh-configuration.html

Change-Id: Ibbf24ebb8fc0afa2fed1cda250fd04daf7fbffc2
Closes-bug: #1713750


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

Title:
  typo in admin doc ssh-configuration.html

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  - [x] I have a fix to the document that I can paste below including
  example: input and output.

  There is typo in the pub key name of doc admin/ssh-configuration.html

  Actual key name in doc: id_ras.pub
  Expected key name in doc: id_rsa.pub

  I will provide a patch for it.

  ---
  Release: 16.0.0.0rc2.dev37 on 2017-08-25 03:14
  SHA: 8b162ba21f06272f915070473640d493dd70beec
  Source: 
https://git.openstack.org/cgit/openstack/nova/tree/doc/source/admin/ssh-configuration.rst
  URL: https://docs.openstack.org/nova/pike/admin/ssh-configuration.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1713750/+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 1713927] [NEW] gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-xenial fails constantly

[Jakub Libosvar]

Public bug reported:

The job is at almost 100% failure rate.
http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=11

It went up from 24% to 100% at about Aug 26 6pm UTC.

Logs: http://logs.openstack.org/32/498932/1/check/gate-grenade-dsvm-
neutron-dvr-multinode-ubuntu-xenial/6ba16a7/logs/grenade.sh.txt.gz

** Affects: neutron
 Importance: Critical
 Status: New


** Tags: gate-failure l3-dvr-backlog

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

Title:
  gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-xenial fails constantly

Status in neutron:
  New

Bug description:
  The job is at almost 100% failure rate.
  
http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=11

  It went up from 24% to 100% at about Aug 26 6pm UTC.

  Logs: http://logs.openstack.org/32/498932/1/check/gate-grenade-dsvm-
  neutron-dvr-multinode-ubuntu-xenial/6ba16a7/logs/grenade.sh.txt.gz

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