date:20180209

[Yahoo-eng-team] [Bug 1748591] [NEW] neutron extension-list is fetched in every request related to neutron

2018-02-09 Thread Akihiro Motoki

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

Public bug reported:

neutron extension-list is fetched for every request related to neutron.

neutron extension-list rarely changes in usual deployments. There is no need to 
fetch it in every request.
Horizon already caches nova and cinder extension list. The same thing can be 
done for neutron extension-list.

** Affects: horizon
 Importance: High
 Assignee: Akihiro Motoki (amotoki)
 Status: New


** Tags: large-scale queens-backport-potential

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

Title:
  neutron extension-list is fetched in every request related to neutron

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  neutron extension-list is fetched for every request related to
  neutron.

  neutron extension-list rarely changes in usual deployments. There is no need 
to fetch it in every request.
  Horizon already caches nova and cinder extension list. The same thing can be 
done for neutron extension-list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1748591/+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 1731431] Re: Cloud-init could not identify OVF datasource

2018-02-09 Thread Launchpad Bug Tracker

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
   Status: Incomplete => Expired

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

Title:
  Cloud-init could not identify OVF datasource

Status in cloud-init:
  Expired

Bug description:
  Deployed OVF template with latest Xenial to vmWare vSphere ESXi via
  vCenter based on the latest OVA, sourced from: http://cloud-
  images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64.ova
  (dated November 9, 2017).

  Cannot attach requested contents due to sensitive data.

  **
  # A new feature in cloud-init identified possible datasources for#
  # this system as:#
  #   ['Ec2', 'None']  #
  # However, the datasource used was: OVF  #
  ##
  # In the future, cloud-init will only attempt to use datasources that#
  # are identified or specifically configured. #
  # For more information see   #
  #   https://bugs.launchpad.net/bugs/1669675  #
  ##
  # If you are seeing this message, please file a bug against  #
  # cloud-init at  #
  #https://bugs.launchpad.net/cloud-init/+filebug?field.tags=dsid  #
  # Make sure to include the cloud provider your instance is   #
  # running on.#
  ##

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1731431/+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 1737092] Re: server-generated directory index forbidden by Options directive

2018-02-09 Thread Launchpad Bug Tracker

[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]

** Changed in: horizon
   Status: Incomplete => Expired

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

Title:
  server-generated directory index forbidden by Options directive

Status in OpenStack Dashboard (Horizon):
  Expired

Bug description:
  Bug describe:

  httpd error_log:
  [Fri Dec 08 11:20:31.803594 2017] [autoindex:error] [pid 78430] [client 
192.168.20.67:6467] AH01276: Cannot serve directory /var/www/html/: No matching 
DirectoryIndex (index.html) found, and server-generated directory index 
forbidden by Options directive
  [Fri Dec 08 11:25:50.652786 2017] [core:error] [pid 78427] [client 
192.168.20.67:6471] End of script output before headers: django.wsgi
  [Fri Dec 08 11:32:27.556274 2017] [mpm_prefork:notice] [pid 78410] AH00170: 
caught SIGWINCH, shutting down gracefully
  [Fri Dec 08 11:32:48.251386 2017] [suexec:notice] [pid 79126] AH01232: suEXEC 
mechanism enabled (wrapper: /usr/sbin/suexec)
  [Fri Dec 08 11:32:48.266330 2017] [auth_digest:notice] [pid 79126] AH01757: 
generating secret for digest authentication ...
  [Fri Dec 08 11:32:48.267016 2017] [lbmethod_heartbeat:notice] [pid 79126] 
AH02282: No slotmem from mod_heartmonitor
  [Fri Dec 08 11:32:48.277801 2017] [mpm_prefork:notice] [pid 79126] AH00163: 
Apache/2.4.6 (CentOS) mod_wsgi/3.4 Python/2.7.5 configured -- resuming normal 
operations
  [Fri Dec 08 11:32:48.277830 2017] [core:notice] [pid 79126] AH00094: Command 
line: '/usr/sbin/httpd -D FOREGROUND'
  [Fri Dec 08 11:32:55.489711 2017] [autoindex:error] [pid 79144] [client 
192.168.20.67:6612] AH01276: Cannot serve directory /var/www/html/: No matching 
DirectoryIndex (index.html) found, and server-generated directory index 
forbidden by Options directive
  [Fri Dec 08 11:37:59.339107 2017] [core:error] [pid 79142] [client 
192.168.20.67:6611] End of script output before headers: django.wsgi


  curl -l localhost/dashboard

  
  500 Internal Server Error
  
  Internal Server Error
  The server encountered an internal error or
  misconfiguration and was unable to complete
  your request.
  Please contact the server administrator at 
   root@localhost to inform them of the time this error occurred,
   and the actions you performed just before this error.
  More information about this error may be available
  in the server error log.
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1737092/+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 1737130] Re: disable_root: 1 but root can still log in

2018-02-09 Thread Launchpad Bug Tracker

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
   Status: Incomplete => Expired

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

Title:
  disable_root: 1 but root can still log in

Status in cloud-init:
  Expired

Bug description:
  In my cloud.cfg I have tried:
  disable_root: true
  disable_root: 1
  disable_root: True

  But root is still able to log in via ssh.

  RHEL 7.3
  Openstack 10
  cloud-init 0.7.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1737130/+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 1748582] [NEW] Trunk subports don't have a device ID

2018-02-09 Thread Ivar Lazzaro

Public bug reported:

When adding a port to a Trunk, it gets bound to the parent's host and gets the 
owner type trunk:subport.
However, the parent device_id is not passed to the subport itself. This will 
make checks like the networking_sfc port pair validation fail as it expects 
both the port pair ports to belong to the same device [0]
Ofc sfc could check the parent's device ID in case of a subport, but I think it 
also makes sense for the neutron port to show such ID as part of the binding.

[0] https://github.com/openstack/networking-
sfc/blob/stable/queens/networking_sfc/db/sfc_db.py#L484-L496

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

Title:
  Trunk subports don't have a device ID

Status in neutron:
  New

Bug description:
  When adding a port to a Trunk, it gets bound to the parent's host and gets 
the owner type trunk:subport.
  However, the parent device_id is not passed to the subport itself. This will 
make checks like the networking_sfc port pair validation fail as it expects 
both the port pair ports to belong to the same device [0]
  Ofc sfc could check the parent's device ID in case of a subport, but I think 
it also makes sense for the neutron port to show such ID as part of the binding.

  [0] https://github.com/openstack/networking-
  sfc/blob/stable/queens/networking_sfc/db/sfc_db.py#L484-L496

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1748582/+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 1748354] Re: ec2: systemctl restart cloud-init after upgrade 17.1.46 -> 17.2.30

2018-02-09 Thread Launchpad Bug Tracker

This bug was fixed in the package cloud-init -
17.2-34-g644048e3-0ubuntu1

---
cloud-init (17.2-34-g644048e3-0ubuntu1) bionic; urgency=medium

  * New upstream snapshot.
- EC2: Fix get_instance_id called against cached datasource pickle.
  [Chad Smith] (LP: #1748354)
- cli: fix cloud-init status to report running when before result.json
  [Chad Smith] (LP: #1747965)
- net: accept network-config in netplan format for renaming interfaces
  [Ryan Harper] (LP: #1709715)
- Fix ssh keys validation in ssh_util [Tatiana Kholkina]

 -- Scott Moser   Fri, 09 Feb 2018 17:04:03 -0500

** Changed in: cloud-init (Ubuntu)
   Status: In Progress => 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/1748354

Title:
  ec2: systemctl restart cloud-init after upgrade 17.1.46 -> 17.2.30

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

Bug description:
  During proposed SRU testing, I discovered an upgrade issue for EC2
  customers who don't reboot their instances after cloud-init upgrade
  and instead issue the commandline 'systemctl restart cloud-init'.

  
  The following traceback is caused by the new instance document changes added 
in rev https://git.launchpad.net/cloud-init/commit/?id=703241a3.

  What this changeset didn't account for is our pickled
  ec2localdatasource from earlier get_data runs, not persisting an
  Ec2LocalDatasouce.identity attribute so subsequent get_instance_id
  calls wouldn't see this attribute on the class yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cloud-init 17.2-30-gf7deaf15-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-1050.59-aws 4.4.98
  Uname: Linux 4.4.0-1050-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CloudName: Amazon - Ec2
  Date: Thu Feb  8 23:42:52 2018
  Ec2AMI: ami-c9a693ac
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2b
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  cloud-init-log-warnings:
   2018-02-08 23:35:05,664 - DataSourceEc2.py[DEBUG]: strict_mode: warn, 
cloud_platform=AWS
   2018-02-08 23:39:12,559 - util.py[WARNING]: failed stage init
   AttributeError: 'DataSourceEc2Local' object has no attribute 'identity'
   2018-02-08 23:42:09,995 - util.py[WARNING]: failed stage init
   AttributeError: 'DataSourceEc2Local' object has no attribute 'identity'
  user_data.txt:

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1748354/+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 1746996] Re: bagpipe: IPAllocation DB query failing, engine facade mismatch

2018-02-09 Thread Miguel Lavalle

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

Title:
  bagpipe: IPAllocation DB query failing, engine facade mismatch

Status in networking-bgpvpn:
  Confirmed
Status in BaGPipe:
  Fix Released
Status in neutron:
  Fix Released

Bug description:
  
networking_bgpvpn.tests.unit.services.bagpipe.test_bagpipe.TestBagpipeServiceDriverV2RPCs.test_router_itf_event_network_assoc
  is currently failing

  Traceback (most recent call last):
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/networking_bgpvpn/neutron/services/service_drivers/bagpipe/bagpipe_v2.py",
 line 260, in registry_router_interface_before_delete
  context, router_id, network_id)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/local/lib/python2.7/site-packages/oslo_log/helpers.py",
 line 67, in wrapper
  return method(*args, **kwargs)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/networking_bgpvpn/neutron/services/service_drivers/bagpipe/bagpipe_v2.py",
 line 218, in notify_router_interface_deleted
  network_id=net_id) +
File "neutron/objects/base.py", line 561, in get_objects
  return [cls._load_object(context, db_obj) for db_obj in db_objs]
File "neutron/objects/base.py", line 496, in _load_object
  obj.from_db_object(db_obj)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/src/networking-bagpipe/networking_bagpipe/objects/bgpvpn.py",
 line 156, in from_db_object
  self._load_subnets(obj)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/src/networking-bagpipe/networking_bagpipe/objects/bgpvpn.py",
 line 150, in _load_subnets
  subnets_info = _get_subnets_info(self.obj_context, self.network_id)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/src/networking-bagpipe/networking_bagpipe/objects/bgpvpn.py",
 line 62, in _get_subnets_info
  for subnet in subnets
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/src/networking-bagpipe/networking_bagpipe/objects/bgpvpn.py",
 line 47, in _get_gateway_mac_by_subnet
  port = Port.get_object(obj_context, id=ip_allocation.port_id)
File "neutron/objects/base.py", line 538, in get_object
  return cls._load_object(context, db_obj)
File "neutron/objects/base.py", line 496, in _load_object
  obj.from_db_object(db_obj)
File "neutron/objects/ports.py", line 409, in from_db_object
  super(Port, self).from_db_object(db_obj)
File "neutron/objects/base.py", line 440, in from_db_object
  self.load_synthetic_db_fields(db_obj)
File "neutron/objects/base.py", line 737, in load_synthetic_db_fields
  for obj in synth_db_objs]
File "neutron/objects/base.py", line 498, in _load_object
  context.session.expunge(obj.db_obj)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/orm/session.py",
 line 1650, in expunge
  state_str(state))
  InvalidRequestError: Instance  is not present 
in this Session

  
  "git bisect" show that neutron commit 
906eda44d2c230be99fc5c61daa0f359ab46a3ad [1] introduces the issue

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/bgpvpn/+bug/1746996/+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 1748354] Re: ec2: systemctl restart cloud-init after upgrade 17.1.46 -> 17.2.30

2018-02-09 Thread Scott Moser

** Also affects: cloud-init
   Importance: Undecided
   Status: New

** Changed in: cloud-init
   Status: New => Fix Committed

** Changed in: cloud-init
   Importance: Undecided => Medium

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

Title:
  ec2: systemctl restart cloud-init after upgrade 17.1.46 -> 17.2.30

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  In Progress

Bug description:
  During proposed SRU testing, I discovered an upgrade issue for EC2
  customers who don't reboot their instances after cloud-init upgrade
  and instead issue the commandline 'systemctl restart cloud-init'.

  
  The following traceback is caused by the new instance document changes added 
in rev https://git.launchpad.net/cloud-init/commit/?id=703241a3.

  What this changeset didn't account for is our pickled
  ec2localdatasource from earlier get_data runs, not persisting an
  Ec2LocalDatasouce.identity attribute so subsequent get_instance_id
  calls wouldn't see this attribute on the class yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cloud-init 17.2-30-gf7deaf15-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-1050.59-aws 4.4.98
  Uname: Linux 4.4.0-1050-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CloudName: Amazon - Ec2
  Date: Thu Feb  8 23:42:52 2018
  Ec2AMI: ami-c9a693ac
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2b
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  cloud-init-log-warnings:
   2018-02-08 23:35:05,664 - DataSourceEc2.py[DEBUG]: strict_mode: warn, 
cloud_platform=AWS
   2018-02-08 23:39:12,559 - util.py[WARNING]: failed stage init
   AttributeError: 'DataSourceEc2Local' object has no attribute 'identity'
   2018-02-08 23:42:09,995 - util.py[WARNING]: failed stage init
   AttributeError: 'DataSourceEc2Local' object has no attribute 'identity'
  user_data.txt:

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1748354/+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 1748559] [NEW] image-create header is static

2018-02-09 Thread Brian Rosmaita

Public bug reported:

Part of interoperable image import is that the image-create response
should return a 'OpenStack-image-import-methods' header containing the
list of methods supported by that cloud.  Currently, it always returns
'glance-direct'.  It needs to populate the header from the
enabled_image_methods configuration setting.

** Affects: glance
 Importance: High
 Assignee: Brian Rosmaita (brian-rosmaita)
 Status: In Progress

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

Title:
  image-create header is static

Status in Glance:
  In Progress

Bug description:
  Part of interoperable image import is that the image-create response
  should return a 'OpenStack-image-import-methods' header containing the
  list of methods supported by that cloud.  Currently, it always returns
  'glance-direct'.  It needs to populate the header from the
  enabled_image_methods configuration setting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1748559/+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 1748546] [NEW] ovsfw tempest tests random fails

2018-02-09 Thread Slawek Kaplonski

Public bug reported:

Some random tests from neutron-tempest-ovsfw job are failing very often.
Only common thing in those failing tests is that test fails because
instance is not reachable and it looks that it is not reachable because
of some missing firewall Openflow rules.

Example of failing tests can be found e.g. on:
http://logs.openstack.org/57/542257/4/check/neutron-tempest-
ovsfw/cf76bcb/logs/testr_results.html.gz or on
http://logs.openstack.org/54/537654/4/check/neutron-tempest-
ovsfw/5c90b2b/logs/testr_results.html.gz (except hard_reboot test which
is different problem and is covered in
https://bugs.launchpad.net/neutron/+bug/1747709)

** Affects: neutron
 Importance: High
 Assignee: Slawek Kaplonski (slaweq)
 Status: Confirmed


** Tags: gate-failure ovs-fw

** Changed in: neutron
 Assignee: (unassigned) => Slawek Kaplonski (slaweq)

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

Title:
  ovsfw tempest tests random fails

Status in neutron:
  Confirmed

Bug description:
  Some random tests from neutron-tempest-ovsfw job are failing very
  often. Only common thing in those failing tests is that test fails
  because instance is not reachable and it looks that it is not
  reachable because of some missing firewall Openflow rules.

  Example of failing tests can be found e.g. on:
  http://logs.openstack.org/57/542257/4/check/neutron-tempest-
  ovsfw/cf76bcb/logs/testr_results.html.gz or on
  http://logs.openstack.org/54/537654/4/check/neutron-tempest-
  ovsfw/5c90b2b/logs/testr_results.html.gz (except hard_reboot test
  which is different problem and is covered in
  https://bugs.launchpad.net/neutron/+bug/1747709)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1748546/+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 1748544] [NEW] set_admin_password in the libvirt driver does not save the password in system metadata

2018-02-09 Thread melanie witt

Public bug reported:

We have an API for setting the admin password for an already created
instance and we have a metadata API for retrieving the encrypted
password. In the libvirt driver, when a request to set the admin
password is received, it is indeed set in the guest but the instance
system metadata is never updated with the encrypted password, so
attempts to retrieve the password via the metadata service API result
in an empty string returned instead of the encrypted password.

** Affects: nova
 Importance: Undecided
 Assignee: melanie witt (melwitt)
 Status: In Progress


** Tags: libvirt

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

Title:
  set_admin_password in the libvirt driver does not save the password in
  system metadata

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  We have an API for setting the admin password for an already created
  instance and we have a metadata API for retrieving the encrypted
  password. In the libvirt driver, when a request to set the admin
  password is received, it is indeed set in the guest but the instance
  system metadata is never updated with the encrypted password, so
  attempts to retrieve the password via the metadata service API result
  in an empty string returned instead of the encrypted password.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1748544/+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 1446078] Re: Apache error logs contains non-error messages

2018-02-09 Thread Akihiro Motoki

There is no good solution that horizon can do more and there are possible 
configurations.
I am marking this as Won't Fix.

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

Title:
   Apache error logs contains non-error messages

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

Bug description:
  In the file /var/log/apache2/horizon.error.log there are many lines
  that are not errors:

  [Fri Apr 17 14:49:32.604840 2015] [:error] [pid 28933:tid 140515448411904] 
Login successful for user "admin".
  [Fri Apr 17 13:04:25.892490 2015] [:error] [pid 28933:tid 140515448411904] 
Logging out user "admin".
  [Fri Apr 17 06:08:22.662311 2015] [:error] [pid 28933:tid 140515414841088] 
Creating user with name "demo"
  [Fri Apr 17 14:50:51.395871 2015] [:error] [pid 28933:tid 140515414841088] 
Project switch successful for user "admin".
  [Thu Apr 16 08:40:23.971582 2015] [:error] [pid 28933:tid 140515473590016] 
Deleted token 9295d3bcfb74cda6703b91a94487072c

  All these messages are logged with class 'ERROR'. As these messages
  are success messages they must be of type 'INFO'

  To reproduce the bug - Login to the dashboard and then check the
  horizon.error.log, You'll find the login success message in the log
  with class [:error]

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1446078/+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 1748512] [NEW] web-download is subject to same port scan vulnerability as v1 copy_from

2018-02-09 Thread Erno Kuvaja

Public bug reported:

The feature is currently at parr with v1 copy_from which means
https://bugs.launchpad.net/glance/+bug/1606495 does apply as well.

** Affects: glance
 Importance: Critical
 Assignee: Erno Kuvaja (jokke)
 Status: In Progress

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

** Changed in: glance
 Assignee: (unassigned) => Erno Kuvaja (jokke)

** Changed in: glance
Milestone: None => queens-rc2

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

Title:
  web-download is subject to same port scan vulnerability as v1
  copy_from

Status in Glance:
  In Progress

Bug description:
  The feature is currently at parr with v1 copy_from which means
  https://bugs.launchpad.net/glance/+bug/1606495 does apply as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1748512/+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 1747650] Re: Make bdms querying in multiple cells use scatter-gather

2018-02-09 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/541246
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=ea6757092df85b6cce38980ae5b7f54b76657e01
Submitter: Zuul
Branch:master

commit ea6757092df85b6cce38980ae5b7f54b76657e01
Author: Surya Seetharaman 
Date:   Tue Feb 6 12:36:50 2018 +0100

Make bdms querying in multi-cell use scatter-gather and ignore down cell

This patch makes the querying of bdms from multiple cells in the
_get_instance_bdms_in_multiple_cells function of extended_volumes use
scatter_gather_cells thus making the process, parallel. It also adds
warnings in case a cell is not available; which the operator can later
tweak, if an exception needs to be raised. So for now, cells that are
not reachable are ignored and it proceeds to the next cell.

Change-Id: I0e05eb1e2ad37962968b79100bf4a96c7d6ddd8f
Closes-Bug: #1747650


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

Title:
  Make bdms querying in multiple cells use scatter-gather

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Currently the "_get_instance_bdms_in_multiple_cells" function in
  extended_volumes runs sequentially and this affects the performance in
  case of large deployments (running a lot of cells) :
  
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/extended_volumes.py#L50

  So it would be nice to use the scatter_gather_cells function to do
  this operation in parallel.

  Also apart from the performance scaling point of view, in case
  connection to a particular cell fails, it would be nice to have
  sentinels returned which is done by the scatter_gather_cells function.
  This helps when a cell is down.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1747650/+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 1736468] Re: glance-scrubber does not work using SSL

2018-02-09 Thread Brian Rosmaita

As of Queens, the scrubber no longer contacts the glance registry (which
required keystone authentication), but instead goes directly to the
database.

Fixed by Change-Id: I26f570b85617200880543b7114730a1ac76d3fb1

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

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

Title:
  glance-scrubber does not work using SSL

Status in Glance:
  Fix Released

Bug description:
  Using glance registry and glance api over SSL, glance-scrubber doe not
  work in Ocata.

  This is the error i'm getting :

  glance-scrubber  --config-file /etc/glance/glance-scrubber.conf

  Option "verbose" from group "DEFAULT" is deprecated for removal.  Its value 
may be silently ignored in the future.
  2017-12-05 10:17:15.870 950 DEBUG glance_store.backend [-] Attempting to 
import store cinder _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.871 950 DEBUG glance_store.backend [-] Attempting to 
import store file _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.871 950 DEBUG glance_store.backend [-] Attempting to 
import store glance.store.cinder.Store _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.872 950 DEBUG glance_store.backend [-] Attempting to 
import store glance.store.filesystem.Store _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.872 950 DEBUG glance_store.backend [-] Attempting to 
import store glance.store.http.Store _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.872 950 DEBUG glance_store.backend [-] Attempting to 
import store glance.store.rbd.Store _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.873 950 DEBUG glance_store.backend [-] Attempting to 
import store glance.store.sheepdog.Store _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.873 950 DEBUG glance_store.backend [-] Attempting to 
import store glance.store.swift.Store _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.873 950 DEBUG glance_store.backend [-] Attempting to 
import store glance.store.vmware_datastore.Store _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.874 950 DEBUG glance_store.backend [-] Attempting to 
import store http _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.874 950 DEBUG glance_store.backend [-] Attempting to 
import store no_conf _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.874 950 DEBUG glance_store.backend [-] Attempting to 
import store rbd _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.875 950 DEBUG glance_store.backend [-] Attempting to 
import store sheepdog _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.875 950 DEBUG glance_store.backend [-] Attempting to 
import store swift _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.876 950 DEBUG glance_store.backend [-] Attempting to 
import store vmware _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.876 950 DEBUG glance_store.backend [-] Registering 
options for group glance_store register_opts 
/usr/lib/python2.7/site-packages/glance_store/backend.py:160
  2017-12-05 10:17:15.876 950 DEBUG glance_store.backend [-] Registering 
options for group glance_store register_opts 
/usr/lib/python2.7/site-packages/glance_store/backend.py:160
  2017-12-05 10:17:15.877 950 DEBUG glance_store.backend [-] Attempting to 
import store glance.store.filesystem.Store _load_store 
/usr/lib/python2.7/site-packages/glance_store/backend.py:231
  2017-12-05 10:17:15.878 950 DEBUG glance_store.capabilities [-] Store 
glance_store._drivers.filesystem.Store doesn't support updating dynamic storage 
capabilities. Please overwrite 'update_capabilities' method of the store to 
implement updating logics if needed. update_capabilities 
/usr/lib/python2.7/site-packages/glance_store/capabilities.py:97
  2017-12-05 10:17:15.878 950 DEBUG glance_store.backend [-] Registering store 
glance.store.filesystem.Store with schemes ('file', 'filesystem') create_stores 
/usr/lib/python2.7/site-packages/glance_store/backend.py:278
  2017-12-05 10:17:15.879 950 DEBUG glance_store.driver [-] Late loading 
location class glance_store._drivers.filesystem.StoreLocation 
get_store_location_class 
/usr/lib/python2.7/site-packages/glance_store/driver.py:89
  2017-12-05 10:17:15.879 950 DEBUG

[Yahoo-eng-team] [Bug 1714937] Re: keystone returns 500 on password change

2018-02-09 Thread Lance Bragstad

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

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

Title:
  keystone returns 500 on password change

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  $ openstack user set --password-prompt demo 
  User Password:
  Repeat User Password:
  An unexpected error prevented the server from fulfilling your request. (HTTP 
500) (Request-ID: req-175ea0bf-02d3-4d73-a3ca-662612c36543)
  $

  Although there is an error, the password has been changed, though.

  Traceback from keystone log:

  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG 
keystone.common.authorization [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 
None None] RBAC: Authorizing 
identity:update_user(user_id=30f37144f2494fd5b46d97acb72de22c, 
user={u'password': u'***', u'enabl
  ed': True}) {{(pid=1804) _build_policy_check_credentials 
/opt/stack/keystone/keystone/common/authorization.py:137}}
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG 
keystone.policy.backends.rules [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 
None None] enforce identity:update_user: {'is_delegated_auth': False, 
'access_token_id': None, 'user_id': u'd55b3e8a3e084ba6a
  061b73c33112b05', 'roles': [u'admin'], 'user_domain_id': u'default', 
'consumer_id': None, 'trustee_id': None, 'is_domain': False, 
'is_admin_project': True, 'trustor_id': None, 'token': , 'project_id': u'a42a75e7ca804a6288f3eb51c0fd9eb7', 
'trust_id': None, 'project_domain_id': u'default'} {{(pid=1804) enforce 
/opt/stack/keystone/keystone/policy/backends/rules.py:33}}
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG 
oslo_policy.policy [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 None None] 
The policy file policy.json could not be found. {{(pid=1804) load_rules 
/usr/local/lib/python2.7/dist-packages/oslo_policy/pol
  icy.py:532}}
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG 
keystone.common.authorization [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 
None None] RBAC: Authorization granted {{(pid=1804) check_policy 
/opt/stack/keystone/keystone/common/authorization.py:240}}
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG 
keystone.notifications [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 None 
None] Invoking callback _user_callback for event identity 
invalidate_user_tokens internal for {'resource_info': u'30f37144f2494f
  d5b46d97acb72de22c'} {{(pid=1804) notify_event_callbacks 
/opt/stack/keystone/keystone/notifications.py:297}}
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG 
keystone.notifications [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 None 
None] Invoking callback _delete_user_tokens_callback for event identity 
invalidate_user_tokens internal for {'resource_info': u'
  30f37144f2494fd5b46d97acb72de22c'} {{(pid=1804) notify_event_callbacks 
/opt/stack/keystone/keystone/notifications.py:297}}
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: WARNING 
stevedore.named [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 None None] Could 
not load blah
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR 
keystone.common.wsgi [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 None None] 
(u'Unable to find %(name)r driver in %(namespace)r.', {'namespace': 
'keystone.token.persistence', 'name': 'blah'}): ImportEr
  ror: (u'Unable to find %(name)r driver in %(namespace)r.', {'namespace': 
'keystone.token.persistence', 'name': 'blah'})
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR 
keystone.common.wsgi Traceback (most recent call last):
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR 
keystone.common.wsgi   File "/opt/stack/keystone/keystone/common/wsgi.py", line 
228, in __call__
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR 
keystone.common.wsgi result = method(req, **params)
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR 
keystone.common.wsgi   File 
"/opt/stack/keystone/keystone/common/controller.py", line 94, in inner
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR 
keystone.common.wsgi return f(self, request, *args, **kwargs)
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR 
keystone.common.wsgi   File 
"/opt/stack/keystone/keystone/identity/controllers.py", line 255, in update_user
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR 
keystone.common.wsgi return self._update_user(request, user_id, user)
  Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR 
keystone.common.wsgi   File 
"/opt/stack/keystone/keystone/identity/controllers.py", line 248, in 
_update_user
  Sep 04 11:36:44 jh-devstack-02

[Yahoo-eng-team] [Bug 1748452] [NEW] need a genconfig gate

2018-02-09 Thread Brian Rosmaita

Public bug reported:

With zuul3, it should be possible for us to have an automated gate job
that regenerates the config files.  It would be good for 2 reasons:

1 - prevent bugs like https://bugs.launchpad.net/glance/+bug/1748399
from slipping through

2 - could maybe also compare the generated configs to the current ones,
and propose a patch if necessary

That would be cool and would allow us to keep the default configs in
etc/ up-to-date

** Affects: glance
 Importance: Medium
 Status: Triaged


** Tags: testing

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

Title:
  need a genconfig gate

Status in Glance:
  Triaged

Bug description:
  With zuul3, it should be possible for us to have an automated gate job
  that regenerates the config files.  It would be good for 2 reasons:

  1 - prevent bugs like https://bugs.launchpad.net/glance/+bug/1748399
  from slipping through

  2 - could maybe also compare the generated configs to the current
  ones, and propose a patch if necessary

  That would be cool and would allow us to keep the default configs in
  etc/ up-to-date

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1748452/+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 1744239] Re: collectstatic broken in case of template customization

2018-02-09 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/535674
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=dc0bce63a03e37e9f3f181930ba6d6b7c8b1346e
Submitter: Zuul
Branch:master

commit dc0bce63a03e37e9f3f181930ba6d6b7c8b1346e
Author: Radomir Dopieralski 
Date:   Wed Feb 7 19:32:42 2018 +0100

Fix collectstatic in case of theme customization

When doing theme customization with templates
collectstatic failes with a traceback

Change-Id: I0fdb80ddde1f73b657d445c75b55636d6f2e8d88
Closes-bug: #1744239


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

Title:
  collectstatic broken in case of template customization

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Originally posted on Ask Openstack:
  
https://ask.openstack.org/en/question/107544/ocata-theme-customization-with-templates/

  The problem affects Ocata and Pike for sure.

  In my case I have the following dir structure at:
  /usr/share/openstack-dashboard/openstack_dashboard/themes/default

  .
  |-- _styles.scss
  |-- _variables.scss
  |-- horizon
  |   `-- components
  |   `-- _selects.scss
  |-- img
  |   |-- logo-switch.png
  |   `-- logo-switchengines.png
  `-- templates
  `-- auth
  |-- _footer_switch.html
  |-- _login_page.html
  `-- _splash.html

  This was working fine in Newton. Now I am testing Pike and I get:

  /usr/share/openstack-dashboard/manage.py collectstatic --noinput

  Failes with the following Traceback
  Traceback (most recent call last):
File "/usr/share/openstack-dashboard/manage.py", line 25, in 
  execute_from_command_line(sys.argv)
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 354, in execute_from_command_line
  utility.execute()
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 303, in execute
  settings.INSTALLED_APPS
File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 48, 
in __getattr__
  self._setup(name)
File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 44, 
in _setup
  self._wrapped = Settings(settings_module)
File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 92, 
in __init__
  mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
  __import__(name)
File "/usr/share/openstack-dashboard/openstack_dashboard/settings.py", line 
442, in 
  THEME_COLLECTION_DIR, ROOT_PATH)
File 
"/usr/share/openstack-dashboard/openstack_dashboard/utils/settings.py", line 
332, in find_static_files
  (templates_part, override_path) = theme_file.split('/templates/')
  ValueError: need more than 1 value to unpack

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1744239/+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 1744846] Re: Show all when the network list or router list filtered by tenant

2018-02-09 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/536687
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=00ecfcdb0b8bcd2de93a80f0929c4d627d5dc04a
Submitter: Zuul
Branch:master

commit 00ecfcdb0b8bcd2de93a80f0929c4d627d5dc04a
Author: wangliangyu 
Date:   Tue Jan 23 14:31:12 2018 +0800

Filtering networks or routers by non-existing tenants return an empty list

When networks or routers are filtered by a tenant which does not exist,
there will be return a list no filtered. But we expect an empty list.

Change-Id: I8faca01ab67240a76818d6752f796a6de3c51b5f
Closes-Bug: #1744846


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

Title:
  Show all when the network list or router list filtered by tenant

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  1.Access Admin->Netwrok->Netwroks or Admin->Network->Routers and select the 
tenant filter;
  2.Filter a tenant which does not exist;
  3.Now,the all result will be shown in page, not an empty list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1744846/+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 1746985] Re: Can not specified security groups when creating a port

2018-02-09 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/540463
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=736312b8d92512e6a964bdd4f7d35ca630b190e9
Submitter: Zuul
Branch:master

commit 736312b8d92512e6a964bdd4f7d35ca630b190e9
Author: wei.ying 
Date:   Fri Feb 2 21:27:56 2018 +0800

Support specified security groups when creating a port

This patch allows users to specifie security groups when creating
a port. After a port is created, the backend specifies a 'default'
security group. To be consistent with this configuration, the page
initialization also defaults to a 'default' security group.

Change-Id: I13fe4648c3b5f8311602844e08044af8f7b47fd8
Closes-Bug:#1746985


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

Title:
  Can not specified security groups when creating a port

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Env: devstack master branch

  Currently, after a user creates a port through Horizon, the port
  security group defaults to 'default', and the user can modify the
  port's security group by 'Edit Port' row action.

  According to the neutron api doc[1], when creating a port, we can
  actually specify security groups as well.

  [1] https://developer.openstack.org/api-ref/network/v2/index.html
  #create-port

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1746985/+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 1744361] Re: test_server_security_groups failed to reboot with "Domain not found: no domain with matching uuid" because of missing vif event from linuxbridge agent

2018-02-09 Thread Matt Riedemann

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

** Also affects: nova/queens
   Importance: Medium
 Assignee: melanie witt (melwitt)
   Status: Fix Released

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

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

** Changed in: nova/ocata
 Assignee: (unassigned) => Lee Yarwood (lyarwood)

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

Title:
  test_server_security_groups failed to reboot with "Domain not found:
  no domain with matching uuid" because of missing vif event from
  linuxbridge agent

Status in neutron:
  Confirmed
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  Fix Committed
Status in OpenStack Compute (nova) pike series:
  Fix Committed
Status in OpenStack Compute (nova) queens series:
  Fix Released

Bug description:
  This happened in master (Queens) in tempest-linuxbridge job:

  http://logs.openstack.org/56/534456/1/check/neutron-tempest-
  linuxbridge/7693ca5/logs/testr_results.html.gz

  From tempest log:

  Traceback (most recent call last):
File "tempest/api/compute/security_groups/test_security_groups.py", line 
105, in test_server_security_groups
  'ACTIVE')
File "tempest/common/waiters.py", line 96, in wait_for_server_status
  raise lib_exc.TimeoutException(message)
  tempest.lib.exceptions.TimeoutException: Request timed out
  Details: (SecurityGroupsTestJSON:test_server_security_groups) Server 
dd2ec3b0-f909-4104-ae2a-9b878d936ed4 failed to reach ACTIVE status and task 
state "None" within the required time (196 s). Current status: HARD_REBOOT. 
Current task state: reboot_started_hard.

  In nova-compute log, we see this:

  Jan 19 10:38:37.869397 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
WARNING nova.virt.libvirt.driver [None req-838e0ebe-afe5-4cca-abcc-4ba116889cba 
service nova] [instance: dd2ec3b0-f909-4104-ae2a-9b878d936ed4] Timeout waiting 
for vif plugging callback for instance with vm_state active and task_state 
reboot_started_hard.: Timeout: 300 seconds
  Jan 19 10:38:37.880789 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
DEBUG nova.compute.manager [None req-838e0ebe-afe5-4cca-abcc-4ba116889cba 
service nova] [instance: dd2ec3b0-f909-4104-ae2a-9b878d936ed4] Checking state 
{{(pid=28907) _get_power_state 
/opt/stack/new/nova/nova/compute/manager.py:1183}}
  Jan 19 10:38:37.885265 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
ERROR nova.compute.manager [None req-838e0ebe-afe5-4cca-abcc-4ba116889cba 
service nova] [instance: dd2ec3b0-f909-4104-ae2a-9b878d936ed4] Cannot reboot 
instance: Domain not found: no domain with matching uuid 
'dd2ec3b0-f909-4104-ae2a-9b878d936ed4' (instance-0023): libvirtError: 
Domain not found: no domain with matching uuid 
'dd2ec3b0-f909-4104-ae2a-9b878d936ed4' (instance-0023)
  Jan 19 10:38:37.981484 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
DEBUG nova.compute.manager [None req-838e0ebe-afe5-4cca-abcc-4ba116889cba 
service nova] [instance: dd2ec3b0-f909-4104-ae2a-9b878d936ed4] Instance has 
been destroyed from under us while trying to set it to ERROR {{(pid=28907) 
_set_instance_obj_error_state /opt/stack/new/nova/nova/compute/manager.py:586}}
  Jan 19 10:38:38.150498 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
ERROR oslo_messaging.rpc.server [None req-838e0ebe-afe5-4cca-abcc-4ba116889cba 
service nova] Exception during message handling: libvirtError: Domain not 
found: no domain with matching uuid 'dd2ec3b0-f909-4104-ae2a-9b878d936ed4' 
(instance-0023)
  Jan 19 10:38:38.150813 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
ERROR oslo_messaging.rpc.server Traceback (most recent call last):
  Jan 19 10:38:38.151125 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 
163, in _process_incoming
  Jan 19 10:38:38.151388 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message)
  Jan 19 10:38:38.151668 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
220, in dispatch
  Jan 19 10:38:38.151939 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, 
ctxt, args)
  Jan 19 10:38:38.152205 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
190, in _do_dispatch
  Jan 19 10:38:38.152491 ubuntu-xenial-rax-iad-0002010825 nova-compute[28907]: 
ERROR oslo_messaging.rpc.server

[Yahoo-eng-team] [Bug 1739042] Re: _move_operation_alloc_request fails with TypeError when using 1.12 version allocation request

2018-02-09 Thread Chris Dent

The strings in the log don't seem to be showing up in recent logstash,
so I'm going to mark this one dead, so it's not lingering.

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

Title:
  _move_operation_alloc_request fails with TypeError when using 1.12
  version allocation request

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Seen here in the alternate hosts series:

  http://logs.openstack.org/58/511358/43/check/openstack-tox-
  functional/e642310/job-output.txt.gz#_2017-12-19_00_18_34_585930

  2017-12-19 00:18:34.585930 | ubuntu-xenial | Traceback (most recent call 
last):
  2017-12-19 00:18:34.585992 | ubuntu-xenial |   File 
"/home/zuul/src/git.openstack.org/openstack/nova/.tox/functional/local/lib/python2.7/site-packages/oslo_messaging/rpc/server.py",
 line 163, in _process_incoming
  2017-12-19 00:18:34.586021 | ubuntu-xenial | res = 
self.dispatcher.dispatch(message)
  2017-12-19 00:18:34.586082 | ubuntu-xenial |   File 
"/home/zuul/src/git.openstack.org/openstack/nova/.tox/functional/local/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py",
 line 220, in dispatch
  2017-12-19 00:18:34.586114 | ubuntu-xenial | return 
self._do_dispatch(endpoint, method, ctxt, args)
  2017-12-19 00:18:34.586179 | ubuntu-xenial |   File 
"/home/zuul/src/git.openstack.org/openstack/nova/.tox/functional/local/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py",
 line 190, in _do_dispatch
  2017-12-19 00:18:34.586207 | ubuntu-xenial | result = func(ctxt, 
**new_args)
  2017-12-19 00:18:34.586241 | ubuntu-xenial |   File 
"nova/conductor/manager.py", line 603, in build_instances
  2017-12-19 00:18:34.586267 | ubuntu-xenial | 
host.allocation_request_version)
  2017-12-19 00:18:34.586300 | ubuntu-xenial |   File 
"nova/scheduler/utils.py", line 800, in claim_resources
  2017-12-19 00:18:34.586335 | ubuntu-xenial | user_id, 
allocation_request_version=allocation_request_version)
  2017-12-19 00:18:34.586370 | ubuntu-xenial |   File 
"nova/scheduler/client/__init__.py", line 37, in __run_method
  2017-12-19 00:18:34.586402 | ubuntu-xenial | return 
getattr(self.instance, __name)(*args, **kwargs)
  2017-12-19 00:18:34.586435 | ubuntu-xenial |   File 
"nova/scheduler/client/report.py", line 61, in wrapper
  2017-12-19 00:18:34.586459 | ubuntu-xenial | return f(self, *a, **k)
  2017-12-19 00:18:34.586493 | ubuntu-xenial |   File 
"nova/scheduler/client/report.py", line 110, in wrapper
  2017-12-19 00:18:34.586516 | ubuntu-xenial | return f(self, *a, **k)
  2017-12-19 00:18:34.586552 | ubuntu-xenial |   File 
"nova/scheduler/client/report.py", line 1126, in claim_resources
  2017-12-19 00:18:34.586586 | ubuntu-xenial | payload = 
_move_operation_alloc_request(current_allocs, ar)
  2017-12-19 00:18:34.586625 | ubuntu-xenial |   File 
"nova/scheduler/client/report.py", line 199, in _move_operation_alloc_request
  2017-12-19 00:18:34.586657 | ubuntu-xenial | for a in 
dest_alloc_req['allocations']) - cur_rp_uuids
  2017-12-19 00:18:34.586685 | ubuntu-xenial | TypeError: string indices 
must be integers

  This is due to using a 1.12 version allocation candidate request bug
  _move_operation_alloc_request is expecting the <1.12 format, where
  allocations is a list instead of a dict.

  I don't know if we should change the calling code to format the
  allocation request to the <1.12 format, or make
  _move_operation_alloc_request handle both styles (probably better to
  do the latter).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1739042/+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 1748327] Re: Recover from a failed compute node in nova

2018-02-09 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/542508
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=b516c48fdfbc1b54cd55f17b1a446c5c7d661f11
Submitter: Zuul
Branch:master

commit b516c48fdfbc1b54cd55f17b1a446c5c7d661f11
Author: Matt Riedemann 
Date:   Thu Feb 8 19:32:11 2018 -0500

doc: fix the link for the evacuate cli

This was broken during the openstack admin guide docs migration
in pike.

Change-Id: Ibb886657ed97f3e6462ceef0002ef3fe1aec767d
Closes-Bug: #1748327


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

Title:
  Recover from a failed compute node in nova

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) pike series:
  Confirmed

Bug description:
  - [x] This doc is inaccurate in this way: __

  The link to the admin guide in this section is wrong:

  https://docs.openstack.org/nova/latest/admin/node-down.html#evacuate-
  instances

  It should go here now:

  https://docs.openstack.org/nova/latest/admin/evacuate.html

  ---
  Release: 17.0.0.0b4.dev209 on 2018-02-08 22:27
  SHA: 55021f89ea2b10efd5d47f0f1c9c2f5a5cdb7557
  Source: 
https://git.openstack.org/cgit/openstack/nova/tree/doc/source/admin/node-down.rst
  URL: https://docs.openstack.org/nova/latest/admin/node-down.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1748327/+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 1741000] Re: Can't force-delete instance with task_state not 'None'

2018-02-09 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/530879
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=0d2031a5c408ef5919387c680eeaac68709a0f6c
Submitter: Zuul
Branch:master

commit 0d2031a5c408ef5919387c680eeaac68709a0f6c
Author: Rajesh Tailor 
Date:   Wed Jan 3 13:31:38 2018 +0530

Allow force-delete even if task_state is not None

As of now, if vm task_state is not 'None', and user tries
to force-delete instance, then he gets HTTP 500 Error
and instance deletion doesn't progress.

The same is not the case, when user tries with delete api
instead of force-delete api, even if vm task_state is not 'None'.

Fixed the issue by allowing force-delete to delete instance
in task_state other than None.

Change-Id: Ida1a9d8761cec9585f031ec25e5692b8bb55661e
Closes-Bug: #1741000


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

Title:
  Can't force-delete instance with task_state not 'None'

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Problem Description:

  When user tries to force-delete instance which is not in task_state
  'None', throws 500 error on console, as below:

  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8)

  Steps to reproduce:
  1) Create instance.
  $ nova boot --flavor  --image  

  2) To change the instance task_state to anything other than 'None', I tried 
to resize the instance.
  $ nova resize  

  3) Try to force-delete instance, just after above step, so that instance task 
state is anything in (resize_prep, resize_migrating, resize_migrated, 
resize_finish), but not 'None'.
  $ nova force-delete 

  4) User gets below error on console:

  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8)

  
  Actual result: 
  User gets 500 ClientException Error.

  Expected result:
  The instance should be deleted without any error.

  traceback from nova-api logs:

  DEBUG oslo_concurrency.lockutils [None 
req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8 demo demo] Lock 
"fbe6eec8-be64-4473-8434-1d795e7ca5fb" released by 
"nova.context.get_or_set_cached_cell_and_set_connections" :: held 0.0
  00s {{(pid=24369) inner 
/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:285}}
  ERROR nova.api.openstack.wsgi [None req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8 
demo demo] Unexpected exception in API method: InstanceInvalidState: Instance 
6abb021a-174e-4551-acc1-a96653a9bf83 in task_state resize_prep. Cannot 
force_delete while the instance is in this state.
  ERROR nova.api.openstack.wsgi Traceback (most recent call last):
  ERROR nova.api.openstack.wsgi   File 
"/opt/stack/nova/nova/api/openstack/wsgi.py", line 803, in wrapped
  ERROR nova.api.openstack.wsgi return f(*args, **kwargs)
  ERROR nova.api.openstack.wsgi   File 
"/opt/stack/nova/nova/api/openstack/compute/deferred_delete.py", line 61, in 
_force_delete
  ERROR nova.api.openstack.wsgi self.compute_api.force_delete(context, 
instance)
  ERROR nova.api.openstack.wsgi   File "/opt/stack/nova/nova/compute/api.py", 
line 201, in inner
  ERROR nova.api.openstack.wsgi return function(self, context, instance, 
*args, **kwargs)
  ERROR nova.api.openstack.wsgi   File "/opt/stack/nova/nova/compute/api.py", 
line 141, in inner
  ERROR nova.api.openstack.wsgi method=f.__name__)
  ERROR nova.api.openstack.wsgi InstanceInvalidState: Instance 
6abb021a-174e-4551-acc1-a96653a9bf83 in task_state resize_prep. Cannot 
force_delete while the instance is in this state.
  ERROR nova.api.openstack.wsgi 
  INFO nova.api.openstack.wsgi [None req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8 
demo demo] HTTP exception thrown: Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
  
  DEBUG nova.api.openstack.wsgi [None req-2578def4-a83d-458c-a3cb-c5fa1e6b56a8 
demo demo] Returning 500 to user: Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.

  
  NOTE: If user tries delete api instead of force-delete api for instance 
deletion, in that case instance is deleted and no error is thrown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1741000/+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 1748399] Re: Config generation failing after recent patch

2018-02-09 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/542699
Committed: 
https://git.openstack.org/cgit/openstack/glance/commit/?id=225a33967e5f210e1dae9ec18f1132eff8abacbd
Submitter: Zuul
Branch:master

commit 225a33967e5f210e1dae9ec18f1132eff8abacbd
Author: yatin 
Date:   Fri Feb 9 13:24:31 2018 +0530

Fix wrong usage of extend in list_image_import_opts

Review https://review.openstack.org/#/c/541740/ wrongly
used "extend" method in image_import_opts, this patch
fixes it.

Change-Id: I00375575d601ea6d970bb93c3f01f35c034976a2
Closes-Bug: #1748399


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

Title:
  Config generation failing after recent patch

Status in Glance:
  Fix Released

Bug description:
  tox -egenconfig failing after https://review.openstack.org/#/c/541740/  with 
Error:-
  Traceback (most recent call last):
    File "/root/glance/.tox/genconfig/bin/oslo-config-generator", line 11, in 

  sys.exit(main())
    File 
"/root/glance/.tox/genconfig/lib/python2.7/site-packages/oslo_config/generator.py",
 line 770, in main
  generate(conf)
    File 
"/root/glance/.tox/genconfig/lib/python2.7/site-packages/oslo_config/generator.py",
 line 731, in generate
  groups = _get_groups(_list_opts(conf.namespace))
    File 
"/root/glance/.tox/genconfig/lib/python2.7/site-packages/oslo_config/generator.py",
 line 489, in _list_opts
  for group, group_opts in loader():
    File "/root/glance/glance/opts.py", line 165, in list_image_import_opts
  return [(g, copy.deepcopy(o)) for g, o in opts]
  TypeError: 'NoneType' object is not iterable
  ERROR: InvocationError: 
'/root/glance/.tox/genconfig/bin/oslo-config-generator --config-file 
etc/oslo-config-generator/glance-image-import.conf'
   summary 
_
  ERROR:   genconfig: commands failed

  Review https://review.openstack.org/#/c/541740/ wrongly used "extend"
  method in image_import_opts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1748399/+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 1746996] Re: bagpipe: IPAllocation DB query failing, engine facade mismatch

2018-02-09 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/541513
Committed: 
https://git.openstack.org/cgit/openstack/networking-bagpipe/commit/?id=53e073f1b8b8de4105762140fcc5aaa2645ec752
Submitter: Zuul
Branch:master

commit 53e073f1b8b8de4105762140fcc5aaa2645ec752
Author: Ihar Hrachyshka 
Date:   Tue Feb 6 18:13:37 2018 -0800

Use new facade for OVO objects

This is to accommodate for neutron plugin code issuing callbacks from
under new facade contexts.

Depends-On: I15ec238c18a464f977f7d1079605b82965052311
Change-Id: Ie4ad57f6357c59f2a978467099642b08e730133e
Closes-Bug: #1746996


** Changed in: networking-bagpipe
   Status: New => Fix Released

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

Title:
  bagpipe: IPAllocation DB query failing, engine facade mismatch

Status in networking-bgpvpn:
  Confirmed
Status in BaGPipe:
  Fix Released
Status in neutron:
  Confirmed

Bug description:
  
networking_bgpvpn.tests.unit.services.bagpipe.test_bagpipe.TestBagpipeServiceDriverV2RPCs.test_router_itf_event_network_assoc
  is currently failing

  Traceback (most recent call last):
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/networking_bgpvpn/neutron/services/service_drivers/bagpipe/bagpipe_v2.py",
 line 260, in registry_router_interface_before_delete
  context, router_id, network_id)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/local/lib/python2.7/site-packages/oslo_log/helpers.py",
 line 67, in wrapper
  return method(*args, **kwargs)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/networking_bgpvpn/neutron/services/service_drivers/bagpipe/bagpipe_v2.py",
 line 218, in notify_router_interface_deleted
  network_id=net_id) +
File "neutron/objects/base.py", line 561, in get_objects
  return [cls._load_object(context, db_obj) for db_obj in db_objs]
File "neutron/objects/base.py", line 496, in _load_object
  obj.from_db_object(db_obj)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/src/networking-bagpipe/networking_bagpipe/objects/bgpvpn.py",
 line 156, in from_db_object
  self._load_subnets(obj)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/src/networking-bagpipe/networking_bagpipe/objects/bgpvpn.py",
 line 150, in _load_subnets
  subnets_info = _get_subnets_info(self.obj_context, self.network_id)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/src/networking-bagpipe/networking_bagpipe/objects/bgpvpn.py",
 line 62, in _get_subnets_info
  for subnet in subnets
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/src/networking-bagpipe/networking_bagpipe/objects/bgpvpn.py",
 line 47, in _get_gateway_mac_by_subnet
  port = Port.get_object(obj_context, id=ip_allocation.port_id)
File "neutron/objects/base.py", line 538, in get_object
  return cls._load_object(context, db_obj)
File "neutron/objects/base.py", line 496, in _load_object
  obj.from_db_object(db_obj)
File "neutron/objects/ports.py", line 409, in from_db_object
  super(Port, self).from_db_object(db_obj)
File "neutron/objects/base.py", line 440, in from_db_object
  self.load_synthetic_db_fields(db_obj)
File "neutron/objects/base.py", line 737, in load_synthetic_db_fields
  for obj in synth_db_objs]
File "neutron/objects/base.py", line 498, in _load_object
  context.session.expunge(obj.db_obj)
File 
"/home/teom7365/prog/openstack/networking-bgpvpn/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/orm/session.py",
 line 1650, in expunge
  state_str(state))
  InvalidRequestError: Instance  is not present 
in this Session

  
  "git bisect" show that neutron commit 
906eda44d2c230be99fc5c61daa0f359ab46a3ad [1] introduces the issue

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/bgpvpn/+bug/1746996/+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 1745038] Re: Unable to use SSL URI for OVSDB connection

2018-02-09 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/536983
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=8806477abfdac68c409056e22f5e0c50791b8a27
Submitter: Zuul
Branch:master

commit 8806477abfdac68c409056e22f5e0c50791b8a27
Author: Tim Rozet 
Date:   Tue Jan 23 16:47:23 2018 -0500

Fixes using SSL OVSDB connection

When creating SSL OVSDB connection it is required to set the private
key, certificate, and the CA certificate in order to communicate with
OVSDB.  This patch configures these when an SSL connection URI is used.
The settings must be provided as part of neutron.conf under [ovs]
section.

Closes-Bug: 1745038

Change-Id: I19fd9dd0c72260835eb91e557a6029ec9d652179
Signed-off-by: Tim Rozet 


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

Title:
  Unable to use SSL URI for OVSDB connection

Status in neutron:
  Fix Released

Bug description:
  When specifying an ssl connection to use with neutron.conf/ovsdb_connection, 
such as:
  ovsdb_connection=ssl:127.0.0.1:6639

  The connection will fail because there is missing SSL configuration
  for key, cert, and ca cert that is required when creating an SSL
  stream connection to OVSDB.  This configuration is not part of
  ovsdbapp and must be setup before invoking the IDL helper function
  that asks ovsdbapp to open the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1745038/+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 1748399] [NEW] Config generation failing after recent patch

2018-02-09 Thread yatin

Public bug reported:

tox -egenconfig failing after https://review.openstack.org/#/c/541740/  with 
Error:-
Traceback (most recent call last):
  File "/root/glance/.tox/genconfig/bin/oslo-config-generator", line 11, in 

sys.exit(main())
  File 
"/root/glance/.tox/genconfig/lib/python2.7/site-packages/oslo_config/generator.py",
 line 770, in main
generate(conf)
  File 
"/root/glance/.tox/genconfig/lib/python2.7/site-packages/oslo_config/generator.py",
 line 731, in generate
groups = _get_groups(_list_opts(conf.namespace))
  File 
"/root/glance/.tox/genconfig/lib/python2.7/site-packages/oslo_config/generator.py",
 line 489, in _list_opts
for group, group_opts in loader():
  File "/root/glance/glance/opts.py", line 165, in list_image_import_opts
return [(g, copy.deepcopy(o)) for g, o in opts]
TypeError: 'NoneType' object is not iterable
ERROR: InvocationError: '/root/glance/.tox/genconfig/bin/oslo-config-generator 
--config-file etc/oslo-config-generator/glance-image-import.conf'
 summary 
_
ERROR:   genconfig: commands failed

Review https://review.openstack.org/#/c/541740/ wrongly used "extend"
method in image_import_opts.

** Affects: glance
 Importance: Critical
 Assignee: yatin (yatinkarel)
 Status: Confirmed

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

Title:
  Config generation failing after recent patch

Status in Glance:
  Confirmed

Bug description:
  tox -egenconfig failing after https://review.openstack.org/#/c/541740/  with 
Error:-
  Traceback (most recent call last):
    File "/root/glance/.tox/genconfig/bin/oslo-config-generator", line 11, in 

  sys.exit(main())
    File 
"/root/glance/.tox/genconfig/lib/python2.7/site-packages/oslo_config/generator.py",
 line 770, in main
  generate(conf)
    File 
"/root/glance/.tox/genconfig/lib/python2.7/site-packages/oslo_config/generator.py",
 line 731, in generate
  groups = _get_groups(_list_opts(conf.namespace))
    File 
"/root/glance/.tox/genconfig/lib/python2.7/site-packages/oslo_config/generator.py",
 line 489, in _list_opts
  for group, group_opts in loader():
    File "/root/glance/glance/opts.py", line 165, in list_image_import_opts
  return [(g, copy.deepcopy(o)) for g, o in opts]
  TypeError: 'NoneType' object is not iterable
  ERROR: InvocationError: 
'/root/glance/.tox/genconfig/bin/oslo-config-generator --config-file 
etc/oslo-config-generator/glance-image-import.conf'
   summary 
_
  ERROR:   genconfig: commands failed

  Review https://review.openstack.org/#/c/541740/ wrongly used "extend"
  method in image_import_opts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1748399/+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 1748591] [NEW] neutron extension-list is fetched in every request related to neutron

[Yahoo-eng-team] [Bug 1731431] Re: Cloud-init could not identify OVF datasource

[Yahoo-eng-team] [Bug 1737092] Re: server-generated directory index forbidden by Options directive

[Yahoo-eng-team] [Bug 1737130] Re: disable_root: 1 but root can still log in

[Yahoo-eng-team] [Bug 1748582] [NEW] Trunk subports don't have a device ID

[Yahoo-eng-team] [Bug 1748354] Re: ec2: systemctl restart cloud-init after upgrade 17.1.46 -> 17.2.30

[Yahoo-eng-team] [Bug 1746996] Re: bagpipe: IPAllocation DB query failing, engine facade mismatch

[Yahoo-eng-team] [Bug 1748354] Re: ec2: systemctl restart cloud-init after upgrade 17.1.46 -> 17.2.30

[Yahoo-eng-team] [Bug 1748559] [NEW] image-create header is static

[Yahoo-eng-team] [Bug 1748546] [NEW] ovsfw tempest tests random fails

[Yahoo-eng-team] [Bug 1748544] [NEW] set_admin_password in the libvirt driver does not save the password in system metadata

[Yahoo-eng-team] [Bug 1446078] Re: Apache error logs contains non-error messages

[Yahoo-eng-team] [Bug 1748512] [NEW] web-download is subject to same port scan vulnerability as v1 copy_from

[Yahoo-eng-team] [Bug 1747650] Re: Make bdms querying in multiple cells use scatter-gather

[Yahoo-eng-team] [Bug 1736468] Re: glance-scrubber does not work using SSL

[Yahoo-eng-team] [Bug 1714937] Re: keystone returns 500 on password change

[Yahoo-eng-team] [Bug 1748452] [NEW] need a genconfig gate

[Yahoo-eng-team] [Bug 1744239] Re: collectstatic broken in case of template customization

[Yahoo-eng-team] [Bug 1744846] Re: Show all when the network list or router list filtered by tenant

[Yahoo-eng-team] [Bug 1746985] Re: Can not specified security groups when creating a port

[Yahoo-eng-team] [Bug 1744361] Re: test_server_security_groups failed to reboot with "Domain not found: no domain with matching uuid" because of missing vif event from linuxbridge agent

[Yahoo-eng-team] [Bug 1739042] Re: _move_operation_alloc_request fails with TypeError when using 1.12 version allocation request

[Yahoo-eng-team] [Bug 1748327] Re: Recover from a failed compute node in nova

[Yahoo-eng-team] [Bug 1741000] Re: Can't force-delete instance with task_state not 'None'

[Yahoo-eng-team] [Bug 1748399] Re: Config generation failing after recent patch

[Yahoo-eng-team] [Bug 1746996] Re: bagpipe: IPAllocation DB query failing, engine facade mismatch

[Yahoo-eng-team] [Bug 1745038] Re: Unable to use SSL URI for OVSDB connection

[Yahoo-eng-team] [Bug 1748399] [NEW] Config generation failing after recent patch

28 matches

Site Navigation

Mail list logo

Footer information