[Yahoo-eng-team] [Bug 1785606] Re: When working with python3 header banner is not rendered properly
** Changed in: vitrage-dashboard 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/1785606 Title: When working with python3 header banner is not rendered properly Status in OpenStack Dashboard (Horizon): Fix Released Status in Vitrage Dashboard: Fix Released Bug description: When running horizon under python 3, the header banner response returned is in bytes format, and python 3 interprets it different from python 2, thus breaking the banner completely To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1785606/+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 1784387] Re: rebuild API reference should discuss implications of specifying a new image
Reviewed: https://review.openstack.org/588931 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=330c95090881a21eddf9f1483762e453330d6e45 Submitter: Zuul Branch:master commit 330c95090881a21eddf9f1483762e453330d6e45 Author: Takashi NATSUME Date: Sun Aug 5 02:39:47 2018 +0900 api-ref: Add descriptions for rebuild Add descriptions about specifying a new image and asynchronous postconditions in the rebuild operation in the compute API reference. Change-Id: I0fd136d07dffc2be845b4b9330fae98c7115789b Closes-Bug: #1784387 ** 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/1784387 Title: rebuild API reference should discuss implications of specifying a new image Status in OpenStack Compute (nova): Fix Released Bug description: The imageRef parameter description does not describe what happens during rebuild if a new image is provided, nor is there any asynchronous post-condition section for what the user should expect: https://developer.openstack.org/api-ref/compute/#rebuild-server- rebuild-action There are a few implications of specifying a new imageRef: 1. You cannot specify a new image for a volume-backed server, it will result in an error. 2. For non-volume-backed servers, specifying a new image will result in validating that the image is acceptable for the current compute host on which the server is running. If the new image is not valid, the server will go into "ERROR" status and can be rebuilt with a different image. The description of the API does not really mention what it does, i.e. destroys and re-creates the server including the root disk (if not on shared storage - which the user won't know beforehand) while preserving attached volumes and ports. As for asynchronous post-conditions, if the server was in status SHUTOFF before the rebuild, it will be stopped and in status SHUTOFF after the rebuild, otherwise it will be ACTIVE if the rebuild was successful or ERROR if the rebuild failed. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1784387/+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 1785415] Re: os-server-groups API samples should indicate they are using microversion 2.64
Reviewed: https://review.openstack.org/589006 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=00b585a1b94099e58177a04b204ca94fa0bc5908 Submitter: Zuul Branch:master commit 00b585a1b94099e58177a04b204ca94fa0bc5908 Author: Yikun Jiang Date: Mon Aug 6 10:33:27 2018 +0800 Add microversion info in the os-server-groups API samples The os-server-groups samples are using 2.64 but don't explicitly say that, so we need something like "(v2.64)" in the os-server-groups.inc. In this patch, we add microversion info in the os-server-groups API samples. Change-Id: Ia7e25ceba532e6cfd0ed18cf3cc8113512d50323 Closes-bug: #1785415 ** 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/1785415 Title: os-server-groups API samples should indicate they are using microversion 2.64 Status in OpenStack Compute (nova): Fix Released Bug description: The samples in https://developer.openstack.org/api-ref/compute /#server-groups-os-server-groups are using microversion 2.64 but don't explicitly say that. The samples were changed in Rocky with change: https://github.com/openstack/nova/commit/5cdb1ce26b0ec53c231723bcc6ce880aa8f43f0f Normally when the API samples are using a microversion beyond 2.1, they put that into the description of the request/response samples, like this: https://github.com/openstack/nova/blob/b046a998443d4586d4ca7a2863b785b909a4d076 /api-ref/source/os-hypervisors.inc Example List Hypervisors (v2.33): JSON response So we'll want something like "(v2.64)" in the os-server-groups samples. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1785415/+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 1770712] Re: It would be nice if cloud-init provides full version in logs
This bug was fixed in the package cloud-init - 18.3-9-g2e62cb8a- 0ubuntu1~18.04.2 --- cloud-init (18.3-9-g2e62cb8a-0ubuntu1~18.04.2) bionic-proposed; urgency=medium * cherry-pick 3cee0bf8: oracle: fix detect_openstack to report True on (LP: #1784685) cloud-init (18.3-9-g2e62cb8a-0ubuntu1~18.04.1) bionic-proposed; urgency=medium * New upstream snapshot. (LP: #1777912) - docs: note in rtd about avoiding /tmp when writing files - ubuntu,centos,debian: get_linux_distro to align with platform.dist - Fix boothook docs on environment variable name (INSTANCE_I -> INSTANCE_ID) [Marc Tamsky] - update_metadata: a datasource can support network re-config every boot - tests: drop salt-minion integration test - Retry on failed import of gpg receive keys. - tools: Fix run-container when neither source or binary package requested. - docs: Fix a small spelling error. [Oz N Tiram] - tox: use simplestreams from git repository rather than bzr. cloud-init (18.3-0ubuntu1~18.04.1) bionic-proposed; urgency=medium * debian/rules: update version.version_string to contain packaged version. (LP: #1770712) * debian/patches/openstack-no-network-config.patch add patch to ignore Openstack network_config from network_data.json by default * New upstream release. (LP: #1777912) - release 18.3 - docs: represent sudo:false in docs for user_groups config module - Explicitly prevent `sudo` access for user module [Jacob Bednarz] - lxd: Delete default network and detach device if lxd-init created them. - openstack: avoid unneeded metadata probe on non-openstack platforms - stages: fix tracebacks if a module stage is undefined or empty [Robert Schweikert] - Be more safe on string/bytes when writing multipart user-data to disk. - Fix get_proc_env for pids that have non-utf8 content in environment. - tests: fix salt_minion integration test on bionic and later - tests: provide human-readable integration test summary when --verbose - tests: skip chrony integration tests on lxd running artful or older - test: add optional --preserve-instance arg to integraiton tests - netplan: fix mtu if provided by network config for all rendered types - tests: remove pip install workarounds for pylxd, take upstream fix. - subp: support combine_capture argument. - tests: ordered tox dependencies for pylxd install - util: add get_linux_distro function to replace platform.dist [Robert Schweikert] - pyflakes: fix unused variable references identified by pyflakes 2.0.0. - - Do not use the systemd_prefix macro, not available in this environment [Robert Schweikert] - doc: Add config info to ec2, openstack and cloudstack datasource docs - Enable SmartOS network metadata to work with netplan via per-subnet routes [Dan McDonald] - openstack: Allow discovery in init-local using dhclient in a sandbox. - tests: Avoid using https in httpretty, improve HttPretty test case. - yaml_load/schema: Add invalid line and column nums to error message - Azure: Ignore NTFS mount errors when checking ephemeral drive [Paul Meyer] - packages/brpm: Get proper dependencies for cmdline distro. - packages: Make rpm spec files patch in package version like in debs. - tools/run-container: replace tools/run-centos with more generic. - Update version.version_string to contain packaged version. - cc_mounts: Do not add devices to fstab that are already present. [Lars Kellogg-Stedman] - ds-identify: ensure that we have certain tokens in PATH. - tests: enable Ubuntu Cosmic in integration tests [Joshua Powers] - read_file_or_url: move to url_helper, fix bug in its FileResponse. - cloud_tests: help pylint - flake8: fix flake8 errors in previous commit. - typos: Fix spelling mistakes in cc_mounts.py log messages [Stephen Ford] - tests: restructure SSH and initial connections [Joshua Powers] - ds-identify: recognize container-other as a container, test SmartOS. - cloud-config.service: run After snap.seeded.service. - tests: do not rely on host /proc/cmdline in test_net.py [Lars Kellogg-Stedman] - ds-identify: Remove dupe call to is_ds_enabled, improve debug message. - SmartOS: fix get_interfaces for nics that do not have addr_assign_type. - tests: fix package and ca_cert cloud_tests on bionic - ds-identify: make shellcheck 0.4.6 happy with ds-identify. - pycodestyle: Fix deprecated string literals, move away from flake8. - azure: Add reported ready marker file. [Joshua Chan] - tools: Support adding a release suffix through packages/bddeb. - FreeBSD: Invoke growfs on ufs filesystems such that it does not prompt. [Harm Weites] - tools: Re-use the orig tarball in packages/bddeb if it is around. - netinfo: fix netdev_pformat when a nic does not have an address assigned. - collect-log
[Yahoo-eng-team] [Bug 1770712] Re: It would be nice if cloud-init provides full version in logs
This bug was fixed in the package cloud-init - 18.3-9-g2e62cb8a- 0ubuntu1~16.04.2 --- cloud-init (18.3-9-g2e62cb8a-0ubuntu1~16.04.2) xenial-proposed; urgency=medium * cherry-pick 3cee0bf8: oracle: fix detect_openstack to report True on (LP: #1784685) cloud-init (18.3-9-g2e62cb8a-0ubuntu1~16.04.1) xenial-proposed; urgency=medium * New upstream snapshot. (LP: #1777912) - docs: note in rtd about avoiding /tmp when writing files - ubuntu,centos,debian: get_linux_distro to align with platform.dist - Fix boothook docs on environment variable name (INSTANCE_I -> INSTANCE_ID) [Marc Tamsky] - update_metadata: a datasource can support network re-config every boot - tests: drop salt-minion integration test - Retry on failed import of gpg receive keys. - tools: Fix run-container when neither source or binary package requested. - docs: Fix a small spelling error. [Oz N Tiram] - tox: use simplestreams from git repository rather than bzr. cloud-init (18.3-0ubuntu1~16.04.1) xenial-proposed; urgency=medium * debian/rules: update version.version_string to contain packaged version. (LP: #1770712) * debian/patches/openstack-no-network-config.patch add patch to ignore Openstack network_config from network_data.json by default * Refresh patches against upstream: + azure-use-walinux-agent.patch + ds-identify-behavior-xenial.patch * New upstream release. (LP: #1777912) - release 18.3 - docs: represent sudo:false in docs for user_groups config module - Explicitly prevent `sudo` access for user module [Jacob Bednarz] - lxd: Delete default network and detach device if lxd-init created them. - openstack: avoid unneeded metadata probe on non-openstack platforms - stages: fix tracebacks if a module stage is undefined or empty [Robert Schweikert] - Be more safe on string/bytes when writing multipart user-data to disk. - Fix get_proc_env for pids that have non-utf8 content in environment. - tests: fix salt_minion integration test on bionic and later - tests: provide human-readable integration test summary when --verbose - tests: skip chrony integration tests on lxd running artful or older - test: add optional --preserve-instance arg to integraiton tests - netplan: fix mtu if provided by network config for all rendered types - tests: remove pip install workarounds for pylxd, take upstream fix. - subp: support combine_capture argument. - tests: ordered tox dependencies for pylxd install - util: add get_linux_distro function to replace platform.dist [Robert Schweikert] - pyflakes: fix unused variable references identified by pyflakes 2.0.0. - - Do not use the systemd_prefix macro, not available in this environment [Robert Schweikert] - doc: Add config info to ec2, openstack and cloudstack datasource docs - Enable SmartOS network metadata to work with netplan via per-subnet routes [Dan McDonald] - openstack: Allow discovery in init-local using dhclient in a sandbox. - tests: Avoid using https in httpretty, improve HttPretty test case. - yaml_load/schema: Add invalid line and column nums to error message - Azure: Ignore NTFS mount errors when checking ephemeral drive [Paul Meyer] - packages/brpm: Get proper dependencies for cmdline distro. - packages: Make rpm spec files patch in package version like in debs. - tools/run-container: replace tools/run-centos with more generic. - Update version.version_string to contain packaged version. - cc_mounts: Do not add devices to fstab that are already present. [Lars Kellogg-Stedman] - ds-identify: ensure that we have certain tokens in PATH. - tests: enable Ubuntu Cosmic in integration tests [Joshua Powers] - read_file_or_url: move to url_helper, fix bug in its FileResponse. - cloud_tests: help pylint - flake8: fix flake8 errors in previous commit. - typos: Fix spelling mistakes in cc_mounts.py log messages [Stephen Ford] - tests: restructure SSH and initial connections [Joshua Powers] - ds-identify: recognize container-other as a container, test SmartOS. - cloud-config.service: run After snap.seeded.service. - tests: do not rely on host /proc/cmdline in test_net.py [Lars Kellogg-Stedman] - ds-identify: Remove dupe call to is_ds_enabled, improve debug message. - SmartOS: fix get_interfaces for nics that do not have addr_assign_type. - tests: fix package and ca_cert cloud_tests on bionic - ds-identify: make shellcheck 0.4.6 happy with ds-identify. - pycodestyle: Fix deprecated string literals, move away from flake8. - azure: Add reported ready marker file. [Joshua Chan] - tools: Support adding a release suffix through packages/bddeb. - FreeBSD: Invoke growfs on ufs filesystems such that it does not prompt. [Harm Weites] - tools: Re-use the orig tarball in packages/bddeb
[Yahoo-eng-team] [Bug 1784685] Re: Oracle: cloud-init openstack local detection too strict for oracle cloud
This bug was fixed in the package cloud-init - 18.3-9-g2e62cb8a- 0ubuntu1~16.04.2 --- cloud-init (18.3-9-g2e62cb8a-0ubuntu1~16.04.2) xenial-proposed; urgency=medium * cherry-pick 3cee0bf8: oracle: fix detect_openstack to report True on (LP: #1784685) cloud-init (18.3-9-g2e62cb8a-0ubuntu1~16.04.1) xenial-proposed; urgency=medium * New upstream snapshot. (LP: #1777912) - docs: note in rtd about avoiding /tmp when writing files - ubuntu,centos,debian: get_linux_distro to align with platform.dist - Fix boothook docs on environment variable name (INSTANCE_I -> INSTANCE_ID) [Marc Tamsky] - update_metadata: a datasource can support network re-config every boot - tests: drop salt-minion integration test - Retry on failed import of gpg receive keys. - tools: Fix run-container when neither source or binary package requested. - docs: Fix a small spelling error. [Oz N Tiram] - tox: use simplestreams from git repository rather than bzr. cloud-init (18.3-0ubuntu1~16.04.1) xenial-proposed; urgency=medium * debian/rules: update version.version_string to contain packaged version. (LP: #1770712) * debian/patches/openstack-no-network-config.patch add patch to ignore Openstack network_config from network_data.json by default * Refresh patches against upstream: + azure-use-walinux-agent.patch + ds-identify-behavior-xenial.patch * New upstream release. (LP: #1777912) - release 18.3 - docs: represent sudo:false in docs for user_groups config module - Explicitly prevent `sudo` access for user module [Jacob Bednarz] - lxd: Delete default network and detach device if lxd-init created them. - openstack: avoid unneeded metadata probe on non-openstack platforms - stages: fix tracebacks if a module stage is undefined or empty [Robert Schweikert] - Be more safe on string/bytes when writing multipart user-data to disk. - Fix get_proc_env for pids that have non-utf8 content in environment. - tests: fix salt_minion integration test on bionic and later - tests: provide human-readable integration test summary when --verbose - tests: skip chrony integration tests on lxd running artful or older - test: add optional --preserve-instance arg to integraiton tests - netplan: fix mtu if provided by network config for all rendered types - tests: remove pip install workarounds for pylxd, take upstream fix. - subp: support combine_capture argument. - tests: ordered tox dependencies for pylxd install - util: add get_linux_distro function to replace platform.dist [Robert Schweikert] - pyflakes: fix unused variable references identified by pyflakes 2.0.0. - - Do not use the systemd_prefix macro, not available in this environment [Robert Schweikert] - doc: Add config info to ec2, openstack and cloudstack datasource docs - Enable SmartOS network metadata to work with netplan via per-subnet routes [Dan McDonald] - openstack: Allow discovery in init-local using dhclient in a sandbox. - tests: Avoid using https in httpretty, improve HttPretty test case. - yaml_load/schema: Add invalid line and column nums to error message - Azure: Ignore NTFS mount errors when checking ephemeral drive [Paul Meyer] - packages/brpm: Get proper dependencies for cmdline distro. - packages: Make rpm spec files patch in package version like in debs. - tools/run-container: replace tools/run-centos with more generic. - Update version.version_string to contain packaged version. - cc_mounts: Do not add devices to fstab that are already present. [Lars Kellogg-Stedman] - ds-identify: ensure that we have certain tokens in PATH. - tests: enable Ubuntu Cosmic in integration tests [Joshua Powers] - read_file_or_url: move to url_helper, fix bug in its FileResponse. - cloud_tests: help pylint - flake8: fix flake8 errors in previous commit. - typos: Fix spelling mistakes in cc_mounts.py log messages [Stephen Ford] - tests: restructure SSH and initial connections [Joshua Powers] - ds-identify: recognize container-other as a container, test SmartOS. - cloud-config.service: run After snap.seeded.service. - tests: do not rely on host /proc/cmdline in test_net.py [Lars Kellogg-Stedman] - ds-identify: Remove dupe call to is_ds_enabled, improve debug message. - SmartOS: fix get_interfaces for nics that do not have addr_assign_type. - tests: fix package and ca_cert cloud_tests on bionic - ds-identify: make shellcheck 0.4.6 happy with ds-identify. - pycodestyle: Fix deprecated string literals, move away from flake8. - azure: Add reported ready marker file. [Joshua Chan] - tools: Support adding a release suffix through packages/bddeb. - FreeBSD: Invoke growfs on ufs filesystems such that it does not prompt. [Harm Weites] - tools: Re-use the orig tarball in packages/bddeb
[Yahoo-eng-team] [Bug 1784685] Re: Oracle: cloud-init openstack local detection too strict for oracle cloud
This bug was fixed in the package cloud-init - 18.3-9-g2e62cb8a- 0ubuntu1~18.04.2 --- cloud-init (18.3-9-g2e62cb8a-0ubuntu1~18.04.2) bionic-proposed; urgency=medium * cherry-pick 3cee0bf8: oracle: fix detect_openstack to report True on (LP: #1784685) cloud-init (18.3-9-g2e62cb8a-0ubuntu1~18.04.1) bionic-proposed; urgency=medium * New upstream snapshot. (LP: #1777912) - docs: note in rtd about avoiding /tmp when writing files - ubuntu,centos,debian: get_linux_distro to align with platform.dist - Fix boothook docs on environment variable name (INSTANCE_I -> INSTANCE_ID) [Marc Tamsky] - update_metadata: a datasource can support network re-config every boot - tests: drop salt-minion integration test - Retry on failed import of gpg receive keys. - tools: Fix run-container when neither source or binary package requested. - docs: Fix a small spelling error. [Oz N Tiram] - tox: use simplestreams from git repository rather than bzr. cloud-init (18.3-0ubuntu1~18.04.1) bionic-proposed; urgency=medium * debian/rules: update version.version_string to contain packaged version. (LP: #1770712) * debian/patches/openstack-no-network-config.patch add patch to ignore Openstack network_config from network_data.json by default * New upstream release. (LP: #1777912) - release 18.3 - docs: represent sudo:false in docs for user_groups config module - Explicitly prevent `sudo` access for user module [Jacob Bednarz] - lxd: Delete default network and detach device if lxd-init created them. - openstack: avoid unneeded metadata probe on non-openstack platforms - stages: fix tracebacks if a module stage is undefined or empty [Robert Schweikert] - Be more safe on string/bytes when writing multipart user-data to disk. - Fix get_proc_env for pids that have non-utf8 content in environment. - tests: fix salt_minion integration test on bionic and later - tests: provide human-readable integration test summary when --verbose - tests: skip chrony integration tests on lxd running artful or older - test: add optional --preserve-instance arg to integraiton tests - netplan: fix mtu if provided by network config for all rendered types - tests: remove pip install workarounds for pylxd, take upstream fix. - subp: support combine_capture argument. - tests: ordered tox dependencies for pylxd install - util: add get_linux_distro function to replace platform.dist [Robert Schweikert] - pyflakes: fix unused variable references identified by pyflakes 2.0.0. - - Do not use the systemd_prefix macro, not available in this environment [Robert Schweikert] - doc: Add config info to ec2, openstack and cloudstack datasource docs - Enable SmartOS network metadata to work with netplan via per-subnet routes [Dan McDonald] - openstack: Allow discovery in init-local using dhclient in a sandbox. - tests: Avoid using https in httpretty, improve HttPretty test case. - yaml_load/schema: Add invalid line and column nums to error message - Azure: Ignore NTFS mount errors when checking ephemeral drive [Paul Meyer] - packages/brpm: Get proper dependencies for cmdline distro. - packages: Make rpm spec files patch in package version like in debs. - tools/run-container: replace tools/run-centos with more generic. - Update version.version_string to contain packaged version. - cc_mounts: Do not add devices to fstab that are already present. [Lars Kellogg-Stedman] - ds-identify: ensure that we have certain tokens in PATH. - tests: enable Ubuntu Cosmic in integration tests [Joshua Powers] - read_file_or_url: move to url_helper, fix bug in its FileResponse. - cloud_tests: help pylint - flake8: fix flake8 errors in previous commit. - typos: Fix spelling mistakes in cc_mounts.py log messages [Stephen Ford] - tests: restructure SSH and initial connections [Joshua Powers] - ds-identify: recognize container-other as a container, test SmartOS. - cloud-config.service: run After snap.seeded.service. - tests: do not rely on host /proc/cmdline in test_net.py [Lars Kellogg-Stedman] - ds-identify: Remove dupe call to is_ds_enabled, improve debug message. - SmartOS: fix get_interfaces for nics that do not have addr_assign_type. - tests: fix package and ca_cert cloud_tests on bionic - ds-identify: make shellcheck 0.4.6 happy with ds-identify. - pycodestyle: Fix deprecated string literals, move away from flake8. - azure: Add reported ready marker file. [Joshua Chan] - tools: Support adding a release suffix through packages/bddeb. - FreeBSD: Invoke growfs on ufs filesystems such that it does not prompt. [Harm Weites] - tools: Re-use the orig tarball in packages/bddeb if it is around. - netinfo: fix netdev_pformat when a nic does not have an address assigned. - collect-log
[Yahoo-eng-team] [Bug 1783467] Re: fail to create volume type encryption
Reviewed: https://review.openstack.org/585629
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=633897ae549257789961014afa81cf209c0e05d5
Submitter: Zuul
Branch:master
commit 633897ae549257789961014afa81cf209c0e05d5
Author: zhubx007
Date: Wed Jul 25 12:12:27 2018 +0800
fix bug of fail to create volume type encryption from dashboard
Due to the commit https://review.openstack.org/#/c/573093/,
the body of create and update from dashboard for volume
type encryption does not match the schemas of it's API.
The schemas url is https://github.com/openstack/cinder/blob
/master/cinder/api/schemas/volume_type_encryption.py
So that, pop the volume_type_id and name from the data to
match the schemas.
Change-Id: I032e59251a0d54cd09ead8cf3b0ac2527d9261db
Closes-Bug: #1783467
** 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/1783467
Title:
fail to create volume type encryption
Status in Cinder:
New
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
branch: master
deploy tool: devstack, local.conf file can be found as attachment.
os: centos7
When I try to create the volume type encryption, the msg 'Unable to
create encrypted volume type.' occurs. I find the msg from the command
'journal -f --unit devstack@c-*'.
Jul 25 10:28:30 dev devstack@c-api.service[8775]: INFO
cinder.api.openstack.wsgi [None req-5b1be177-9550-422b-a7cb-c43875ae697c admin
admin] GET
http://172.16.140.46/volume/v3/414592cac9954402b6e34f25998d10ed/types?is_public=None
Jul 25 10:28:30 dev devstack@c-api.service[8775]: DEBUG
cinder.api.openstack.wsgi [None req-5b1be177-9550-422b-a7cb-c43875ae697c admin
admin] Empty body provided in request {{(pid=8777) get_body
/opt/stack/cinder/cinder/api/openstack/wsgi.py:718}}
Jul 25 10:28:30 dev devstack@c-api.service[8775]: DEBUG
cinder.api.openstack.wsgi [None req-5b1be177-9550-422b-a7cb-c43875ae697c admin
admin] Calling method 'index' {{(pid=8777) _process_stack
/opt/stack/cinder/cinder/api/openstack/wsgi.py:872}}
Jul 25 10:28:30 dev devstack@c-api.service[8775]: INFO
cinder.api.openstack.wsgi [None req-5b1be177-9550-422b-a7cb-c43875ae697c admin
admin]
http://172.16.140.46/volume/v3/414592cac9954402b6e34f25998d10ed/types?is_public=None
returned with HTTP 200
Jul 25 10:28:30 dev devstack@c-api.service[8775]: [pid: 8777|app: 0|req:
409/805] 172.16.140.46 () {64 vars in 1370 bytes} [Wed Jul 25 10:28:30 2018]
GET /volume/v3/414592cac9954402b6e34f25998d10ed/types?is_public=None =>
generated 701 bytes in 22 msecs (HTTP/1.1 200) 7 headers in 285 bytes (1
switches on core 0)
Jul 25 10:28:30 dev devstack@c-api.service[8775]: INFO
cinder.api.openstack.wsgi [None req-fae4a561-8c6b-4d34-b567-55698cbeebd0 admin
admin] POST
http://172.16.140.46/volume/v3/414592cac9954402b6e34f25998d10ed/types/fd1d6e02-7a50-4336-b19c-9b48671c183b/encryption
Jul 25 10:28:30 dev devstack@c-api.service[8775]: DEBUG
cinder.api.openstack.wsgi [None req-fae4a561-8c6b-4d34-b567-55698cbeebd0 admin
admin] Action: 'create', calling method: create, body: {"encryption":
{"volume_type_id": "fd1d6e02-7a50-4336-b19c-9b48671c183b", "name":
"lvmdriver-3", "control_location": "front-end", "key_size": null, "provider":
"luks", "cipher": null}} {{(pid=8776) _process_stack
/opt/stack/cinder/cinder/api/openstack/wsgi.py:869}}
Jul 25 10:28:30 dev devstack@c-api.service[8775]: INFO
cinder.api.openstack.wsgi [None req-fae4a561-8c6b-4d34-b567-55698cbeebd0 admin
admin]
http://172.16.140.46/volume/v3/414592cac9954402b6e34f25998d10ed/types/fd1d6e02-7a50-4336-b19c-9b48671c183b/encryption
returned with HTTP 400
But I can create the volume type encryption by the CLI command 'cinder
encryption-type-create '.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1783467/+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 1785897] Re: keyerror in admin floating IP panel when neutron dns-integration is not enabled
Reviewed: https://review.openstack.org/585639 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=446abc41bfe562bcc1d2933bd42d0225c6f3cb53 Submitter: Zuul Branch:master commit 446abc41bfe562bcc1d2933bd42d0225c6f3cb53 Author: zhubx007 Date: Wed Jul 25 14:08:50 2018 +0800 add dns_name and dns_domain into admin column https://review.openstack.org/#/c/561185/ According to the above merged commit, dns_name and dns_domain are added into project/floating_ips/tables.py. But because of the class 'FloatingIPsTable' inherits the project_tables.FloatingIPsTable, so that we should add dns_name and dns_domain into columns of Meta. If not, if you click the Admin/Network/Floating IPs, the page will crash. Closes-Bug: #1785897 Change-Id: I6e933749a56a492989cab002c1b65656b7e2c65b ** 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/1785897 Title: keyerror in admin floating IP panel when neutron dns-integration is not enabled Status in OpenStack Dashboard (Horizon): Fix Released Bug description: when neutron dns-integration is not enabled (the default devstack configuration), key error for dns_name and dns_domain occurs when we access the admin floating IP panel. The admin floating IP panel is completely broken in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1785897/+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 1785897] [NEW] keyerror in admin floating IP panel when neutron dns-integration is not enabled
Public bug reported: when neutron dns-integration is not enabled (the default devstack configuration), key error for dns_name and dns_domain occurs when we access the admin floating IP panel. The admin floating IP panel is completely broken in this case. ** Affects: horizon Importance: Critical Assignee: Akihiro Motoki (amotoki) Status: In Progress -- 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/1785897 Title: keyerror in admin floating IP panel when neutron dns-integration is not enabled Status in OpenStack Dashboard (Horizon): In Progress Bug description: when neutron dns-integration is not enabled (the default devstack configuration), key error for dns_name and dns_domain occurs when we access the admin floating IP panel. The admin floating IP panel is completely broken in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1785897/+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 1756994] Re: Misleading log messages "Unexpected attempt to pop events during shutdown" on source host during live migration
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/pike
Assignee: (unassigned) => s10 (vlad-esten)
** Changed in: nova/queens
Assignee: (unassigned) => s10 (vlad-esten)
** Changed in: nova/pike
Status: New => In Progress
** Changed in: nova/pike
Importance: Undecided => Low
** Changed in: nova/queens
Status: New => In Progress
** Changed in: nova/queens
Importance: Undecided => Low
--
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/1756994
Title:
Misleading log messages "Unexpected attempt to pop events during
shutdown" on source host during live migration
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) pike series:
In Progress
Status in OpenStack Compute (nova) queens series:
In Progress
Bug description:
As seen here:
http://logs.openstack.org/71/551371/6/check/legacy-tempest-dsvm-
multinode-live-
migration/4d466b2/logs/subnode-2/screen-n-cpu.txt.gz#_Mar_19_14_25_07_798071
Mar 19 14:25:07.797329 ubuntu-xenial-rax-dfw-000304 nova-compute[29059]:
DEBUG nova.compute.manager [None req-24e1d4e3-6f9c-4438-8059-5f7cf69566f0
service nova] [instance: 6347c3ea-894c-4cc8-a3b4-ea9bfe49033e] Received event
network-vif-plugged-cd0afcf3-c654-488e-b578-6d3c45f3a5a5 {{(pid=29059)
external_instance_event /opt/stack/new/nova/nova/compute/manager.py:7702}}
Mar 19 14:25:07.797762 ubuntu-xenial-rax-dfw-000304 nova-compute[29059]:
DEBUG oslo_concurrency.lockutils [None req-24e1d4e3-6f9c-4438-8059-5f7cf69566f0
service nova] Lock "6347c3ea-894c-4cc8-a3b4-ea9bfe49033e-events" acquired by
"nova.compute.manager._pop_event" :: waited 0.000s {{(pid=29059) inner
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:273}}
Mar 19 14:25:07.798071 ubuntu-xenial-rax-dfw-000304 nova-compute[29059]:
DEBUG nova.compute.manager [None req-24e1d4e3-6f9c-4438-8059-5f7cf69566f0
service nova] [instance: 6347c3ea-894c-4cc8-a3b4-ea9bfe49033e] Unexpected
attempt to pop events during shutdown {{(pid=29059) _pop_event
/opt/stack/new/nova/nova/compute/manager.py:347}}
Mar 19 14:25:07.798448 ubuntu-xenial-rax-dfw-000304 nova-compute[29059]:
DEBUG oslo_concurrency.lockutils [None req-24e1d4e3-6f9c-4438-8059-5f7cf69566f0
service nova] Lock "6347c3ea-894c-4cc8-a3b4-ea9bfe49033e-events" released by
"nova.compute.manager._pop_event" :: held 0.001s {{(pid=29059) inner
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:285}}
Mar 19 14:25:07.798780 ubuntu-xenial-rax-dfw-000304 nova-compute[29059]:
DEBUG nova.compute.manager [None req-24e1d4e3-6f9c-4438-8059-5f7cf69566f0
service nova] [instance: 6347c3ea-894c-4cc8-a3b4-ea9bfe49033e] No waiting
events found dispatching
network-vif-plugged-cd0afcf3-c654-488e-b578-6d3c45f3a5a5 {{(pid=29059)
pop_instance_event /opt/stack/new/nova/nova/compute/manager.py:363}}
Mar 19 14:25:07.799222 ubuntu-xenial-rax-dfw-000304 nova-compute[29059]:
WARNING nova.compute.manager [None req-24e1d4e3-6f9c-4438-8059-5f7cf69566f0
service nova] [instance: 6347c3ea-894c-4cc8-a3b4-ea9bfe49033e] Received
unexpected event network-vif-plugged-cd0afcf3-c654-488e-b578-6d3c45f3a5a5 for
instance with vm_state active and task_state migrating.
This is when the destination host has plugged VIFs during
pre_live_migration, and then because the external server events are
routed to the host that the instance is currently on (source host
during live migration), the events are routed there and nothing is
waiting on them. The message is misleading since the compute service
isn't shutting down, it's just that nothing is waiting on the event,
which is OK.
That comes from this code:
https://github.com/openstack/nova/blob/43c72f02f277d6f1083e5e9a4009d3d03d965368/nova/compute/manager.py#L346
That should be comparing self._events to None which indicates
shutdown:
https://github.com/openstack/nova/blob/43c72f02f277d6f1083e5e9a4009d3d03d965368/nova/compute/manager.py#L398
https://github.com/openstack/nova/blob/43c72f02f277d6f1083e5e9a4009d3d03d965368/nova/compute/manager.py#L1166
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1756994/+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 1584752] Re: copy image id to image metadata from volume
*** This bug is a duplicate of bug 1746483 *** https://bugs.launchpad.net/bugs/1746483 ** This bug has been marked a duplicate of bug 1746483 Not able to boot from Volume / Volume snapshot when using isolated_images -- 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/1584752 Title: copy image id to image metadata from volume Status in OpenStack Compute (nova): In Progress Bug description: According to https://review.openstack.org/#/c/204947/ image id is considered to be useless and ignored to put to image metadata, but actually, it is used for IsolatedHostsFilter: https://bugs.launchpad.net/nova/+bug/1584747 we should add it back. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1584752/+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 1645272] Re: Hostname of server is not updated when update instance name
As noted this isn't a bug, so marking it invalid. Would require a spec to change this behavior, but I doubt we'd do it, since nova shouldn't have access to the guest once it's created. You'd have to rebuild the server if you wanted to change the hostname in the guest. ** Changed in: nova Status: In Progress => 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/1645272 Title: Hostname of server is not updated when update instance name Status in OpenStack Compute (nova): Invalid Bug description: Currently we can update instance name and description using update API, but it only performs update in data in DB, the hostname in VM is still unchanged. 1. create a server with name 'old' 2. update the name of server to 'new' 3. get the details of server from nova, the name has been updated 4. restart (stop and then start)/reboot the nova server 5. login the server, and found the hostname has not been udpate to 'new' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1645272/+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 1661793] Re: Should generate migration record after successfully claimed
Is this still an issue? If so, please explain what the issue is in more detail - what is the user impact? Conductor is now passing the migration record it creates down to the compute, so I don't think RT creates it anymore and this shouldn't be an issue. See: https://github.com/openstack/nova/commit/9868a4d9c1c3b705d328fc11bba634857cde0f2e ** Changed in: nova Status: In Progress => 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/1661793 Title: Should generate migration record after successfully claimed Status in OpenStack Compute (nova): Invalid Bug description: Currently the migration record was generated before successful claim, http://git.openstack.org/cgit/openstack/nova/tree/nova/compute/resource_tracker.py#n197 this may lead to an bad migration record if the claim failed afterwards and reschedule also failed. It could be better if we generate the migration records after successfully claimed. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1661793/+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 1746202] Re: Invalid query parameter could lead to HTTP 500
Looks like this is fixed for nova as of
https://review.openstack.org/#/c/539164/
** Tags added: api
** 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/1746202
Title:
Invalid query parameter could lead to HTTP 500
Status in Cinder:
Fix Released
Status in Manila:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Invalid query parameter could lead to HTTP 500, although Nova used JSON
Schema verification
to check input query params, but query like:
GET /servers?limit=%88 will still lead to HTTP 500, as it failed to parse at
webob which is
pre JSON Schema check.
GET http://10.76.150.18/compute/v2.1/servers/detail?limit=%88
Response:
{
"computeFault": {
"message": "Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.\n",
"code": 500
}
}
Traceback:
DEBUG nova.api.openstack.wsgi [None req-ee355759-13c3-4f63-a41f-920d7385878d
admin admin] Calling method 'http://bugs.launchpad.net/nova/ and attach the Nova API lo
Jan 30 17:46:56 kevin-dev devstack@n-api.service[4374]:
Jan 30 17:46:56 kevin-dev devstack@n-api.service[4374]: DEBUG
nova.api.openstack.wsgi [None req-ee355759-13c3-4f63-a41f-920d7385878d admin
admin] Returning 500 to user: Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API l
Jan 30 17:46:56 kevin-dev devstack@n-api.service[4374]: {{(pid=4377) __call__
/opt/stack/nova/nova/api/openstack/wsgi.py:1079}}
Jan 30 17:46:56 kevin-dev devstack@n-api.service[4374]: INFO
nova.api.openstack.requestlog [None req-ee355759-13c3-4f63-a41f-920d7385878d
admin admin] 10.8.4.18 "GET /compute/v2.1/servers/detail?limit=%89" status: 500
len: 202 microversion: 2.49 time: 0.531050
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1746202/+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 1747600] Re: Network cleanups don't work after max retries in a child cell
*** This bug is a duplicate of bug 1777505 ***
https://bugs.launchpad.net/bugs/1777505
This isn't a nova bug, it's a devstack bug, and already fixed.
** Also affects: devstack
Importance: Undecided
Status: New
** Changed in: nova
Status: Confirmed => Invalid
** This bug has been marked a duplicate of bug 1777505
nova_cell1_conf is not configured for [neutron]
--
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/1747600
Title:
Network cleanups don't work after max retries in a child cell
Status in devstack:
New
Status in OpenStack Compute (nova):
Invalid
Bug description:
In cellv2 deployment wit supper-conductor and cell-conductor, the retry logic
is done in cell-conductor, in devstack deployment, cell-conductor reads
nova_cell1.conf and there is no Neutron endpoint info, also, we cannot get this
information from context as network is not included here:
https://github.com/openstack/nova/blob/9519601401ee116a9197fe3b5d571495a96912e9/nova/context.py#L121
if the retry attempts exceeds, we will try to cleanup networks, and
this is happen in cell-conductor, so the below exception will happen:
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
DEBUG nova.network.neutronv2.api [None req-647f2fa0-f66b-4fa4-aef1-2e075b49dc75
admin admin] [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
deallocate_for_instance() {{(pid=27117) deallocate_for_
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [None req-647f2fa0-f66b-4fa4-aef1-2e075b49dc75
admin admin] [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd] Failed to
deallocate networks: EndpointNotFound: ['internal
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
Traceback (most recent call last):
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
File "/usr/local/lib/python2.7/dist-packages/nova/conductor/manager.py", line
364, in _cleanup_allocated_networks
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
context, instance, requested_networks=requested_networks)
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
File "/usr/local/lib/python2.7/dist-packages/nova/network/neutronv2/api.py",
line 1253, in deallocate_for_instance
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
data = neutron.list_ports(**search_opts)
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
File "/usr/local/lib/python2.7/dist-packages/nova/network/neutronv2/api.py",
line 114, in wrapper
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
ret = obj(*args, **kwargs)
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 786, in list_ports
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
**_params)
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
File "/usr/local/lib/python2.7/dist-packages/nova/network/neutronv2/api.py",
line 114, in wrapper
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
ret = obj(*args, **kwargs)
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 369, in list
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
for r in self._pagination(collection, path, **params):
Feb 06 08:36:00 donotdelete-allinone-zhuli-417094 nova-conductor[27093]:
ERROR nova.conductor.manager [instance: cf53bacd-4cae-45f3-b0b4-549330a167bd]
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 3
[Yahoo-eng-team] [Bug 1785606] Re: When working with python3 header banner is not rendered properly
Reviewed: https://review.openstack.org/589121 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=f7eefaa9937f2fc1e05caee65334cdd0d93159c9 Submitter: Zuul Branch:master commit f7eefaa9937f2fc1e05caee65334cdd0d93159c9 Author: Yuval Adar Date: Mon Aug 6 14:14:24 2018 +0300 force plain text for header response Change-Id: I239a1ccc530ce652cc2165eef38b9f8193769102 Closes-Bug: #1785606 ** 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/1785606 Title: When working with python3 header banner is not rendered properly Status in OpenStack Dashboard (Horizon): Fix Released Status in Vitrage Dashboard: In Progress Bug description: When running horizon under python 3, the header banner response returned is in bytes format, and python 3 interprets it different from python 2, thus breaking the banner completely To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1785606/+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 1785568] Re: Multiple migration requests for same vm might fail
I believe this should be fixed in Nova Placement. Not sure this belongs to tripleo. ** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Status: New => Incomplete ** Changed in: tripleo Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1785568 Title: Multiple migration requests for same vm might fail Status in OpenStack Compute (nova): Incomplete Status in tripleo: Won't Fix Bug description: If there are multiple migration requests for the same instance, the placement inventory might not be cleaned up in time, leading to further migration requests to this compute to fail: Allocation for VCPU on resource provider b6d1973f- bc39-4ea0-8d28-15f988f762e1 violates min_unit, max_unit, or step_size. Requested: 5, min_unit: 1, max_unit: 4, step_size: 1 Placement API returning an error response: Unable to allocate inventory: Unable to create allocation for 'VCPU' on resource provider The requested amount would violate inventory constraints To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1785568/+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 1785848] [NEW] Neutron server producing tracebacks with 'L3RouterPlugin' object has no attribute 'is_distributed_router' when DVR is enabled
Public bug reported: In environments where DVR is enabled and when an instance with floating IPs is moved from one host to another (due to live migration or shelving / un-shelvinng) the Neutron server produces the following traceback: Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/neutron_lib/callbacks/manager.py", line 197, in _notify_loop callback(resource, event, trigger, **kwargs) File "/opt/stack/new/neutron/neutron/db/l3_dvrscheduler_db.py", line 460, in _notify_l3_agent_port_update l3plugin.is_distributed_router(fip['router_id']) and AttributeError: 'L3RouterPlugin' object has no attribute 'is_distributed_router' The problem was introduced by this patch: https://review.openstack.org/#/c/579058. Line https://review.openstack.org/#/c/579058/3/neutron/db/l3_dvrscheduler_db.py@460 wrongly tries to call is_distributed_router as though it is a method in the L3 plugin. The real intent was to call it from module neutron/db/l3_dvr_db.py, since it is defined there outside any classes ** Affects: neutron Importance: Medium Assignee: Miguel Lavalle (minsel) Status: New ** Changed in: neutron Assignee: (unassigned) => Miguel Lavalle (minsel) ** Changed in: neutron Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1785848 Title: Neutron server producing tracebacks with 'L3RouterPlugin' object has no attribute 'is_distributed_router' when DVR is enabled Status in neutron: New Bug description: In environments where DVR is enabled and when an instance with floating IPs is moved from one host to another (due to live migration or shelving / un-shelvinng) the Neutron server produces the following traceback: Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/neutron_lib/callbacks/manager.py", line 197, in _notify_loop callback(resource, event, trigger, **kwargs) File "/opt/stack/new/neutron/neutron/db/l3_dvrscheduler_db.py", line 460, in _notify_l3_agent_port_update l3plugin.is_distributed_router(fip['router_id']) and AttributeError: 'L3RouterPlugin' object has no attribute 'is_distributed_router' The problem was introduced by this patch: https://review.openstack.org/#/c/579058. Line https://review.openstack.org/#/c/579058/3/neutron/db/l3_dvrscheduler_db.py@460 wrongly tries to call is_distributed_router as though it is a method in the L3 plugin. The real intent was to call it from module neutron/db/l3_dvr_db.py, since it is defined there outside any classes To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1785848/+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 1785827] [NEW] Performance regression in libvirt get_available_resource()
Public bug reported: Description === Periodic task update_available_resource takes 20 seconds for 100 instances on local storage: https://github.com/openstack/nova/blob/stable/pike/nova/compute/resource_tracker.py#L694 Steps to reproduce == 1. /etc/nova/nova.conf: [DEFAULT] preallocate_images=space [libvirt] images_type=raw 2. Launch 100 instances on the host 3. See, that every update_available_resource() takes 20 seconds This performance regression was introduced in this commit: https://github.com/openstack/nova/commit/d88b75e81eabfbd463007f6a4f27e6966a466530 and following commit doubles the time: https://github.com/openstack/nova/commit/938c0a745325fa73d098c6d5ddd20b2a599f9624 Expected result === update_available_resource() takes less than 5 seconds Actual result = update_available_resource() lasts for 20-30 seconds Environment === 1. Exact version of OpenStack you are running: OpenStack Pike nova 16.1.4, commit b58c7f0 2. Which hypervisor did you use? Libvirt + KVM/QEMU 2. Which storage type did you use? local storage, raw ** Affects: nova Importance: Undecided Status: New ** Summary changed: - Performance regression in libvirt get_available_resource(nodename) + Performance regression in libvirt get_available_resource() -- 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/1785827 Title: Performance regression in libvirt get_available_resource() Status in OpenStack Compute (nova): New Bug description: Description === Periodic task update_available_resource takes 20 seconds for 100 instances on local storage: https://github.com/openstack/nova/blob/stable/pike/nova/compute/resource_tracker.py#L694 Steps to reproduce == 1. /etc/nova/nova.conf: [DEFAULT] preallocate_images=space [libvirt] images_type=raw 2. Launch 100 instances on the host 3. See, that every update_available_resource() takes 20 seconds This performance regression was introduced in this commit: https://github.com/openstack/nova/commit/d88b75e81eabfbd463007f6a4f27e6966a466530 and following commit doubles the time: https://github.com/openstack/nova/commit/938c0a745325fa73d098c6d5ddd20b2a599f9624 Expected result === update_available_resource() takes less than 5 seconds Actual result = update_available_resource() lasts for 20-30 seconds Environment === 1. Exact version of OpenStack you are running: OpenStack Pike nova 16.1.4, commit b58c7f0 2. Which hypervisor did you use? Libvirt + KVM/QEMU 2. Which storage type did you use? local storage, raw To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1785827/+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 1785800] [NEW] Not possible to delete volume which was attached
Public bug reported:
Description
===
Fail to delete a volume after detaching the volume using Cinder command.
[stack@undercloud~(tm5)]$ openstack volume list
+--+--+++-+
| ID | Name | Status
| Size | Attached to |
+--+--+++-+
| 471ed957-7c6d-492f-ac83-978d15fc1aa9 | vol-du- | in-use
| | Attached to vm-du on /dev/vdb |
+--+--+++-+
[stack@undercloud~(tm5)]$ openstack volume show
471ed957-7c6d-492f-ac83-978d15fc1aa9
++-+
| Field | Value
|
++-+
| attachments| [{u'server_id':
u'9e20ca48-0651-4099-b2ea-aafcfd2a8ecf', u'attachment_id':
u'4412a78a-053e-41ab-8576-50d8e2f0ae33',
[stack@undercloud~(tm5)]$ cinder --os-volume-api-version 3.27 attachment-delete
4412a78a-053e-41ab-8576-50d8e2f0ae33
[stack@undercloud~(tm5)]$ openstack volume list
+--+--+---++-+
| ID | Name | Status
| Size | Attached to |
+--+--+---++-+
| 471ed957-7c6d-492f-ac83-978d15fc1aa9 | vol-du- |
available | | |
+--+--+---++-+
[stack@undercloud~(tm5)]$ openstack volume delete
471ed957-7c6d-492f-ac83-978d15fc1aa9
[stack@undercloud~(tm5)]$ openstack volume list
+--+--+--++-+
| ID | Name | Status
| Size | Attached to |
+--+--+--++-+
| 471ed957-7c6d-492f-ac83-978d15fc1aa9 | vol-du- |
deleting | | |
+--+--+--++-+
[stack@undercloud~(tm5)]$ openstack volume list
+--+--+---++-+
| ID | Name | Status
| Size | Attached to |
+--+--+---++-+
| 471ed957-7c6d-492f-ac83-978d15fc1aa9 | vol-du- |
available | | |
+--+--+---++-+
Steps to reproduce
==
1. Create volume.
2. Create VM.
3. Attach the VM to the volume - volume status - "in-use".
4. Delete the attachment using cinder - cinder --os-volume-api-version 3.27
attachment-delete .
5. Check that the volume status is - "available".
6. Delete the volume.
- See that the volume not deleted and remain in "available" status.
Expected result
===
1. Volume will be deleted after the attachment delete using cinder.
Actual result
=
1. Fails to delete the Volume.
logs show:
cinder-volume.log
2018-08-07 13:59:50.705 56 ERROR cinder.volume.manager
[req-82d30576-84c6-43a5-aada-5a8ce0aacd6f 8976f232d27248d791d4f11aae85569d
17cd957fbbc9463797e37bee9afa366d - default default] Un
[Yahoo-eng-team] [Bug 1785809] [NEW] Delete action not working on qos panel
Public bug reported: Description of problem: New qos policy delete action not working correctly and returning error not found message. How reproducible: Every time Actual results: Try to delete qos policy. Returns error message. Expected results: Try to delete qos policy. Qos policy deleted. ** Affects: horizon Importance: Undecided Assignee: Beth Elwell (bethelwell) Status: In Progress ** Changed in: horizon Assignee: (unassigned) => Beth Elwell (bethelwell) -- 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/1785809 Title: Delete action not working on qos panel Status in OpenStack Dashboard (Horizon): In Progress Bug description: Description of problem: New qos policy delete action not working correctly and returning error not found message. How reproducible: Every time Actual results: Try to delete qos policy. Returns error message. Expected results: Try to delete qos policy. Qos policy deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1785809/+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 1785771] [NEW] nova.compute.manager ResourceProviderRetrievalFailed: Failed to get resource provider
Public bug reported: openstack:Q centos7.5 (openstack) compute service list ++--+--+--+-+---++ | ID | Binary | Host | Zone | Status | State | Updated At | ++--+--+--+-+---++ | 4 | nova-consoleauth | controller01 | internal | enabled | up| 2018-08-07T08:49:10.00 | | 7 | nova-scheduler | controller01 | internal | enabled | up| 2018-08-07T08:49:16.00 | | 13 | nova-conductor | controller01 | internal | enabled | up| 2018-08-07T08:49:09.00 | | 27 | nova-compute | compute02| nova | enabled | up| 2018-08-07T08:49:09.00 | ++--+--+--+-+---++ [root@controller01 ~]# su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova /usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py:332: NotSupportedWarning: Configuration option(s) ['use_tpool'] not supported exception.NotSupportedWarning Found 2 cell mappings. Skipping cell0 since it does not contain hosts. Getting computes from cell 'cell1': b781e305-4ec9-4a44-817b-71f0d91a4160 Found 0 unmapped computes in cell: b781e305-4ec9-4a44-817b-71f0d91a4160 [root@controller01 ~]# D08014c5-cf6b-4236-ad15-52b624d1ab4d Where is this uuid generated?No clue to this question /var/log/nova/nova-compute.log: 2018-08-07 16:37:56.013 168722 DEBUG oslo_concurrency.lockutils [req-960d6cfa-8ff4-4258-b7b2-eae671d27118 - - - - -] Lock "compute_resources" acquired by "nova.compute.resource_tracker._update_available_resource" :: waited 0.000s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:273 2018-08-07 16:37:56.117 168722 DEBUG oslo_concurrency.lockutils [req-960d6cfa-8ff4-4258-b7b2-eae671d27118 - - - - -] Lock "placement_client" acquired by "nova.scheduler.client.report._create_client" :: waited 0.000s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:273 2018-08-07 16:37:56.120 168722 DEBUG oslo_concurrency.lockutils [req-960d6cfa-8ff4-4258-b7b2-eae671d27118 - - - - -] Lock "placement_client" released by "nova.scheduler.client.report._create_client" :: held 0.004s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:285 2018-08-07 16:37:56.804 168722 ERROR nova.scheduler.client.report [req-960d6cfa-8ff4-4258-b7b2-eae671d27118 - - - - -] [None] Failed to retrieve resource provider tree from placement API for UUID d08014c5-cf6b-4236-ad15-52b624d1ab4d. Got 503: 503 Service Unavailable No server is available to handle this request. . 2018-08-07 16:37:56.805 168722 DEBUG oslo_concurrency.lockutils [req-960d6cfa-8ff4-4258-b7b2-eae671d27118 - - - - -] Lock "compute_resources" released by "nova.compute.resource_tracker._update_available_resource" :: held 0.792s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:285 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager [req-960d6cfa-8ff4-4258-b7b2-eae671d27118 - - - - -] Error updating resources for node compute02.: ResourceProviderRetrievalFailed: Failed to get resource provider with UUID d08014c5-cf6b-4236-ad15-52b624d1ab4d 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager Traceback (most recent call last): 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 7284, in update_available_resource_for_node 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager rt.update_available_resource(context, nodename) 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 680, in update_available_resource 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager self._update_available_resource(context, resources) 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", line 274, in inner 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager return f(*args, **kwargs) 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 704, in _update_available_resource 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager self._init_compute_node(context, resources) 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 571, in _init_compute_node 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager self._update(context, cn) 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 878, in _update 2018-08-07 16:37:56.805 168722 ERROR nova.compute.manager inv_data, 2018-08-07 16:
[Yahoo-eng-team] [Bug 1785776] [NEW] resize revert still hitting the legacy allocation handling
Public bug reported: During reverting a resize or a migration Nova still hits the legacy allocation handling code even if the migration is started without any old compute or controller in the system. Search for "Doing legacy allocation math" in [2] for examples. It is caused by a faulty logic in compute manager[1]. It tries to decide if the reverted migration holds allocation or not to see if the migration is a legacy one or not. However in case of [1] the cn_uuid points to the destination node. Migration never holds allocation on the destination node so the condition at L3955 never be true and the code falls to the legacy path. It seems that the legacy path still able to handled the allocation properly in the above case so no resource is leaked. [1] https://github.com/openstack/nova/blob/8688b25ca7379391cba28fab30b5a628957e673e/nova/compute/manager.py#L3952-L3955 [2] http://logs.openstack.org/72/587772/1/check/neutron-tempest-multinode-full/0a2fb57/logs/screen-n-cpu.txt.gz ** Affects: nova Importance: Low Assignee: Balazs Gibizer (balazs-gibizer) Status: New ** Tags: compute resize ** Changed in: nova Importance: Undecided => Low ** Changed in: nova Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer) ** Tags added: compute ** Tags added: resize -- 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/1785776 Title: resize revert still hitting the legacy allocation handling Status in OpenStack Compute (nova): New Bug description: During reverting a resize or a migration Nova still hits the legacy allocation handling code even if the migration is started without any old compute or controller in the system. Search for "Doing legacy allocation math" in [2] for examples. It is caused by a faulty logic in compute manager[1]. It tries to decide if the reverted migration holds allocation or not to see if the migration is a legacy one or not. However in case of [1] the cn_uuid points to the destination node. Migration never holds allocation on the destination node so the condition at L3955 never be true and the code falls to the legacy path. It seems that the legacy path still able to handled the allocation properly in the above case so no resource is leaked. [1] https://github.com/openstack/nova/blob/8688b25ca7379391cba28fab30b5a628957e673e/nova/compute/manager.py#L3952-L3955 [2] http://logs.openstack.org/72/587772/1/check/neutron-tempest-multinode-full/0a2fb57/logs/screen-n-cpu.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1785776/+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 1785358] Re: add one option to send the events into kvp pool.
*** This bug is a duplicate of bug 1722959 *** https://bugs.launchpad.net/bugs/1722959 ** Changed in: cloud-init Status: New => Invalid ** This bug has been marked a duplicate of bug 1722959 Implement Key-Value Pair Telemetry for Azure -- 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/1785358 Title: add one option to send the events into kvp pool. Status in cloud-init: Invalid Bug description: could you please help approve the changes to add one option to send the events into the kvp pool. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1785358/+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
