Public bug reported:
This is found during bug analysis 1737024 and discussion on
https://review.openstack.org/#/c/541152/
and it turn out InstanceNotRunning
is not handled in current implementation and can lead to potential back trace
so better to handle it
** Affects: nova
Importance:
Public bug reported:
Running Horizon - Pike
Load object storage container A, switch over to container B and back to
container A again before letting the the container B object list load.
It is possible to see the objects from container B listed among the
output from container A.
Please see attac
** Project changed: django-openstack-auth => horizon
** Changed in: horizon
Assignee: Akihiro Motoki (amotoki) => (unassigned)
** Tags added: low-hanging-fruit
** Description changed:
In openstack_auth/backend.py, str() is used for logging of exception
messages, but exception message ca
You have been subscribed to a public bug:
In openstack_auth/backend.py, str() is used for logging of exception messages,
but exception message can contain multi-byte strings and if so str() will fail
with UnicodeEncodeError.
We should use '%s' for logging (with more appropriate description).
ht
Public bug reported:
Description
===
The hw_disk_bus image metadata key
https://github.com/openstack/glance/blob/master/etc/metadefs/compute-libvirt-image.json#L13-L27
allows users to specify the bus to which guest hard disk images are attched for
libvirt instances.
The valid values of h
Reviewed: https://review.openstack.org/555339
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=93838575c1c866df114b595921720d72ebb1c1e8
Submitter: Zuul
Branch:master
commit 93838575c1c866df114b595921720d72ebb1c1e8
Author: Lance Bragstad
Date: Thu Mar 22 18:13:24 201
Reviewed: https://review.openstack.org/553108
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=4b572e564dcd5d9f8f608caba922f844f24cbc00
Submitter: Zuul
Branch:master
commit 4b572e564dcd5d9f8f608caba922f844f24cbc00
Author: Gage Hugo
Date: Wed Mar 14 18:32:57 2018 -05
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
*** This bug is a duplicate of bug 1755965 ***
https://bugs.launchpad.net/bugs/1755965
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Commi
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
This bug is believed to be fixed in cloud-init in 18.2. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yah
As far as I understand, this test shouldn't even exist in scope of
tempest, because you can't guarantee that backend will be slow to
process the request. This kind of interaction would be better served by
a test with better execution flow control. I am not sure if glance have
those, but in neutron
set this to fix released as the current master branch seems to cover the
changes linked in the related branch.
** 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 clou
Public bug reported:
While launching the ubuntu instance on Openstack got the following
error.
“Error: Failed to perform requested operation on instance "ubuntu", the
instance has an error status: Please try again later [Error: Exceeded
maximum number of retries. Exhausted all hosts available for
Public bug reported:
http://logs.openstack.org/periodic/git.openstack.org/openstack/neutron/master
/openstack-tox-py27-with-oslo-master/f65fec8/job-output.txt.gz
2018-03-27 06:16:32.984356 | ubuntu-xenial | --- import errors ---
2018-03-27 06:16:32.984599 | ubuntu-xenial | Failed to import test m
Reviewed: https://review.openstack.org/555699
Committed:
https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=e1231cd6eabb0992820d0c0fdc629c8a96b5f6b9
Submitter: Zuul
Branch:master
commit e1231cd6eabb0992820d0c0fdc629c8a96b5f6b9
Author: YAMAMOTO Takashi
Date: Fri Mar 23 17:40
Reviewed: https://review.openstack.org/539865
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=24d9e06ec68dfd0ead9bc56ad186e7b4e0acd8fb
Submitter: Zuul
Branch:master
commit 24d9e06ec68dfd0ead9bc56ad186e7b4e0acd8fb
Author: Tetsuro Nakamura
Date: Thu Feb 1 04:32:41 2018 +
Public bug reported:
This was somewhat known, but raised in merge proposal at
https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/342102
At least the sysconfig renderer, and possibly others don't clean up old
files that were rendered by cloud-init.
This means you may get stal
The code in [1] was added in Newton, and I think we'd be OK to add a
warning if you're not using cells v1 and the osapi_compute minimum
version is < 15 in that code as a breadcrumb at least, and we could
backport that through to queens, pike and ocata.
For nova-status, we'd likely add a check that
Public bug reported:
when neutron_tempest_plugin (https://github.com/openstack/neutron-
tempest-plugin/commit/cbbb1c5740c3771ab819cabed894001cebc0b269)
installed and all tests ran, there were resources left after the last
tempest test has finished:
(note to myself: sosreport-
testtwosecgroupsneut
Public bug reported:
This bug tracks cloud-init upstream release of version 18.2.
== Release Notes ==
Hello All,
Cloud-init release 18.2 is now available.
The 18.2 release:
* spanned just over 1 month.
* had 9 contributors from 6 domains.
* Fixed 16 launchpad.net issues.
Highlights:
- New
Reviewed: https://review.openstack.org/527900
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=e97623e1587355c9bc97266c586d20b35a0c3f74
Submitter: Zuul
Branch:master
commit e97623e1587355c9bc97266c586d20b35a0c3f74
Author: wangliangyu
Date: Thu Dec 14 17:05:12 2017 +0
Public bug reported:
This was encoutered on Ocata after and upgrade from Newton, but affects
master to the best of my knowledge.
During our upgrade from Newton -> Ocata after we finished cells_v2
migration and map'd instances accordingly, `nova show $uuid` no longer
worked. Returning the error:
Public bug reported:
Currently the nova scheduler does not filter out cell0 from the list of
cells that it considers for scheduling. Since cell0 does not have any
computes and is only a graveyard cell, it should be filtered out from
the global cell cache that is maintained by the host_manager
(htt
Public bug reported:
The UUID token provider and SQL token storage driver were removed when
Rocky opened for development [0]. The keystone-manage token_flush
command was not removed with the rest of the code. As a result, if you
run keystone-manage token_flush, you'll get an unexpected error:
> k
** Changed in: nova
Importance: Undecided => Medium
** Summary changed:
- The pause status of the virtual machine to perform the shelve operation
reported error
+ Failed to shelve paused instance with libvirt
** Summary changed:
- Failed to shelve paused instance with libvirt
+ Failed to sh
it looks like that it was introduced by following nova change:
commit 33cc64fb81773f0c246073d23c525357c9aa3b08
Author: Aaron Rosen
Date: Mon Jan 20 15:10:27 2014 -0800
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a m
Public bug reported:
There are two issues to fix: B101 assert_used and the B108:
hardcoded_tmp_directory found by bandit
scanner.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
There is a missing tag with the stable queens migrations. This is
addressed with https://review.openstack.org/#/c/554038/
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering
As there is no any activity on this bug and Ocata is now in phase III of
support (only security bug fixes) I think that we should close this bug.
** Changed in: neutron
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
Public bug reported:
Description
===
I have some compute nodes, the compute have 40 instances and after
reboot compute node, Some instances can't start with this error:
"InstanceNotFound: Instance efd0ca78-da5c-4051-98dc-ba1817167cf7 could
not be found."
Full trace log: https://paste.ub
43 matches
Mail list logo
