[Yahoo-eng-team] [Bug 1680742] Re: Replace six.iteritems with dict.items

[fupingxie]

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

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

Title:
   Replace six.iteritems with dict.items

Status in Glance:
  Invalid

Bug description:
  according to https://wiki.openstack.org/wiki/Python3,
  now we should avoid using six.iteritems and replace
  it with dict.items.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1680742/+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 1725067] [NEW] cloud-init resizefs fails when booting with root=PARTUUID=

[Steve Langasek]

Public bug reported:

A freshly build Ubuntu 17.10 image that's configured to boot without
initramfs by passing root=PARTUUID= on the kernel commandline
comes up degraded because cloud-init fails to resize the root partition.

Oct 20 00:07:30 ubuntu cloud-init[493]: 2017-10-20 00:07:30,656 - 
util.py[WARNING]: Failed to resize filesystem (cmd=('resize2fs', '/dev/root'))
Oct 20 00:07:30 ubuntu cloud-init[493]: 2017-10-20 00:07:30,662 - 
util.py[WARNING]: Running module resizefs () failed

Looking at the code, I see that there are two separate implementations
of rootdev_from_cmdline, one in cloudinit/util.py and one in
cloudinit/config/cc_resizefs.py; and the second does not handle
partuuid.

>>> from cloudinit.util import rootdev_from_cmdline
>>> rootdev_from_cmdline('BOOT_IMAGE=/boot/vmlinuz-4.4.0-1007-kvm 
>>> root=PARTUUID=f122607f-3631-4411-bd34-de4bed76e0f7 ro console=tty1 
>>> console=ttyS0 systemd.log_level=debug')
'/dev/disk/by-partuuid/f122607f-3631-4411-bd34-de4bed76e0f7'
>>> from cloudinit.config.cc_resizefs import rootdev_from_cmdline
>>> rootdev_from_cmdline('OT_IMAGE=/boot/vmlinuz-4.4.0-1007-kvm 
>>> root=PARTUUID=f122607f-3631-4411-bd34-de4bed76e0f7 ro console=tty1 
>>> console=ttyS0 systemd.log_level=debug')
'/dev/PARTUUID=f122607f-3631-4411-bd34-de4bed76e0f7'
>>>

This is related to bug #1684869; I'm not sure if it's the same bug
reintroduced or if was never fixed properly on trunk (17.1).

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

** Affects: cloud-init (Ubuntu)
 Importance: Medium
 Status: New

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

** Changed in: cloud-init (Ubuntu)
   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/1725067

Title:
  cloud-init resizefs fails when booting with root=PARTUUID=

Status in cloud-init:
  New
Status in cloud-init package in Ubuntu:
  New

Bug description:
  A freshly build Ubuntu 17.10 image that's configured to boot without
  initramfs by passing root=PARTUUID= on the kernel commandline
  comes up degraded because cloud-init fails to resize the root
  partition.

  Oct 20 00:07:30 ubuntu cloud-init[493]: 2017-10-20 00:07:30,656 - 
util.py[WARNING]: Failed to resize filesystem (cmd=('resize2fs', '/dev/root'))
  Oct 20 00:07:30 ubuntu cloud-init[493]: 2017-10-20 00:07:30,662 - 
util.py[WARNING]: Running module resizefs () failed

  Looking at the code, I see that there are two separate implementations
  of rootdev_from_cmdline, one in cloudinit/util.py and one in
  cloudinit/config/cc_resizefs.py; and the second does not handle
  partuuid.

  >>> from cloudinit.util import rootdev_from_cmdline
  >>> rootdev_from_cmdline('BOOT_IMAGE=/boot/vmlinuz-4.4.0-1007-kvm 
root=PARTUUID=f122607f-3631-4411-bd34-de4bed76e0f7 ro console=tty1 
console=ttyS0 systemd.log_level=debug')
  '/dev/disk/by-partuuid/f122607f-3631-4411-bd34-de4bed76e0f7'
  >>> from cloudinit.config.cc_resizefs import rootdev_from_cmdline
  >>> rootdev_from_cmdline('OT_IMAGE=/boot/vmlinuz-4.4.0-1007-kvm 
root=PARTUUID=f122607f-3631-4411-bd34-de4bed76e0f7 ro console=tty1 
console=ttyS0 systemd.log_level=debug')
  '/dev/PARTUUID=f122607f-3631-4411-bd34-de4bed76e0f7'
  >>>

  This is related to bug #1684869; I'm not sure if it's the same bug
  reintroduced or if was never fixed properly on trunk (17.1).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1725067/+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 1472612] Re: multi domain support false issue

[Gary W. Smith]

As David Lyle commented, this functionality is working fine in the
current version.

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

Title:
  multi domain support false issue

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  When using the new domains support code, and you wish to disable this
  feature (to not use domains in horizon), this creates a number of
  issues for project admin users.   They suddenly  lose the ability to
  manage members, create projects, update_projects, modify quotas,
  delete projects(s)

  You can observe this behavior by setting:

  OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT = False

  in the local settings file

  domain support patches need to have backwards compatibility with
  project admin behavior in a non domain world.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1472612/+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 1583790] Re: Soft reboot fails for an instance that is shut down

[Gary W. Smith]

In the current version of horizon there is no "soft reboot" option in an
instance that is shut off.

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

Title:
  Soft reboot fails for an instance that is shut down

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Steps to reproduce
  1. Login as admin or non admin user.
  2. Spin up a new instance if none are available.
  3. Shut down instance.
  4. Soft reboot instance. Operation fails

  Expected behavior:

  Soft reboot should not be an available option for an instance that has
  been shut down. Openstack CLI does not allow soft reboot of an
  instance that has been shutdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1583790/+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 1648111] Re: Restrict location updates to active, queued images

[Brian Rosmaita]

This was addressed by Change-Id:
I593ad2d3c7402c4fb87a475c8d44060baed5ff69


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

Title:
  Restrict location updates to active, queued images

Status in Glance:
  Fix Released

Bug description:
  https://review.openstack.org/366995
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/glance" 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 4ac8adbccc2b7bbef3d53f9141079c48f9c768f4
  Author: Nikhil Komawar 
  Date:   Wed Sep 7 17:29:41 2016 -0400

  Restrict location updates to active, queued images
  
  Currently image location updates (removing, replacing) are permitted for
  images even if their state is not ``active``.
  
  This need is to:
   * Prevent the replacement of image locations of images that are not
 ``active`` or ``queued`` by returning a Conflict Error
  (409 response code).
   * Prevent removal of image locations of images that are not ``active``
 by returning a Conflict Error (409 response code).
  
  Changing of image locations when the image state is not ``active`` can
  result in bad experiences for the users.
   *  If one tries to change or remove the location for an image while it
  is in ``saving`` state, Glance would be trying to write data to a
  previously saved location while the user updates the custom
  location. This results in a race condition.
   *  For images that are in ``queued`` state and no image data has been
  uploaded yet, there is no need for an image location to be
  removed and permitting users to remove the image
  location can result in a bad experience. However users can be
  allowed to replace the image location to maintain backward
  compatibility and also because replacing could mean replacing an
  empty location by a non-empty image location.
  *   For images in ``deactivated`` state, it is essential that image
  locations are not updated as it does not abide with the purpose of
  the image state being set to ``deactivated`` and may cause security
  concerns.
  
  This commit introduces the following change in behavior:
* If an image is in ``active`` state, removing/replacing the custom
  locations on that image will be allowed so there is no change in
  behavior for this case.
* If an image is in ``saving`` or ``deactivated``, the status of
  that image will be checked while trying to replace/remove the custom
  location and a HTTP 409 Conflict status will be returned in response
  to the user.
* If an image is in ``queued`` state, removing the custom
  image location will not be permitted as an image in queued status
  should not have any location associated with it. Replacing of location
  may be permitted here though.
* If an image is in ``deleted`` or ``pending_delete`` state, a HTTP
  409 Conflict status will be returned, if that image is visible to
  the user (in case of admins). Otherwise, the location cannot be
  removed/replaced anyway.  Please note ``pending_delete`` is another
  form of the ``deleted`` status and behavior in either case should be
  expected to be same.
* If an image is in ``killed`` status, a HTTP 409 Conflict status will
  be returned.
  
  TODO:
  Atomicity is required such that glance permits removal/replacement of
  image locations on certain permissible image transition states handling
  the race conditions like:
* In case where the status of the image is ``saving`` and it
  has just moved to ```active`` status, ideally removing/replacing
  custom location should be allowed. However, due to lack of
  atomicity in setting image status glance will ignore setting the
  location and a 409 will be returned.
* In case where the status of the image is ``deactivated`` and it
  has just been moved to ``active`` status, ideally
  removing/replacing custom location should be allowed. Again, due
  to lack of atomicity in setting image status glance will ignore
  the request and a 409 will be returned.
* In case where the status of the image is ``active`` and it has
  just been moved to ``deactivated`` status, due to lack of

[Yahoo-eng-team] [Bug 1673195] Re: Image signature documentation modify key manager api class

[Brian Rosmaita]

This bug is invalid.  The review that generated it already contained the
required documentation change.

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

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

Title:
  Image signature documentation modify key manager api class

Status in Glance:
  Invalid

Bug description:
  https://review.openstack.org/376302
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/glance" 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 90f4c1d46749c9f3099118d9a4a442929d5df153
  Author: Darren White 
  Date:   Mon Sep 26 09:43:27 2016 +0100

  Image signature documentation modify key manager api class
  
  Added documentation to doc/source/signature.rst describing
  how to change which key manager Glance will use to sign and
  verify images.
  
  Removed generated sample conf files.
  
  DocImpact
  
  Change-Id: I384d07a7aa5606a97d41ea76c9ab6d6c7ca86811

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1673195/+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 1552947] Re: Fix location update

[Brian Rosmaita]

Addressed by Change-Id: I593ad2d3c7402c4fb87a475c8d44060baed5ff69

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

Title:
  Fix location update

Status in Glance:
  Fix Released

Bug description:
  https://review.openstack.org/280786
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/glance" 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 9aa0debabff6fb20ea3bc46e1e467e893b05801c
  Author: Fei Long Wang 
  Date:   Tue Feb 9 16:40:34 2016 +1300

  Fix location update
  
  After commit Ieb03aaba887492819f9c58aa67f7acfcea81720e, the command
  location-update is totally broken now. This patch fixes the issue
  and a test case is added. Besides, with this change, location
  add/remove/update can't be executed if the show_multiple_locations
  is False.
  
  APIImpact
  DocImpact
  
  Closes-Bug: #1537626
  
  Change-Id: I7284dee828bc8ca00747bc7668b37fa7176afc85

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1552947/+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 1680310] Re: Accept Range requests and set appropriate response

[Brian Rosmaita]

This was addressed by Change-Id:
I70e3f60c3ce3d0eeb7b457496dbbe623b2ff473e

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

Title:
  Accept Range requests and set appropriate response

Status in Glance:
  Fix Released

Bug description:
  https://review.openstack.org/441501
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/glance" 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 423f3401741a64f0ead66bcb8cb0cd8cafb02cf8
  Author: Dharini Chandrasekar 
  Date:   Fri Mar 3 22:38:34 2017 +

  Accept Range requests and set appropriate response
  
  Currently glance v2 API incorrectly accepts ‘Content-Range’ header
  for random image access and does not set response headers.
  As per rfc7233, ‘Range’ requests should be accepted and ‘Content-Range’
  must be returned in the response headers.
  
  This patch enables Glance v2 API to accept the more appropriate ‘Range’
  requests and sets ‘Content-Range’ response header.
  
  For backward compatibility with pre-Pike Glance clients, the incorrect
  'Content-Range' header will be accepted silently in perpetuity.
  Thus this patch contains tests for 'Content-Range' in requests to
  prevent regressions.
  
  DocImpact
  Implements lite-spec I5bdadde682a0c50836bd95e2a6651d6e7e18f172
  Closes-Bug: #1677391
  
  Co-Authored-By: Hemanth Makkapati 
  
  Change-Id: Ib7ebc792c32995751744be3f36cbc9a0c1eead2a

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1680310/+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 1721761] Re: Fix 500 if user passes name with more than 80 characters

[Brian Rosmaita]

The change appears in the schema, so it's self-documenting.
Additionally, the change is documented in a release note.

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

Title:
  Fix 500 if user passes name with more than 80 characters

Status in Glance:
  Fix Released

Bug description:
  https://review.openstack.org/507433
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/glance" 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 2562da28c6171cc5372d3a695af00e22134a360b
  Author: Dinesh Bhor 
  Date:   Tue Sep 19 18:35:56 2017 +0530

  Fix 500 if user passes name with more than 80 characters
  
  Following apis are returning 500 error if user passes name with more
  than 80 characters:
  * md-tag-create
  * md-tag-update
  * md-object-create
  * md-object-update
  * md-property-create
  * md-property-update
  
  This happens because there is a discrepancy in db column length and
  glance-api length check in schema validation. In database the 'name'
  field for these API's is defined as of maximum 80 characters and in
  schema it is defined as of maximum 255 characters. So if user passes
  name with more than 80 characters and less than 255 characters
  database fails to store that value and shouts with following error
  which leads to 500 error to API user:
  
  (pymysql.err.DataError) (1406, u"Data too long for column 'name' at
  row 1")
  
  Fixed this issue by changing the maximum allowed length for 'name'
  from 255 to 80 in schema validation.
  
  APIImpact
  DocImpact
  Closes-Bug: #1719252
  Change-Id: I4ae67457c3e4f5a6bfc3c1db2d305a9b7587395f

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1721761/+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 1724951] [NEW] Ntp schema definition permits empty ntp cloud-config, but code disallows

[Chad Smith]

Public bug reported:

Our docs and jsonschema definition allows an empty cloud-config
definition for ntp. When provided, that empty cloud-config definition
should just install ntp with sensible defaults

>From https://cloudinit.readthedocs.io/en/latest/topics/modules.html#ntp

"If no ntp servers or pools are provided, 4 pools will be used in the
format {0-3}.{distro}.pool.ntp.org."

When running with an empty ntp cloud-config, we get a traceback from
cc_ntp.

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 793, in 
_run_modules
freq=freq)
  File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
return self._runners.run(name, functor, args, freq, clear_on_fail)
  File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
results = functor(*args)
  File "/usr/lib/python3/dist-packages/cloudinit/config/cc_ntp.py", line 109, 
in handle
" is a %s %instead"), type_utils.obj_name(ntp_cfg))
RuntimeError: ("'ntp' key existed in config, but not a dictionary type, is a %s 
%instead", 'NoneType')

Steps to reproduce:
$ cat >ntp.yaml < In Progress

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

** Changed in: cloud-init
 Assignee: (unassigned) => Chad Smith (chad.smith)

** Description changed:

  Our docs and jsonschema definition allows an empty cloud-config
  definition for ntp. When provided, that empty cloud-config definition
  should just install ntp with sensible defaults
- 
  
  From https://cloudinit.readthedocs.io/en/latest/topics/modules.html#ntp
  
  "If no ntp servers or pools are provided, 4 pools will be used in the
  format {0-3}.{distro}.pool.ntp.org."
  
- 
- 
- When running with an empty ntp cloud-config, we get a traceback from cc_ntp.
- 
+ When running with an empty ntp cloud-config, we get a traceback from
+ cc_ntp.
  
  Traceback (most recent call last):
-   File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 793, in 
_run_modules
- freq=freq)
-   File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
- return self._runners.run(name, functor, args, freq, clear_on_fail)
-   File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
- results = functor(*args)
-   File "/usr/lib/python3/dist-packages/cloudinit/config/cc_ntp.py", line 109, 
in handle
- " is a %s %instead"), type_utils.obj_name(ntp_cfg))
+   File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 793, in 
_run_modules
+ freq=freq)
+   File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
+ return self._runners.run(name, functor, args, freq, clear_on_fail)
+   File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
+ results = functor(*args)
+   File "/usr/lib/python3/dist-packages/cloudinit/config/cc_ntp.py", line 109, 
in handle
+ " is a %s %instead"), type_utils.obj_name(ntp_cfg))
  RuntimeError: ("'ntp' key existed in config, but not a dictionary type, is a 
%s %instead", 'NoneType')
- 
  
  Steps to reproduce:
  $ cat >ntp.yaml ntp.yaml 

[Yahoo-eng-team] [Bug 1723423] Re: Ironic node cannot be used if it does not report VCPU

[OpenStack Infra]

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

commit b25928dc0459e44c5cef8c1f16db76d779fbf556
Author: Dmitry Tantsur 
Date:   Fri Oct 13 15:18:16 2017 +0200

Pick ironic nodes without VCPU set

Starting with the Pike release, reporting VCPU/memory/disk is no longer 
required.
However, we used VCPU to check if a node is available, so nodes without 
VCPU in
their properties were always ignored. This patch changes the logic to use 
the existing
_node_resources_unavailable call.

This change also fixes another related issue: when disk or memory are 
missing from
properties, the virt driver tries to report zero max_unit for them, which 
is not
allowed by placement.

Change-Id: I1bbfc152189252c5c45e6153695a802d17b76690
Closes-Bug: #1723423


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

Title:
  Ironic node cannot be used if it does not report VCPU

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Even though reporting VCPU is optional, starting with Pike, due to
  code at
  
https://github.com/openstack/nova/blob/10661dc5e2e3f2e2f37b6a86ea22f71b4b833fc9/nova/virt/ironic/driver.py#L762
  nodes without VCPU are not recognized. This has to be changes to
  properly call _node_resources_unavailable instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1723423/+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 1313186] Re: No way to configure ntp

[Chad Smith]

Just updating a stale bug here to the right state.
Ntp support was released in rev b455902450e3f9ccb0cb876b460bdc7d5f6e24db. Aug 
10, 2016 with the cc_ntp module. 
http://cloudinit.readthedocs.io/en/latest/topics/modules.html#ntp

** Changed in: cloud-init
   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/1313186

Title:
  No way to configure ntp

Status in cloud-init:
  Fix Released

Bug description:
  Currently, there is no way to write /etc/ntp.conf (or equivalent on
  non-rhel systems). One way to do it in rhel vms is to pass the ntp
  servers as part of the config drive through nova, and then write a
  cc_update_ntp script to read these and populate /etc/ntp.conf.
  Similarly for other distros.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1313186/+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 1721179] Re: A cell cannot be deleted once a host is added to the cell

[OpenStack Infra]

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

commit f4f17b364e28389f22bf9c6017dd7aef918c7104
Author: Takashi NATSUME 
Date:   Sun Oct 8 00:55:50 2017 +0900

Add 'delete_host' command in 'nova-manage cell_v2'

Add 'delete_host' command in 'nova-manage cell_v2'.
Add an optional 'force' option in 'nova-manage cell_v2 delete_cell'.
If specifying the 'force' option, a cell can be deleted
even if the cell has hosts.

Change-Id: I8cd7826c2c03687c6b85731519778f09d542b236
Closes-Bug: #1721179


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

Title:
  A cell cannot be deleted once a host is added to the cell

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

Bug description:
  Description
  ===

  In cell v2 environment, once a host is added to a cell,
  the cell cannot be deleted even though the cell does not have any hosts.

  Steps to reproduce
  ==

  In cell v2 environment, a cell to delete has only one compute host.

  1. Delete the nova-compute service

  > nova service-delete db8e01f5-021d-4c87-a4eb-f3e5089e6105

  The records are soft deleted in the 'services' table and the 'compute_nodes' 
table of the cell database. 
  But the record in 'host_mappings' table of api database is not deleted.

  2. Delete the cell

  > nova-manage cell_v2 delete_cell --cell_uuid 
0fcd92ba-b257-4fbc-94d5-9ac6a77ccf81
  There are existing hosts mapped to cell with uuid 
0fcd92ba-b257-4fbc-94d5-9ac6a77ccf81.

  The command fails with the message above.
  It is caused because the host record remains in the 'host_mappings' table of 
api database.

  But there is no ways to delete the host record in the 'host_mappings'
  table.

  Expected result
  ===

  The cell can be deleted if the cell does not have any hosts.
  Or we should have the way to delete the host from the cell.

  Actual result
  =

  The cell cannot be deleted even though the cell does not have any hosts.
  (We don't have the way to delete the host from the cell.)

  Environment
  ===

  OS: Ubuntu 16.04.2 LTS
  nova master(commit 8ca24bf1ff80f39b14726aca22b5cf52603ea5a0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1721179/+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 1662626] Re: live-migrate left in migrating as domain not found

[Corey Bryant]

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

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

** Also affects: cloud-archive/pike
   Importance: Medium
 Assignee: Shane Peters (shaner)
   Status: Fix Released

** Changed in: cloud-archive/newton
   Importance: Undecided => Medium

** Changed in: cloud-archive/newton
   Status: New => Fix Released

** Changed in: cloud-archive/ocata
   Importance: Undecided => Medium

** Changed in: cloud-archive/ocata
   Status: New => Fix Released

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

Title:
  live-migrate left in migrating as domain not found

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in Ubuntu Cloud Archive ocata series:
  Fix Released
Status in Ubuntu Cloud Archive pike series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) newton series:
  Fix Committed
Status in OpenStack Compute (nova) ocata series:
  Fix Committed
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Triaged
Status in nova source package in Zesty:
  Fix Released
Status in nova source package in Artful:
  Fix Released

Bug description:
  A live-migration stress test was working fine when suddenly a VM
  stopped migrating. It failed with this error:

  ERROR nova.virt.libvirt.driver [req-df91ac40-820f-4aa9-945b-
  b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c
  669472610b194bfa9bf03f50f86d725a - - -] [instance: 62034d78-3144-4efd-
  9c2c-8a792aed3d6b] Error from libvirt during undefine. Code=42
  Error=Domain not found: no domain with matching uuid '62034d78-3144
  -4efd-9c2c-8a792aed3d6b' (instance-0431)

  The full stack trace:

  2017-02-05 02:33:41.787 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Migration running for 240 secs, memory 9% 
remaining; (bytes processed=15198240264, remaining=1680875520, 
total=17314955264)
  2017-02-05 02:33:45.795 19770 INFO nova.compute.manager 
[req-abff9c69-5f82-4ed6-af8a-fd1dc81a72a6 - - - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] VM Paused (Lifecycle Event)
  2017-02-05 02:33:45.870 19770 INFO nova.compute.manager 
[req-abff9c69-5f82-4ed6-af8a-fd1dc81a72a6 - - - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] During sync_power_state the instance has 
a pending task (migrating). Skip.
  2017-02-05 02:33:45.883 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Migration operation has completed
  2017-02-05 02:33:45.884 19770 INFO nova.compute.manager 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] _post_live_migration() is started..
  2017-02-05 02:33:46.156 19770 INFO os_vif 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] Successfully unplugged vif 
VIFBridge(active=True,address=fa:16:3e:a2:90:55,bridge_name='brq476ab6ba-b3',has_traffic_filtering=True,id=98d476b3-0ead-4adb-ad54-1dff63edcd65,network=Network(476ab6ba-b32e-409e-9711-9412e8475ea0),plugin='linux_bridge',port_profile=,preserve_on_delete=True,vif_name='tap98d476b3-0e')
  2017-02-05 02:33:46.189 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Deleting instance files 
/var/lib/nova/instances/62034d78-3144-4efd-9c2c-8a792aed3d6b_del
  2017-02-05 02:33:46.195 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Deletion of 
/var/lib/nova/instances/62034d78-3144-4efd-9c2c-8a792aed3d6b_del complete

  2017-02-05 02:33:46.334 19770 ERROR nova.virt.libvirt.driver [req-
  df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c
  669472610b194bfa9bf03f50f86d725a - - -] [instance: 62034d78-3144-4efd-
  9c2c-8a792aed3d6b] Error from libvirt during undefine. Code=42
  Error=Domain not found: no domain with matching uuid '62034d78-3144
  -4efd-9c2c-8a792aed3d6b' (instance-0431)

  2017-02-05 02:33:46.363 19770 WARNING nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 

[Yahoo-eng-team] [Bug 1662626] Re: live-migrate left in migrating as domain not found

[Corey Bryant]

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

** Changed in: nova (Ubuntu Xenial)
   Status: New => Triaged

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

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

** Changed in: cloud-archive/mitaka
   Importance: Undecided => Medium

** Changed in: nova (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  live-migrate left in migrating as domain not found

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in Ubuntu Cloud Archive ocata series:
  Fix Released
Status in Ubuntu Cloud Archive pike series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) newton series:
  Fix Committed
Status in OpenStack Compute (nova) ocata series:
  Fix Committed
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Triaged
Status in nova source package in Zesty:
  Fix Released
Status in nova source package in Artful:
  Fix Released

Bug description:
  A live-migration stress test was working fine when suddenly a VM
  stopped migrating. It failed with this error:

  ERROR nova.virt.libvirt.driver [req-df91ac40-820f-4aa9-945b-
  b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c
  669472610b194bfa9bf03f50f86d725a - - -] [instance: 62034d78-3144-4efd-
  9c2c-8a792aed3d6b] Error from libvirt during undefine. Code=42
  Error=Domain not found: no domain with matching uuid '62034d78-3144
  -4efd-9c2c-8a792aed3d6b' (instance-0431)

  The full stack trace:

  2017-02-05 02:33:41.787 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Migration running for 240 secs, memory 9% 
remaining; (bytes processed=15198240264, remaining=1680875520, 
total=17314955264)
  2017-02-05 02:33:45.795 19770 INFO nova.compute.manager 
[req-abff9c69-5f82-4ed6-af8a-fd1dc81a72a6 - - - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] VM Paused (Lifecycle Event)
  2017-02-05 02:33:45.870 19770 INFO nova.compute.manager 
[req-abff9c69-5f82-4ed6-af8a-fd1dc81a72a6 - - - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] During sync_power_state the instance has 
a pending task (migrating). Skip.
  2017-02-05 02:33:45.883 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Migration operation has completed
  2017-02-05 02:33:45.884 19770 INFO nova.compute.manager 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] _post_live_migration() is started..
  2017-02-05 02:33:46.156 19770 INFO os_vif 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] Successfully unplugged vif 
VIFBridge(active=True,address=fa:16:3e:a2:90:55,bridge_name='brq476ab6ba-b3',has_traffic_filtering=True,id=98d476b3-0ead-4adb-ad54-1dff63edcd65,network=Network(476ab6ba-b32e-409e-9711-9412e8475ea0),plugin='linux_bridge',port_profile=,preserve_on_delete=True,vif_name='tap98d476b3-0e')
  2017-02-05 02:33:46.189 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Deleting instance files 
/var/lib/nova/instances/62034d78-3144-4efd-9c2c-8a792aed3d6b_del
  2017-02-05 02:33:46.195 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Deletion of 
/var/lib/nova/instances/62034d78-3144-4efd-9c2c-8a792aed3d6b_del complete

  2017-02-05 02:33:46.334 19770 ERROR nova.virt.libvirt.driver [req-
  df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c
  669472610b194bfa9bf03f50f86d725a - - -] [instance: 62034d78-3144-4efd-
  9c2c-8a792aed3d6b] Error from libvirt during undefine. Code=42
  Error=Domain not found: no domain with matching uuid '62034d78-3144
  -4efd-9c2c-8a792aed3d6b' (instance-0431)

  2017-02-05 02:33:46.363 19770 WARNING nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] 

[Yahoo-eng-team] [Bug 1662626] Re: live-migrate left in migrating as domain not found

[Corey Bryant]

** Changed in: cloud-archive
   Status: Confirmed => Fix Released

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

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

** Changed in: nova (Ubuntu)
   Importance: Undecided => Medium

** Also affects: nova (Ubuntu Artful)
   Importance: Medium
   Status: Fix Released

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

** Also affects: nova (Ubuntu Xenial)
   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/1662626

Title:
  live-migrate left in migrating as domain not found

Status in Ubuntu Cloud Archive:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) newton series:
  Fix Committed
Status in OpenStack Compute (nova) ocata series:
  Fix Committed
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  New
Status in nova source package in Zesty:
  New
Status in nova source package in Artful:
  Fix Released

Bug description:
  A live-migration stress test was working fine when suddenly a VM
  stopped migrating. It failed with this error:

  ERROR nova.virt.libvirt.driver [req-df91ac40-820f-4aa9-945b-
  b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c
  669472610b194bfa9bf03f50f86d725a - - -] [instance: 62034d78-3144-4efd-
  9c2c-8a792aed3d6b] Error from libvirt during undefine. Code=42
  Error=Domain not found: no domain with matching uuid '62034d78-3144
  -4efd-9c2c-8a792aed3d6b' (instance-0431)

  The full stack trace:

  2017-02-05 02:33:41.787 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Migration running for 240 secs, memory 9% 
remaining; (bytes processed=15198240264, remaining=1680875520, 
total=17314955264)
  2017-02-05 02:33:45.795 19770 INFO nova.compute.manager 
[req-abff9c69-5f82-4ed6-af8a-fd1dc81a72a6 - - - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] VM Paused (Lifecycle Event)
  2017-02-05 02:33:45.870 19770 INFO nova.compute.manager 
[req-abff9c69-5f82-4ed6-af8a-fd1dc81a72a6 - - - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] During sync_power_state the instance has 
a pending task (migrating). Skip.
  2017-02-05 02:33:45.883 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Migration operation has completed
  2017-02-05 02:33:45.884 19770 INFO nova.compute.manager 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] _post_live_migration() is started..
  2017-02-05 02:33:46.156 19770 INFO os_vif 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] Successfully unplugged vif 
VIFBridge(active=True,address=fa:16:3e:a2:90:55,bridge_name='brq476ab6ba-b3',has_traffic_filtering=True,id=98d476b3-0ead-4adb-ad54-1dff63edcd65,network=Network(476ab6ba-b32e-409e-9711-9412e8475ea0),plugin='linux_bridge',port_profile=,preserve_on_delete=True,vif_name='tap98d476b3-0e')
  2017-02-05 02:33:46.189 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Deleting instance files 
/var/lib/nova/instances/62034d78-3144-4efd-9c2c-8a792aed3d6b_del
  2017-02-05 02:33:46.195 19770 INFO nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Deletion of 
/var/lib/nova/instances/62034d78-3144-4efd-9c2c-8a792aed3d6b_del complete

  2017-02-05 02:33:46.334 19770 ERROR nova.virt.libvirt.driver [req-
  df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c
  669472610b194bfa9bf03f50f86d725a - - -] [instance: 62034d78-3144-4efd-
  9c2c-8a792aed3d6b] Error from libvirt during undefine. Code=42
  Error=Domain not found: no domain with matching uuid '62034d78-3144
  -4efd-9c2c-8a792aed3d6b' (instance-0431)

  2017-02-05 02:33:46.363 19770 WARNING nova.virt.libvirt.driver 
[req-df91ac40-820f-4aa9-945b-b2fce73461f8 29c0371e35f84fdaa033f2dbfe2c042c 
669472610b194bfa9bf03f50f86d725a - - -] [instance: 
62034d78-3144-4efd-9c2c-8a792aed3d6b] Error monitoring migration: Domain not 
found: no domain with matching uuid '62034d78-3144-4efd-9c2c-8a792aed3d6b' 
(instance-0431)
  2017-02-05 02:33:46.363 19770 ERROR nova.virt.libvirt.driver [instance: 

[Yahoo-eng-team] [Bug 1620226] Re: Wrong cinder quota value been accepted

[Akihiro Motoki]

Following the comments on the above horizon review
https://review.openstack.org/365520, the horizon bug was fixed as bug
1611027, so it looks better to remove horizon from the affected
projects.

** No longer affects: horizon

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

Title:
  Wrong cinder quota value been accepted

Status in OpenStack Heat:
  Fix Released

Bug description:
  While testing cinder quota in heat resource, 
  find out we have accept wrong quota value and added it to cinder.
  For example, if we already have 2 volumes in project, we then update quota to 
accept 1 volume.
  That means quotas will not consider the real fact in heat (and to limit the 
real fact should be the only good quota provided).
  Consider that horizon already precheck this kind of mistake, we should add 
check to prevent that.

  On further test with horizon, also find out that horizon should not
  use only total volumes size to validate gigabytes quota. Gigabytes
  refer to total size of volumes and snapshots. That's what cinder react
  as well(if you set gigabytes equal to total volumes size, it will
  raise error when creating snapshots).

To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1620226/+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 1672714] Re: ThemableChoiceField: choise list is displayed only in a form; may reduce usability

[Akihiro Motoki]

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

My previous comment was wrong. This is a duplicate of bug 1603496.

** This bug has been marked a duplicate of bug 1603496
   UX: Dropdown with several items does not fit in modal

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

Title:
  ThemableChoiceField: choise list is displayed only in a form; may
  reduce usability

Status in OpenStack Dashboard (Horizon):
  Confirmed

Bug description:
  When I try to switch ChoiceField in "settings" dashboard (/settings)
  to ThemableChoiceField, I see a problem on how a choice list is
  displayed which potentially reduces the usability. In /settings we
  have long choice list in Language and Timezone. Currently the list of
  choices is displayed using a full window, but after switching to
  ThemableChoiceField, the list of choices is displayed only inside the
  form. It reduces the usablilty because users can see a small set of
  choices at once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1672714/+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 1331258] Re: workflow default success/error messaging bug

[Akihiro Motoki]

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

** Changed in: horizon
 Assignee: David Cusatis (dcusati) => (unassigned)

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

Title:
  workflow default success/error messaging bug

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Default workflow success and failure messages are:

  success_message = _("%s completed successfully.")
  failure_message = _("%s did not complete.")
  
https://github.com/openstack/horizon/blob/master/horizon/workflows/base.py#L595

  According to the class definition, failure message is supposed to be:
  "{{ workflow.name }} did not complete."

  However, it ends up using the row.name and appearing as "demo did not
  complete."

  When it should be "Edit project did not complete".

  Please see attachment.

  You can try this out for yourself by going to /admin/projects/workflows.py 
(https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/admin/projects/workflows.py#L346)
  and commenting out the two success and failure messages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1331258/+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 1580317] Re: horizon's cinder api should cache extensions list

[Gary W. Smith]

This is being done in current versions of horizon

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

Title:
  horizon's cinder api should cache extensions list

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  As described in bug: https://bugs.launchpad.net/horizon/+bug/1258593
  horizon's services apis (in this case cinder api) should cache more 
aggressively regardless of request. Starting with the extensions list methods

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1580317/+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 1722417] Re: [Performance] Useless network API calls on instance panel

[Gary W. Smith]

Changing status to Opinion since there is some debate about whether this
can be safely removed.  If the consensus on the horizon team is that
this should indeed be pursued, feel free to change the status back to
New.

** Tags added: performance

** Changed in: horizon
   Status: In Progress => Opinion

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

Title:
  [Performance] Useless network API calls on instance panel

Status in OpenStack Dashboard (Horizon):
  Opinion

Bug description:
  The function calling at 
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/views.py#L95
 is useless because Horizon is using the detailed API to get server list, see 
https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/nova.py#L529
  With detailed API, the addresses of server are returned. So there is no need 
to call Neutron API to get the addresses info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1722417/+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 1476123] Re: serial console does not honor webroot setting

[Gary W. Smith]

As Itxaka indicated above, this has been fixed.

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

Title:
  serial console does not honor webroot setting

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Steps to Reproduce:
  ===
  1. install openstack-nova-serialproxy
  2. On /etc/openstack-dashboard/local_settings set CONSOLE_TYPE = "SERIAL"
  3. On compute node edit /etc/nova/nova.conf set 
  [serial_console]  
   enabled=True
   base_url=ws://10.35.64.150:6083/
   listen=0.0.0.0
  4. Restart services
  5. Restasrt httpd 
  6. launch instance.

  Actual results:
  ===
  The requested URL
  /project/instances/2dd47f65-4563-4281-af96-b88ba50e9a25/serial was not found 
on
  this server.

  Expected results:
  =
  serial console opened successfully

  Additional info:
  
  Serial console opened successfully via CLI

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1476123/+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 1617360] Re: The input field display should be depend on the choice

[Gary W. Smith]

This works correctly in pike.

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

Title:
  The input field display should be depend on the choice

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Reproduce:
  1, Open Admin/System/Metadata Definitions panel
  2, Click the button "Import Namespace"
  3, There will show the "Import Namespace" form. The "Metadata Definition 
File" field and "Namespace JSON" are all shown.
  But this two field should only show one and show which one should depend on 
the "Namespace Definition Source".
  Please see the screenshot for more detail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1617360/+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 1605339] Re: LaunchInstance NG : Redundant label "Delete Volume on Instance Delete"

[Gary W. Smith]

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

** This bug has been marked a duplicate of bug 1584917
   [ng launch instance] Delete Vol on Instance Delete toggle shows up twice

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

Title:
  LaunchInstance NG : Redundant label "Delete Volume on Instance Delete"

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Master release :
  
openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/source/source.html

  --- _old_source.html2016-07-21 19:09:20.271671469 +0200
  +++ source.html 2016-07-21 19:17:25.669747936 +0200
  @@ -34,19 +34,6 @@
 
   

  -
  -  
  -
  -  Delete Volume on Instance Delete
  -  
  -{$ ::option.label $}
  -  
  -
  -  
  -
 

 

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1605339/+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 1544888] Re: cinder quota not available in a non-default domain

[Gary W. Smith]

Marking horizon bug as invalid since this is reproducible with the
cinder CLI.

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

Title:
  cinder quota not available in a non-default domain

Status in Cinder:
  Confirmed
Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  I am running a multi-domain environment and am unable to access cinder quota 
information in Horizon from a non-default domain.
  My default domain is with the SQL back end and the other one with an LDAP 
back end.

  The effects include not being able to launch instances and not being
  able to modify quota information.

  The error I get performing related actions is this:
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/usage/quotas.py#L152

  And for example the code failing when launching an instance is this:
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L225

  I tried to remove unnecessary information from logs (Time, request
  id-s, sensitive information).

  From horizon logs(apache2 error log):
   [:error]  Internal Server Error: /horizon/project/instances/launch
   [:error]  Traceback (most recent call last):
   [:error]File 
"/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 111, in 
get_response
   [:error]  response = wrapped_callback(request, *callback_args, 
**callback_kwargs)
   [:error]File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/decorators.py",
 line 36, in dec
   [:error]  return view_func(request, *args, **kwargs)
   [:error]File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/decorators.py",
 line 52, in dec
   [:error]  return view_func(request, *args, **kwargs)
   [:error]File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/decorators.py",
 line 36, in dec
   [:error]  return view_func(request, *args, **kwargs)
   [:error]File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/decorators.py",
 line 84, in dec
   [:error]  return view_func(request, *args, **kwargs)
   [:error]File 
"/usr/lib/python2.7/dist-packages/django/views/generic/base.py", line 69, in 
view
   [:error]  return self.dispatch(request, *args, **kwargs)
   [:error]File 
"/usr/lib/python2.7/dist-packages/django/views/generic/base.py", line 87, in 
dispatch
   [:error]  return handler(request, *args, **kwargs)
   [:error]File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/workflows/views.py",
 line 167, in post
   [:error]  context = self.get_context_data(**kwargs)
   [:error]File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/workflows/views.py",
 line 91, in get_context_data
   [:error]  workflow = self.get_workflow()
   [:error]File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/workflows/views.py",
 line 81, in get_workflow
   [:error]  entry_point=entry_point)
   [:error]File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/workflows/base.py",
 line 651, in __init__
   [:error]  valid = step.action.is_valid()0
   [:error]File "/usr/lib/python2.7/dist-packages/django/forms/forms.py", 
line 162, in is_valid
   [:error]  return self.is_bound and not bool(self.errors)
   [:error]File "/usr/lib/python2.7/dist-packages/django/forms/forms.py", 
line 154, in errors
   [:error]  self.full_clean()
   [:error]File "/usr/lib/python2.7/dist-packages/django/forms/forms.py", 
line 354, in full_clean
   [:error]  self._clean_form()
   [:error]File "/usr/lib/python2.7/dist-packages/django/forms/forms.py", 
line 378, in _clean_form
   [:error]  cleaned_data = self.clean()
   [:error]File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/instances/workflows/create_instance.py",
 line 367, in clean
   [:error]  self._check_quotas(cleaned_data)
   [:error]File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/instances/workflows/create_instance.py",
 line 224, in _check_quotas
   [:error]  available_volume = usages['volumes']['available']
   [:error]  KeyError: 'available'

  
  And a related bug seems to be a call to cinder api:

  INFO cinder.api.openstack.wsgi GET 
http://openstack:8776/v2/febe06c4fb8e4b4ea5cbd86f3827ced1/os-quota-sets/febe06c4fb8e4b4ea5cbd86f3827ced1?usage=False
  ERROR cinder.api.middleware.fault  Caught error: Non-default domain is not 
supported (Disable debug mode to suppress these details.) (HTTP 401) 
(Request-ID: req-4d088b3f-abb6-4475-b72c-f915f6c6413b) (HTTP 401)

[Yahoo-eng-team] [Bug 1704402] Re: dns-sortlist not recognized in network-config

[Scott Moser]

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

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

Title:
  dns-sortlist not recognized in network-config

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  New

Bug description:
  I'm using LXD with Ubuntu images, and cloud-init to do initial setup
  of container.  I'm not sure, but I believe the issue is in cloud-init,
  but would appreciate a pointer to the right location if not.
  Currently using network-config meta data, cloud-init takes the
  following config and converts correctly:

  version: 1
  config:
   - type: physical
 name: eth0
   - type: nameserver
 address: ['xx.xx.xx.xx']
 search: ['example.local', 'example.org']

  However including the following line is not recognized:

 sortlist: ['xx.xx.xx.xx', 'xx.xx.xx.xx']

  Please add support for this standard nameserver option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1704402/+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 1672133] Re: local-memory cache backend of Django session backend can't pass session data after logining

[Gary W. Smith]

The above code is Django's rather than Horizon's.  Consider filing a bug
with the Django project.

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

Title:
  local-memory cache backend of Django session backend can't pass
  session data after logining

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  the browser remained in the login page after login with right user and 
password, when I change backend session engine from mysql to local-memory 
cache. I inspect the code, and found this code: 
  in .../django/core/cache/__init__.py
  class CacheHandler(object):

  def __init__(self):
  self._caches = local()

  def __getitem__(self, alias):

  try:
  return self._caches.caches[alias]
  except AttributeError:
  self._caches.caches = {}
  except KeyError:
  getitemp("no caches.caches.caches key in cache handler getitem, ")
  pass

  if alias not in settings.CACHES:
  raise InvalidCacheBackendError(
  "Could not find config for '%s' in settings.CACHES" % alias
  )
  cache = _create_cache(alias)
  self._caches.caches[alias] = cache
  return cache
  def all(self):
  return getattr(self._caches, 'caches', {}).values()

  caches = CacheHandler()

  in Login view, the user has autenticated, and the session info has been 
recorded in caches._caches.caches[alias],
  but when browser re-targets to project view, the backend is a new process 
with new caches(),so 
  except AttributeError:
  self._caches.caches = {}
  no old session data in it, the view return to login page again.
  Is this a bug? or a Django bug? 
  thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1672133/+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 1676327] Re: UnicodeDecodeError 'ascii' codec can't decode byte 0xc5 in position

[Sylvain Bauza]

Fixed in
https://github.com/openstack/nova/commit/564958dba6c280eb8e11ae9bbc819c7da6e204bd

which is Pike.

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

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

Title:
  UnicodeDecodeError 'ascii' codec can't decode byte 0xc5 in position

Status in Mirantis OpenStack:
  Confirmed
Status in Mirantis OpenStack 10.0.x series:
  Confirmed
Status in Mirantis OpenStack 9.x series:
  Confirmed
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Detailed bug description:
   We can't launch instance with non-ascii symbol in the name or in image 
description field
  Steps to reproduce:
   Enable Debug=True on the nova-compute host, restart nova-compute service.
  Launch instance with name f.e. "iš instance"
  Expected results:
   Instance in active state
  Actual result:
   Instance in ERROR state
  Reproducibility:
   100%
  Workaround:
   Set DEBUG=False

  Description of the environment:
  - Operation system: Ubuntu, RHEL
  - Versions of components: MOS 9.0, 9.1

  Additional information:

  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager 
[req-a427a02d-9563-4f6b-8111-e6b5dc15f830 ec0ffcafc20244029d090e7e98aa0461 
9b05738c81444d5e8ba74669c058f53a - - -] [instance: 25073828-c38f-4ec4-a3a7-5
  e9e092806e4] Instance failed to spawn
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4] Traceback (most recent call last):
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2218, in 
_build_resources
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4] yield resources
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2064, in 
_build_and_run_instan
  ce
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4] block_device_info=block_device_info)
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2793, in 
spawn
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4] write_to_disk=True)
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 4737, in 
_get_guest_xml
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4] context)
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 4603, in 
_get_guest_config
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4] flavor, virt_type, self._host)
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 437, in 
get_config
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4] 'vif': vif, 'virt_type': virt_type})
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4]   File 
"/usr/lib/python2.7/logging/__init__.py", line 1425, in debug
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4] self.logger.debug(msg, *args, 
**kwargs)
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4]   File 
"/usr/lib/python2.7/logging/__init__.py", line 1140, in debug
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4] self._log(DEBUG, msg, args, **kwargs)
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4]   File 
"/usr/lib/python2.7/logging/__init__.py", line 1271, in _log
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4] self.handle(record)
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4]   File 
"/usr/lib/python2.7/logging/__init__.py", line 1281, in handle
  2017-03-27 09:03:26.005 2489897 ERROR nova.compute.manager [instance: 
25073828-c38f-4ec4-a3a7-5e9e092806e4] 

[Yahoo-eng-team] [Bug 1722184] Re: Resize/migrate instance will leave instance directory in source host with ceph storage

[Sylvain Bauza]

Fixed in Pike with https://review.openstack.org/#/c/437356/

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

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

Title:
  Resize/migrate instance will leave instance directory in source host
  with ceph storage

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===
  In kvm + ceph scenario, we resize or migrate an instance, the instance root 
directory will remain in source host. When we do live migration of the instance 
to the original source host, it will raise an exception that the The supplied 
disk path (%(path)s) already exists.

  Steps to reproduce
  ==
  1. Create an instance. Remember the host that the instance is running.
  2. Resize/migrate this instance.

  Expected result
  ===
  The instance directory in source host does not exist.

  Actual result
  =
  The instance directory in source host still exist.

  Environment
  ===
  CentOS 7.2 + Openstack mitaka 

  Logs & Configs
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1722184/+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 1724514] Re: privsep helper command exited non-zero in neutron-fwaas

[OpenStack Infra]

Reviewed:  https://review.openstack.org/512985
Committed: 
https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=8a82773a6860b873f5c89d6819e6ef404aeaffda
Submitter: Zuul
Branch:master

commit 8a82773a6860b873f5c89d6819e6ef404aeaffda
Author: Cao Xuan Hoang 
Date:   Wed Oct 18 16:31:05 2017 +0700

Fix UTs gate failed

This patch fix UTs gate failed because of recent change in
Neutron: Id802e77543177fbb95ff15c2c7361172e8824633

Change-Id: Ic4116ac6b9a3be723e25d54f5e52adaa4dfc7d37
Closes-bug: #1724514


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

Title:
  privsep helper command exited non-zero in neutron-fwaas

Status in neutron:
  Fix Released

Bug description:
  eg. http://logs.openstack.org/26/512926/2/check/openstack-tox-
  py27/3e7d6f7/testr_results.html.gz

  ft1.9: 
neutron_fwaas.tests.unit.services.firewall.agents.l3reference.test_firewall_l3_agent.TestFwaasL3AgentRpcCallback.test_get_router_info_list_two_routers_one_without_router_info_StringException:
 Traceback (most recent call last):
File 
"/home/zuul/src/git.openstack.org/openstack/neutron/neutron/tests/base.py", 
line 118, in func
  return f(self, *args, **kwargs)
File 
"neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py",
 line 360, in test_get_router_info_list_two_routers_one_without_router_info
  rtr_with_ri=True)
File 
"neutron_fwaas/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py",
 line 351, in _get_router_info_list_router_without_router_info_helper
  ri.router['tenant_id'])
File 
"neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent.py", line 
137, in _get_router_info_list_for_tenant
  self.agent_api.is_router_in_namespace(ri.router_id)]
File 
"/home/zuul/src/git.openstack.org/openstack/neutron/neutron/agent/l3/l3_agent_extension_api.py",
 line 64, in is_router_in_namespace
  local_namespaces = self._local_namespaces()
File 
"/home/zuul/src/git.openstack.org/openstack/neutron/neutron/agent/l3/l3_agent_extension_api.py",
 line 33, in _local_namespaces
  local_ns_list = ip_lib.list_network_namespaces()
File 
"/home/zuul/src/git.openstack.org/openstack/neutron/neutron/agent/linux/ip_lib.py",
 line 1038, in list_network_namespaces
  return privileged.list_netns(**kwargs)
File 
"/home/zuul/src/git.openstack.org/openstack/neutron-fwaas/.tox/py27/local/lib/python2.7/site-packages/oslo_privsep/priv_context.py",
 line 204, in _wrap
  self.start()
File 
"/home/zuul/src/git.openstack.org/openstack/neutron-fwaas/.tox/py27/local/lib/python2.7/site-packages/oslo_privsep/priv_context.py",
 line 215, in start
  channel = daemon.RootwrapClientChannel(context=self)
File 
"/home/zuul/src/git.openstack.org/openstack/neutron-fwaas/.tox/py27/local/lib/python2.7/site-packages/oslo_privsep/daemon.py",
 line 327, in __init__
  raise FailedToDropPrivileges(msg)
  oslo_privsep.daemon.FailedToDropPrivileges: privsep helper command exited 
non-zero (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1724514/+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 1707129] Re: Error in docs for configuring distributed virtual routing

[yanpuqing]

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

Title:
  Error in docs for configuring distributed virtual routing

Status in neutron:
  Fix Released

Bug description:
  The doc for configuring Network nodes in the /neutron/doc/source/admin
  /config-dvr-ha-snat.rst is that:

  "Configure the Open vSwitch agent. Add the following to
  /etc/neutron/plugins/ml2/ml2_conf.ini:

  [ovs]
  local_ip = TUNNEL_INTERFACE_IP_ADDRESS
  bridge_mappings = external:br-ex

  [agent]
  enable_distributed_routing = True
  tunnel_types = vxlan
  l2_population = True"

  It should be ml2_conf rather than ovs_conf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1707129/+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 1724771] Re: start image as instance via horizon failed

[Markus Zoeller (markus_z)]

@Robert Holling: 
Because of the information before, I think it's a setup/configuration issue. 
Feel free to re-open this issue if you think there is a bug in OpenStack. 

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

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

Title:
  start image as instance via horizon failed

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  environment:
  - fresh/inital installation of OpenStack Pike on Ubuntu 16.04.3 LTS
  - Horizon, Glance, Nova and Keystone as components on three different nodes 
with five compute nodes

  steps to procedure until error:
  - download cirros-image as described in manual -> donwload worked, image is 
shown in horizon
  - created a flavor (128 MB RAM, 1G HDD,...) -> worked, flavor created
  - tried to start image as an instance by klicking on , choosing name 
and flavor -> failure with the following message:

  "Unexpected API Error. Please report this at
  http://bugs.launchpad.net/nove/ and attach the NOVA API log if
  possible. 
  (HTTP 500) (Request-ID: req-xx)"

  I expected, that the instance should start...

  If I wouldn't get the message with "... please report this at..." I wouldn't 
do that here. 
  So, hopefully we could get an answer resp. solution.

  THX & kind regards
  Robert

  infos:
  a) result of command $ dpkg -l | grep nova:

  ii  nova-api   2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - API frontend
  ii  nova-common2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - common files
  ii  nova-conductor 2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - conductor service
  ii  nova-consoleauth   2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - Console Authenticator
  ii  nova-novncproxy2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - NoVNC proxy
  ii  nova-placement-api 2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - placement API frontend
  ii  nova-scheduler 2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - virtual machine scheduler
  ii  python-nova2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute Python libraries
  ii  python-novaclient  2:9.1.0-0ubuntu1~cloud0
all  client library for OpenStack Compute API - Python 2.7

  b) hypervisor QEMU
  c) storage not implemented yet (CINDER t.b.d.)
  d) network not implemented yet (NEUTRON t.b.d)

  attachments:
  a) nova-api.log file as requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1724771/+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 1696309] Re: net-ip-availability-list not support filter by project id

[OpenStack Infra]

Reviewed:  https://review.openstack.org/471604
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=8ab3a7dc0d5778dfb9c8fdf7e5e0526f1eadd39e
Submitter: Zuul
Branch:master

commit 8ab3a7dc0d5778dfb9c8fdf7e5e0526f1eadd39e
Author: Dongcan Ye 
Date:   Wed Jun 7 15:04:30 2017 +0800

Add network ip availability filtered by project_id

Currently we can't get network ip availability list by project id,
This patch fixes it.
Also add project_id attribute in net-ip-availability-show.

Change-Id: I3eed5a26e5674740b331f772eb7f510b41fae4e4
Closes-Bug: #1696309


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

Title:
  net-ip-availability-list not support filter by project id

Status in neutron:
  Fix Released

Bug description:
  List network ip availability filtered by project id not supported.

  $ neutron net-ip-availability-list --project-id 
6d0a93fb8cfc4c2f84e3936d95a17bad
  neutron CLI is deprecated and will be removed in the future. Use openstack 
CLI instead.
  
+--+--+--+---+--+
  | network_id   | tenant_id| 
network_name | total_ips | used_ips |
  
+--+--+--+---+--+
  | 34bed001-306a-4b1c-a441-c9f6bf95b361 | b76ff5120e234f11a7e7a35a5b60277e | 
private-net  |   253 |2 |
  | 4ebdcf94-6ec9-498c-a2c6-b7746aaf09f5 | c04b15f261854c13bff01610313e7b99 | 
dvr-net  |   253 |4 |
  | e374af03-4461-4316-bf8c-d95f5ed8526c | 274428ff074a4b639809fb28a52c2621 | 
private-net  |   253 |5 |
  | bd1aa0a3-fe2f-42b1-b4e0-6405d4609279 | ed343dbff2384a07bf5871f0cac018f5 | 
private-net  |   253 |2 |
  | 3a4a15f6-5eb3-4f4e-acf5-940131030e9f | c04b15f261854c13bff01610313e7b99 | 
ceph-net |   253 |7 |
  | 9cd01eb4-906a-4c68-b705-0520bfe1b1e6 | 6d0a93fb8cfc4c2f84e3936d95a17bad | 
net12|   253 |1 |

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1696309/+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 1724771] [NEW] start image as instance via horizon failed

[Robert Holling]

Public bug reported:

environment:
- fresh/inital installation of OpenStack Pike on Ubuntu 16.04.3 LTS
- Horizon, Glance, Nova and Keystone as components on three different nodes 
with five compute nodes

steps to procedure until error:
- download cirros-image as described in manual -> donwload worked, image is 
shown in horizon
- created a flavor (128 MB RAM, 1G HDD,...) -> worked, flavor created
- tried to start image as an instance by klicking on , choosing name and 
flavor -> failure with the following message:

"Unexpected API Error. Please report this at
http://bugs.launchpad.net/nove/ and attach the NOVA API log if possible.
 (HTTP 500)
(Request-ID: req-xx)"

I expected, that the instance should start...

If I wouldn't get the message with "... please report this at..." I wouldn't do 
that here. 
So, hopefully we could get an answer resp. solution.

THX & kind regards
Robert

infos:
a) result of command $ dpkg -l | grep nova:

ii  nova-api   2:16.0.0-0ubuntu2~cloud0 
  all  OpenStack Compute - API frontend
ii  nova-common2:16.0.0-0ubuntu2~cloud0 
  all  OpenStack Compute - common files
ii  nova-conductor 2:16.0.0-0ubuntu2~cloud0 
  all  OpenStack Compute - conductor service
ii  nova-consoleauth   2:16.0.0-0ubuntu2~cloud0 
  all  OpenStack Compute - Console Authenticator
ii  nova-novncproxy2:16.0.0-0ubuntu2~cloud0 
  all  OpenStack Compute - NoVNC proxy
ii  nova-placement-api 2:16.0.0-0ubuntu2~cloud0 
  all  OpenStack Compute - placement API frontend
ii  nova-scheduler 2:16.0.0-0ubuntu2~cloud0 
  all  OpenStack Compute - virtual machine scheduler
ii  python-nova2:16.0.0-0ubuntu2~cloud0 
  all  OpenStack Compute Python libraries
ii  python-novaclient  2:9.1.0-0ubuntu1~cloud0  
  all  client library for OpenStack Compute API - Python 2.7

b) hypervisor QEMU
c) storage not implemented yet (CINDER t.b.d.)
d) network not implemented yet (NEUTRON t.b.d)

attachments:
a) nova-api.log file as requested

** Affects: nova
 Importance: Undecided
 Status: New

** Attachment added: "current nova-api.log after error"
   
https://bugs.launchpad.net/bugs/1724771/+attachment/4975633/+files/nova-api.log

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

Title:
  start image as instance via horizon failed

Status in OpenStack Compute (nova):
  New

Bug description:
  environment:
  - fresh/inital installation of OpenStack Pike on Ubuntu 16.04.3 LTS
  - Horizon, Glance, Nova and Keystone as components on three different nodes 
with five compute nodes

  steps to procedure until error:
  - download cirros-image as described in manual -> donwload worked, image is 
shown in horizon
  - created a flavor (128 MB RAM, 1G HDD,...) -> worked, flavor created
  - tried to start image as an instance by klicking on , choosing name 
and flavor -> failure with the following message:

  "Unexpected API Error. Please report this at
  http://bugs.launchpad.net/nove/ and attach the NOVA API log if
  possible. 
  (HTTP 500) (Request-ID: req-xx)"

  I expected, that the instance should start...

  If I wouldn't get the message with "... please report this at..." I wouldn't 
do that here. 
  So, hopefully we could get an answer resp. solution.

  THX & kind regards
  Robert

  infos:
  a) result of command $ dpkg -l | grep nova:

  ii  nova-api   2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - API frontend
  ii  nova-common2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - common files
  ii  nova-conductor 2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - conductor service
  ii  nova-consoleauth   2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - Console Authenticator
  ii  nova-novncproxy2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - NoVNC proxy
  ii  nova-placement-api 2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - placement API frontend
  ii  nova-scheduler 2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute - virtual machine scheduler
  ii  python-nova2:16.0.0-0ubuntu2~cloud0   
all  OpenStack Compute Python libraries
  ii  python-novaclient  2:9.1.0-0ubuntu1~cloud0
all  

[Yahoo-eng-team] [Bug 1724766] [NEW] neutron not support userspace/dpdk conntrack

[Rong.Wang]

Public bug reported:

ovs 2.6 has support the basic userspace conntrack, may be neutron should
support it.

https://github.com/openvswitch/ovs/blob/v2.6.0/NEWS#L93

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: conntrack

** Tags added: conntrack

** Description changed:

  ovs 2.6 has support the basic userspace conntrack, may be neutron should
  support it.
+ 
+ https://github.com/openvswitch/ovs/blob/v2.6.0/NEWS#L93

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

Title:
  neutron not support userspace/dpdk conntrack

Status in neutron:
  New

Bug description:
  ovs 2.6 has support the basic userspace conntrack, may be neutron
  should support it.

  https://github.com/openvswitch/ovs/blob/v2.6.0/NEWS#L93

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